vCenter Converter 6.2 failed to install on Windows Server 2008 R2 or later
Article ID: 301298
Updated On:
Products
VMware
Issue/Introduction
Symptoms:
- When install vCenter Converter standalone 6.x, the installation finished with pop window "Could not start service".
- vCenter Converter Agent, vCenter Converter Server or vCenter Converter Worker service cannot turn to "Running" in Windows Service Manager.
- Event ID 7009 can be get in Windows event viewer with content "A timeout was reached (30000 milliseconds) while waiting for the VMware vCenter Converter Standalone Worker service to connect".
Environment
VMware vCenter Converter Standalone 6.x
Cause
This issue occurs because Service Control Manager generates an event if a service does not respond within the defined timeout period (the default timeout period is 30000 milliseconds).
Resolution
To change the service timeout period:
-
Click the Start button, then click Run, type regedit, and click OK.
-
In the Registry Editor, click the registry subkey HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control.
-
In the details pane, locate the ServicesPipeTimeout entry, right-click that entry and then select Modify.
Note: If the ServicesPipeTimeout entry does not exist, you must create it by selecting New on the Edit menu, followed by the DWORD Value, then typing ServicesPipeTimeout, and clicking Enter.
-
Click Decimal, enter the new timeout value in milliseconds, and then click OK.（Modify the value to a larger one. Here is no recommended value, adjust this value accordingly.）
-
Restart the computer.
-
Manual start vCenter Converter Agent/Server/Worker service in Windows Service Manager. If the service is still failed to start with Windows event 7009, increase the "ServicesPipeTimeout" value.
Additional Information
Feedback
Yes
No
Powered by
