Hi,

I have discussed this issue recently in the ASP.NET Forum of UT but I thought maybe this is not ASP.NET problem but Windows Server problem.

Here is a brief summary:

I have two customers, both using Windows Server 2008 R2. Both using the same ASP.NET application and the same VFP 9 application.
The VFP9 application (small EXE) is being executed from the ASP.NET. The application named PrintOrder.exe prints one-page order report.

For both customers the printing works. But in the case of one customer I see the PrintOrder.exe process in the Task Manager on the server (I am connecting via RDT). And there are as many instances of the PrintOrder.exe in the Task Manager as the time this program (PrintOrder.exe) was executed in the ASP.NET application. The second/other customer shows NO process PrintOrder.exe in the Task Manager (so it means that the process starts, does its job, and closed). The program PrintOrder.exe is executed from the ASP.NET application with the command Start Process.

Yesterday I manually Ended many of these processes because I am afraid that the server will have a serious problem.

What could be different between these two Server 2008 R2 servers that causes the PrintOrder.exe process Stay in the Task Manager?

TIA