Home > Vmware Converter > Vmware Converter Failed Platform-specific Error 2338

Vmware Converter Failed Platform-specific Error 2338


Covered by US Patent. Now the V2V process actually completed after 2.5 days and the server is running good so far! Also with Converter 5.5 you can try to transfer both disks simultaneously try to change data connections per task. I saw a 45min be cut down by 10 mins or so. weblink

Try Free For 30 Days Join & Write a Comment Already a member? It look to be working now after we allowed port 902. Covered by US Patent. Get 1:1 Help Now Advertise Here Enjoyed your answer?

Vmware Converter Detected A Write Error During The Cloning Of Volume

The Converter Error 2338 error is the Hexadecimal format of the error caused. I saw that those errors are mentioned with Converter 4.3, but I'm using Converter 5.1 The source VM is Windows 7SP1   Attaching the log for more information. I had a C drive with an extended "D" partition...Thanks!ReplyDelete42954c90-ecb7-11e1-b58a-000bcdcb8a73August 23, 2012 at 2:13 AMThanks a lots for this info. so stop any MSSQL services before converting. 0 This discussion has been inactive for over a year.

Newer Post Older Post Home Subscribe to: Post Comments (Atom) Search This Blog Loading... Join & Ask a Question Need Help in Real-Time? As for the drives that I am not sure of, I would assume dynamic because they are on dynamic disk but not sure. Chkdsk /b None of it seems to work.

Windows 2003 to be converted, and because you VM is using an old OS, you may need to downgrade the vCenter Converter Standalone 5.5, to 5.0. 0 Message Active 6 KapsZ28, Jan 20, 2015 KapsZ28, Jan 20, 2015 #4 Jan 21, 2015 #5 KapsZ28 2[H]4U Messages: 2,091 Joined: May 29, 2009 Well this is interesting. View the job, right click, export logs, it will be in a zip like so "" Open the zip file, in there open another zip file "" or simular and in All the above actives may result in the deletion or corruption of the entries in the windows system files.

Previously, Jakob was employed for 7,5 years in NNIT (Danish IT service provider owned by Novo Nordisk) working mainly with VMware virtual infrastructure and design. Xml Comment Same issue in different environment. I noticed that you said you tried converting the disks individually to VMware Workstation - but have you tried them individually to the ESXi host (skipping the Workstation)? You may get a better answer to your question by starting a new discussion.

Failed An Error Occurred During The Conversion Converter Fault Fileiofault

Compatibility: Windows 7, 8, Vista, XP Download Size: 6MB Requirements: 300 MHz Processor, 256 MB Ram, 22 MB HDD Limitations: This download is a free evaluation version. This is with SSL enabled. Vmware Converter Detected A Write Error During The Cloning Of Volume Join our community for more solutions or to ask questions. Error: Unable To Clone Volume 'c:'. I am really interested in seeing if there a way to speed this up.   Thanks! 0 0 11/18/13--10:29: Re: Any reason for painfully slow transfer rates with VMWare Converter?

Will you re-paste it. 0 Jalapeno OP bmeiont Jan 16, 2013 at 5:17 UTC   Warrior5Delta wrote: I noticed in the error about block size?  while setting up have a peek at these guys Newer Than: Search this thread only Search this forum only Display results as threads More... Text Quote Post |Replace Attachment Add link Text to display: Where should this link go? GetManagedDiskName: Get disklib file name as vpxa-nfcssl://[STORAGE_NAME] machinename/[email protected]:902!52 e6 48 9e 56 79 78 ed-5f cd 39 28 d9 e1 11 27   This error is the machine that you are A File I/o Error Occurred While Accessing

I ended up converting with the C: drive only and then doing a robocopy to a "new" D: drive that I presented to the VM.  1 Jalapeno OP

I also found this blog post that mentions that changing the network speed fixed it:

I would also run a chkdsk on the source machine. So I ran Got it? 1 week ago VM /ETC 2 years ago A. check over here The Universal Restore technology has much higher success rates than vendor-specific due to it's wider coverage - it can do P2P and V2V and even V2P.

The purpose of the blog is to act as an electronic notepad - to get those things noted that one discovers during daily operations - as well as, hopefully, being helpful I saw that those errors are mentioned with Converter 4.3, but I'm using Converter 5.1 The source VM is Windows 7SP1 Attaching the log for more information. Our own platform runs for now version 4.3 and the remote location run 5.1 I need to import few VM's from the remote location to our own location and trying to

Join & Ask a Question Need Help in Real-Time?

Disclaimer: This website is not affiliated with Wikipedia and should not be confused with the website of Wikipedia, which can be found at Notify me of new posts by email. Also - what percentage is the conversion at when it fails? Connect with top rated Experts 14 Experts available now in Live!

With such big disk I'll say that transfer speed is lowered because files are read one-by-one and written one-by-one, that's because there is a warning about this type of transfer. 0 This tool will scan and diagnose, then repairs, your PC with patent pending technology that fix your windows operating system registry structure. This website should be used for informational purposes only. this content Solved VMWare p2v coversion fails at 1 % Posted on 2013-11-17 VMware 2 Verified Solutions 4 Comments 6,952 Views Last Modified: 2013-11-17 Hi All Currently i have a physical

Instructions To Fix (Converter Error 2338) error you need to follow the steps below: Step 1: Download (Converter Error 2338) Repair Tool Step 2: Click the "Scan" button Are the drives basic or dynamic? The disks are dynamic...RAID 5 config. As for your error, were you ever able to rectify them?

KapsZ28, Jan 20, 2015 KapsZ28, Jan 20, 2015 #2 Jan 20, 2015 #3 gimp [H]ardForum Junkie Messages: 9,205 Joined: Jul 25, 2008 FWIW, I had issues with the latest vCenter Converter. For the first VM, go to Edit Settings and attach the disk from the second VM, 'servername_Ddrive'. After creating a rule which enables traffic between the source server and the server VMware Converter was running on, AND creating a rule which allowed traffic on ports 902 and 443 Usually some firewall could break the connection.

How could I tell? Verify that the converter server and the running source machines have a network access to the source and destination ESX/ESXi hosts." Based on research, it would seem to be a SSL This is ok - as long as the drive has been succesfully cloned, this is what matters (see below). I had to roll back a version or two.

Any help will be highly appreciated. Re: Fails at 1% with error "FAILED: An error occurred during the conversion: 'Platform-specific error 2338' " QNige Jun 21, 2013 11:47 AM (in response to POCEH) I had the same About skip to main | skip to sidebar Virtual Infrastructure Tips - VMware A blog about VMware virtual infrastructure with howto's, tips, and tools. I found this KB article that says it is a "known issue" and that you should convert the disks individually.

Better fit would probably be Acronis Backup & Recovery. Solved Converter 5.1 - Error 2338 Posted on 2013-06-19 VMware 1 Verified Solution 4 Comments 5,362 Views Last Modified: 2013-06-20 Hi, I have several VM's on 2 locations, one datacenter that To fix this you can edit the host file on machine you want to virtualise.