M
Marlene Arauz Martin
Hello,
How's everybody???
I have an aspx. page that is calling an executable,....like this...
System.Diagnostics.ProcessStartInfo psi= new
System.Diagnostics.ProcessStartInfo();
psi.FileName="RATE2.exe";
psi.WorkingDirectory=Application["TempDir"].ToString();
System.Diagnostics.Process p= System.Diagnostics.Process.Start(psi );
p.WaitForExit();
I did my development on my computer that is running Windows 2000, and now I
want to deploy on a Windows 2003 server, but the calling to the executable
is not working, I don't even see any error, but I'm pretty sure is a
security issue. I tested configuring IIS 6.0 to run in IIS 5.0 isolation
mode, and it worked.
I'm not familiarize with II6.0, I'm not sure what user I have to give access
to run the executable.
Any ideas???
M.A.R.
How's everybody???
I have an aspx. page that is calling an executable,....like this...
System.Diagnostics.ProcessStartInfo psi= new
System.Diagnostics.ProcessStartInfo();
psi.FileName="RATE2.exe";
psi.WorkingDirectory=Application["TempDir"].ToString();
System.Diagnostics.Process p= System.Diagnostics.Process.Start(psi );
p.WaitForExit();
I did my development on my computer that is running Windows 2000, and now I
want to deploy on a Windows 2003 server, but the calling to the executable
is not working, I don't even see any error, but I'm pretty sure is a
security issue. I tested configuring IIS 6.0 to run in IIS 5.0 isolation
mode, and it worked.
I'm not familiarize with II6.0, I'm not sure what user I have to give access
to run the executable.
Any ideas???
M.A.R.