|
When I try to run on a Windows 7 64bit host: paexec \xxx.xxx.xxx.xxx -u Administrator -p xxx qwinsta I get the following error: Remote app failed to start. Returned error: Failed to start "qwinsta". The system cannot find the file specified. [Err=0x2, 2] PAExec returning exit code -9 When I try to explicitly state where the file is (I have checked that the file actually is in that directory) I still get the same error paexec \xxx.xxx.xxx.xxx -u Administrator -p xxx c:windowssystem32qwinsta WHen I copy the qwinsta.exe from c:windowssystem32 to c:windowssyswow64 the command works. The strange thing is that I still try to start the application in c:windowssystem32 and not in the sysow64 directory. paexec \xxx.xxx.xxx.xxx -u Administrator -p xxx c:windowssystem32qwinsta Any ideas on how to get this to work or anything more that I might try? |
|
PAExec is a 32-bit application. Because of that, it is under the WOW64 File Redirection 'feature' in Windows. To get around it, use the -dfr option: -dfr Disable WOW64 File Redirection when launching the new process 1
Thanks, I had missed the -dfr option since I used psexec before but that one just hangs when executed via jenkins. Added -dfr to my command and now it works on both 64 and 32 bit computers.
(03 Aug '12, 14:10)
ef02lajo
|
