-
WMI not working on newer Windows O/S (2008 Server R2)
I have an issue with wmic not working when my Pandora server is accessing a Windows 2008 server. For all servers running Windows 2003 Server wmic works fine.
The Windows 2008 servers all return the same message:
ERROR: WMI query execute
NTSTATUS: NT code 0xc002001b – NT code 0xc002001bThe exact same test command line is used in tests against 2003 and 2008 servers and the test against the 2008 server fails consistently with the aforementioned error.
Does anyone have any idea how to resolve this?
-
14 Replies
-
Which Version of WMI do you use? (wmic -V or wmic –version)
Can you post one of your wmi strings?
Can you please run this WMI query against a w2k8 Server: “SELECT LoadPercentage from Win32_Processor”additionally this post may help you: http://forums.pandorafms.com/index.php/topic,1250.msg14956.html#msg14956
-
-
Which Version of WMI do you use? (wmic -V or wmic –version)
Can you post one of your wmi strings?
Can you please run this WMI query against a w2k8 Server: “SELECT LoadPercentage from Win32_Processor”additionally this post may help you: http://forums.pandorafms.com/index.php/topic,1250.msg14956.html#msg14956
WMIC Version is 4.0.0tp4-SVN on Mint 14
As I indicted in the original post, WMI requests to Windows 2003 boxes work fine. The test below worked to a 2003 server but failed on the 2008 server.
wmic -U DOMAIN/user%pword //server “select caption from Win32 OperatingSystem”
It fails consistently on 2008 servers with NTSTATUS: NT code 0x002001b – NT code 0x002001b
To rule out security or firewall issues, I also tested wmic requests from Windows workstations and they worked fine with the same user.
-
Hello
I believe there is another issue going on here. Is the system a 64 bits system.
If it is the error is generated because the 64 bits agent won’t be launched till oficial release of version 5.1.Regards
IvoGreat to know the 64 bit agent is coming but I don’t think that’s the problem. I am using the WMI server so the Pandora agent on the Windows 2008 server wouldn’t be part of the problem.
-
Hello
The current agent executes all commands in a X32 powershell. While it needs to execute commands in a X64 powershell.
Can you try executing the X64 powershell and execute those queries in the powershell posting here the results.
We recomend the installation of a wmi explorer to make sure the queries exist in the machine.
The finest explorer is the Ka – Soft wmi explorer.Regards
Ivo -
-
-
Below is the wmic command line test with user and password removed.
wmic -U 212RESOURCES/% //and-winserv1 “select caption from Win32_OperatingSystem”Result from Windows Server 2008 machines:
ERROR: WMI query execute.
NTSTATUS: NT code 0xc002001b – NT code 0xc002001bResult from Windows Server 2003 machines:
caption from Win32_OperatingSystem”
CLASS: Win32_OperatingSystem
Caption|Name
Microsoft(R) Windows(R) Server 2003, Standard Edition|Microsoft Windows Server 2003 R2 Standard Edition|C:WINDOWS|DeviceHarddisk0Partition1 -
-
Below is the wmic command line test with user and password removed.
wmic -U 212RESOURCES/% //and-winserv1 “select caption from Win32_OperatingSystem”Result from Windows Server 2008 machines:
ERROR: WMI query execute.
NTSTATUS: NT code 0xc002001b – NT code 0xc002001bResult from Windows Server 2003 machines:
caption from Win32_OperatingSystem”
CLASS: Win32_OperatingSystem
Caption|Name
Microsoft(R) Windows(R) Server 2003, Standard Edition|Microsoft Windows Server 2003 R2 Standard Edition|C:WINDOWS|DeviceHarddisk0Partition1Some remote WMI queries fails and there is no way to know why :(. Could be due a network connectivity problem. Try to launch the same command 3-5 times. If works 1 of 5 is because a timeout or some kind of quota problem in the windows server end. But, thats not a solution, just a excuse to explain the problem is on the server side, not in the monitoring technology.
Anyway, the most secure way to obtain information is to install an agent in the server you want to monitor. WMI is well known for having this kind of problems, if you google for “NT code 0xc002001b” you will see all WMI remote monitoring software have exactly the same problem (because all WMI remote monitoring technology relief in the same wmi protocol and code), but in Pandora FMS you have a very powerful native software agents so you can solve this issue. Try it.
-
Remote queries to all Windows 2008 server fail consistently so this is not a network issue.
The agent is installed to the machine and I am finding that it will not correctly return the results of power shell scripts. The scripts return a single numeric value, however, the value is not returned to the Pandora server. This is why I resorted to remote WMI in the first place (not to mention the centralized configuration advantages).
-
-
As indicated in my previous posts, local and remote WMI queries work fine on all of the Windows 2008 servers when requested from other windows machines.
The Pandora server is the only box from which the WMI queries fail.
The Pandora server can only run WMI queries on Windows 2003 servers. The problem appears to be with the WMI client on the Pandora server.
Thanks
-
You can list the available aliases by using WMIC /? help. WMIC has a progressive help system. You can use /? at any time and at any depth to discover the additional options that are available in the current context. More about…WMIC Commands
Lee
