Hello all,

I'm trying to run an V2V Live migration from one cluster location to another cluster location, same VCenter.

I'm using VMware Converter 5.5 Standalone client and ESX 5.5.

The job submits, but gives the error: An error occured while opening a virtual disk. Verify that the Converter Server and the running source machine have a network access to the source and destination ESX/ESXi hosts.

The conversion starts, the VM is created, but fails. I found this error in the log Unable to submit job: converter.fault.ManagedDiskOpenFault.

Anybody got any clues how to solve this?

Thanks in advance!

Best Regards,

Martijn W

I'm trying to convert an acronis tru image backup of a windows 2003 server to a VM on an esxi server, a system I'd converted previously on converter 4.x and exsi 5.1 and using the same image and same PC to convert it, but now It is failing at 59% with the status:

FAILED: An error occurred during the conversion: 'A file error was encountered' and error: Error: Unable to clone disk C:\Windows\TEMP\vmware-temp\vmware-me\nvdsxwvgwgxyklny\disk-1.vmdk on the virtual machine 'server'.

Not sure where to go with this.

Anybody got any ideas???

I had to remove the "/3GB" switch from the Boot.ini to convert a Windows 2003 x86 server running SQL, but the converted virtual server now only recognises 1.6GB RAM. Is it safe to put the "/3GB" switch back into the Boot.ini to fix this? We are using VMware 5.1.

Reference:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1030145

HELP HELP HELP.

We have RDM disk and we move it to new storage and delete VM from old inventory site and add vm to new inventory site. NOW our disk not connect becouse it rdm.

PLS help, how we can convert it -rdmp.vmdk file to the .vmdk file?

Trying to P2V a Win 2008 R2 machine. Largest Physical disk is 2 TB. Yes dynamic disks. Not re-sizing, Failed at 96% after more than 2 days

Here's what I found in the worker log (attached)

2014-11-02T20:34:32.355-08:00 [09880 info 'task-1'] GetManagedDiskName: Get disklib file name as vpxa-nfcssl://[DataStore] [MachineName]_3-000002.vmdk@[HostName]:902!52 92 92 fc 65 6a fb b3-81 c1 cd f4 83 68 a8 29

2014-11-02T20:34:33.652-08:00 [09880 warning 'Default'] [,0] [NFC ERROR] NfcFssrvrProcessErrorMsg: received diskLib error 18 from server: NfcFssrvrOpen: Failed to open '[DataStore] [MachineName]-000002.vmdk': The parent virtual disk has been modified since the child was created. The content ID of the parent virtual disk does not match the corresponding parent

2014-11-02T20:34:33.652-08:00 [09880 info 'Default'] Sysimgbase_DiskLib_OpenWithPassPhrase failed with 'The parent virtual disk has been modified since the child was created. The content ID of the parent virtual disk does not match the corresponding parent content ID in the child' (error code:18)

2014-11-02T20:34:33.652-08:00 [09880 info 'Default'] Error 18 opening disk vpxa-nfcssl://[DataStore] [MachineName]-000002.vmdk@[HostName]:902!52 fb 2e 73 fc 7f cb 0a-aa d4 66 33 f4 4f 99 aa.

2014-11-02T20:34:33.652-08:00 [09880 warning 'Default'] ERROR 18 opening disk vpxa-nfcssl://[DataStore] [MachineName]-000002.vmdk@[HostName]:902!52 fb 2e 73 fc 7f cb 0a-aa d4 66 33 f4 4f 99 aa.

2014-11-02T20:34:33.652-08:00 [09880 error 'task-1'] [BaseDiskSetComputer::DoOpen] OpenDisks failed, mntapi error: 290

2014-11-02T20:34:33.652-08:00 [09880 error 'task-1'] [BaseDiskSetComputer::AnalyzeErrorAndThrow] Error occurred when opening disk set, MNTAPI_ERROR = 290 MNTAPI errorType = 2, errorCode = 18

2014-11-02T20:34:33.652-08:00 [09880 error 'task-1'] TaskImpl has failed with std::Exception: Platform-specific error 18

2014-11-02T20:34:33.652-08:00 [09880 info 'task-1'] TargetVmManagerImpl::DeleteVM

