|
|
|
date: Tue, 08 Jul 2008 21:44:10 +0200,
group: microsoft.public.scripting.wsh
back
Re: Permissions different for WshShell and .exe in Server 20003 SP1 and SP2 ?
"Keith" wrote in message
news:k418745g6a17b1k64cbv4l2v0os6cu380q@4ax.com...
>>> 88 : Set WshShell = Server.CreateObject("Wscript.Shell")
>>> 89 : WshShell.run "D:\DATAII~1\xyz\abc\code.exe xyz"
>>> 90 : Set WshShell=nothing
>>> Now this works fine on my old Windows Server 2003 server with SP1 on
>>> it but I just can't get it to run on my new server with SP2, I always
>>> get this error
>>>
>>> "Microsoft VBScript runtime error '800a0046'
>>> Permission denied
>>> /abc/download.asp, line 89 "
>>>
>>>
>>> Does SP2 do things differently ? Do I need to authorize acces to some
>>> kind of virtual directory used by the the .exe to run maybe ?
>>>
>>> TIA !
>>
>>- Shouldn't it be
>> 88 : Set WshShell = WScript.CreateObject("Wscript.Shell")
>> 89 : WshShell.run "D:\DATAII~1\xyz\abc\code.exe xyz"
>>- What happens when you run "D:\DATAII~1\xyz\abc\code.exe xyz"
>> from a Command Prompt?
>
> It runs fine, no errors.
> I tried to replace Server.CreateObject by WScript.CreateObject as you
> suggested but I get :
> "Microsoft VBScript runtime error '800a01a8'
> Object required:
> /abc/download.asp, line 87''
>
> Did you suggest this because running an .exe is done differently
> betwwen SP1 and SP2 ?
>
> Thanks for your help.
The confusion is because this is a WSH group, and yours is an ASP
application.
That said, I would tend to code the .run as:
>> 89 : WshShell.run """D:\DATAII~1\xyz\abc\code.exe"" xyz"
however, perhaps the issue is that the service account that actually runs
ASP code on the server, which typically has little access to the system for
security reasons, may lack the access required to the .exe itself.
/Al
date: Wed, 9 Jul 2008 00:15:20 -0600
author: Al Dunbar aam
|
|
