PsTools : psexec - network name is no longer available

 

I am currently running psexec.exe version 1.93.

 

I have a SQL Server (Windows 2008 R2 64-bit) and an Application Server (Windows 2008 32-bit) used in this scenario.  From a SQL job, I am calling psexec to launch an executable on the application server.  This executable is actually communicating back to a database on the same SQL server. 

 

Here is the command being called:

psexec \\appserver -accepteula -w "C:\Winservices" "C:\WinServices\DetectComp.exe"

 

I have placed the psexec command in the c:\windows\system32\ directory of the application server.

 

This particular executable that I am calling takes about 45 minutes to process.  What I am seeing at times is that part way through the process, psexec looses connection to the application server.  Because of this, it reports an error back to SQL Agent and I get a page to notify me the process failed.  But, what is truly happening is that the executable is still running fine on the application server (communicating to the SQL server) and it will complete successfully.  It is just psexec that lost connection between the 2 machines.  My guess is that this is caused by a small network hiccup that the executable I am calling handles fine but psexec doesn't like.

 

Does psexec have any type of retry scenario that will allow us to connect back up to the command it had already started to continue to monitor it?  I don't see anything like this in the help information.  I do see there is an option to run psexec in non-interactive mode and while this could resolve this issue, I really do need it to run interactively so I can get the results of the called executables.

 

What is the best way to resolve this issue?

 

Here is some of the logging the SQL jog has.  It is not all in order.  The multiple dots are the processing of the detectcomp.exe to show it is still processing.