Tips to Troublshoot WMI-based Monitoring Errors in OpManager

This document lists the errors encountered often when configuring WMI-based monitors in OpManager. Here are the error codes, possible causes, and resolutions:

• 80070005 - Access is denied
• 80041064 - User credentials cannot be used for local connections
• 800706BA - The RPC server is unavailable
• 80041010 - Invalid class
• 80041003 - Access Denied
• 80040154 - WMI Components are not registered
• 80080005 - Internal execution failure in the WMI Service
• 8004106C - WMI is taking up too much memory
• 8004100E - Invalid namespace
• 80041017 - Invalid query
  

80070005 - Access is denied

Cause

This error occurs when incorrect login credentials are configured.

Solution

• If the device is in a domain, ensure to configure the correct domain name, user name, and password. If the device is in a workgroup, it is sufficient to configure only the user name and password. For instance, if the domain name is BigDom, username is admin, in the user name field, type BigDom\admin.
  
  
• It is also not necessary to specify the user name and password for devices that have user access from the machine where OpManager is installed.
  
  
• Despite the correct credentials, if you still face issues, troubleshoot further using the following steps:
  
  
  • Check if the user account is valid in the target machine by opening a command prompt and executing the following command:
    
    net use \\<monitored device name>\ADMIN$ /u:"<Domain Name\User Name>" "<password>"
    
    If this command throw errors, the provided user account is not valid on the target machine.
    
    
  • Check if 'Remote DCOM' is enabled in the monitored workstation. If it is not enabled, enable it as follows:
    
    
    1. Select Start > Run
    2. Type dcomcnfg in the text box and click OK
    3. Select the Default Properties tab
    4. Select the Enable Distributed COM in this machine checkbox
    5. Click OK
       
       

    To enable DCOM on Windows XP hosts:
    
    

    1. Select Start > Run
    2. Type dcomcnfg in the text box and click OK
    3. Click on Component Services > Computers > My Computer
    4. Right-click and select Properties
    5. Select the Default Properties tab
    6. Select the 'Enable Distributed COM' in this machine checkbox
    7. Click OK
       
       
  • If the above steps do not help, try changing the service Log-on details as follows:
    
    
    • Go to Windows Service UI.
    • Open "Properties" dialog of the "ManageEngine OpManager" service
    • Go to "Log On" tab
    • In the "Log on as" option select "This Account".
    • Configure the user name and password here of the account which has access to the remote machine.
      
    • Save and restart opmanager.
    • Try the above 3 steps again.

            Note: You will not find the tray icon and splash screen after you make these changes.

80041064 - User credentials cannot be used for local connections

Cause

This error is encountered when you specify the Username and password for monitoring the machine where OpManager is running.

Solution

Do not specify Username and password for the localhost. To resolve the issue, remove the configured user name and password from "Passwords" link in the device snapshot page.

800706BA - The RPC server is unavailable.

Cause

This error is encountered when the RPC and WMI services are not running and if the device is not pingable.

Solution

• Check if the device is up and running, and pingable.
  
  
• Check the Remote Procedure Call(RPC) and Windows Management Instrumentation(WMI) Services are running
  
  
  1. Select Start > Run
  2. Type 'services.msc' in the text box and click OK
  3. In the listed services, see if the status of  RPC and WMI services are shown as started.
     
  4. Start the services if it is not started.
     
     
• A firewall might be configured on the remote computer. Such exceptions mostly occur in Windows XP (with SP 2), when the default Windows firewall is enabled. Disable the default Firewall in the Windows XP machine as follows:
  
  
  1. Select Start > Run
  2. Type Firewall.cpl and click OK
  3. In the General tab, click Off
  4. Click OK.
     
     
• If the firewall cannot be disabled, Enable Remote Administration(for administrators) by executing the following command on the remote machine :  "netsh firewall set service RemoteAdmin"
  
  
• A firewall might be blocking the WMI traffic.  Give access to WMI traffic in the firewall. You will need to open the ports 445,135 in the firewall.

80041010 - Invalid class.

Cause

This error occurs when the required WMI class is not registered.

Solution

• Check whether the desired application is installed.
• To register all the WMI classes for the installed application. Run the below commands:
  
  
  • For Windows 2000 'winmgmt /resyncperf' command from the monitored device.
  • For Windows XP and 2003 'wmiadap /f' command from the monitored device.

 80041003 - Access Denied

Cause

This error occurs when the user name provided does not have sufficient access privileges to perform the operation.

Solution

1. It is possible that this user does not belong to the Administrator group for this host machine.
   
2. Try moving the user to the Administrator Group of the workstation.
   
3. Try with an administrator (preferably a Domain Administrator) account.

80040154 - WMI Components are not registered

Cause

This error occurs when the  WMI is not available in the remote windows workstation. This happens in Windows NT. Such error codes might also occur in higher versions of Windows if the WMI Components are not registered properly.

Solution

• Install WMI core in the remote workstation. This can be downloaded from the Microsoft web site.
• Register the WMI DLL files by executing the following command in the command prompt:
  
  winmgmt /RegServer
  
  
• Install the WMI for Windows NT by downloading the below exe:
  
  http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=C174CFB1-EF67-471D-9277-4C2B1014A31E
  

80080005 - Internal execution failure in the WMI Service

Cause

This error occurs when there is some internal execution failure in the WMI Service (winmgmt.exe) running in the host machine. The last update of the WMI Repository in that workstation could have failed.

Solution

Restart the WMI Service in the remote workstation:

1. Select Start > Run.
2. Type Services.msc and click OK.
3. In the Services window that opens, select Windows Management Instrumentation service.
4. Right-click and select Restart.

8004106C - WMI is taking up too much memory

Cause

This error occurs when WMI is taking up too much memory. This could be caused either by low memory availability or excessive memory consumption by WMI.

Solution

• WMI is taking up too much memory.
  
• This could be caused either by low memory availability or excessive memory consumption by WMI.
  
• Try restarting or reinstalling the wmi service.

8004100E - Invalid namespace.

Cause

Invalid namespace Compiler is not a normal error. It is possible that the desired application using the namespace is not installed properly.

Solution

• Try re-installing the application or the WMI services alone.
• Contact http://support.opmanager.com with logs.

80041017 - Invalid query

Cause

'Query was not syntactically valid' is not a normal error. It is possible that the desired application using the namespace is not installed properly.

Solution

• Try reinstalling the application or the WMI services alone.
• Contact support with logs.

For any other error codes, refer the MSDN knowledge base.

Copyright © 2003-2006, AdventNet Inc. All Rights Reserved.