B.1 Discovery

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

Problems or Messages

Solutions

"Application has generated an error" during registration of physical server

This error occurs if the physical server is unable to contact the Portability Suite Server. A common cause is incorrect information entered during the registration process. To restart the registration process, enter RegisterMachine.bat. Ping to confirm basic connectivity with the Portability Suite Server.

My physical server has completed the registration process, but is not seen in Portability Suite 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 Portability Suite Client.

Problems discovering source and target servers

Knowledge Base Article Q20291 contains troubleshooting checklists for discovering:

  • 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" during discovery of existing Windows servers

Check for IIS configuration and network settings.

Could not find file "\\{servername}\admin$\{randomID}.xml"

This error might occur when you are attempting to discover a Windows NT 4.0 Server with an older version of WMI Core installed. It can also occur with a Windows Server 2000 or 2003. For Windows NT 4.0 servers, verify the version of WMI installed on the server by doing the following:

  1. Locate the wbemcore.dll file in the \winnt\system32\wbem directory.

  2. Right-click wbemcore.dll and click Properties.

  3. Check the version number of the file. If the version number is not 1.50.xxxx, upgrade the WMI core to V1.5. See the following Microsoft Web site).

After WMI v1.5 has been installed, rediscover the server.

In some cases, reinstalling WMI 1.5 might resolve the issue. If this discovery error still occurs after installing WMI 1.5 on a Windows NT 4.0 Server or if it is still occurring when you attempt to discover a Windows 2000/2003 Server, do the following:

  1. Ensure that the Admin$ share on the remote machine is accessible and then proceed to the next step. If the share is not accessible, enable it and try the discovery again.

  2. Navigate to the ..\PlateSpin Portability Suite Server\Web directory.

  3. Using a text editor, open the web.config file. Locate the <add key= "MachineDiscoveryUsingService" value= "false" /> entry near the end of the file and change the value to "true".

  4. Save the web.config file and retry the discovery.

Rebooting the target machine as soon as the job indicates Recoverable Error status

During the configuration service step, there might be a delay when the Portability Suite Server receives notification from the machine that is being configured. The job then indicates a Recoverable Error status.

It is not necessary to reboot the target machine. Wait at least 30 minutes before attempting to reboot or perform other interventions.

Related Knowledge Base Articles:

ID

Description

Q20339

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

Q20894

ERRMSG: Recoverable Error: ControllerConnectionBroken during discovery

Q20291

ERRMSG: Server details discovery problems

Q20853

FAQ: MSVS is discovered as a regular server in Portability Suite

Q20732

FAQ: Network path not found error during discovery

Q20868

INFO: Files and directories are not cleaned up after discovery of a Windows VM