# Troubleshooting common data collection errors
All possible error messages (for all protocols) for issues with data collection have been listed below. Click any message under a protocol to view why that error might have occurred, and how to resolve it.
If you don't find your error listed here, or if you need any assistance with OpManager in general, please get in touch with our support team at [opmanager-support@zohocorp.com](mailto:opmanager-support@zohocorp.com).
## Error Messages by Protocol
| Protocol | Error message |
|---|---|
| [SNMP](#snmpd) |
- [Request Timed Out](#snmp1)
- [Null variable in response](#snmp2)
- [IO error sending PDU. Send Error: Session Remote Host Unknown](#snmp3)
- [There is no such variable name in this MIB.](#snmp4)
- [No Error code registered](#snmp5)
- [This is a end of MIB View.](#snmp6)
- [There is no such object in this MIB.](#snmp7)
- [Session Remote Host Unknown](#snmp8)
- [There is no such instance in this MIB.](#snmp9)
- [A no access error occurred](#snmp10)
|
| [WMI](#wmi) | - [The RPC server is unavailable](#wmi1)
- [Access is denied](#wmi2)
- [Specified class is invalid / Invalid Class Error](#wmi3)
- [Query was not syntactically valid.](#wmi4)
- [Empty response received from device](#wmi5)
- [No WMI Credentials associated to the device](#wmi6)
- [Problem in collecting/processing data from the device](#wmi7)
- [The remote procedure call failed](#wmi8)
- [Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk.](#wmi9)
- [Call was canceled by the message filter](#wmi10)
- [Server execution failed](#wmi11)
- [Unspecified error / Null](#wmi12)
- [Not enough storage is available to complete this operation](#wmi13)
- [WMI is taking up too much memory.](#wmi14)
- [No more threads can be created in the system](#wmi15)
- [User credentials cannot be used for local connections](#wmi16)
|
| [CLI](#cli) | - [No CLI Credentials associated to the device](#cli1)
- [Script execution failed: timed out](#cli2)
- [Communication not established: Socket error](#cli3)
- [Unable to establish CLI Connection to the device](#cli4)
- [Exception during logging in or Incorrect Login Parameters](#cli5)
- [No data received from the device](#cli6)
|
| [HyperV](#hyper-v) | - [Credential Failure](#hyperv1)
- [Configuration data missing](#hyperv2)
- [Empty response received from device](#hyperv3)
- [Reporting server info is not available](#hyperv4)
- [Problem in collecting data from this entity](#hyperv5)
|
| [VMware](#vmware) | - [Problem in collecting data from this entity](#vmware1)
- [Unable to establish a session with the device](#vmware2)
- [Service content is not available](#vmware3)
- [Host system details not found](#vmware4)
- [Unable to get hardware related metrics](#vmware5)
- [Counter value is not available](#vmware6)
- [Unable to fetch data due to host communication failure](#vmware7)
- [Unable to fetch metrics data](#vmware8)
- [Reporting server info is not available](#vmware9)
- [Older way of monitoring is being used](#vmware10)
- [vSphere not returning data for this entity](#vmware11)
- [Hardware stats polling failed for device](#vmware12)
|
| [Hypervisor (Xen)](#xen) | - [Reporting server info is not available](#xen1)
- [UUID is empty](#xen2)
- [Problem in collecting data from this entity](#xen3)
- [No response received from Xen API](#xen4)
- [No response from Xen API for host data source](#xen5)
- [No response from Xen API for VM data source](#xen6)
|
| [Nutanix](#nutanix) | - [Reporting server info is not available](#nutanix1)
- [Problem in collecting data from this entity](#nutanix2)
- [No response received from Prism API](#nutanix3)
- [Cluster Response Object Is Null](#nutanix4)
- [Host Response Object Is Null](#nutanix5)
- [VM Response Object Is Null](#nutanix6)
|
| [UCS](#ucs) | - [Problem in collecting data from this device](#ucs1)
- [No UCS Credentials associated to the device](#ucs2)
- [Credential failure](#ucs3)
- [No data received from the device](#ucs4)
|
| [Hardware](#hardware) | - [SNMP response not received](#hardware1)
|
| [URL](#url) | - [Connection timed out](#url1)
- [Host Unknown](#url2)
- [Host Unavailable](#url3)
- [403 Forbidden](#url4)
- [400 - Bad request. The request could not be understood by the server due to malformed syntax. The client should not repeat the request without modifications.](#url5)
- [503 Service Unavailable](#url6)
- [302 Redirection](#url7)
- [301 Redirection](#url8)
- [401 Unauthorized](#url9)
- [500](#url10)
|
| [Script](#script) | - [Credentials are not given for the device](#script1)
- [Internal Server Error while processing this request](#script2)
- [ScriptExecutionException](#script3)
- [Configure the device type for the device.](#script4)
- [For Windows machines scripts cannot be executed remotely](#script5)
- [TimeoutException](#script6)
- [Polling has failed](#script7)
- [CommandLine syntax is incorrect](#script8)
- [CommandLine should contain ${FileName} variable](#script9)
|
| [Interface](#interface) | - [Error in response. There is no such variable name in this MIB. Index: 1 Errored Object ID: OID](#interface1)
- [Error: Request Timed Out](#interface2)
- [Snmp Request send failed. Invalid request ID obtained for interface INTERFACE_NAME \| ErrorCode : ERROR_CODE \| ErrorString : ERROR_STRING](#interface3)
|
**Disclaimer:**
The troubleshooting steps mentioned below might include some actions to be done outside of the OpManager environment. Please perform them at your own risk and exercise due diligence when executing them in your network. It is highly advised to consult your system and network administrators with the necessary troubleshooting measures before you proceed with performing them.
---
## SNMP
### `Request Timed Out`
This error might be displayed due to the following reasons:
1. Wrong credentials/Wrong community name
2. The SNMP agent in the monitored device is unable to respond to OpManager's requests within 5 seconds (the default timeout)
3. Device is unreachable
4. Port is not available
**Steps to troubleshoot this issue:**
1. Check if the right credentials and the community name have been provided.
2. For point 2, increasing timeout will resolve this issue. You can add a new credential profile with increased timeout value for that device.
3. Also check if the device is reachable and if the corresponding port is available in the device.
---
### `Null variable in response`
This error might be displayed when the response from the MIB OID associated with that monitor is getting a "Null" response from the end device.
**Steps to troubleshoot this issue:**
You can perform an SNMP walk on the device (using SNMPwalk tool or any other third-party tool) and check the response from the corresponding OID.
---
### `IO error sending PDU. Send Error: Session Remote Host Unknown`
This error might occur due to the following reasons:
1. IP Address/DNS name not resolved
2. Port is not open
**Steps to troubleshoot this issue:**
1. Check the device by performing an SNMP walk.
2. If there are issues with DNS, resolve them and make sure the port is available.
---
### `There is no such variable name in this mib.`
The SNMP Agent does not support the MIB.
**Steps to troubleshoot this issue:**
1. You can perform an SNMP walk on the device and check the corresponding OID.
2. If the response is proper but you're still encountering this issue, [please contact our support team](mailto:opmanager-support@zohocorp.com) with logs and required screenshots.
---
### `No Error code registered`
This is the default value of error code. This is to indicate that no error code has been registered.
**Steps to troubleshoot this issue:**
1. Since no proper error code has been registered, you can check the OID response in the MIB browser or through an SNMP walk.
2. If the response there is proper or if any other error messages are displayed, [please contact our support team](mailto:opmanager-support@zohocorp.com) with logs and required screenshots.
---
### `This is a end of MIB View.`
If a getBulk/getNext operation is running and the OID selected is the last node of the MIB, this error will occur. This might be due to internal configuration issues.
**Steps to troubleshoot this issue:**
To identify the cause of this issue and troubleshoot it, [please contact our support team](mailto:opmanager-support@zohocorp.com) with the logs, MIB/OID details and required screenshots.
---
### `There is no such object in this MIB.`
It denotes that the added MIBS have not been implemented in the device.
**Steps to troubleshoot this issue:**
1. Use the SNMP walk command to check if the MIB is correct.
2. It is recommended to contact the vendor and get the necessary MIBs and then create custom monitors.
---
### `Session Remote Host Unknown`
This error might occur due to the following reasons:
1. IP Address/DNS name not resolved
2. Port is not open
**Steps to troubleshoot this issue:**
1. Check the device by performing an SNMP walk.
2. If there are issues with DNS, resolve them and make sure the port is available.
---
### `There is no such instance in this MIB.`
It denotes that the added OID instance has not been implemented in the device.
**Steps to troubleshoot this issue:**
1. Check the corresponding OID with an SNMP walk.
2. If you don't receive a response, please contact the concerned vendor about this.
3. It is recommended to contact the vendor and get the necessary MIBs and then create custom monitors.
---
### `A no access error occurred`
This error occurs if the OID that you are trying to set a value to, has no read/write access.
**Steps to troubleshoot this issue:**
1. Check it with the SNMP walk command.
2. Also, check the user access in SNMP configuration if you provided the necessary privileges.
3. If these two points are satisfied and you still encounter the same issue, [please contact our support team](mailto:opmanager-support@zohocorp.com) with necessary logs.
---
## WMI
### `The RPC server is unavailable`
This error is encountered when the device is not reachable, or RPC/WMI service is not running.
**Steps to troubleshoot this issue:**
Refer this KB to troubleshoot this RPC unavailability issue:
https://www.manageengine.com/network-monitoring/kb/troubleshooting-rpc-server-unavailability.html