Troubleshooting problems when adding servers to the PowerRecon Inventory

This article provides information on how to troubleshoot issues that arise when attempting to add servers to the PowerRecon Inventory.  This includes errors such as the following:

Network Path Not found

Access Denied

The RPC Server is unavailable

Failed. The Network location cannot be reached

• Ensure that Windows Management Instrumentation (WMI) is installed and that the service is running (on both the machine being added and the PowerRecon Server)
• Ensure that DCOM is enabled (on both the machine being added and the PowerRecon Server - see instructions below on how to check if DCOM is enabled)
• Ensure that the RPC service is running (on both the machine being added and the PowerRecon Server)
• Ensure that the Remote registry service is running (Please see TID 7920526 for more details)
• Ensure that File and Printer Sharing for Microsoft Networks is installed and enabled on the machine being added
• Ensure that the administrative shares Admin$ and C$ on the source server are accessible from the PowerRecon Server
• Try discovery using a local admin account with the user name syntax: hostname\LocalAdmin
• Try discovery with a domain admin account with the user name syntax: domain\DomainAdmin
• If you are using the UPN (User Principal Name) format for the credentials, ensure that the PowerRecon Server is installed on a Windows 2003 Server ( see TID 7920527  for more information)
• If you are experiencing problems discovering a Windows NT 4.0 Server, ensure that the Server service is running and the latest WMI core version is installed. ( See the link below to download WMI Core V1.5 from Microsoft's web site )
• If problems still exist after checking the above, please see the related articles below

TEST 1:

If you are still experiencing problems discovering servers after verifying the above, Microsoft's Windows Management Instrumentation Tester (WBEMTest) can be used to troubleshoot WMI connections as follows:

1. On the machine where the PowerRecon Server is installed, click on the Windows Start button and then select Run
   Type "Wbemtest" (without the quotes) and press Enter.
2. In the Namespace enter in the name of the machine you are trying to discover with \root\cimv2 appended.  For example,  if your machine name is win2k you would enter: \\win2k\root\cimv2 as the namespace
3. Enter in the appropriate credentials using either the hostname\LocalAdmin or domain\DomainAdmin format
4. Click on the Connect button to test the WMI connection.  If an error message is returned after clicking on  "Connect", this indicates that a WMI connection cannot be established between the machine where PowerRecon Server is installed and the machine being added.  Please contact your Support Administrator for further assistance.

TEST 2:


Another good test to try is to launch the Windows Performance Monitor on the PowerRecon Server and then try monitoring the remote server that is experiencing problems when being added to the PowerRecon inventory.  If the remote server cannot be monitored using Windows Performance monitor or an error appears, this most likely indicates that a connection cannot be established between the remote server and the PowerRecon Server.  Please contact your Support Administrator for further assistance.

1. Click on the Windows Start button and select Run
2. Type "dcomcnfg" (without quotes) and press Enter
3. On a Windows NT/2000 server machine, the DCOM Configuration dialog window should appear.  Click on the Default Properties tab and ensure that "Enable Distributed COM on this computer" is checked.
4. For Windows 2003, the Component Services window will appear instead.  In the Computers folder of the console tree of the Component Services administrative tool, right-click on the computer for which you want to check if DCOM is enabled and then click on Properties.  Click on the Default Properties tab and ensure that "Enable Distributed COM on this computer" is checked."
5. If DCOM was not enabled, please enable it and restart the Windows Management Instrumentation Service (if rebooting the server is not possible) and rerun the job to add the machine again to PowerRecon's Inventory