Joined: Mar 28, 2006
Posted: Mar 30, 2006 01:27 PM
Msg. 1 of 2
Since there is no upgrade path between 2.x and 3.x, and based on recommendations from technical support, we have decided to deploy both Prophet-X 3.0 and 2.57 across my client's organization. This will allow users running 2.x versions to not be interrupted when we roll out new desktops.
However, I am experiencing many issues with regard to running version 2.57 in a locked-down environment. Here are the scenarios I tried:
Installed the program as an administrator
Ran the program as a user
*Didn't work* I get the error message "Can't register server API from Prx"
Using regmon, it looks like the program is trying to write to HKCR. Next, I tried the scenario below:
Elevated a user's permissions to local admin
Ran the install as the user w/ elevated privileges
Started the program, runs fine. Was able to connect to server.
Removed local admin privledges from user
Started the program again, prompted for login
Pressed OK to login
*Didn’t work* Error message “Connection Failed: No Router File”
Using filemon, it is clear that Prophet-X is accessing the incorrect location for the routers.dat file. It is looking for the file in C:\Program Files\FIMI\ProphetX\My ProphetX Files (correct location is C:\Program Files\FIMI\ProphetX). The strange part is that regmon shows that it read the location of the router file correctly, and filemon shows that it was able to access the (correct) file earlier, before I click OK to login.
If I re-elevate the user to local admin, the logon works with no error message. I can’t find any indication (using filemon or regmon) as to why Prophet-X “knows” the correct file location when run with administrative privileges and not with regular user privileges. When I run as an administrator, Prophet-X simply goes to the correct location without any failure messages. There is no indication that Prophet-X is able to access any "new" or "different" registry information as an admin either.
I have tried other techniques, such as repackaging (using InstallShield’s Repackager), but the same thing happens. The GPO here is not very strict, either.
Elevating every user that needs Prophet-X to local admin is definitely unacceptable at this organization. Is there another way around this? There must be some way to run this program without being a local administrator…?
Thanks for your help!
West Monroe Partners, LLC