Please let me know if you've seen this before? Multiple searches turned up nothing

Have a vcenter 192.168.62.10 (no admin permission to login)

Will convert a Physical Linux centos 192.168.62.20 to VMWare

We have 2 ESXi server 192.168.62.100 and 62.200

In case to convert it, we created a win2003 (192.168.62.30) VM, and installed Converter standalone 5.5 on it

Error: after we went through each step, able to connect to linux via root, setup vcenter ip as host, and pickup 62.100 as VM lost to locate the new VM;

setup helper network, assign a new IP 192.168.62.31 to it, it running into process, waiting for long time and failed

Question:

1. Is this converter only running on vcenter? I have to login vcenter to install the converter and running there?

2. if my way reasonable, how to make it work?

Thanks

Michael

Note: I've removed specific server names from the logs.

I've been working on a P2V for a few days with zero success.  The error I am getting is: A general system error occurred platform-specific error 38.  If I look into vCenter the VM will be created and then deleted within about 20 seconds and fail before 1%.

The specific server details are:

Windows Server 2008 x64.

VMware Converter Standalone 6.0 (I've tried versions 5.5.3 and 4.1 and the exact thing happens)

The first time I attempted to P2V this server it made it to 80ish percent and then rebooted.  Ever since then I've been getting this failure.  I had noticed there were some old folders in the vSAN datastore referencing this server so I removed that folder which did not resolve the problem.

This area of the log seems to be the portion where it fails:

2015-05-19T11:21:01.345-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=task-1] GetManagedDiskName: Get virtual disk filebacking [vsanDatastore] ca545b55-ffc5-354a-c334-fc15b4132df0/<VMNAME>.vmdk

2015-05-19T11:21:01.345-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=task-1] GetManagedDiskName: updating nfc port as 902

2015-05-19T11:21:01.345-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=task-1] GetManagedDiskName: get protocol as vpxa-nfcssl

2015-05-19T11:21:01.345-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=task-1] GetManagedDiskName: Get disklib file name as vpxa-nfcssl://[vsanDatastore] ca545b55-ffc5-354a-c334-fc15b4132df0/<VMNAME>.vmdk@<ESXiHOSTNAME>:902!52 a3 49 48 4d 8d f5 c1-cf 8a 14 3d 95 19 3b 78

2015-05-19T11:21:03.155-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=Default] error 'Insufficient permission to access file' (error code:38) creating child in DiskLib

2015-05-19T11:21:03.264-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=Default] error 'Insufficient permission to access file' (error code:38) creating child in DiskLib

2015-05-19T11:21:03.264-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=Default] Error 38 opening disk vpxa-nfcssl://[vsanDatastore] ca545b55-ffc5-354a-c334-fc15b4132df0/<VMNAME>.vmdk@<ESXiHOSTNAME>:902!52 a3 49 48 4d 8d f5 c1-cf 8a 14 3d 95 19 3b 78.

2015-05-19T11:21:03.264-04:00 warning vmware-converter-worker[05232] [Originator@6876 sub=Default] ERROR 38 opening disk disk-2000.

2015-05-19T11:21:03.264-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=Default] Attempt to opening disk disk-2000 again [rest 2] (sleep for 5 sec).

2015-05-19T11:21:08.272-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=task-1] Reusing existing VIM connection to <VCENTERNAME>

2015-05-19T11:21:08.287-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=task-1] GetManagedDiskName: Get virtual disk filebacking [vsanDatastore] ca545b55-ffc5-354a-c334-fc15b4132df0/<VMNAME>.vmdk

2015-05-19T11:21:08.287-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=task-1] GetManagedDiskName: updating nfc port as 902

2015-05-19T11:21:08.287-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=task-1] GetManagedDiskName: get protocol as vpxa-nfcssl

2015-05-19T11:21:08.287-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=task-1] GetManagedDiskName: Get disklib file name as vpxa-nfcssl://[vsanDatastore] ca545b55-ffc5-354a-c334-fc15b4132df0/<VMNAME>.vmdk@<ESXiHOSTNAME>:902!52 c4 4f 5f 39 0c c3 12-18 2b 4c 44 77 75 63 ad

