Like Show 0 Likes (0) Actions 7. I also changed the useSSL on the Converter VM to "false". CONTINUE READING Join & Write a Comment Already a member? Didn't seem to make a difference. check over here
Join Now For immediate help use Live now! Same error occurred. I can't remember exactly what, but it just didn't work. 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 https://communities.vmware.com/thread/449613?start=0&tstart=0
Keith 0 Featured Post 6 Surprising Benefits of Threat Intelligence Promoted by Recorded Future All sorts of threat intelligence is available on the web. After that, you can boot the VM now containing both drives. KapsZ28, Jan 21, 2015 KapsZ28, Jan 21, 2015 #5 Jan 25, 2015 #6 REDYOUCH [H]ardness Supreme Messages: 4,474 Joined: Mar 17, 2001 Connect to the target ESX server directly, not through This issue is not observed in Service Pack 1 for Windows XP Professional 64-bit.
Is VSS is in good shape? only took about 8hrs... An alternative workaround that will most likely work as well is to do a cold clone. please share the exact transfer rate if its around 3 mbps then there might be network configuration problem . If I have lost confidence in myself, I have the universe
I've tried rebooting, running the Converter as Administrator. Anyone run across something similar? Reply Subscribe RELATED TOPICS: VMWare Converter Issues no encrytion vmware converter still slow VMware Converter agent install loop   16 Replies Habanero Thanks in advance, 7 commentsshareall 7 commentssorted by: besttopnewcontroversialoldrandomq&alive (beta)[–]killer833 2 points3 points4 points 1 year ago*(2 children)whats the error? The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.
Even installed the Converter on the server I am trying to convert. https://www.experts-exchange.com/questions/28161376/Converter-5-1-Error-2338.html You could try cold cloning? just running the latest updates from tuesday - will reboot tonight... A standard network interface card, can be used to connect and existing ESXi server to a remote iSCS… VMware How to create and use VMs TAGs in Veeam Backup Jobs – Other suggestion was removing Static IP on the server and use dhcp before conversion...
and try again. 0 0 11/18/13--08:37: Re: Any reason for painfully slow transfer rates with VMWare Converter? Quoth KB2003813: Frequently Asked Questions on VMware vSphere 5.x for VMFS-5: VMFS5 in ESXi 5.5 now supports upto 62 TB VMDK and non-passthrough RDM. Connect with top rated Experts 15 Experts available now in Live! http://prcflow.com/vmware-converter/vmware-converter-platform-specific-error-18.html I had to roll back a version or two.
So I loaded the converter directly on the server itself - This fails instantly with "A general System error occurred: Unknown Error" ------------------------- trimmed log section with error --------------------------- 2012-06-10T23:40:05.932-07:00 [02488 None of it seems to work. not too bad really... 0 Mace OP George1421 Jun 16, 2012 at 1:59 UTC Hey, I'm glad you got it to migrate. Sometimes you are the
The actual error should be in the Converter Agent log on the source machine, but I expect it to be something like "Unable to open a destination virtual disk". This example is showing remote access and installation using a Dell server. Re: Converter 5.1 - error 2338 vipclubber Feb 23, 2014 9:24 PM (in response to tomerleib) THIS IS THE DNS ERROR of not being able to resolve FQDN name of the Workaround: Update to the latest service pack where the issue is resolved.
First Name Please enter a first name Last Name Please enter a last name Email We will never share this with anyone. Covered by US Patent. kept failing on the D: volume before I removed all AD - DC via DCPromo and changing of FMSO roles. http://prcflow.com/vmware-converter/failed-an-error-occurred-during-the-conversion-39-platform-specific-error-2338-39.html The converter is installed on dedicated VM with external NIC that is reachable from the remote location and internal NIC that is connected to the vcenter and the ESXi hosts.
This issue is not observed in Service Pack 1 for Windows XP Professional 64-bit.