Error Message Troubleshooting

Movere returns error messages directly from the system(s) being scanned, as well as from the Movere service and cloud. There are two different types of error messages return during Movere scans. The first part of an error message string comes directly from Movere, and often relates to the success of accessing and scanning the target devices. The second part of an error message comes directly from the device/system being scanned, such as a Windows, SQL Server, or Linux error message. The most frequently seen error messages are outlined below..

Movere Error Codes:

System Error Messages:

Error:
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. (provider: Named Pipes Provider, Error: 40 - Could not open a connection to SQL Server)
Issue:
If workgroup, device name is not recognized by SQL. If tied to a domain, TCPIP connections are not enabled (Movere does not connect over named pipes).
Solution:
Enable TCPIP connections if machine is connected to a domain; for workgroup machines, follow guidance from” https://support.movere.io/hc/en-us/articles/360001804648-Scanning-Windows-Workgroup-Servers
 
Error:
An error has occurred while copying bot to Admin$.; Exception message: Access to the path '\\[devicename]\Admin$\Temp' is denied.
Issue:
User account being leveraged against the target machine does not have Local Admin rights to the target machine.
Solution:
 Re-run the scan using a Local Admin account.
 
Error:
An error has occurred while copying bot to Admin$. Attempting C$ now; Exception message: The network path was not found.
Issue:
User and/or machine running the console does not have rights to connect to the target machine.
Solution:
Attempt scans using different credentials that are confirmed to have access to the target machines, and/or run scans from a machine that can connect to the target machines.
 
Error:
An error has occurred while copying bot to Admin$.; Exception message: Access to the path '\\[devicename]\Admin$\Temp' is denied.
Issue:
User account being leveraged against the target machine does not have Local Admin rights to the target machine.
Solution:
Re-run the scan using a Local Admin account.
 
Error:
An error has occurred while copying bot to Admin$. Attempting C$ now; Exception message: The network path was not found.
Issue:
User and/or machine running the console does not have rights to connect to the target machine.
Solution:
Attempt scans using different credentials that are confirmed to have access to the target machines, and/or run scans from a machine that can connect to the target machines.
 
Error:
An error has occurred while copying bot to C$; Exception message: The network path was not found.
Issue:
User and/or machine running the console does not have rights to connect to the target machine.
Solution:
Move the console to a different machine that has confirmed connectivity to the target machines, or use credentials from a user account that has permission to access the C$ drive on the target machines.
 
Error:
Remote Scan Error; Exception message: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
Issue:
Indicates that Movere is trying to scan using the FQDN name of the target machine and cannot successfully scan, and thus is defaulting to a remote connection and failing as well.
Solution:
Attempt to scan the target machine using either the short name or IP address.
 
Error:
Does not resolve in DNS
Issue:
DNS entry for the target machine is corrupt or inaccurate.
Solution:
Scan by short-name or IP address to get around any DNS entry issues
 
Error:
Unable to copy files; Exception message: The specified network name is no longer available
Issue:
Movere cannot connect to the target machine, due to loss/closing of network connections or the target machine is powered off
Solution:
Ensure the target machines is powered on during the scan and that the machine itself is still accessible, (i.e. it has been disabled or removed from the network).
 
Error:
An error occurred while retrieving Windows Services; Exception type: System.NullReferenceException; Exception message: Object reference not set to an instance of an object
Issue:
Indicates that Movere has tried to return Windows services information, but cannot do so successfully because the registry is corrupted, which return a WMI errors. Often seen due to incorrect user permissions or issues with scanning Windows 2008 UAC.
Solution:
Check the registry on the target machine and rebuild if necessary before re-scanning with Movere.
 
Error:
PING Failed
Issue:
Connectivity is not present; can occur between console and target machine, target machine and cloud, and/or console and Movere cloud.
Solution:
Confirm the machine running the console, and the user accounts(s) being leveraged during the scanning, has connectivity to and can access the target machines, as well as the Movere cloud.
 
Error:
Error connecting to SQL; Exception type: System.Data.SqlClient.SqlException; Exception message: Login failed for user 'sa'
Issue:
Indicates that the "sa" account does not have the correct permissions to access the SQL database(s)
Solution:
Ensure the 'sa' account has db_datareader access to the target databases, as well as ConnectSQL and View Server State enabled. Otherwise, leverage a different account that has these permissions.
 
Error:
Error The remote server returned an Error: (412) Precondition Failed.; Exception message: The remote server returned an Error: (412)
Issue:
Indicates that the Movere console and/or bots cannot access the Movere cloud, which can occur due to network connectivity issues, port 443 is blocked or unavailable, and/or the upload URLs in the bot config files is inaccurate.
Solution:
Download a new copy of the Movere console, as well as a new token.txt file, and attempt to rescan once more.
 
Error:
Movere Cloud Host Ping:   PING Failed
Issue:
Indicates that the console and/or bots cannot access the Movere cloud, likely due to no internet connection on the endpoints, or port 443 is blocked.
Solution:
Ensure internet connections are enabled on the target machines, and that port 443 outbound is opened. If not uploading directly from the target machines, ensure the console machine can connect to the internet over port 443.
 
Error:
The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.; Exception message: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
Issue:
Indicates that the machine you are uploading from does not support TLS 1.2, (which is required to upload Movere data), or that any whitelisting has expired and Movere is no longer trusted within the environment.
Solution:
Either update the machine used for uploading to TLS 1.2, or upload the data from a different machine that does support TLS 1.2. Alternatively, check any whitelisting policies for Movere and ensure they are active. https://support.movere.io/hc/en-us/articles/360011696673-Movere-URLs-and-IP-Addresses-for-Whitelisting
 
