I have 9 supposedly identically configured W2K servers.
On one of them ASPExec stopped executing 16 bits apps, including batch files. Executes 32bit apps in same or different directory no problem.
I could have sworn the feature that stopped working was tested and working when installed. Process works just fine in development server.
On errant server, have given aspexec.dll and cmd.exe full control with IWAM_ and IUSR_whatever id's. See thread333-1171593.
Does anyone know why this happens?
code sample:
Set Executor = Server.CreateObject("ASPExec.Execute")
Executor.Application = "L:\WebsiteDir\temp.bat"
Executor.Parameters = AppParam
Executor.ShowWindow = True
strResult = Executor.ExecuteWinAppAndWait
or
strResult = Executor.ExecuteWinApp
or
strResult = Executor.ExecuteDosApp (which never worked for me anyway)
16 bit app now returns error code 5, instead of 258 (the normal "it worked" code). I think 5 is permission denied, however I'm not sure.
On one of them ASPExec stopped executing 16 bits apps, including batch files. Executes 32bit apps in same or different directory no problem.
I could have sworn the feature that stopped working was tested and working when installed. Process works just fine in development server.
On errant server, have given aspexec.dll and cmd.exe full control with IWAM_ and IUSR_whatever id's. See thread333-1171593.
Does anyone know why this happens?
code sample:
Set Executor = Server.CreateObject("ASPExec.Execute")
Executor.Application = "L:\WebsiteDir\temp.bat"
Executor.Parameters = AppParam
Executor.ShowWindow = True
strResult = Executor.ExecuteWinAppAndWait
or
strResult = Executor.ExecuteWinApp
or
strResult = Executor.ExecuteDosApp (which never worked for me anyway)
16 bit app now returns error code 5, instead of 258 (the normal "it worked" code). I think 5 is permission denied, however I'm not sure.