All, On our slower servers that take over 5 minutes to reboot after installing and rebooting (after agent install), they fail. We have to manually go into "edit" and re-launch the import. Is there a way to change the timeout to over 5 minutes to accomodate slower machines or does anyone have any other suggestions?
There is no time window as in converter application waiting for the source machine to reboot after installing the agent. In fact, you could install the agent today and reboot the machine tomorrow and execute the conversion the day after.
Could you detail the specs of your source machine such as Os servicepack disk space etc. Also detail each step you are taking so we can better assess your situation
Here is what we do, kinda high level...
1. We go through Import Machine Wizard
2. The VMware Converter Agent Installs on the source machine and reboots the server. This takes over 5 minutes and produces this error in the logs....
\[2007-08-28 14:37:37.871 'ClientConnection' 420 warning] Failed to connect to
servername\pipe\vmware-ufad-p2v30-vmdb. Reason: The network path was not found. . Error code: 53.
\[2007-08-28 14:37:40.871 'ClientConnection' 420 error] Giving up trying to connect to
\[2007-08-28 14:37:40.871 'VmdbSvc' 420 verbose] Unregistering callback...
\[2007-08-28 14:37:40.871 'VmdbSvc' 420 verbose] ...done
\[2007-08-28 14:37:40.871 'P2V' 420 error] \[task,295] Task failed: P2VError UFA_NOT_RUNNING()
Can you see if the agent will install directly?
Simply install converter 3.0.1 directly to the physical source machine as the "local" administrator. Then simply run the conversion without the use of a middle (proxy) machine.
Yes, you are correct. If the agent is installed manaully or already there for some other reason, we do not have a problem. With that being said we would like to figure out how to use the built-in feature if possible. This leads me back to understanding the timeout value that the Converter "gives up" with contacting the server it's trying to import.
Thanks for all your help!