Remember, the Movere Console logs each task it performs and the responses it receives. Each task that the Movere Console is configured to perform is written to a separate Log.Service file:
Separate log service files allow the Console to perform multiple tasks simultaneously. These log files can be quickly merged into a single file from a command prompt using the command ‘copy Log.Service*.csv AllServiceLogs.csv’:
If you are having difficulty extracting data from a Server, the service logs can help diagnose the problem. The most common error messages include:
- The network path was not found: Movere cannot copy the inventory engine to the targeted endpoint. This could mean the endpoint is no longer on the network, a firewall is blocking access, the device is currently powered off, it is residing on a different network segment that cannot be accessed from the one Movere is being run from, or file sharing has been disabled. When this occurs, Movere will then attempt a remote WMI scan.
- The RPC server is unavailable: Similar to the network path not found error message above, the targeted endpoint is unavailable, i.e. no longer on the network, firewall blocking access, powered off, on a different network, or remote administration has been disabled.
- PING Failed: Similar to the error messages above, the targeted endpoint may no longer be on the network or a firewall is blocking ICMP traffic, prohibiting it from responding.
- Insufficient memory to continue the execution of the program: Movere leverages the .NET framework, which controls the resources it receives and the priority in which they are given. When the target endpoint has insufficient resources, instead of placing the endpoint under further strain, Movere terminates itself.
- Insufficient system resources exist to complete the requested service: Similar to the insufficient memory error, this typically means that the targeted endpoint has insufficient processing power to perform the requested tasks. Once again, Movere will terminate itself to avoid placing further strain on the system.
- Logon Failure: The target account name is incorrect: The user account being used has not been granted access to the targeted endpoint.
- Cannot open database ‘…’ requested by the login. The login failed. Login failed for user '…': Similar to the logon failure above, but specific to SQL. The user account Movere is using does not have the minimum read only access required to query the database.
- There is not enough space on the disk: Movere requires at least 5MB of disk space in order to deliver the inventory engine to the targeted endpoint. If there is less than 5MB available, then an insufficient disk space error will be received.
- An error occurred while connecting to SQL Engine '…\...' to retrieve a list of SQL databases. The SELECT permission was denied: The user account Movere is using can access Windows Server, but cannot access the SQL Server instance installed on it. Movere will still see the databases that are not in an ‘OFFLINE’ state, but without an awareness of each database’s state, they will all be returned with an ‘UNKNOWN’ state.
NOTE: ‘…\...’ will be the SQL Server \ Instance name Movere is attempting to connect to.
- The target database ('…') is in an availability group and is currently accessible for connections when the application intent is set to read only: Movere is attempting to query a high availability copy of a database residing in a SQL Availability Group that does not permit secondary read only access. In this configuration, Movere should be set to query the primary version of the database.
NOTE: ‘…’ will be the name of the database Movere is attempting to query.
- A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections: In most cases, the SQL Server instance on the targeted endpoint does not permit remote connections or the number of concurrent connections is limited and at the time the scan occurred there were no connections available.
Familiarizing yourself with these common error messages, and what they typically represent, will allow you to troubleshoot issues with your customer real time. We also recommend a preliminary scan targeting only a small number of systems to confirm that the user account(s) Movere has been given permission to use, has the required level of access to the systems being targeted. We also recommend testing the access Movere has been given against the customer’s IT asset management tool, if they have one in place, and it is one of the five Movere supports. Using this approach, you will:
- Confirm that Movere can access both Windows and SQL Server,
- Extract the data already collected by the customer’s existing IT asset management tool,
- Immediately give the customer access to data, so that they can begin familiarizing themselves with the visualizations on the Movere website; and
- Accelerate your progress as Movere will mark as inventoried any Windows systems it was able to extract the minimum amount of required data from. While Movere will by default target all of the customers Windows Servers, if the time available to complete the scans is very limited, then bringing in the customer’s own IT asset management data upfront could reduce scanning times by more than 60%.