09-20-2011 04:44 PM
When sending an AMT power command (power on/power off/reset) through the winrm API, sometimes (about 5% of the time) there is a COMException that causes the command sent to fail
System.Runtime.InteropServices.COMException (0x80338012): The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig".
Sending the command again after a few seconds sometimes solves this issue, but our software requires a greater success rate than this.
The source and destination machine are both running on an internal LAN. The trusted hosts is configured correctly and this happens on a version 4.2.20 AMT machine
Please advise on how to reduce the occurence of this exception happening.
09-21-2011 03:50 PM
Handling for generic network errors can be tricky whether on a single or multiple subnets. You can try trapping the error and retrying the command once or twice or until a different response is returned.