An Error Occurred During The Conversion
Contents |
Followers Follow VMware 396221 Followers Follow Join the Community! Creating your account only takes a few minutes. Join Now I am in the
Failed An Error Occurred During The Conversion 'the Operation Experienced A Network Error'
process of converting 2 physical servers into virtual server using tghe latest failed an error occurred during the conversion 'platform-specific error 3' vmware converter. When I try to convert the physical machine straight to the esxi 5 host, I
Failed An Error Occurred During The Conversion 'platform-specific Error 2338'
get an error that states: FAILED: An error occurred during the conversion: 'BlockLevelVolumeCloneMgr::CloneVolume: Detected a write error during the cloning of volume \WindowsBitmapDriverVolumeId=[2E-E6-5D-9E-00-00-80-02-00-00-00-00]. Error: 37409 (type: 1, code: 2338)' https://kb.vmware.com/kb/2006659 So I tried a different route, converting it into a workstation virtual machine then converting onto the esxi host machine. Both these machine have two drives. c:\ and d:\. I read that if split up the conversion by drives then that might work. When I try converting just the C:\ into a vmware workstation virtual machine and https://community.spiceworks.com/topic/288806-vmware-p2v-conversions-fail then onto the esxi host, no problems. But when I try the d:\ drive or converting both drives in a single task, it failes with this error: FAILED: A general system error occurred: SQL_CANTOPEN: unable to open database file Can anyone help me out, Its been hassling me for a while now and I forget I have folks out there who know a whole lot more about these things than I do. Appreciative for all help, BT Reply Subscribe View Best Answer RELATED TOPICS: Vmware conversions - P2V thick or thin ? VMware Free edition & P2V conversions p2v vmware deployment build, I appreciate your insight   15 Replies Chipotle OP Alaerus Jan 8, 2013 at 4:37 UTC Do you have the option of getting the machine offline? If so, what I do is to clone the system using Acronis True Image, then convert that image to a VM using the VMWare Standalone Converter. I've had better success with this method personally rather than cloning a live syst
Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create https://www.experts-exchange.com/questions/28119911/Vmware-5-1-P2-V-error-FAILED-An-error-occurred-during-the-conversion-'BlockLevelVolumeCloneMgr-CloneVolume-Detected-a-write-error-during-the-cloning-of-volume-WindowsBitmapDriverVolumeId.html a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups https://payze.wordpress.com/tag/converter-fault-fileiofault/ Website Testing Store Headlines Experts Exchange > Questions > Vmware 5.1 P2 V error FAILED: An error occurred during the conversion: 'BlockLevelVolumeCloneMgr::CloneVolume: Detected a write error during the cloning an error of volume \WindowsBitmapDriverVolumeId Want to Advertise Here? Solved Vmware 5.1 P2 V error FAILED: An error occurred during the conversion: 'BlockLevelVolumeCloneMgr::CloneVolume: Detected a write error during the cloning of volume \WindowsBitmapDriverVolumeId Posted on 2013-05-06 VMware Virtualization 1 Verified Solution 7 Comments 8,581 Views Last Modified: 2013-05-10 While running a P2V of a desktop PC receive error FAILED: An error an error occurred occurred during the conversion: 'BlockLevelVolumeCloneMgr::CloneVolume: Detected a write error during the cloning of volume \WindowsBitmapDriverVolumeId=[8D-0B-8D-0B-00-7E-00-00-00-00-00-00]. Error: 37409 (type: 1, code: 2338)' Any suggestions would be appreciated? 0 Question by:bergquistcompany Facebook Twitter LinkedIn Google LVL 42 Active 1 day ago Best Solution bypaulsolov If you can login than you just need to run vmware tools to put the drivers on the system. Because it is an OEM copy the VM may not work properly due to the install not seeing OEM hardware. Go to Solution 7 Comments LVL 42 Overall: Level 42 VMware 30 Virtualization 16 Message Active 1 day ago Expert Comment by:paulsolov2013-05-06 What type of OS? What type of hardware and windows license type? 0 LVL 116 Overall: Level 116 VMware 108 Virtualization 69 Message Active today Expert Comment by:Andrew Hancock (VMware vExpert / EE MVE)2013-05-07 at what percentage did this occur? Have you checked the physical disk for errors? See my EE Articles HOW TO: Synchronize changes when completing a P2V or V2V with VMware vCenter Converter Standalone 5
2 comments Problem I have had some with regards to converting Hyper-V VM's to VMware Infrastructure VM's using the VMware vCenter Converter Standalone, and one of the errors (that I remember) was FAILED: An error occurred during the conversion: ‘converter.fault.FileIOFault'. I have also experienced very slow conversions of these Hyper-V VM's, for example 2-3 days. Explanation Converter uses NFC (a proprietary VMware protocol) for cloning to managed destinations. Security was enhanced by encrypting the data, however this has a significant performance affect and in turn can cause errors with regards to IO at various stages of the conversion. Resolution Switching off SSL encryption has prevented all errors and performance is vastly better (e.g. instead of 2-3 days now conversions are taking 2-3 hours). Just do the following; Open the converter-worker.xml configuration file. It is located in "%ALLUSERSPROFILE%\VMware\VMware vCenter Converter Standalone" folder for Windows Vista or newer or in "%ALLUSERSPROFILE%\Application Data\VMware\VMware vCenter Converter Standalone" for older Windows versions. Search for the block of code starting with