2015-05-19T11:21:10.035-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=Default] error 'Insufficient permission to access file' (error code:38) creating child in DiskLib

2015-05-19T11:21:10.159-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=Default] error 'Insufficient permission to access file' (error code:38) creating child in DiskLib

2015-05-19T11:21:10.159-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=Default] Error 38 opening disk vpxa-nfcssl://[vsanDatastore] ca545b55-ffc5-354a-c334-fc15b4132df0/<VMNAME>.vmdk@<ESXiHOSTNAME>:902!52 c4 4f 5f 39 0c c3 12-18 2b 4c 44 77 75 63 ad.

2015-05-19T11:21:10.159-04:00 warning vmware-converter-worker[05232] [Originator@6876 sub=Default] ERROR 38 opening disk disk-2000.

2015-05-19T11:21:10.159-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=Default] Attempt to opening disk disk-2000 again [rest 1] (sleep for 10 sec).

2015-05-19T11:21:20.175-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=task-1] Reusing existing VIM connection to <VCENTERNAME>

2015-05-19T11:21:20.206-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=task-1] GetManagedDiskName: Get virtual disk filebacking [vsanDatastore] ca545b55-ffc5-354a-c334-fc15b4132df0/<VMNAME>.vmdk

2015-05-19T11:21:20.206-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=task-1] GetManagedDiskName: updating nfc port as 902

2015-05-19T11:21:20.206-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=task-1] GetManagedDiskName: get protocol as vpxa-nfcssl

2015-05-19T11:21:20.206-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=task-1] GetManagedDiskName: Get disklib file name as vpxa-nfcssl://[vsanDatastore] ca545b55-ffc5-354a-c334-fc15b4132df0/<VMNAME>.vmdk@<ESXiHOSTNAME>:902!52 71 6c db 92 78 8d bf-b8 f7 a0 f6 88 c8 3c dc

2015-05-19T11:21:21.969-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=Default] error 'Insufficient permission to access file' (error code:38) creating child in DiskLib

2015-05-19T11:21:22.093-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=Default] error 'Insufficient permission to access file' (error code:38) creating child in DiskLib

2015-05-19T11:21:22.093-04:00 info vmware-converter-worker[05232] [Originator@6876 sub=Default] Error 38 opening disk vpxa-nfcssl://[vsanDatastore] ca545b55-ffc5-354a-c334-fc15b4132df0/<VMNAME>.vmdk@<ESXiHOSTNAME>:902!52 71 6c db 92 78 8d bf-b8 f7 a0 f6 88 c8 3c dc.

2015-05-19T11:21:22.093-04:00 warning vmware-converter-worker[05232] [Originator@6876 sub=Default] ERROR 38 opening disk disk-2000.

2015-05-19T11:21:22.093-04:00 error vmware-converter-worker[05232] [Originator@6876 sub=task-1] [BaseDiskSetComputer::OpenDiskSet] OpenDisks failed, mntapi error: 609

2015-05-19T11:21:22.093-04:00 error vmware-converter-worker[05232] [Originator@6876 sub=task-1] [BaseDiskSetComputer::AnalyzeErrorAndThrow] Error occurred when opening disk set, MNTAPI_ERROR = 609 MNTAPI errorType = 1, errorCode = 38

2015-05-19T11:21:22.093-04:00 error vmware-converter-worker[05232] [Originator@6876 sub=task-1] AnalyzeErrorAndThrow(): Insufficient permissions to open file

2015-05-19T11:21:22.093-04:00 error vmware-converter-worker[05232] [Originator@6876 sub=task-1] AnalyzeErrorAndThrow(): Platform errorType 1, errorCode 38

2015-05-19T11:21:22.093-04:00 error vmware-converter-worker[05232] [Originator@6876 sub=task-1] TaskImpl has failed with std::Exception: Platform-specific error 38

Hi,

In my current environment we have boot from SAN configuration and we have entire storage coming from remote SAN (Multipath configured). I have tired VMware vCenter Converter Standalone 6.0 to migrate physical SUSE 11 to Virtual Machine but got error "FAILED: An error occurred during the conversion:'Partition number must be set for the boot volume'" at 97%.

