Is your error not listed below or want a further explanation? Contact support@infrasightlabs.com and they’ll help you out.
Common WMI errors
| Error | What happened? | Suggested action |
| Recently scanned by WMI through another IP. Delaying scan. | The WMI target was recently scanned with a different WMI credential and was put furthest back in the queue. | Make sure the target machine has been scanned with WMI. |
| Access is denied. | vScope was unable to login to the target machine with WMI/WinRM using a WMI credentials. | Ensure the WMI credential has permission to remotely login to the target machine. |
| The RPC Server is unavailable | vScope cannot use the RPC service which is required to inventory the target machine. | Troubleshoot with: https://support.vscope.net/wmi-troubleshoot-rpc-server-is-unavailable/ |
| WinRM Login failed: HTTP: 401: Unspecific Access Denied | Most commonly combined with WMI succeeding. vScope not able to login to the target machines using WinRM. | Ensure the correct credentials are used. |
Common MS SQL errors
| Error | What happened? | Suggested action |
| Connection refused: connect | vScope could not connect to the database, | Ensure that the vScope server can communicate with the database and that the correct ports are used. |
| No valid credentials: [Login timed out.] | vScope could not login. | Ensure that the credential have access to the database. Is the credential using the recommended format "domain\..."? |
Common HTTP errors
| Error | What happened? | Suggested action |
| No response | vScope did not get a response on port 80, 8080, 443 or 8443. | Are you expecting vScope to find a web certificate on this target? Is the certificate using a different port? |
Add ports to the HTTP credential:
https://support.vscope.net/specify-ports-for-certificate-scanning/
Common SMI-S errors
| Error | What happened? | Suggested action |
| Connection refused | The SMI-S probe was unable to inventory the storage. | Ensure that the credential is using the correct port and that the vScope server can communicate with the target. |
| No response: Connect timed out | The connection timed out. | Ensure that the credential is correct and that it uses the correct port. |
Common SNMP errors
| Error | What happened? | Suggested action |
| No response: Connection timed out | The SNMP credential was unable to connect to the target. | Make sure that the correct SNMP version and port are being used for the target. |
Common VMware errors
| Error | What happened | Suggested action |
| No response: VDI SDK invoke exception:java.net.SocketTimeoutException | The VMware credential was unable to connect/did not find the vCenter. | Make sure the credential is using the correct port and that the server can communicate with the target. |
Common Azure RM errors
| Error | What happened? | Suggested action |
| Failed to retrieve... | vScope was not able to retrieve data using the specified API endpoint. | Confirm that the vScope azure application has the correct API permissions. |
How to set up Azure RM:
https://support.vscope.net/setting-up-discovery-of-azure-resource-manager/
Related articles
