Troubleshoot issues with discovery client

This page shows you how to resolve issues with the discovery client.

Installation issues

The following issues might occur during the installation of the discovery client.

Database installation

In some cases, the PostgreSQL database installation might fail due to security software installed on the machine. Some customers reported installation issues with programs such as CyberArk, bit9 (aka Carbon Black), and McAfee.

To solve the problem, verify that PostgreSQL 12 is not installed by checking the Add/Remove Programs window on your machine. Then, you can try to install PostgreSQL in interactive mode by following these steps.

  1. Open a command prompt in administrator mode.
  2. Navigate to the discovery client installation folder (typically C:\"Program Files"\"Migration Center Discovery Client").
  3. Run the postgreSQLsetupmanual.bat script to launch the PostgreSQL installation.
  4. Follow the steps on the screen, and leave all the default settings provided.
  5. After the PostgreSQL installation, verify that the following services are installed in Windows Services:
    • Migration Center DataCollector
    • Migration Center DataTransmitter
    • Migration Center PostgreSQL

If the installation still fails, contact Google Cloud Support and provide the following information:

  • If you run security software on your machine, include the details in the request.
  • The error message for the installation. You can typically find it in the AppData > Local > Temp folder.

Connection issues

During the initial authorization phase of the discovery client, you might encounter issues with connectivity or with the PostgreSQL database. Review the error message in the app to determine the cause of the issue.

Connection from Windows services failed

This error occurs when the discovery client cannot establish a connection with Migration Center.

To solve this issue, click the View resolution options link, enter valid proxy credentials, then click Save. Click Retry to test the connection again.

Enable proxy

The discovery client and the corresponding Windows services use the default proxy settings returned by Windows. In some cases, the Local System user does not have the proxy that is normally available for users logged into the system. In such instances, you can set the proxy settings in the discovery client with the following steps:

  1. In the discovery client app, go to the Settings tab.
  2. Enable proxy credentials.
  3. Enter the proxy host and port.
  4. Enter the proxy credentials, if needed.

Data collection issues

The following issues might occur when you collect data with the discovery client.

Data collection not occurring

If you successfully installed the discovery client and you added your assets, but the collection doesn't occur, try the following troubleshooting strategies:

  1. Confirm that discovery client is authorized. For more information, see Authorize the discovery client.
  2. Verify that all your credential groups are scheduled for data collection.
  3. In the discovery client app, go to Settings, then click Test Call Home to test the connectivity to Migration Center.
  4. Verify that you don't have firewall rules blocking traffic to specific ports.
    • For Linux machines, allow TCP inbound traffic to port 22.
    • For Windows WMI, allow TCP inbound traffic to port 135 and TCP inbound dynamic ports as follows.
      • Ports 49152 through 65535 for Windows Server 2008 and newer.
      • Ports 1025 through 5000 for Windows Server 2003 and earlier.

Subnet scan not running

If the subnet scan is not running, try the following troubleshooting strategies:

  1. Confirm that the discovery client is authorized.
  2. In the discovery client app, go to Settings, then click Test Call Home to test the connectivity to Migration Center.
  3. Open services.msc in Windows and confirm that the following Migration Center services are running:
    • Migration Center DataCollector
    • Migration Center DataTransmitter
    • Migration Center PostgreSQL

IP range scan not working

In some cases, you might get the following error message while performing an IP range scan:

A connection attempt failed because the connected party did not properly
respond after a period of time, or established connection failed because
connected host has failed to respond.

To resolve the issue, make sure that Internet Control Message Protocol (ICMP) requests with the ping command are allowed by your firewall rules.

RPC server unavailable

In some cases, you might receive the following error:

The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)

This error is the result of communication issues between discovery client and the asset. Some common causes for this error are the following:

  • The asset does not exist or is shut down. Verify that the asset is turned on by pinging it and using the remote desktop to connect to the server.
  • There is a firewall blocking the line of sight to the asset. Verify that there is a line of sight to the asset by using ping and RDP to the asset. You might need to modify network rules, or use a different discovery client that can access the asset.
  • Windows Firewall is blocking remote WMI calls to the asset. Connect using RDP to the machine and check if Windows Firewall is turned on. Follow the steps to modify the firewall rules.

Access denied (0x80070005)

In some cases, you might receive the following error:

0x80070005-E_ACCESS_DENIED

This error occurs when the credentials are incorrect or the user account doesn't have remote access to the computer through DCOM. To solve this error, try one of the following strategies:

  1. Verify that the credentials are correct. In particular:
    1. Enter domain accounts as DOMAIN\USERNAME.
    2. Enter local accounts as .\USERNAME.
  2. Grant the user Remote Launch and Remote Activation permissions in dcomcnfg.
    1. Click Start > Run, then enter dcomcnfg.
    2. Expand Component Services and Computers.
    3. Right-click My Computer, then select Properties.
    4. Under COM Security, click Edit Limits for both sections.
    5. Grant the user Remote Access, Remote Launch, and Remote Activation permissions.
    6. Go to DCOM Config, then find Windows Management Instrumentation.
    7. Grant the user Remote Launch and Remote Activation permissions.

For more information, see the WMI troubleshooting page.

Access denied (0x80041003)

In some cases, you might receive the following error:

0x80041003-WBEM_E_ACCESS_DENIED

This error occurs when the credentials provided have no access to the WMI namespace. To solve this error, try to locate and update the WMI control.

  1. In the Control Panel, double-click Administrative Tools.
  2. In the Administrative Tools window, double-click Computer Management.
  3. Right-click the WMI Control icon, then select Properties.
  4. Click the Security tab.
  5. Click Root folder, then click Security.
  6. Grant the user Execute Methods, Enable Account and Remote Enable access to the namespace.
  7. Press the Advanced button.
  8. Double-click on Principal, then change the Applied to value to This namespace and subnamespaces.

For more information, see the Namespace security troubleshooting page.

Permission denied

In some cases, you might receive a Permission denied (password) or Permission denied (publickey) error.

This error occurs when discovery client fails to authenticate to the Linux asset using the Linux credentials provided. To solve this error, try the following strategy.

  1. From the Credentials, click into the group with the error.
  2. Click View all errors. This lists all the assets that have issues.
  3. To correct a specific asset, click the three dots next to the asset and select Edit asset.
  4. Modify the asset credentials by selecting the asset-specific credentials from the drop-down. These override the global credential to which the asset is assigned.
  5. From the assets list, click Test authorization from the three dot menu next to the asset to test the credentials you just entered.