Error:
Connecting to remote server ps.outlook.com failed with the following error message : WinRM cannot complete the operation. Verify that the specified computer name is valid, that the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet. For more information, see the about_Remote_Troubleshooting Help topic.
Issue:
Indicates that there is a Windows Rights Management policy or feature in place that prevents Movere from successfully connecting to the Office 365 subscription.
Solution:
Move the Movere console, including all config files, to a workstation and re-run the scan from there. Workstation-based O365 scans often do not encounter WinRM policies and will run successfully.
 
Error:
Error The operation has timed out; Exception message: The operation has timed out
Issue:
Indicates that the connection between the device uploading a payload to Movere and Movere's cloud has timed out or been severed.
Solution:
his is commonly seen when network connections are terminated or the bandwidth is not sufficient to upload the file. To resolve, attempt to manually upload the payload from a different machine and/or network connection.
 
Error:
Unable to retrieve perf counter details for winlogon, Category does not exist.
Issue:
Indicates that a device's performance counters are corrupted in some way
Solution:
The best thing to do is to work with the customer to access this server and check the performance counters, and rebuild them if possible. If Movere cannot access the counters, ARC scans will not be able to return performance data.
 
Error:
The requested security protocol is not supported.
Issue:
Indicates that the machine you are uploading from does not support TLS 1.2, which is required to upload Movere data.
Solution:
Work with the customer to either update the machine used for uploading to TLS 1.2, or upload the data from a different machine that does support TLS 1.2.
 
Error:
An error occurred while retrieving IIS details.; Exception type: System.Runtime.InteropServices.COMException; Exception message: The object identifier does not represent a valid object.
Issue:
Indicates that Movere is attempting to scan an IIS datapoint, but it is unable to access or emulate this component. This error explains that Movere has checked if IIS is installed and seen a likely IIS component, but the component is not actually installed or Movere cannot access the data.
Solution:
Work with the customer to either update the machine used for uploading to TLS 1.2, or upload the data from a different machine that does support TLS 1.2.
 
Error:
Could not check whether Arc2 process is running; Exception message: No such interface supported
Issue:
These errors arise when a new ARC scan is attempting to identify if ARC is already running on the target machine, (in order to terminate the previous scan), but Movere cannot due to an access issue to the service list or target machine.
Solution:
This error will not impact the new ARC scan from running. The same message will be thrown for Arc4 processes.
 
Error:
An error occurred while accessing user security logs; Exception type: System.IndexOutOfRangeException; Exception message: Index was outside the bounds of the array
Issue:
Indicates that the length of the security logs has exceeded the limit that Movere can query. This is commonly seen for domain controllers and/or customers that are not using a GPO to limit length of the security log.
Solution:
This only impacts collection of log data and does not hinder the rest of the scan. To collect this log data, work with the customer to clean up or limit the length of the security log and rescan with Movere.
 
Error:
An error occurred while retrieving Windows Features details.; Exception type: System.Management.ManagementException; Exception message: Generic failure
Issue:
Notes that Movere was unable to access, view, or scan a specific IIS datapoint.
Solution:
This error does not impact the broader inventory or ARC scanning of these machines, and this data is not currently visible on the Movere website.
 
Error:
An error occurred while parsing XML config file.; Exception type: System.Xml.XmlException; Exception message: Data at the root level is invalid. Line 1, position 1.
Issue:
Notes that Movere was unable to access, view, or scan the specific .NET datapoint.
Solution:
This error does not impact the broader inventory or ARC scanning of these machines, and this data is not currently visible on the Movere website.
 
Error:
An error has occurred while copying bot to C$; Exception message: The user name or password is incorrect
Issue:
This indicates that the password and/or user name of the credentials entered into the Movere console are inaccurate
Solution:
Ensure the correct password is entered.
 

Error:
Logon failure: the user has not been granted the requested logon type at this computer
Issue:
Indicates that the device running the Movere console does not have permission to scan the target device. Can also indicate incorrect privileges for the account leveraged for scanning.
Solution:
This is common when running a scan from a machine in one domain, targeting machines in another domain. This error pertains to the device running the scan, (not the user running the scan). To resolve, run the scan from within the domain being targeted. This error is also often seen when using a service account for scanning, where the account was denied "interactive logon" before being granted "Local Admin" rights. To resolve, re-create the service account and grant "Local Admin" rights before denying interactive logon.

Error:
Device is Terminal Server or Citrix Xen App. Skipping non-idle processes…
Issue:
ARC data collection for process-level information of Terminal Servers and Citrix systems is being skipped.
Solution:
Movere will skip process data collection during ARC scanning by default for Terminal Citrix and Xen servers. ARC data for the device will still be collected.
 
Error:
Could not load file or assembly 'Microsoft.Web.Administration, Version=7.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
Issue:
Indicates a partial install of .NET.
Solution:
Update the target device(s) to .NET 3.5 or higher.
 
Error:
Net 3.5 not present. Removing Arc binaries
Issue:
Indicates the minimum ARC requirement of .NET 3.5 on the target device(s) is not met.
Solution:
Update the target device(s) to .NET 3.5 or higher.
 
Error:
C:\Users\User\Documents\Movere\Console\\FrameworkVerifier\FrameworkVerifier.exe ' is denied
Issue:
Indicates that one or more credentials entered into the Console do not have access to the Movere Console folder.
Solution:
Grant the credential(s) Full Access to the Console folder by adding the credential(s) via the folder Permissions. All credentials entered into the Console for scanning must have full access to the Console folder in order to pass the bots and FrameworkVerifier to the target devices.