WMI FAQ and Troubleshooting
This article is contributed by Ziyun Immortals
WMI FAQ and Troubleshooting
Description: This document WMI problem and solve the collection, may relate to our company multiple products, please select reference use. A FAQ and Solution 1 1. When you add servers, MICROSOFT. NET, and EXCHANGE servers through WMI, you are prompted to verify that the validation failed. Please confirm the username and password. 1 2. Memory utilization data displays an error while monitoring WINDOWS servers in WMI mode. 1 3. How do I rebuild a WMI class? 1 4. When you monitor a Windows machine in WMI mode, which services should run on a remote Windows computer. 2 5. When you try to add a server monitor through WMI mode, you are prompted for "authentication failed or access denied." 2 6. When I configure server monitor for a server, I am prompted with the following error: "Error # RPC server busy, unable to complete operation" 6 7. When you add server monitor through WMI mode, you are prompted with the error "RPC server is not available." 6 8. <OPMANAGER> The WMI monitor is not running. Always show "ERROR # ACCESS DENIED". 72. The WBEMTEST test tool is used 8 1. Use the WBEMTEST tool to test. 8 2. Common errors and resolutions (ELA) 8 3. Common Errors and Solutions (Opmanager) 10
A Frequently asked questions and how to solve them
1. When adding servers,. NET, and servers, you are prompted to verify that the validation failed. When you add servers, Microsoft. NET, and Exchange servers through WMI, you are prompted to verify that the validation failed. Please confirm the username and password "Please confirm username and password". Workaround: Please enter the username in the <domainname>\<username> format Note: note: In Opmanger for local WMI authentication, you do not need to enter a username and password.
2.
The memory utilization data displays an error while the server is in use. Memory utilization data displays an error while monitoring Windows servers in WMI mode. Workaround: In WMI, we use Win32_OperatingSystem to get the memory data for the WINDOWS2003 server. When system memory exceeds 4GB, accurate information is not reported. This is a problem with Windows 2003 SP1. See http://support.microsoft.com/kb/906868/For more information and install patches.
3.
How do I rebuild a WMI class? Workaround:
The MOF (Managed Object format) file is a mechanism through which information about the WMI class enters the WMI repository. Class definitions in the repository
May be corrupted, in this case, recompile the MOF file and copy and replace it with the class definition when the operating system was originally installed. At the command prompt, execute the following command: Windows 2003/xp * C:\windows\system32\wbem\Mofcomp.exe c:\windows\system32\wbem\cimwin32.mof * c:\ Windows\system32\wbem\mofcomp.exe C:\WINDOWS\SYSTEM32\WBEM\CIMWIN32.MFL
Windows C:\winnt\system32\wbem\Mofcomp.exe * c:\winnt\system32\wbem\ c:\winnt\system32\wbem\cimwin32.mof * Mofcomp.exe C:\WINNT\SYSTEM32\WBEM\CIMWIN32.MFL
If you are prompted not to find the path, use%windir% (Windows directory name) to replace Windows (if the system is Windows 2003/XP) or Winnt (if the system is Windows 2000). Refer to the links below for more information Http://www.microsoft.com/technet/scriptcenter/topics/help/wmi.mspx#ECIAC
4.
Machine when the computer runs. When you monitor a Windows machine in WMI mode, which services should run on a remote Windows computer. The following services should be run on a remote Windows machine: 1 remote Procedure call (RPC) remoting procedure calls-port: 135 2) Windows Management Instrumentation (WMI) Window S management Specification-port: 445 If the firewall is enabled, these ports should be open at the firewall.
5.
Mode when you add Server monitor, you are prompted for "authentication failed or access denied" when you try to add Server monitor through WMI mode. 1 Domain name and IP address problem the domain name \ user name is the username such as: adventnet\admin if the username is not a domain name account, try using the host name \ Username. such as: Admin\admin
If you do not know the domain name or user name, please confirm the user account through the Control Panel-->. You can view the users on the system and the domains and workgroups to which they belong. -Use WBEMTest to find error messages when connecting to remote systems Click Start--> Run--> WBEMTest Open the Windows Management Instrumentation Tester. Click the Connect button. In the first text box (root\default), enter <\\hostname\root\cimv2> enter a username and password. Click on the Connection button, if prompted incorrectly, please enter the IP address in the hostname.
<\\ipaddress\root\cimv2>
If normal, you can access the machine only through the IP address. This may be due to an error entry in the Hosts file in the <C:\Windows\system32\drivers\etc\hosts> file. Removes the error entry in the file and attempts to access it with a host name. 2) DCOM Settings
On the remote computer: Check that the remote computer is enabled for DCOM Click Start--> Run--> input dcomcnfg, open the Component Services console. Click on the Component Services--> Select the computer--> click My Computer (right click to select Properties).
Click on the Default Property tab to check that the properties are configured as follows: A to enable distributed COM on this computer The default authentication level is connection C) The default impersonation level is impersonation or identity if the above properties have changed, please configure it above, and then check the applications Manager Whether it can be added.
Then make sure to make changes in the registry as well. Start--> run--> enter regedit and open the Registry Editor console.
Click on My Computer-> HKEY_LOCAL_MACHINE->software-> Microsoft->
OLE-> enabledcom, set to ' Y '.
3 Check COM Security Click Start--> Run--> input dcomcnfg, open the Component Services console. Click on the Component Services--> Select the computer--> click My Computer (right click to select Properties). Click on the COM Security tab to check whether the properties are configured as follows: Click on the Edit default value in the Access permission. Then check that SELF and SYSTEM are enabled for remote access. Click on My Computer, click DCOM Configuration, select Windows Management instrumentation. Then right-click the Select attribute to check whether the authentication level is set to default.
4 WMI security on a remote computer: Checks whether the specified user has sufficient permissions to access WMI from a remote computer. Click Start--> Run--> input, wmimgmt.msc Open the Windows Management Architecture console. Right-click WMI control and select Properties-> security-> security settings. Then check to see if the group that the user belongs to has full permissions, such as remote activation. If not, select the check box to allow and save changes. Then try adding the server to the applications Manager. If you do not want to change the permissions for the group, create a user with the Guest role. Enter the control Panel--> user account to add a user with a Guest role. Then go to the Windows Management console and click the Add button. In Windows 2000, the most recently added users are listed. You can choose to add and grant all permissions. In Windows XP, enter the username machinename\username in the Enter the Object names to select text box. Click OK to add the user and grant permissions to save. Try adding the server again.
5 Verify user rights on the remote computer click Start--> run--> input gpedit.msc. Open the Group Policy console. Click Local Computer Policy-> Computer Configuration-> Windows Settings-> Security Settings-> Local Policy-> User Rights Assignment-> Authentication impersonate the client. After adding the user, try adding the server again. Adding a Windows monitor in WMI mode requires the user to have administrator privileges.
6 Local Security settings if the remote machine is a Windows XP computer, make sure that the GUEST account is not forced to use Telnet. Click Start--> Run--> enter secpol.msc and open the Local Security Settings console. Click Local Policy-> security option-> Network access: Sharing and security mode for local accounts, if set to guest only, right click on Properties, change to Classic, and then restart the computer. 7 for Windows XP SP2 Computer, configure the firewall to allow remote control. Method: Open a command prompt and enter the netsh firewall set service remoteadmin.
8 The necessary Windows services ensure that all remote access and WMI-related services are enabled and run on the remote computer. In Windows XP, you should run the following services or allow the command to start. COM + Event System remote access Auto Connection Manager remote Access Connection Manager remote Procedure call (RPC) Remot E Procedure Call (RPC) Locator Remote Registry Server Windows Management instrumentation Windows Management instrumentatio N Driver Extensions WMI performance Adapter Workstation
9) Click Start--
> Run--> input wmimgmt.msc to open the Windows management Architecture console. Right-click the attribute-> logging. Enable "verbose" on the remote machine.
6.
When I configure server monitor for a server, the server is busy and when I configure Server monitor for a server, I am prompted with the following error: # The RPC server is busy, prompting the following error: ' Cannot complete operation ' cannot complete operation ' please refer to the following link to resolve the RPC server problem. http://support.microsoft.com/kb/177446 http://support.microsoft.com/kb/905700
7.
mode when adding server monitor, the error "RPC server is not available" prompts for error "RPC server unavailable" when adding server Monitor in WMI mode. 1 Try using the domain name/username and adding server 2 using only the username to check whether the remote Windows computer can be ping from the applications Manager machine. Attempt to ping with host name and IP address. 3 Check to see if there is a firewall between the machine running applications Manager and the remote Windows computer. If you have a firewall, open the ports in your firewall for monitoring. The ports are 135 (RPC) and 445 (WMI). Then try adding the monitor again. If the port is open, the same error still occurs. WMI on a remote computer may use a random port to reply to a WMI request (that is, a request you made to a remote server from the applications Manage machine). But you can restrict it to use only a certain range of ports. Therefore, these ports must be open. For more information on how to restrict port range assignments, refer to the links below. http://support.microsoft.com/kb/300083
The above configuration should be done on the remote computer that you want to monitor. 4 Check that the RPC and WMI services are running on the remote computer. On the remote computer, click Start--> run--> enter services.msc. Check to see if Remote Procedure call and Windows Management Instrumentation service are running. If it is not, start both services, and then try to add a monitor to applications Manager. 5 Use WBEMTest to find error messages that occur when connecting to a remote system. Click Start--> Run--> WBEMTest
Open the Windows Management Instrumentation Tester, click the Connect button, and in the first text box (root\default), enter <\\hostname\root\cimv2>. Enter your username and password and click the Connect button. If you are prompted for an error, try entering an IP address at the host name, that is, if <\\ipaddress\root\cimv2> is normal, you can access the machine only through the IP address. This may be due to an error entry in the Hosts file in the <C:\Windows\system32\drivers\etc\hosts> file. Removes the error entry in the file and attempts to access it with a host name. 8. The monitor is not running. "Error Access denied" is always displayed. <OpManager> The WMI monitor is not running. Always show "error # Access Denied". The reason login authentication is incorrect. The solution performs the following steps: 1. Verify that the domain administrator username and password that are connected to the device are provided as indicated above. If the device is in a domain, the user name should be similar to the domain name \ Administrator name. 2. If the logon credentials specified in step 1
Correct, use the Resource Monitor-> to add a monitor-> a WMI based monitor-> available/used disk space (in MB/GB) to associate a WMI based monitor (preferably with a usable/used space graphic in MB/GB) to Exchang E Server. You should get a list of available drivers for your device at this time. 3. If step 2 fails, try enabling WMI, RPC services, and try again on the Windows system. 4. This problem may also occur if the DCOM settings are not configured correctly. You can cmd> CDs from the command prompt [opmanagerhome]\conf\application\scripts\ cmd> cscript Cpu.vbs [machinename] [domainname]\[ Username] [Password] When running the VBS script, this is determined by examining the exact error message. 5. You can also configure the DCOM settings in the following ways: From the Windows 2000 Server's run prompt, type \ dcomcnfg\ and expand the Component Services-> the tree under the computer. Click My Computer from the icon bar and select the default properties. Check the following: Enable distributed COM on this computer. Enable the COM Internet service on this computer. Select the default impersonation level as impersonation. If you want, you can also edit COM security settings. 6. If none of the above 4 steps resolve the issue, try changing the service login details as follows.
Go to the Windows service UI. Open the Properties dialog box for the Manageengineopmanager service. Go to the login page sign. In the Logon as option, select this account and enter the domain name \ Username and password that have access to WMI data. Save and restart the Opmanager. Note: This action will make the tray icon and startup picture disappear.
Two Use of Wbemtest test tools
1.
Tool Test. Use the WBEMTest tool to test.
1. Run >wbemtest on the monitor host, click Connect 2. The input in the namespace \ \ ip\root\cimv2 monitored is 3. Enter user name and password 4. See if the connection succeeded 2. Common errors and resolution (ELA) common errors and Solutions (ELA)
Access to the Deny code
Reason
Workaround Check that the login name and password you entered are correct
The logon name and password for the workstation provided by 0x80070005 are incorrect
Remote DCOM functionality for remote workstations is checked to see if remote DCOM is turned on. If it is turned on, open it with a prohibited face: Select Start > Run 1. 2.3. 4. Enter DCOMCNFG in the input box and click OK to select Default Property tab select the Distributed COM checkbox to open this machine click OK
Open the Windows XP host dcom:1. 2.3. 4. Select Start > Run enter DCOMCNFG in the input box and click OK click Component Services > Computer > My Computer Right click and select Properties
5. Select default Property page Sign 6. Select the Distributed COM checkbox to open this machine 7. Click to determine the remote host user account Invalid open command Line window to perform the following command to check whether the user account is valid: net use \\<remotecomputername>\c$/u:<domainname\use rname> "& Lt;password> "net use \\<remotecomputername>\admin$/u:<domainname \username>" <password> " If these commands display any errors, the target host provided
The user account is definitely invalid. The user name provided by 0x80041003 does not have sufficient privileges to perform a scan operation on the user group move the users to the Administrator. It is possible that the user does not enter the group of the workstation or scan the machine into this host's administrators section. Using an administrator (preferably a Domain administrator) account. 0X800706BA The remote host has a firewall configured. This feeling 1. To turn off the default firewall for Windows XP machines: Conditions are mainly in Windows XP (SP 2) 1. Select Start > Run to acknowledge that the firewall is open. 2. Enter firewall.cpl and click OK 3. In the usual page sign, click Close 4. Click OK 2. If the firewall cannot be opened, open I remote management on the remote host by executing the following command: After the netsh firewall set service remoteadmin Scan, you can turn off remote administration with the following command: netsh firewall set serv Ice remoteadmin Disable 0x80040154 1. WMI on the remote host is invalid. This situation appears on Windows NT. If the WMI component is not registered correctly, these errors may appear on a later version of Windows. 2. The WMI component is not registered.
1. Install WMI on the remote host. Can be downloaded from the Microsoft Web site. 2. Execute the following command to register the WMI DLL file: Winmgmt/regserver
0x80080005 this could be the WMI service that is running the WMI service to restart the remote host: (Winmgmt.exe) The host internal Error 1. Select Start > Run error. The last WMI warehouse on the host is 2 more. Enter services.msc and click OK to confirm the new failure. 3. In the Open Services window, select Windows Management Instrumentation service 4. Right-click and choose to restart more error codes, refer to MSDN Knowledge Base 3.
• • • • • • • • • •
Common errors and resolution (Opmanager) common errors and resolutions (Opmanager) 80070005 80041064 800706BA 80041010 80041003 80040154 80080005 8004106C 8004100E 80 041017 Access denied unable to use user credentials for local connection RPC server cannot use invalid class access denied not registered WMI component internal execution in WMI service WMI takes up too much memory invalid namespace invalid query
The error code and workaround are interpreted as follows: 80070005-access Denied cause this error occurs when the configured logon credentials are incorrect. Solution
•
• •
If the device is in the domain, ensure that the correct domain name, user name, and password are configured. If the device is in a workgroup, only the user name and password will be configured. For example, if the domain name is bigdom and the user name is admin, type bigdom\admin in the User name field. You do not have to specify a user name and password for a device that has access to a computer that is opmanager from the installation. If you still experience problems after you use the correct credentials, use the following steps to further resolve: O Check that the user account is valid on the target computer by opening a command prompt and executing the following command: NET use \\<monitored device name>\admin$/u : "< domain \ username >" < password > If this command throws an error, the supplied user account is not valid on the target computer.
O
Check that the workstation being monitored is
"Remote DCOM" is enabled. 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 Enable Distributed COM check box 5 on this computer. Click OK
To enable DCOM in the Windows XP host: 1. 2.3. 4.5. 6.7. Select Start > Run type dcomcnfg in the text box and click OK click Component Services > Computer > My Computer Right click and select Properties Select Default Properties tab Select the Enable Distributed COM check box on this computer click OK
If the above steps do not work, try changing the service logon details as follows:
• • • • • •
Go to the Windows service UI. Open the Properties dialog box for the Manageengineopmanager service. Go to the Login tab. In the Login as option, select this account. This configures the user name and password for an account that has access to remote computers. Save and then restart Opmanager. Try these 3 steps again.
Note: After making these changes, you will not find the tray icon and start picture.
80041064-the failure to use user authentication for local connection reason encountered this error when specifying the user name and password for monitoring the computer running Opmanager. The solution does not specify the user name and password for the local host. To resolve this issue, remove the configured user name and password from the password link in the device Snapshot page. 800706BA-RPC Server Unavailable Reason
This error is encountered when RPC and WMI services are not running and the device cannot be ping. Solution
• •
•
• •
Check to see if the device is started, running, and performing a ping operation. Check to see if Remote Procedure call (RPC) and Windows Management Instrumentation (WMI) services are running. 1. Choose Start > Run. 2. Type "Services.msc" in the text box and click OK. 3. In the services listed, view whether the status of the RPC and WMI services is displayed as started. 4. If not started, start these services. A firewall may be configured on the remote computer. When you enable the default Windows Firewall, this type of exception is most likely to occur in Windows XP (with SP 2). The steps to disable the default firewall on a Windows XP computer are as follows: 1. Select Start > Run. 2. Type firewall.cpl and click OK. 3. On the General tab, click Close. 4. Click OK. If you cannot disable the firewall, enable remote administration (for administrators) by executing the following command on the remote computer: The netsh firewall set service remoteadmin firewall may block WMI traffic. To access WMI traffic in a firewall, you need to open ports 445, 135 in the firewall.
80041010-Invalid class reason This error occurs when the required WMI class is not registered. Solution
• •
Check to see if the required applications are installed. Procedures for registering all WMI classes for an installed application. Run the following command: O for Windows 2000, run the "winmgmt/resyncperf" command from the device you are monitoring. O for Windows XP and 2003, run "wmiadap/f" from the monitored devices
Command.
80041003-Access Denied cause this error occurs when the supplied user name does not have sufficient access rights to perform the operation. Solution 1. This user may not belong to the Administrators group for this host computer. 2. Try to move the user to the workstation's Administrators group.
3. Trial administrator (preferably a domain administrator) account. 80040154-The WMI component is not registered cause this error is encountered when WMI in a remote Windows workstation is not available. This problem occurs in Windows NT. This type of error code can also occur in higher versions of Windows if the WMI component is not registered correctly. Solution
• •
Install the WMI core at the remote workstation. The WMI core can be downloaded from the Microsoft Web site. Register the WMI DLL file by executing the following command at the command prompt: Winmgmt/regserver install wmi:http://www.microsoft.com/downloads/details for Windows NT by downloading the following EXE .aspx?displaylang=en& Familyid= c174cfb1-ef67-471d-9277-4c2b1014a31e
•
Internal execution failure in the 80080005-WMI service occurs because of some internal execution failure in the WMI service (Winmgmt.exe) running on the host computer. The last update of the WMI repository in this workstation may fail. Solution Restart the WMI service in the remote workstation: 1. 2.3. 4. Choose Start > Run. Type services.msc and click OK. In the Open Services window, select the Windows Management Instrumentation service. Right-click and select Reboot
8004106c-wmi consumes too much memory causes this error to occur when WMI consumes too much memory. This may be caused by low memory availability or by WMI using too much memory. Solution
• •
WMI consumes too much memory. This may be caused by low memory availability or by WMI using too much memory.
•
Try restarting or reinstalling the WMI service.
8004100E-Invalid namespace reason namespace compiler invalid is not a normal error. Related applications that use namespaces may not be installed correctly. Solution
• •
Try reinstalling the application or WMI service individually. Use the log to contact http://support.opmanager.com.
80041017-Invalid query reason "Query is not syntactically valid" is not a normal error. Related applications that use namespaces may not be installed correctly. Solution
• •
Try reinstalling the application or WMI service individually. Use the logs to contact support personnel. For additional error codes, refer to the MSDN Knowledgebase.
