Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Only a member of the Admin group can start applications 1

Status
Not open for further replies.
Oct 8, 2001
41
NL
Hi I gues I'am missing something I have instaled a program on a tse mfr18 server. Users can't to start the application, when a user from the admin group tries it it starts. There are no strange rights on the apps dir.....

What am i missing? Robin Plomp
Senior System Engineer
MCSE CCA

Is a dream a lie if it don't come true
Or is it something worse
 
try looking at user rights. User Manager > Policies > User Rights. Check and make sure users have the correct rights.
 
This sounds similar to what I experienced. The program was not WIN2K certified and would only run for administrators. Any other user would get errors when they tried to run it.

The solution was in the registry rights. The program wanted to be able to change entries in the registry but was unable due to the rights associated with each folder.

A friend sent me to to get the program called Regmon. This program told me where to find the entries that were being accessed.

Then using regedit32 I check the rights of the folders. Once I changed the rights the program ran with no errors.

Hope that helps.
 
First. Is it a published app.? If just redo the published app.

Second. Do you see the path as a UNC when the use tries to launch the app.? If so you have to go though explorer all users and recreate the short cuts to all the apps. pointing to the app. using browse don't cut and paste the path names as this won't work...
 
It sounds like your having an ODBC problem...

Terminal Server gets confused on installation of the latesets MDAC file and olny gives rights to the admin group.

see MS Knowledgebase document Q216149, Q225195 & Q216149

Good Luck.

 
I would agree that you should 1st check the rights/permissions of your user accounts against those of the application folders and any other forlder that your application may need to write to. For starters, can you be more specific about what happens when a basic user executes the app? Do you get any kind of msg? -- Devil Dog --
 
Hi
Sysinternals also have a tool called Filemon which does the same as Regmon only it checks what files are accessed instead. I would recommend you to use these two tools and do a capture when a user starts the application to see if there are any Access Denied entrys that can be related to the application. Then all you can do is try and change the permissions for the files and/or registry entries. You can always change them back. These tools are invaluable when troubleshooting problems like this.
Hope this helps

/Hof
 
under which account have you installed the software?
you should install the software under an adminstrator account.
 
I have just fixed a very similar problem using Filemon to show me the files accessed by the application. Changing permissions fixed it.
 
Hi guys, thanks for all the help.

I used the application filemon and found out that the file "msvcirt.dll" was causing the problem. I gave the Users read access to this file and the problem was solved.

Thanks Robin Plomp
Senior System Engineer
MCSE CCA

Is a dream a lie if it don't come true
Or is it something worse
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top