While checking logs we found both the Physical Machine cloned successfully and got error while reconfiguring the destination virtual machine. Further digging into problem we have observed /boot volume is not visible at ‘Source Volume’ TAB in vConverter that means vConverter is not reading /boot volume information from the source Physical Machine. While checking at destination virtual machine we found error at console "Operating System not found".

In VMware vCenter Converter Standalone User's Guide if found "Linux volumes mounted by Device Mapper multipath" is not support for Powered On Machine.

Please help me to understand if vCenter Converter Standalone supports boot from SAN environment?

Hello,

I am trying to migrate my Virtual machine from Esx 4.1 to Esx 5.5. This is completely on new vCenter. However, when i trying to migrate using VM Ware vCenter Converter Standalone, i am getting error "A File I/O error occurred while Accessing." This error shows when i click "finish" on the summary. Attached the diagnose file. Any expert, please advise.

Hi,

The migration from a windows 7 32 bit systems fails at 98%.

FAILED: A general system error occurred:
InternalError

See attachment fot the log file.

Can someone help?

Best regards,

Maurice

Hello:

We have a software package that runs in Windows .NET.  We would like for our customers to be able to use VMWare to run our software on Linux or Mac.

Are there any tutorials on how to do this and what licensing would be needed to run Windows as the guest OS on the host system?

I'm not even sure if VCenter Converter is what I want to use so I'm a complete noob when it comes to VMWare development.

Thank you for any help you can provide!!!

--Todd

Vcenter Converter明明是免费的，为什么每次要去下载的时候都需要注册产品，注册完后还提示不接受这次下载的请求。

Hi,

I can't start the service Vmware vCenter Converter Standalone Server.

SO: Windows Server 2012 R2 Foundation

Regionan language : English

Some advice? What I can do?

Regards,

Marcello

Hi,

With both old school P2V and the new converter tool, we have to uninstall about 10 HP agents/tools from "Add/Remove Programs", manually uninstall the HP  Network Configuration Utility, and delete two registry keys that "Add/Remove Programs" does not remove after the conversion is completed.

Does anyone have any sweet scripts or tools to do all this automatically?

Thanks

SlickBag

This article discusses techniques and best practises for converting a Domain Controller using VMware Converter.

Symptoms

• A converted domain controller does not synchronize

• The DNS services on a converter domain controller does not bind to the network interface

• The local domain database file (NTDS.DIT) is corrupted in the new virtual machine

• The domain controller becomes tombstoned in Active Directory

• Synchronization is unreliable with other domain controllers

• Newly created or removed objects changed on the virtual machine or source reappear in Active Directory

• The update or serial number changes unexpectedly on the domain controller

• Kerberos authentication or trust failures

• DNS lookup failures

• You receive the following errors:

• LSASS.EXE - System Error, security accounts manager initialization failed because of the following error: Directory Services cannot start. Error status 0xc00002e1.

• Event ID: 1103 Description: "The windows directory services database could not be initialized and returned error 1032. Unrecoverable error, the directory can't continue."

Resolution

Introduction

A virtual machine created from an active domain controller may exhibit unexpected behavior. Domain controllers are very sensitive to hardware changes. When a physical server is virtualized the hardware presented to operating system may be very different. In addition it is possible that a virtualized domain controller and an identical physical domain controller may be running simultaneously which may result in unpredictable replication issues across Active Directory or even a tombstone condition. If you are using Windows NT, these change may prevent the directory or DNS servers from binding to the network connection.

Follow one of the below solutions depending on your situation:

Windows 2000, and 2003 Servers

For Windows 2000, and 2003 Servers:

• Ensure another domain controller is online on the network and properly synchronized, if one is not available provision a new domain controller as a virtual machine and promote it. Demote the domain controller using dcpromo. Set any static IP addresses to DHCP prior to conversion. When converted, power off the source server, reassign any static IP addresses and promote the virtualized server.

• Install the Microsoft loopback adapter and assign it an unused static IP address. Set any static IP addresses of the physical network adapters to DHCP, prior to conversion. Power down the source server, then boot it up using the Converter boot CD. Cold clone the server. If a cold clone is not possible, start the server in Directory Recovery mode and perform a hot conversion. Failure to use Directory Recovery mode may result in an incomplete and corrupted copy of NTDS.DIT. After conversion is complete, you can remove the Microsoft Loopback adapter and restore the static IP addresses to the new virtual network cards.

