Virtual machine conversion fails when using using the Copy as New feature in VMware vCenter Converter Standalone 4.0.x
book
Article ID: 340672
calendar_today
Updated On:
Products
VMware
Issue/Introduction
Symptoms:
Using the Copy as New feature on a task with Converter 4.x fails
You see one of these errors:
A General System Error occurred: Remote server closed connection after 0 response bytes read
The Session is not authenticated
Environment
VMware vCenter Converter Standalone 4.0.x
Cause
This issue occurs when Converter caches connection settings to the vCenter. Converter tries to use the same connection settings as vCenter when performing a Copy as New operation, even though the cached information is invalid.
Resolution
To resolve this issue:
Log in to the server that is running Converter as an administrator.
Click Start > Run, typeservices.msc, and click OK. The Services window opens.
Right-click VMware vCenter Converter Standalone Agent and click Restart.
Right-click VMware vCenter Converter Standalone Server and click Restart.
Note: If your problem still exists after trying the steps in this article, file a support request with VMware Support and note this Knowledge Base article ID (1017501) in the problem description. For more information, see How to Submit a Support Request.