PSEXEC help

I'm trying to configure an alert trigger action to "Run an external program" using the following command to restart the Kiwi Web GUI on a remote system names NOCSQL1.

psexec -d \\NOCSQL1 -u NOCSQL1\OrionAdmin -p ***pswd*** net stop "UltiDev Cassini Web Server for ASP.NET 2.0" && net start "UltiDev Cassini Web Server for ASP.NET 2.0"

The following error is reported in the SwAlert.log

2011-01-04 04:54:38,794 [AlertCheckingThread] WARN All - On alert action Execute program : OrionAdmin -p ***pswd*** net stop "UltiDev Cassini Web Server for ASP.NET 2.0" && net start "UltiDev Cassini Web Server for ASP.NET 2.0" the Alerting Engine service was unable to run the program psexec -d \\NOCSQL1 -u NOCSQL1\OrionAdmin -p ***pswd*** net stop "UltiDev Cassini Web Server for ASP.NET 2.0" && net start "UltiDev Cassini Web Server for ASP.NET 2.0"
Error Detail - File not found.

Can anyone advise what needs to be qualified? Is the error refering to the source location for PSEXEC or do I need to specify the -w directory and what would it be? I'm not a sysadmin.

Find more posts tagged with

Accepted answers

michalB

I tried the PSEXEC and it works fine with &&. I would try to run the two commands separately or putting them in a batch file on the remote machine and started the batch file. That might isolate the issue.

All comments

Questionario

have you tried entering the whole path to the executable with file extension?

FormerMember

have you tried entering the whole path to the executable with file extension?

Thanks Questionario.

I just added the path without extension and the login is now successful to the remote system but now get "Access is Denied." using a local account (with Administrator rights) on the remote system. The Windows event log reports access is denied to the ADMIN$ share. Not sure what permissions need to change to execute the NET cmds. Any thoughts?

michalB

psexec uses Admin$ share to upload an executable to the remote system and then starts it as service that then takes commands from the psexec client on your machine. To upload it there, it needs to have access to the Admin$ share. Since it is running under your account, your account would have to be allowed to write to the share.

The easiest thing is to check whether you are administrator on the target machine. If the target machine is not in the same domain as your computer, create a local account on the target machine and on your computer, use the same name and password. This often helps too.

You may also check our Permissions Analyzer free tool to help you with setting the correct privileges on the Admin$ share.

FormerMember

michalb, got it working with the System account (-s option).

psexec -d -s net stop "UltiDev Cassini Web Server for ASP.NET 2.0" && net start "UltiDev Cassini Web Server for ASP.NET 2.0"\\NOCSQL1

The 'net stop' cmd is executed successfully on the target however the 'net start' cmd part is not working. At initial glance, the target system doesn't appear to see the 'net start' cmd. I see the Windows event logs for executing the 'net stop' cmd but I don't see any logs for success or failure of the 'net start'. I believe my syntax using '&&' is accurate. What I don't know yet is whether psexec is passing the && portion of the string to the target system or Windows 2008 is ignoring it. Any further thoughts?