Access to specified path denied when using 'Run as"

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a windows 2k box that is on our domain, and if I am at the Pc with the user logged in, they don't have local admin rights, I try to run a setup.exe file off of a cd to install a program, it prompts me to either put in the admin account password, or to try to run it as the local user. If I put in the local admin password after selecting to use the administrator account, I get the error "Access to the specified path is denied". The only way I can get it to work is if I login locally as the admin, or as myself, I'm part of a group that we have to add to the pc for local admin rights

Any ideas? I saw something on technet about the 'shortcut' not being enclosed in quotes or something, but this is just browsing to the cd in explorer and double-clicking the setup file

Thanks in advance

Steve L.
 
The app is being spawned by explorer. And explorer is single-instanced, so
everything will run in the context of the explorer that's already started.
My hunch is that setup.exe isn't impersonating correctly so it's running in
that default user context. (Just a hunch - I haven't read their code or
debugger this, so I can't know for sure.)

If you run setup with runas or if you kill explorer and start another one
with runas, then do the "click on setup" thing, does everything work?
--
Drew Cooper [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.


Steve L. said:
I have a windows 2k box that is on our domain, and if I am at the Pc with
Click to expand...
the user logged in, they don't have local admin rights, I try to run a
setup.exe file off of a cd to install a program, it prompts me to either put
in the admin account password, or to try to run it as the local user. If I
put in the local admin password after selecting to use the administrator
account, I get the error "Access to the specified path is denied". The only
way I can get it to work is if I login locally as the admin, or as myself,
I'm part of a group that we have to add to the pc for local admin rights.
Any ideas? I saw something on technet about the 'shortcut' not being
Click to expand...
enclosed in quotes or something, but this is just browsing to the cd in
explorer and double-clicking the setup file.
 
I tried running explorer with run as and got the same error, and then tried setup.exe and got the same error

So what you're saying is that if the user is logged in, when we open explorer it's running that in that users' context, then when we run the setup.exe using run as... it's not translating or using the account that we put in...
 
Here's another wrinkle, I noticed on another site that they said if the secondary logon isnt' running that the run as.. won't work, I'm on an xp box now and I went to check it and when I try to view the properties of the service, I get

Unable to open service Secondary Logon for reading on local compute

Error 5: Access Denie

The entry is there in the registry, not sure what the settings are supposed to be.
 
Did you kill the original instance of explorer before spawning the new one?
(There's also a setting to launch explorer in a new process, but it doesn't
always work in an intuitive way, so I don't use or recommend it.)

Right - that's more or less what I'm saying. Again - I haven't read the
setup code and haven't debugged this, so I can't be sure that this is
actually the root cause of the problem. If killing explorer then launching
it with runas as the admin does work, that explanation is probably right.

As for not being able to access the seclogon service properties - was that
as administrator or the other user? Probably a permissions problem. I
don't know what tools we had to query/set service perms in Win2k, but
there's sc.exe on XP and WS03.
--
Drew Cooper [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.


Steve L. said:
I tried running explorer with run as and got the same error, and then
Click to expand...
tried setup.exe and got the same error.
So what you're saying is that if the user is logged in, when we open
Click to expand...
explorer it's running that in that users' context, then when we run the
setup.exe using run as... it's not translating or using the account that we
put in...
 
Well, I found out that our 'admin' team disabled the secondary logon through a domain policy. They never bothered to tell us. We have an account here that adds a group we're in to the local admin of the pc when we login using it. Since that account had domain admin rights, they didn't want us running anything using that account by using "run as..."

Thank you for all your help though, it's greatly appreciated.
 
Back
Top