Calling an executable from an .aspx page hosted on Windows 2003

[Marlene Arauz Martin]

Hello,
How's everybody???

I have an aspx. page that is calling an executable,.... like this...

System.Diagnost ics.ProcessStar tInfo psi= new
System.Diagnost ics.ProcessStar tInfo();
psi.FileName="R ATE2.exe";
psi.WorkingDire ctory=Applicati on["TempDir"].ToString();
System.Diagnost ics.Process p= System.Diagnost ics.Process.Sta rt(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.

[John Saunders]

"Marlene Arauz Martin" <pd*****@nospam .wdsinc.com> wrote in message
news:uU******** ******@TK2MSFTN GP10.phx.gbl...

Hello,
How's everybody???

I have an aspx. page that is calling an executable,.... like this...

System.Diagnost ics.ProcessStar tInfo psi= new
System.Diagnost ics.ProcessStar tInfo();
psi.FileName="R ATE2.exe";
psi.WorkingDire ctory=Applicati on["TempDir"].ToString();
System.Diagnost ics.Process p= System.Diagnost ics.Process.Sta rt(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 suggest that you put a try block around this code and display the
exception in the catch clause.
--
John Saunders
johnwsaundersii i at hotmail

[Mark Shasby]

I have exactly the same problem but no exception is thrown, it just
hangs at the Start method: i.e. event 8 is logged but not event 9.

EventLog.WriteE ntry(
EVENT_LOG_SOURC E,
"see event number",
EventLogEntryTy pe.Information,
8
);

Process.Start(p si);

EventLog.WriteE ntry(
EVENT_LOG_SOURC E,
"see event number",
EventLogEntryTy pe.Information,
9
);
Any other ideas how to debug this anybody?

John Saunders wrote:

"Marlene Arauz Martin" <pd*****@nospam .wdsinc.com> wrote in message
news:uU******** ******@TK2MSFTN GP10.phx.gbl...

Hello,
How's everybody???

I have an aspx. page that is calling an executable,.... like this...

System.Diagno stics.ProcessSt artInfo psi= new
System.Diagno stics.ProcessSt artInfo();
psi.FileName= "RATE2.exe" ;
psi.WorkingDi rectory=Applica tion["TempDir"].ToString();
System.Diagno stics.Process p= System.Diagnost ics.Process.Sta rt(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 suggest that you put a try block around this code and display the
exception in the catch clause.

[John Saunders]

"Mark Shasby" <ma**@shasby.co m> wrote in message
news:OM******** ******@TK2MSFTN GP11.phx.gbl...

I have exactly the same problem but no exception is thrown, it just
hangs at the Start method: i.e. event 8 is logged but not event 9.
EventLog.WriteE ntry(
EVENT_LOG_SOURC E,
"see event number",
EventLogEntryTy pe.Information,
8
);

try
{
Process.Start(p si);
}
catch (Exception ex)
{
EventLog.WriteE ntry(
EVENT_LOG_SOURC E,
ex.ToString(),
EventLogEntryTy pe.Information,
10
);
}

EventLog.WriteE ntry(
EVENT_LOG_SOURC E,
"see event number",
EventLogEntryTy pe.Information,
9
);

Any other ideas how to debug this anybody?

John Saunders wrote:

"Marlene Arauz Martin" <pd*****@nospam .wdsinc.com> wrote in message
news:uU******** ******@TK2MSFTN GP10.phx.gbl...

Hello,
How's everybody???

I have an aspx. page that is calling an executable,.... like this...

System.Diagno stics.ProcessSt artInfo psi= new
System.Diagno stics.ProcessSt artInfo();
psi.FileName= "RATE2.exe" ;
psi.WorkingDi rectory=Applica tion["TempDir"].ToString();
System.Diagno stics.Process p= System.Diagnost ics.Process.Sta rt(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

executableis 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 isolationmode, and it worked.

I suggest that you put a try block around this code and display the
exception in the catch clause.

[Mark Shasby]

Same result - it is already in a try catch as suggested earlier, thanks.
It hangs. try/catch doesn't stop things hanging. Hence the "any OTHER
ideas how to debug this".

John Saunders wrote:

"Mark Shasby" <ma**@shasby.co m> wrote in message
news:OM******** ******@TK2MSFTN GP11.phx.gbl...

I have exactly the same problem but no exception is thrown, it just
hangs at the Start method: i.e. event 8 is logged but not event 9.

EventLog.WriteE ntry(
EVENT_LOG_SOURC E,
"see event number",
EventLogEntryTy pe.Information,
8
);

try
{
Process.Start(p si);
}
catch (Exception ex)
{
EventLog.WriteE ntry(
EVENT_LOG_SOURC E,
ex.ToString(),
EventLogEntryTy pe.Information,
10
);
}

EventLog.WriteE ntry(
EVENT_LOG_SOURC E,
"see event number",
EventLogEntryTy pe.Information,
9
);

Any other ideas how to debug this anybody?

John Saunders wrote:

"Marlene Arauz Martin" <pd*****@nospam .wdsinc.com> wrote in message
news:uU***** *********@TK2MS FTNGP10.phx.gbl ...
Hello,
How's everybody???

I have an aspx. page that is calling an executable,.... like this...

System.Diag nostics.Process StartInfo psi= new
System.Diag nostics.Process StartInfo();
psi.FileNam e="RATE2.exe" ;
psi.Working Directory=Appli cation["TempDir"].ToString();
System.Diag nostics.Process p= System.Diagnost ics.Process.Sta rt(psi );
p.WaitForEx it();

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 suggest that you put a try block around this code and display the
exception in the catch clause.

[John Saunders]

"Mark Shasby" <ma**@shasby.co m> wrote in message
news:%2******** *******@TK2MSFT NGP09.phx.gbl.. .

Same result - it is already in a try catch as suggested earlier, thanks.
It hangs. try/catch doesn't stop things hanging. Hence the "any OTHER
ideas how to debug this".
You had not previously indicated that it was in a try block.

Your code with the event logging is a bit different than your earlier code
(with the WaitForExit). If WaitForExit is still there, are you sure the code
is blocking on the Start and not on the WaitForExit?

Also, is the entire site frozen, or just the one request?
--
John Saunders
johnwsaundersii i at hotmail
John Saunders wrote:

"Mark Shasby" <ma**@shasby.co m> wrote in message
news:OM******** ******@TK2MSFTN GP11.phx.gbl...

I have exactly the same problem but no exception is thrown, it just
hangs at the Start method: i.e. event 8 is logged but not event 9.

EventLog.WriteE ntry(
EVENT_LOG_SOURC E,
"see event number",
EventLogEntryTy pe.Information,
8
);

try
{
Process.Start(p si);
}
catch (Exception ex)
{
EventLog.WriteE ntry(
EVENT_LOG_SOURC E,
ex.ToString(),
EventLogEntryTy pe.Information,
10
);
}

EventLog.WriteE ntry(
EVENT_LOG_SOURC E,
"see event number",
EventLogEntryTy pe.Information,
9
);

Any other ideas how to debug this anybody?

John Saunders wrote:

"Marlene Arauz Martin" <pd*****@nospam .wdsinc.com> wrote in message
news:uU***** *********@TK2MS FTNGP10.phx.gbl ...
>Hello,
>
>
> How's everybody???
>
> I have an aspx. page that is calling an executable,.... like this...
>
>System.Diag nostics.Process StartInfo psi= new
>System.Diag nostics.Process StartInfo();
>psi.FileNam e="RATE2.exe" ;
>psi.Working Directory=Appli cation["TempDir"].ToString();
>System.Diag nostics.Process p= System.Diagnost ics.Process.Sta rt(psi );
>p.WaitForEx it();
>
>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 suggest that you put a try block around this code and display the
exception in the catch clause.

[John Saunders]

"Mark Shasby" <ma**@shasby.co m> wrote in message
news:%2******** *******@TK2MSFT NGP09.phx.gbl.. .

Same result - it is already in a try catch as suggested earlier, thanks.
It hangs. try/catch doesn't stop things hanging. Hence the "any OTHER
ideas how to debug this".
Here's another thought. Have you tried this with other executables? In
particular, try writing a console program which does nothing - not even
writing "Hello, world". It should just exit. Then try starting that program
(using the full path to the executable). See if it works.
--
John Saunders
johnwsaundersii i at hotmail

John Saunders wrote:

"Mark Shasby" <ma**@shasby.co m> wrote in message
news:OM******** ******@TK2MSFTN GP11.phx.gbl...

I have exactly the same problem but no exception is thrown, it just
hangs at the Start method: i.e. event 8 is logged but not event 9.

EventLog.WriteE ntry(
EVENT_LOG_SOURC E,
"see event number",
EventLogEntryTy pe.Information,
8
);

try
{
Process.Start(p si);
}
catch (Exception ex)
{
EventLog.WriteE ntry(
EVENT_LOG_SOURC E,
ex.ToString(),
EventLogEntryTy pe.Information,
10
);
}

EventLog.WriteE ntry(
EVENT_LOG_SOURC E,
"see event number",
EventLogEntryTy pe.Information,
9
);

Any other ideas how to debug this anybody?

John Saunders wrote:

"Marlene Arauz Martin" <pd*****@nospam .wdsinc.com> wrote in message
news:uU***** *********@TK2MS FTNGP10.phx.gbl ...
>Hello,
>
>
> How's everybody???
>
> I have an aspx. page that is calling an executable,.... like this...
>
>System.Diag nostics.Process StartInfo psi= new
>System.Diag nostics.Process StartInfo();
>psi.FileNam e="RATE2.exe" ;
>psi.Working Directory=Appli cation["TempDir"].ToString();
>System.Diag nostics.Process p= System.Diagnost ics.Process.Sta rt(psi );
>p.WaitForEx it();
>
>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 suggest that you put a try block around this code and display the
exception in the catch clause.