Online Help | Network Inventory

Audit Troubleshooting

Here you can see the short list of common issues causing the audit failures:

  • ClosedComputers and devices are offline

    All the Network Nodes you are trying to discover / audit have to be available on a Network (online, turned on, etc.). You can ping a Computer or Device to make sure it is responding correctly. If it is not corresponding, there must be a problem with its configuration.

  • ClosedAudit credentials do not allow administrative access

    The audit credentials used for the Direct Network Scan must correspond to a user account that is a member of the local Administrators group on each Windows client machine (through the membership in a Windows domain group or directly).

    For details, see Managing Audit Credentials.

  • ClosedLocal audit account does not exist

    If you use a local account for the Direct Network Scan of Windows computers,Network Inventory requires that this account belongs to the local Administrators group and exists on every client computer you want audited. For details, see Managing Audit Credentials.

    Even when the requirements are met, however, the Direct Network Scan under a local audit account sometimes may fail with the following error message:

    Failed: Error connecting to host (Error: 1312. A specified logon session does not exist. It may already have been terminated).

    To workaround this issue, on the Automation Server computer, create the local account that you use for the Direct Network Scan, and add this account to the local Administrators group.

  • ClosedAdministrative shares are disabled

    The Direct Network Scan Audit of a Windows computers relies on the hidden administrative share (ADMIN$) that Windows uses to manage the computer environment on the network. Some administrators consider administrative shares to be a security risk and disable them completely. Make sure the administrative shares of a Windows computers are enabled. Moreover, you may experience a variety of other issues unrelated to Alloy Navigator Express when administrative shares are removed or are otherwise missing from your computer.

    For details and resolution, see Microsoft Knowledge Base article Overview of problems that may occur when administrative shares are missing.

  • ClosedClient for Microsoft Component is disabled on the Automation Server

    On Automation Server running Windows XP / Windows Server 2003 or later, you are unable to remotely audit computers when the Client for Microsoft Networks component and Workstation service is not installed and configured.

    1. Make sure that the Client for Microsoft Networks component is installed and enabled.

    2. The Client for Microsoft Networks component corresponds to Windows network service Workstation. Configure and start the Workstation service.

  • ClosedWindows firewall and third-party firewall products are enabled

    Enabled firewall may block access to the remote connection. By default, Windows Firewall closes the ports that are used for file and printer sharing to prevent Internet computers from accessing your shared files and printers. Third-party firewall products may also employ this approach.

    If you are using a firewall, open the ports that are used by File and Printer Sharing for your local network to enable the audit.

    For details and resolution, see Microsoft Knowledge Base article Internet firewalls can prevent browsing and file sharing.

  • ClosedUser Account Control (UAC) is enabled

    UAC enables users to perform common tasks as non-administrators, and as administrators without having to switch users, log off, or use Run As. UAC also affects remote connections to computers. When a local user account is used to connect to a machine, the user is identified as a standard user even if the account is in the Administrators group. Since regular users do not have administrative rights, the audit fails.

    The method of solving this issue depends on whether you are connecting to a remote computer in a domain or in a workgroup, since this determines whether UAC filtering is enabled. For detailed information about disabling UAC, see Administration Guide: Troubleshooting the Direct Network Scan.

  • ClosedNetBios is disabled (Network connection properties)

    Disabled NetBIOS in the network connection properties may lead to the different connection errors (i.e. "No such host is known"). Check this in Network connection properties > Internet protocol (TCP/IP) > Properties > Advanced > Wins tab on the nodes producing the same or similar error when audited.

  • ClosedSSH daemon is disabled for Mac

    The Apple Mac OS X has SSH installed by default but the SSH daemon is not enabled. In this case you can not connect remotely. To enable it, go to System Preferences. Under Internet & Networking, run the Sharing icon. In the appeared list, select the Remote Login option. The SSH daemon starts immediately. You can remotely login with your user name and password.

  • ClosedIncorrect SSH protocol configuration for Linux and Mac

    The Direct Network Scan of Linux and Mac computers establishes connection to the audited computers using the Secure Shell protocol (SSH). By default,Network Inventory accesses client Linux, Mac computers and Linux-based hypervisors (VMware ESX, Xen, and Citrix XenServer) over the standard TCP port 22. However, when the SSH server on your client computers listens on a non-standard TCP port, you can specify another port number when providing audit credentials for the Audit Source or for particular computers.

    For details, see Managing Audit Credentials.

    Make sure that each client Linux and Mac computer has the SSH server running and listening on the TCP port. Otherwise, the Direct Network Scan will fail.

    If you connect to Linux and Mac computers using your SSH private key instead of a password, make sure the SSH public/private key pair is properly set up and the public key is uploaded to all Linux and Mac computers you want to audit. For more information on SSH public key authentication, you can refer to the following Web address:

  • ClosedExtended hardware information is not collected on Linux

    In order to access low-level hardware information (hardware serial numbers and asset tags) from a Linux system during the Direct Network Scan, the user account used for auditing the system must have root privileges. For details, see Linux and Mac Audit Credentials.

    Some administrators consider providing credentials for the root account a security risk. You can configure the Direct Network Scan to collect extended hardware information using audit credentials for a non-root account. For instructions, see Administration Guide: Linux and Mac Direct Network Scan.

  • ClosedWindows Remote Management 2.0 is missing

    The Direct Network Scan of VMware ESXi hypervisors requires that the computer hosting the Automation Server instance has Windows Remote Management (WinRM) 2.0 or later installed. This component is also required for VMware ESX hypervisors when they do not have the SSH server running and listening on the dedicated TCP port.

    WinRM 2.0 component is included in Windows 7 and Windows Server 2008 R2. Windows 8, Windows 8.1, Windows 10, Windows Server 2012, and Windows Server 2012 R2 include WinRM 3.0. If your Automation Server instance is installed on a computer running Windows XP Professional, Windows Vista, Windows Server 2003, Windows Server 2003 R2, or Windows Server 2008, install the Windows Management Framework Core package, which includes WinRM 2.0 and Windows PowerShell 2.0. To download the appropriate update from the Microsoft Download Center, see Microsoft Knowledge Base article Windows Management Framework Core package (Windows PowerShell 2.0 and WinRM 2.0).

  • ClosedThe WS-Management service is not running on VMware ESXi 6.5

    The Direct Network Scan of VMware ESXi 6.5 requires the WS-Management service running on an ESXi host. On a newly installed ESXi 6.5, this service is turned off by default. To turn on the WS-Management service, enter esxcli system wbem set -e 1 on the command line and press Enter.

  • ClosedOther issues

    • You are not allowed to use blank passwords for the audit credentials. Windows XP SP2 and higher will deny access under account with blank password. For details, see Managing Audit Credentials.

    • There should not be DNS issues related to the name of the Network Inventory application host machine or the IP address of the client machine. For example, the name of the DNS entry for the Network Inventory application host machine must match its computer name, and the IP address of the client machine must be unique within the DNS.

In case of any discovery or audit operation failures, system shows the corresponding messages in the status column.

Status Description


Indicates that a process within a task was canceled by the user. Applicable for an operation within a task or the whole task.


Indicates that the operation for the same Network Node was invoked by multiple tasks at the same time. One task is automatically assigned to perform the operation and all the identical operations for this Node were skipped.


Indicates that the Computer was not detected during discovering or the Direct Network Scan Audit was not able to be performed.

Not Loaded

Indicates that the Automation Server was stopped or restarted when audit data upload and was not able to complete the operation.

Not Found

Indicates that the specified Network Node was not found by the specified IP address or in the shared folder.


Indicates that the error occurred during audit data upload to the database.


Indicates that within a defined task, a Computer having the identical IP address had already been audited.


Indicates that a process within a task was forcefully interrupted before the operation was completed.


Indicates that the specified Network Node was excluded from the inventory operations of the specified Site.


Indicates that conflict occurred during audit data upload to the database.

For additional information on troubleshooting the audit, see Administration Guide: Troubleshooting. You can obtain the most up-to-date documentation via the Alloy Software Product Documentation.

For the unresolved failures you can contact with the Alloy Software technical support or use the community forums.