• Decommission the existing domain controller using dcpromo, and provision a new domain controller in a fresh installation of Windows Server in a new virtual machine. Do not perform the conversion at all, but use the source server's host name and IP address. (recommended)

Important Notes:

• Always start using the new virtual machine as soon as possible after decommissioning the physical or source server. Failing to do so leads to a tombstone condition.

• Never use the customization option in the Conversion Wizard. Using this process destroys the server on the destination.

• Always be sure that the source server is powered off or decommissioned before starting the new virtual machine with the network cards connected.

• If the server to be virtualized holds any FSMO roles, transfer the roles to an existing and running domain controller. If a problem happens during the conversion process, you can provision new domain controllers in Active Directory and perform other AD operations without having to sieze roles from the unavailable domain controller.

Windows NT

Converting a Windows NT domain controller is a very involved process that may be trouble prone. VMware does not recommend converting a Windows NT domain controller if at all possible.

Warning: The following conversion process updgrades any NTFS file systems on the source and destination to version 3.0 (NTFS5). Do not perform these steps if you require disk utilities that are not compatible with newer NTFS file systems. To avoid NTFS upgrade, perform a hot clone to convert a stand-alone server. Do not hot clone a domain controller.

Below is a detailed list of complete steps to assist you with fully converting a Windows NT domain controller. This process may take several hours to complete. You should plan a maintenance window accordingly to perform the conversion.

