C.1 Common Discovery Issues and Solutions

Table C-1 Common Issues and Solutions Related to Discovery Operations

Problems or Messages

Solutions

Unable to Configure X2P Migration for a Workload Discovered Using Migrate Agent

Use the PlateSpin Migrate Client or PlateSpin Migrate Web Interface to discover the source workload and then migrate the workload. You can alternatively use a different replication method for the migration.

Discovering a Source Workload By Host Name Fails When a Discovered Under Control Target Has the Same Host Name As the Source

Use the IP Address of the source workload instead of the host name to discover it.

The workload cannot be migrated because it has 0 active partitions. Ensure that the workload has exactly 1 active partition and try again

This error occurs if there is no active partition on the source workload. Use the diskpart SELECT and ONLINE commands to make a partition active:

  1. Open a command prompt as an Administrator and run diskpart.

  2. Enter list volume and make a note of the volume number that you want to make active.

  3. Enter select volume <volume_number>

  4. Enter online volume and then exit.

Application has generated an error occurs during registration of physical server

This error occurs if the physical server is unable to contact the PlateSpin Server. A common cause is incorrect information entered during the registration process.

To restart the registration process:

  1. Enter RegisterMachine.bat.

  2. Ping to confirm basic connectivity with the PlateSpin Server.

My physical server has completed the registration process, but is not seen in PlateSpin Migrate Client.

The full registration process can take some time to complete. After the second command prompt window has closed on the physical server, wait a few minutes before clicking the Refresh button in PlateSpin Migrate Client.

Problems discovering source and target servers

KB Article 7920291 contains troubleshooting checklists for discovering the following:

  • Linux servers and VMware ESX Servers

  • Windows-based source and target servers

The article also has instructions for troubleshooting WMI connections and checking if DCOM is enabled.

Package <…> Not Found occurs during discovery of existing Windows servers

Check for required IIS configuration and network settings.

See Installing Prerequisite Software in the PlateSpin Migrate 2019.11 Installation and Upgrade Guide.

Unable to connect neither to the SSH server running on <IP_address> nor to VMware Virtual Infrastructure web-services at <ip_address>/sdk

This message has a number of possible causes:

  • The workload is unreachable.

  • The workload does not have SSH running.

  • The firewall is on and the required ports have not been opened.

  • The workload’s specific operating system is not supported.

For network and access requirements for a workload, see Access and Communication Requirements across Your Migration Network

Access denied

This authentication problem indicates either an invalid user name or password. For information on proper workload access credentials, see Table 19-2, Guidelines for Machine Type and Credentials for Source Workloads.

Access can be denied for SSH connections if the key algorithm or ciphers settings in the /etc/ssh/sshd_config file on the source Linux workload are missing or are incompatible with the settings used by Migrate server. See Test Credentials or Discovery Fails with Access Denied Error.

Related KB Articles are listed in Table C-2.

Table C-2 KB Articles for Discovery Issues

ID

Description

7920339

ERRMSG: Discovery fails with The request failed with HTTP status 407 message

7920862

ERRMSG: Recoverable Error: ControllerConnectionBroken during discovery

7920291

ERRMSG: Server details discovery problems

7021574

ERRMSG: X2P Target Discovery Failed: Linux job did not complete successfully

For more discovery-related TIDs in the Knowledgebase

Search on “discovery” for the PlateSpin Migrate product.