Author: tutungzone
Subject: Difference in PSEXEC on 32bit and 64bit Server2003
Posted: 19 June 2013 at 7:28pm
I have an application that is executed remotely (can be 32bit or 64bit) using PSEXEC... seems we are having an issue though and I think I need to understand the difference in order to fix the issue. Eula has been accepted on all servers... non-issue. User is admin on all servers... non-issue.
Subject: Difference in PSEXEC on 32bit and 64bit Server2003
Posted: 19 June 2013 at 7:28pm
I have an application that is executed remotely (can be 32bit or 64bit) using PSEXEC... seems we are having an issue though and I think I need to understand the difference in order to fix the issue. Eula has been accepted on all servers... non-issue. User is admin on all servers... non-issue.
For explanation sake, will will say the program being executed is Exist.exe. This programs purpose in life is to watch a process to make sure it is running, if not, fire off the CMD that starts the program. Exist.exe runs as a looping process looking for a specific process name every minute.
Scenarios:
1) If executing Exist.exe locally, the process starts and begins it's "watch." I kill the process it is watching and Exist.exe process fires the CMD to start the killed process back up... console comes up as normal to fire off application and works fine whether on 32bit or 64bit 2003 Server.
2) If executing Exist.exe remotely using PSEXEC to a 32bit 2003 Server, the process starts and begins it's "watch." I kill the process it is watching and Exist.exe process fires the CMD to start the killed process back up... console comes up as normal to fire off application and works fine.
3) If executing Exist.exe remotely using PSEXEC to a 64bit 2003 Server, the process starts and begins it's "watch." I kill the process it is watching and Exist.exe process fires the CMD to start the killed process back up... console comes up as normal to fire off application but application fails to start with a C++ Runtime error.
---
Tried installing C++ libraries thinking maybe the application being launched was looking for a 32bit C++ library on the 64bit Server... no luck, same thing. If I execute the Exist.exe program locally to the 64bit server, running as the same user, on the same session... the process works fine when starting tha application back up. It is almost like the state of the Exist.exe program is running differently when executed from PSEXEC and when ran locally. Hitting my head against a wall here... help!
Just for grins... I use the same PSEXEC command to start the application whether on 32 or 64bit Servers... seems this one application (not the Exist.exe application, but the application executed by the Exist.exe application) does not like how it is being started somehow. I have another similarremote executed "watch" programs in the same environment that work fine on 64bit servers.
Command: c:\TechCode\psexec \\server.domain.com -u domain\user -p
password -i 1 -d "C:\TechScripts\Exist_CAAppServer.exe"
WTF... is there a difference in the state of this process when run locally and when executed remotely?