Application will only load under Administrator account

[Guest]

Archived from groups: microsoft.public.windowsnt.terminalserver.applications (More info?)

Hello,

I have a in house developed application that has been working for over a
year now on Terminal Server however all of a sudden the application will
not load for any user except the actuall administrator account.

Even if I log in as myself (domain administrator) and it will not run.
Basically you may see it pop up in the processes of task manager, but it
immediately goes away.

This particular app requires parameters and if you don't pass any it will
generate an error. Well even that doesn't happen. No error, no visual
cues that it loading or anything... just the quick in and out in the Task
Manager processes.

Does anyone have any clue what could cause this to happen. The fact that
it will run for the administrator account tells me there is nothing wrong
with the application itself otherwise it should bomb there.... but with a
domain admin account i would think it would load as well... arghh.

Any thoughts, opinions, ideas, etc.

Greg

 

[Guest]

Archived from groups: microsoft.public.windowsnt.terminalserver.applications (More info?)

Found the problems...

I have found some details with the FileMon utility.

It looks like it cannot find the following for regular users:
"U:\Program Files\Common Files\System\ADO\msado15.dll"

The U: drive for everyone including the administrator is a mapped path on
a different server.

When I examine the "U:\Program Files\Common Files\.." I see a lot of stuff
is missing from that folder. The administrator has the following
additional folders inside of ..\Common Files\:
Microsoft Shared
ODBC
System

Turns out there is a registry entry hklm\software\microsoft\windows
\currentversion\CommonFilesDir (REG_SZ) that is what sets the
CommonProgramFiles environment variable.

I made the change to the registry, copied all the files from the incorrect
location on the U:... drive over to the M:..., I had to change
approximately 200 registry entries to point to the correct location as
well. I found some registry entries that had the UNC name so I changed
those to the new location as well. I used a tool called Registry Crawler
to do this http://www.4developers.com/regc/ . I then reinstalled MDAC
along with the MDAC security fixes. I used the user change /install each
time I did anything "just in case"

After all was said and done everything started working like a champ.