Table D-1 Common Issues and Solutions Related to Discovery Operations
Problems or Messages |
Solutions |
---|---|
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:
|
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:
|
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:
The article also has instructions for troubleshooting WMI connections and checking if DCOM is enabled. |
Package <…> Not Found occursduring discovery of existing Windows servers |
Check for required IIS configuration and network settings. See |
Could not find file \\{servername}\admin$\{randomID}.xml |
This error might occur on Windows Server 2003 hosts. In some cases, either of these troubleshooting steps addresses the issue:
|
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:
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 22-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 D-2.
Table D-2 KB Articles for Discovery Issues
ID |
Description |
---|---|
ERRMSG: Discovery fails with The request failed with HTTP status 407 message |
|
ERRMSG: Recoverable Error: ControllerConnectionBroken during discovery |
|
ERRMSG: Server details discovery problems |
|
ERRMSG: X2P Target Discovery Failed: Linux job did not complete successfully |
|
For more discovery-related TIDs in the Knowledgebase |