To convert a Windows NT domain controller:

   1. Verify that you have the latest version of VMware Converter. Older versions do not support all Windows NT Fault Tolerant disk types. Use VMware Converter version 3.0.3 or higher.

   2. Ensure the server is running Windows NT Service Pack 5 or higher (Service Pack 6a is recommended).

      To determine this:

         1. Click Start > Run.

         2. Run the winver command. Do not proceed any further if the service pack requirement is not met.

   3. Create a Rescue Diskette. Click Start > Run, and run the rdisk command. If there is a problem with the new virtual machine you may be able to repair the problem using the Rescue Diskette.

   4. Ensure you have a complete and working backup of the server, especially if the Windows NT server is a Primary Domain Controller (PDC).

   5. Ensure another domain controller is available to service user logins.

      Note: If you are taking a PDC server offline, you cannot join any other DCs to the domain until it is online again as a virtual machine.

   6. Install the Microsoft loopback adapter and assign it an unused static IP address.

   7. Set any static IP addresses of the physical network adapters to DHCP.

   8. Properly shut down the source server. Click Start > Shutdown > Shutdown the computer. Power off the server with its physical power switch.

   9. Boot the Converter cold clone CD.

      Warning: Starting the Converter cold clone CD upgrades the NTFS version on the disk on the source and destination virtual machine to version 3.0 (NTFS5). This may prevent disk check (chkdsk) and defrag utilities (Diskeeper) from working on the volume. For more information, see Windows NT 4.0 CHKDSK Refuses to Check NTFS 3.0/3.1 Volumes (http://support.microsoft.com/kb/196707).

      Warning: Performing a hot clone of a Windows NT server may result in a corrupted NTDS.DIT on the destination virtual machine. Do not hot clone a Windows NT domain controller.

  10. Perform the conversion to a new virtual machine, and power off the source server.

      Warning: Do not power the server back on again for any reason after the new virtual machine is powered on with a network connection. Doing so may break synchronization with other domain controllers.

  11. Review the virtual hardware settings on the new virtual machine:

• Adjust the number of virtual NICs.

• Remove any unnecessary devices such as USB controllers, COM ports or floppy drives.

  12. Power on the new virtual machine with the network card disconnected.

  13. Click Start > Settings > Control Panel > Add / Remove Programs. Remove any unnecessary programs used to install or support device drivers, such a RAID management tools, network teaming or management software, wireless card management software, and video and sound drivers.

      Caution: Do not restart if prompted by an uninstall program.

  14. Restart the virtual machine properly.

  15. Remove any additional devices or device drivers that were used to support hardware on the physical server. Use the Control Panel to remove any necessary devices especially COM ports, SCSI controllers, video, and network cards.

      Do not remove the following devices:

• Buslogic SCSI controller

• IDE CD-ROM ATAPI controller

• AMD PC NET network card

  16. Restart the virtual machine properly.

  17. Attempt to install the VMware Tools. If you are missing the CD-ROM drive in the virtual machine or if you are unable to get the network adapter installed, see After converting a physical server running Windows NT the CD-ROM or networking does not work on the VM (http://kb.vmware.com/kb/1002278).

  18. Restart the virtual machine properly.

  19. Assign the static IP addresses used on the source server to the new virtual network adapters, if applicable.

  20. Restart the virtual machine properly.

  21. Ensure the DNS and directory services are started and bound to a valid adapter and start correctly.

  22. Remove the Microsoft loopback adapter.

  23. Restart the virtual machine properly.

  24. Review the server's Event Logs and ensure the necessary services are starting correctly without failures. To view the Event Log, click Start > Run, and run the eventvwr command.

      Note: Some failures may be due to device drivers or services still being installed. You may need to manually disable or remove these services in the Control Panel to prevent these errors.

  25. Shut down the virtual machine properly, then connect the network cards in the virtual device settings.

  26. Start the virtual machine normally.

  27. Ensure the DNS and directory services are started and bound to a valid adapter and start correctly.

  28. Check the Event Logs for any remaining errors and correct as needed.

Important Notes:

• Avoid converting Windows NT domain controllers if possible.

• Before attempting conversion, always be sure another domain controller is online and properly synchronized.

• Never use the customization option in the Conversion Wizard. Using this process destroys the server on the destination.

• Always ensure that the source server is powered off or decommissioned before starting the new virtual machine with the network cards connected.

Virtualizing existing domain controllers

http://kb.vmware.com/kb/1006996

Best practices for using and troubleshooting VMware Converter

http://kb.vmware.com/kb/1004588

I keep getting this error and i have checked all the steps with the helper VM and it gets stuck at 1% then errors after about three hours this is with a static IP for the helper address. converter 5.1 is what i'm using

Thanks!

Hi all, first post on this forum, I usually always manage to find the answer I need here and never had a need to post till now...

Trying to migrate a Windows 2008 R2 Ent SP1 server from A-B.

I always use Converter 5.0.0 (as it does everything I need) till today when I came across this server with disk formatted as GPT. Hence I installed v 5.1.0 locally which has support for GPT disks.

I have then spent the rest of the afternoon trying to make it work, but to no avail. I can telnet to ports 443, 902 from inside the O/S to the target ESXi host and the local firewall is disabled.

The error I keep getting is highlighted below, taken from the most recent converter job logs:

I have also since installed v5.5 of the Standalone converter and got the same error... Please please please help as this is driving me nuts...

2013-11-09T20:44:30.974+01:00 [04480 info 'wizardController'] FillPageContents(): currentPage is 7

2013-11-09T20:44:30.974+01:00 [04480 info 'wizardController'] FillPageContents(): currentPage is 8

2013-11-09T20:44:30.974+01:00 [04480 info 'wizardController'] subpages = 1

2013-11-09T20:44:30.974+01:00 [04480 verbose 'wizardController'] Found data connection TaskSummaryDataConnection

2013-11-09T20:44:30.974+01:00 [04480 verbose 'Default'] Getting VIM connection to x.x.x.x...

2013-11-09T20:44:30.974+01:00 [04480 info 'Default'] Connecting to host x.x.x.x on port 443

2013-11-09T20:44:30.974+01:00 [04480 info 'Default'] localVersion is: vim.version.version9

2013-11-09T20:44:31.067+01:00 [04480 info 'Default'] Remote version is: vim.version.version6

2013-11-09T20:44:31.067+01:00 [04480 verbose 'Default'] [VimApi] Local version vim.version.version9 is compatible with remote version vim.version.version6; using remote version

2013-11-09T20:44:31.161+01:00 [04480 info 'Default'] Authenticating user domain\user

2013-11-09T20:44:31.161+01:00 [04480 verbose 'HttpConnectionPool-000009'] HttpConnectionPoolImpl created. maxPoolConnections = 1; idleTimeout = 900000000; maxOpenConnections = 1; maxConnectionAge = 0

2013-11-09T20:44:31.239+01:00 [04480 error 'Default'] [VimResultFilter] Property vim.UserSession,ipAddress not found

2013-11-09T20:44:31.239+01:00 [04480 error 'Default'] [VimResultFilter] Property vim.UserSession,userAgent not found

2013-11-09T20:44:31.239+01:00 [04480 error 'Default'] [VimResultFilter] Property vim.UserSession,callCount not found

2013-11-09T20:44:31.239+01:00 [04480 verbose 'Default'] VimConnectionStore stopping keepalive

2013-11-09T20:44:31.239+01:00 [04480 info 'Default'] Scheduled timer canceled, StopKeepAlive succeeds

2013-11-09T20:44:31.255+01:00 [04480 info 'vmomi.soapStub[8]'] Resetting stub adapter for server <cs p:04e5f398, TCP:x.x.x.x:443> : Closed

2013-11-09T20:44:31.255+01:00 [04480 info 'wizardController'] FillPage()

2013-11-09T20:44:43.537+01:00 [04932 info 'ThreadPool'] Thread enlisted

2013-11-09T20:45:49.353+01:00 [04044 error 'wizardController'] Unable to submit job: converter.fault.ManagedDiskOpenFault

2013-11-09T20:45:49.353+01:00 [04044 verbose 'Locale'] Default resource used for 'ManagedDiskOpenFault.summary' expected in module 'fault'.

2013-11-09T20:45:49.353+01:00 [04052 error 'ConversionState'] Submit job failed: fault.ManagedDiskOpenFault.summary

2013-11-09T20:45:49.353+01:00 [04052 error 'ConverterWizardWindow'] Next/Finish failed: fault.ManagedDiskOpenFault.summary

2013-11-09T20:56:14.827+01:00 [04052 info 'ConverterSession'] Converter data provider created.

2013-11-09T20:56:14.827+01:00 [04052 info 'DiagnosticDataProvider'] Converter::Client::Gui::Common::DiagnosticDataProvider::DownloadSourceDiagnosticFile - Using last known source computer spec:

--> (converter.ComputerSpec) {

-->    dynamicType = <unset>,

-->    location = (converter.ComputerSpec.LiveComputerLocation) {

-->       dynamicType = <unset>,

-->       hostname = "",

-->       port = <unset>,

-->       username = <unset>,

-->       password = <unset>,

-->       osType = "windowsOs",

-->       verifyPeer = <unset>,

-->       sslThumbprint = <unset>,

-->    },

--> }

2013-11-09T20:58:38.784+01:00 [04044 verbose 'HttpConnectionPool-000003'] [RemoveConnection] Connection removed; cnx: <SSL(<io_obj p:0x04b61d28, h:-1, <TCP '0.0.0.0:0'>, <TCP 'x.x.x.x:443'>>)>; pooled: 0

20

Worker Logs...

2013-11-09T21:08:10.160+01:00 [05032 warning 'Default'] [Converter::Util::PopulateSslIdDb] Empty thumbprint for host host.domain.com

2013-11-09T21:08:10.160+01:00 [05032 info 'Default'] GetManagedDiskName: Get disklib file name as vpxa-nfcssl://san1 host.domain/host.domain.vmdk@host.domain:902!52 f1 7c 6d f7 79 e5 a5-8a 33 d2 60 52 a3 48 90

2013-11-09T21:08:10.301+01:00 [05032 warning 'Default'] [,0] SSL_IsVerifyEnabled: failed to open the product registry key. Falling back to default behavior: verification on. LastError = 0

2013-11-09T21:08:10.301+01:00 [05032 warning 'Default'] [,0] SSL: Unknown SSL Error

2013-11-09T21:08:10.301+01:00 [05032 warning 'Default'] [,0] SSL: connect failed

2013-11-09T21:08:10.301+01:00 [05032 warning 'Default'] [,0] [NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error: The remote host certificate has these problems:

-->

--> * The host certificate chain is incomplete.

-->

--> * Host name does not match the subject name(s) in certificate.

-->

--> * unable to get local issuer certificate

2013-11-09T21:08:10.301+01:00 [05032 info 'Default'] Sysimgbase_DiskLib_OpenWithPassPhrase failed with 'NBD_ERR_NETWORK_CONNECT' (error code:2338)

2013-11-09T21:08:10.301+01:00 [05032 info 'Default'] Error 2338 opening disk vpxa-nfcssl://san1 host.domain/host.domain.vmdk@host.domain:902!52 f1 7c 6d f7 79 e5 a5-8a 33 d2 60 52 a3 48 90.

2013-11-09T21:08:10.301+01:00 [05032 warning 'Default'] ERROR 2338 opening disk vpxa-nfcssl://san1 host.domain/host.domain.vmdk@host.domain:902!52 f1 7c 6d f7 79 e5 a5-8a 33 d2 60 52 a3 48 90.

2013-11-09T21:08:10.301+01:00 [05032 error 'Default'] [BaseDiskSetComputer::DoOpen] OpenDisks failed, mntapi error: 37410

2013-11-09T21:08:10.301+01:00 [05032 error 'Default'] [BaseDiskSetComputer::AnalyzeErrorAndThrow] Error occurred when opening disk set, MNTAPI_ERROR = 37410 MNTAPI errorType = 2, errorCode = 2338

2013-11-09T21:08:10.301+01:00 [05032 error 'Default'] TargetVmManagerImpl::CreateVM: Failed to retrieve the storage mapping with error converter.fault.ManagedDiskOpenFault

2013-11-09T21:08:10.301+01:00 [05032 info 'Default'] TargetVmManagerImpl::CreateVM: The target VM will be deleted now.

2013-11-09T21:08:10.301+01:00 [05032 info 'Default'] TargetVmManagerImpl::DeleteVM

2013-11-09T21:08:10.301+01:00 [05032 info 'Default'] Reusing existing VIM connection to x.x.x.x

2013-11-09T21:08:10.347+01:00 [05032 info 'Default'] Destroying vim.VirtualMachine:vm-4998 on x.x.x.x

2013-11-09T21:08:12.519+01:00 [05032 info 'Default'] Scheduled timer canceled, StopKeepAlive succeeds

2013-11-09T21:08:12.535+01:00 [05032 info 'vmomi.soapStub[23]'] Resetting stub adapter for server <cs p:00572178, TCP:x.x.x.x:443> : Closed

I have added the ips, fqdn's and hostname of all the esxi hosts in this cluster including the VC to the local hosts file.

If you need anymore info, just say....

Would really appreciate any help on this.

Many thanks...

Message was edited by: HadEnough001

Hi everyone.

I was used VMware Converter Standalone 6.0 to converter server 2003 on Hyper-V to host ESX of vCenter.

Hyper-V have IP : 10.132.2.200

vCenter have IP: 10.132.2.177

Host ESXi have IP : 10.132.2.192

We haven't policy firewall for 3 IP this. All ports are open in Firewall.

But, when I convertering 1% that have error with status : FAILED: An error occurred during the conversion: 'The operation experienced a network error'

So, Can you help me fix case this ?

Best regards.

Hello,

this error occurs when I try to p2v a Red Hat Enterprise Linux Server release 5.2 (Tikanga) with converter standalone 4, in the first step (specify source), so I can't execute the p2v process.

I think this version of OS is not supported by converter 4, but I need to p2v this server anyway,

so any kind of help will be much appreciated.

Thank you very much!

Hi folks,

when we try to install (as administrator) the actual converter on our windows 2003 std. 32 bit server (domain controller, 1 nic, fully ms patched) we always receive the following error:

Microsoft Visual C++ Runtime Error: program: ... vmware vcenter converter\vmware-converter.exe. The application has requested the Runtime to terminate it in an unusal way.

The eventlog says:

Product: VMware vCenter Converter Standalone -- Error 1920.Service VMware vCenter Converter Server (vmware-converter-server) failed to start. Verify that you have sufficient privileges to start system services.

We have tried to change temp / tmp enviroment, older converter versions, different installation path, changed service account, deleted tmp / registry entries ... Nothing helps !

Anyone got a solution for that ?

Best regards

Frank