Getting a "general system error occurred: unknown internal error" on vCenter Converter

[bensh]

I have built some VMs on a ESXi 4.1 system as this had a better connection for ISOs etc, with a mind to then convert these VMs once setup and move them to my other ESXi server which is 5.1.

The inital converstion from 4.1 to a Infrastruction, .vmx file went fine, however on the 2nd leg to convert the backup image files from the VMware workstation as a source image up to my 5.1 server I get the error on the final Summary page.

It starts to Submit the job, and I see activity in the logs on the ESXi vSphere client but then it throws the internal error on the Converter.

Logs are attached.

Any ideas?

[a_p_]

Welcome to the Community,

there's a known issue with Converter 5.0 and ESXi 5.1 as the target. Please download the latest Converter 5.0.1 to see whether this solves the issue.

André

[bensh]

Thanks André,

I'll give it a go and post back my findings.

[a_p_]

Here's the KB article describing the issue http://kb.vmware.com/kb/2033315

André

[bensh]

Still recieving the error despite upgrade to 5.1

I will try converting the VM on my 4.1 ESXi server again.

EDIT:

Still no luck in getting the conversion to work yet.

No luck.

The error i'm reciving is after the job is submitted, it opens a bar at the top and says "unknown internal error" then stops the conversion

[bensh]

The file logs could help.

I've had a look around the net and tried most fixes.

Anyone that can help to solve this I will mark as helpful/correct answer.

EDIT:

Logs state a vmodl.fault error?

2012-10-29T12:27:25.609Z [09476 error 'wizardController'] Unable to submit job: vmodl.fault.SystemError
2012-10-29T12:27:25.609Z [05904 error 'ConversionState'] Submit job failed: A general system error occurred: unknown internal error

[ivivanov]

2012-10-29T10:02:26.235Z [01968 info 'Default'] GetManagedDiskName: Get disklib file name as ha-nfcssl://[VM Datastore] OEL4u8/OEL4u8.vmdk@127.0.0.1:902!52 55 c0 17 53 bb 94 16-ff a7 bc 74 94 86 f5 b9
2012-10-29T10:02:26.484Z [01968 warning 'Default'] [,0] SSLVerifyIsEnabled: failed to open the product registry key. Falling back to default behavior: verification off. LastError = 0
2012-10-29T10:02:26.484Z [01968 warning 'Default'] [,0] SSL_VerifyX509: Certificate verification is disabled, so connection will proceed despite the error
2012-10-29T10:02:26.484Z [01968 warning 'Default'] [,0] SSLVerifyIsEnabled: failed to open the product registry key. Falling back to default behavior: verification off. LastError = 0
2012-10-29T10:02:26.484Z [01968 warning 'Default'] [,0] SSL_VerifyX509: Certificate verification is disabled, so connection will proceed despite the error
2012-10-29T10:02:26.594Z [01968 warning 'Default'] [,0] [NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error: 554 PROXY service nfcssl not found.
2012-10-29T10:02:26.594Z [01968 info 'Default'] [,0] Sysimgbase_DiskLib_OpenWithPassPhrase failed with 'NBD_ERR_NETWORK_CONNECT' (error code:2338)
2012-10-29T10:02:26.594Z [01968 info 'Default'] [,0] Error 2338 opening disk ha-nfcssl://[VM Datastore] OEL4u8/OEL4u8.vmdk@127.0.0.1:902!52 55 c0 17 53 bb 94 16-ff a7 bc 74 94 86 f5 b9.
2012-10-29T10:02:26.594Z [01968 info 'Default'] [,0] Error 2338 opening disk ha-nfcssl://[VM Datastore] OEL4u8/OEL4u8.vmdk@127.0.0.1:902!52 55 c0 17 53 bb 94 16-ff a7 bc 74 94 86 f5 b9.

How did you manage to connect to an ESX host on 127.0.0.1?!? Do you want to use VMware Workstation as a destination?? If yes - you need to select VMware Workstation, but not VMware Infrastructure on the Destination page in Converter wizard.

[bensh]

Im tunnelling using the SSH Tunnels on the Putty client forwarding port 443 and 902

Im trying to upload a backup .vmx image to a ESXi server from my local machine to a remote one

[ivivanov]

I am not sure it is going to work. Anyway, the error reported is a network error about not being able to open the remote disk. In general Converter Server machine needs access to the target ESX host. What exactly is your network configuration?

[bensh]

When I put in the IP address and user details of the Destination System, the next step, Destination Virtual Machine loads up all the VMs on the remote ESX server going through 127.0.0.1, so surely that shows that there is a connection to the remote server in that it can see whats on it?

On the following page, Destination Location, it can see the server fine, and locates the Datastore correctly as "VM Datastore"