Managing Devices The Devices view provides many details about an individual device or groups of devices From
ERROR_NO_NET_OR_BAD PATH
The network path was either typed incorrectly, does not exist, or the network provider is not currently available. Target machine or domain is not found or does not exist (it may have been entered incorrectly or not connected to prop- erly).
You can try to retype the path or contact your network admin- istrator.
Error Code Description Solution
device. The information that the agent device is trying to collect may not be supported.
be configured properly. It is recommended that you make sure you have the proper cre- dentials assigned to the device. OR Device cannot provide the information requested. Check to see that you are col- lecting the right type of infor- mation from the right type of device. For example, you cannot collect fan speed, CPU temp, or mem- ory from a printer. notImplemented When you use Internet Explorer on your Win-
dows XP-based computer to try to view a web page, you may receive an error message. This issue may occur if either of the following con- ditions exist:
l A third-party product is interfering with
Internet Explorer.
l The HTTP 1.1 setting is enabled.
Check to see if SNMP was con- figured prop- erly. OR Device cannot provide the information requested (same as
Error Code Description Solution
l SNMP monitoring similar to nosuch-
name.
NoSuchName). Check to see that you are col- lecting the right type of infor- mation from the right type of device. For example, you cannot collect fan speed, CPU temp, or mem- ory from a printer. OR Contact Support RPC_E_SERVERCALL_RETRY- LATER
Call was rejected by callee. You may see this error if you are automating Excel through the COM interface, or implementing an RTD server and calling UpdateNotify from a dif- ferent thread. The error is raised when Excel is not ready to handle your call - for example, if the user is busy editing a cell or pressing the mouse button. This error occurs when the server is heavily stressed. For example, when PacketTrap MSP is trying to collect data for active directory, exchange, SQL server per- formance counters while the target machine is under load.
It is rec-
ommended that you install an agent on the tar- get machine instead of mon- itoring devices using WMI (remote mon- itoring).
ServiceUnavailable The Web server (running the Web site) is cur- rently unable to handle the HTTP request due to a temporary overloading or maintenance of the server. The implication is that this is a tem- porary condition which will be alleviated after some delay. Some servers in this state may also simply refuse the socket connection, in
Check to make sure that the software is run- ning.
Error Code Description Solution
which case a different error may be generated because the socket creation timed out. Also, when the target application or software is not running.
TimedOut or Timeout A remote device is very slow to respond to a request. For SNMP, this error may be caused by assigning the incorrent credentials to the device.
Check the cre- dentials and make sure the devices have enough memory or power to respond quickly. OR Connectivity may be slow. TtlExpired TTL expired in transit. The TTL value deter-
mines the maximum amount of time an IP packet may live in the network without reach- ing its destination. It is effectively a bound on the number of routers an IP packet may pass through before being discarded. This message indicates that the TTL expired in transit. Also, if there was an attempt to ping the device with a smaller TTL value.
Open the Policy Editor to
increase the TTL value set for the Ping monitor.
usmStatsUnknownUserName s
The total number of packets received by the SNMP engine which were dropped because they referenced a user that was not known to the SNMP engine.
Check to make sure that you have the correct SNMP cre- dential assigned.
WBEM_E_NOT_FOUND When you try to open a Windows Management Instrumentation (WMI) namespace on a com-
If a firewall is blocking access
Error Code Description Solution
puter that is running Windows Server 2003 Service Pack 2 (SP2), you receive this error code. This issue occurs because the WMI repos- itory is corrupted. The WMI service does not handle an item deletion operation for the WMI repository correctly. Therefore, the index tree of the WMI repository is corrupted, and the error code that is mentioned in the "Symp- toms" section occurs when you try to open a namespace. Also, firewall may be blocking access to WMI.
to WMI, add the WMI names- pace to the fire- wall exclusion set.
OR
Make sure that WMI services is running in the Windows serv- ice manager.
Viewing the Details of a Device
The main devices page provides a quick summary about your device. You can drill-down to the details page to see more information about a device.
To view the device details
1. In the PacketTrap MSP Studio, select a device on the Devices main page. 2. Double-click it to view its details, as shown in the following image: