A crucial step in troubleshooting inventory progress is to export the Active Directory Devices report and look through the Inventory Status outputs. We can then determine why certain devices have failed inventory, and how to remediate these devices. The following article will provide the most common errors encountered during typical inventory routines, what they mean, and how to resolve them. If you encounter an error that is not listed below, please contact support at our help centre.
Table of Contents
- Success
- Pending
- Access Denied
- Invalid Credentials
- Not in Scope
- No IP Address Returned by DNS
- Connection Timed Out/Unreachable/No Response From Host
- Not Detected
- WMI Error
- SMB Error
- RPC Error
- RREG Error
- Operation Cancelled
- SSH Port Closed
Inventory Status Messages
Success
We have successfully inventoried this endpoint.
Note: If this status is appearing while inventory is labelled Missing, we have successfully inventoried this machine on a previous attempt, but subsequent attempts at re-inventory were unsuccessful; the last successful attempt status was recorded, thus showing ‘success’.
Pending
The endpoint is currently queued for inventory. Once the inventory attempt for this device has been completed, this status message will change accordingly.
Access Denied
The credentials used to access this endpoint do not have the required level of permission.
Ensure a credential meets the following level of permissions is used: either a Domain Admin, a Service Account with access to SMB, RPC, WMI or a Local Admin with adequate remote capabilities.
Invalid Credentials
The credentials used to access this endpoint have been deemed invalid.
Ensure the username and password is correct, the domain is set in the domain field as opposed to the username field and ensure the credential meets the following level of permissions used: either a Domain Admin, a Service Account with access to SMB, RPC, WMI or a Local Admin with adequate remote capabilities.
Not in Scope
This error indicates an endpoint resides in a subnet that has not been added to the tool's inventory scope.
To resolve this error, please ensure the desired subnet scope includes all subnets that host machine IPs within or outside of the network.
No IP Address Returned by DNS
During an Active Directory inventory, our tool attempts to pull an IP address via the Device Name listed in the Active Directory by performing a reverse DNS lookup against the DNS. This can sometimes result in no returned address.
If the tool is able to locate the endpoint via network scanning of the subnets within scope, this error will disappear.
A DNS record may be missing due to the inactivity of the device, the device residing in a subnet outside of scope, an incorrect DNS entry for IP reservation or a DHCP release.
Connection Timed Out/Unreachable/No Response From Host
This indicates an issue between the host machine and the endpoint which prevents a stable connection. This can also be presented as "No Response From Host".
A network connection to the endpoint is required in order to perform inventory.
This issue can be caused by physical, VLAN or Network Firewalls. Ensure the desired endpoint is active and running. A ping test can be conducted in CMD on the host machine against the endpoint to test network connectivity.
Not Detected
This message indicates the endpoint has not been detected yet by the tool. Prior to the endpoint being submitted to the inventory queue, this status message may appear as the tool has not attempted to discover this endpoint.
This can be caused by an endpoint not being detected by our tool during an initial scan.
Ensure the endpoint is online and discoverable.
WMI Error
The tool does not have access to Windows Management Instrumentation or WMI for short.
Windows Management Instrumentation (WMI) is a set of specifications from Microsoft for consolidating the management of devices and applications in a network from Windows computing systems. WMI provides users with information about the status of local or remote computer systems.
Ensure the application and/or host machine can contact the endpoint via TCP 135 and that the Windows Management Instrumentation service is started on the desired endpoint.
We have a guide available to create a GPO that enables this network protocol here and a guide that references the ports used for inventory here.
SMB Error
The tool does not have access to Server Message Block or SMB for short.
The Server Message Block (SMB) protocol is a network file-sharing protocol that allows applications on a computer to read and write to files and request services from server programs in a computer network. The SMB protocol can be used on top of its TCP/IP protocol or other network protocols.
Ensure the application and/or host machine can contact the endpoint via TCP 445 and that file & printer sharing is enabled on the desired endpoint.
We have a guide available to create a GPO that enables this network protocol here and a guide that references the ports used for inventory here.
Note: Windows Server 2003 uses an unsecured version of SMB protocol v1 and cannot be inventoried in a typical fashion. Ensure that WinRM is allowed on the endpoint in order to achieve successful inventory.
RPC Error
The tool does not have access to Remote Procedure Calls or RPC for short.
A Remote Procedure Call is a software communication protocol that one program can use to request a service from a program located in another computer on a network without having to understand the network's details. RPC is used to call other processes on remote systems like a local system.
Ensure the application and/or host machine can contact the endpoint via TCP 139 & 1025 and that the Remote Procedure Call service is started on the desired endpoint.
We have a guide available to create a GPO that enables this network protocol here and a guide that references the ports used for inventory here.
RREG Error
The tool does not have access to Remote Registry or RREG for short.
Windows Registry contains information, settings, options, and other values for programs and hardware installed on all versions of Microsoft Windows operating systems. For example, when a program is installed, a new subkey containing settings such as a program's location, its version, and how to start the program, are all added to the Windows Registry.
RREG uses NetBIOS. Ensure the application and/or host machine can contact the endpoint via UDP 137 and that the Remote Registry service is started on the desired endpoint.
We have a guide available to create a GPO that enables this network protocol here and a guide that references the ports used for inventory here.
Operation Cancelled
This error message indicates an issue outside of ports and services as the operation was cancelled abruptly without denial of access. This can indicate third-party security software preventing the tool's inventory operations on the endpoint.
We have a whitelisting guide for popular security suites available here. While we attempt to provide the most up-to-date instructions for popular security suites, software releases frequently change without notice and hundreds of security software options are possible.
SSH Port Closed
This error indicates that the SSH port on the Linux endpoint is closed. We required access to SSH to inventory Linux endpoints without the use of an SSH Key.
This issue can be resolved by ensuring TCP 22 is open and accepting incoming traffic from the host machine's IP address.