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 button in Portability Suite Client. |
Problems discovering source and target servers |
Knowledge Base Article Q20291 contains troubleshooting checklists for discovering:
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:
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:
|
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: