Troubleshooting issues with WMI
In order to detect a computer’s configuration, the
Octopus application uses the WMI (Windows Management Instrumentation)
components installed upon the computer to inspect.
Various errors may occur during the inspection
process. The table below lists potential errors and provides indications for
their resolution.
|
|
Please
note that the proposed explanations/resolutions are based upon experience
with WMI and that they are not necessarily the only possible ones for the
indicated errors. |
For more information concerning WMI, visit Microsoft’s
Website at the following address:
http://www.microsoft.com/whdc/system/pnppwr/wmi/default.mspx
|
Error
code returned by Octopus |
Meaning |
Explanation
/ Resolution |
|
Unknown Computer |
Unable to resolve the computer’s name into an IP
address. |
·
It is most likely that the
computer no longer exists. If such is the case, change its status to
“Retired”. ·
There is an error in the
computer’s name. ·
There is a technical problem. As
long as you are unable to perform a successful “nslookup”,
the problem will persist. |
|
Connection Timeout |
The computer’s name is recognized, but it is
impossible to connect to it. |
·
The computer is switched off. ·
The computer is not connected to
the network. ·
The computer belongs to another
network/domain which is not “visible” from the station from which the WMI
detect is being performed. In such case, the detection must be performed from
a computer within the same network. |
|
Access Denied |
Insufficient rights to inspect the computer. |
·
The NT account used to perform
the inspection does not have the rights required to perform the detection. We
recommend using a domain administrator account. |
|
RPC Error |
The computer has refused to establish an RPC
connection. |
·
The computer has an active
firewall. The installation of Windows XP SP 2 or of Windows Server 2003 automatically
activates a firewall. You must deactivate the firewall or configure it to
accept RPC connections. ·
The RPC service is deactivated or
is malfunctioning. |
|
Invalid Class Name |
Internal WMI error. |
·
The installation of WMI is faulty
on the inspected computer. Verify the installation of WMI. ·
The default installation of
Windows Server 2003 does not include WMI components. Manually install these components. ·
Windows 95/98/NT does not include
WMI components. Manually
install these components. |
|
Reading Timeout |
The inspection has exceeded the maximum delay. |
·
The inspected computer was unable
to provide its configuration within the expected delay. The computer is too
busy to process the request or a technical problem prevents it from
completing the inspection. |
|
Unknown error |
An unexpected error has occurred during inspection. |
·
A technical problem with the
inspected computer prevents completion of the inspection. |