Troubleshooting the Windows Command adapter

This section provides troubleshooting information specific to the BMC Atrium Orchestrator Windows Command Base Adapter.

Ensure that you verify the following things before you troubleshoot the adapter:

• The adapter is enabled and is in the running state.
• The peer on which adapter is enabled has the peer service running with administrator rights.
• The target is Windows-based and you have provided the valid administrator credentials in the adapter configuration or in the dynamic request.

Message: Could not connect to \\host\IPC$
OR
A specified logon session does not exist. It may already have been terminated.

User Response: Verify that the peer service is running as an administrator or provide the valid administrator credentials to log on to the service.

Message: No command was identified for the targeted OS

Explanation: The error occurs when you execute a FAT command in an adapter request.

User Response: Perform the following error-specific steps:

• For an invalid OS ID or version error, verify the target OS ID and version with all the supported values. The valid supported OS IDs are:
  • Windows NT
  • Windows 2000
  • Windows 2003
  • Windows Server 2008
  • Windows XP
• For connection issues, ensure that the target is reachable and provide the valid administrator credentials.
• You must start the peer service using administrator credentials.