Personalization, Customization and Productivity Tools

[csmith]

We are having an issue with the Business Insights Dashboard report links in MAS200 version 4.3.0.18.  The dashboard displays correctly, but when we try to click on any report link, we briefly see a Providex task appear in the taskbar, then it disappears but the report does not display.  We are running MAS200 as an application (switched from running as a service this morning to see if that would resolve the issue).  All users connect thru terminal services using unified logon.  If we launch MAS200 "MAS90 style", the reports display correctly.  I would appreciate any suggestions.

[Alnoor]

Good troubleshooting by running it MAS90 style! In MAS 200 if you click on File / Run then type *INFO for the program you will see an Installed Directory Path. BID is trying to execute this path (typically a UNC path) from the server. Since MAS 200 is running as an application, go to the MAS server and click on Start / Run and enter that same path from *INFO.

If it works an Explorer window will open and you will be able to create new files in that window (which is based on that UNC path). If it doesn't work which is what it sounds like here, either you will be get a Windows challenge response asking you to enter a user name and password for access to the resource OR the Explorer window will appear but you are unable to create new files.

Typical reasons for not working include:
* The account running your MAS App Server is not a domain account.
* You are using a domain account but it doesn't have proper access to the network share in your UNC path

Hope that helps!

[csmith]

Thanks for the response, Alnoor, but that did not resolve our issue.  On the MAS server, we typed in the UNC path and it opened in Explorer. We were then able to create a new folder with no problems.

[Alnoor]

Is it possible you were logged into the server with a different account than the one for the App Server? For example let's say MAS App Server runs as a service and uses  "MasAdmin" as the service account. If you tried the UNC test while logged into the server as Administrator then you're running the test under context of Administrator.

One more thing - go to File / Run then type *INFO and see if the Installed Directory Path is the expected UNC path or something that would catch you by surprise. For example if you see a mapped drive such as M:\Apps\MAS90 that can explain the error too as the App Server account may not have the same M: drive mapping.

Hope that helps.