Home > Vmware Converter > Vmware Converter Platform Specific Error 2338

Vmware Converter Platform Specific Error 2338

For more information, see Support for virtual machine disks larger than 2 TB in vSphere 5.5 (2058287). Let me know if you want any more information about the error that I got. Get 1:1 Help Now Advertise Here Enjoyed your answer? or install it on the source server ?     FAILED: An error occurred during the conversion:'Platform-specific error 2338'VMWare p2v coversion fails at 1 % 0 0 11/17/13--09:41: Re: VMWare p2v weblink

The physical Windows server is in the same DC as our ESXi servers and vCenter. Unfortunately, that's incorrect. Creating your account only takes a few minutes. 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. Read More Here

Any help will be highly appreciated 0 Question by:cloudbase Facebook Twitter LinkedIn Google LVL 5 Best Solution byAbhishekJha Refer below Vmware thread Go to Solution 4 Comments Message Author Any ideas other than supposedly removing and re-adding the ESXi hosts into vCenter? Join Now I am in the process of converting 2 physical servers into virtual server using tghe latest vmware converter. Both subnets have full access to each other.

I found an old ESXi host that isn't attached to vCenter and so far it looks like the data is copying. Newer Than: Search this thread only Search this forum only Display results as threads More... These six sources will help you identify the most popular threat actor tactics, techniques, and procedures (TTPs). That geekcubo link didnt take me any where.

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 you can also give these two a try if your environment is up to spec. Horizon and Skype for Business galcontactsThis is an archived post. When I try converting just the C:\ into a vmware workstation virtual machine and then onto the esxi host, no problems.

Recent Posts Menu Log in or Sign up [H]ard|Forum Forums > Bits & Bytes > Virtualized Computing > Unable to P2V using vCenter Converter Discussion in 'Virtualized Computing' started by KapsZ28, As for your error, were you ever able to rectify them? All rights reserved. permalinkembedsaveparentgive gold[–]Gatorvi[VCP] 0 points1 point2 points 1 year ago(0 children)I am very happy with 5.5 using it 2-3 times a week lately permalinkembedsaveparentgive goldaboutblogaboutsource codeadvertisejobshelpsite rulesFAQwikireddiquettetransparencycontact usapps & toolsReddit for iPhoneReddit for Androidmobile

yes no add cancel older | 1 | .... | 32 | 33 | 34 | (Page 35) | 36 | 37 | 38 | .... | 239 | newer HOME Though for a 100MB system volume it copied at block level, that finished in 8 seconds according to the Converter log. Share This Page Legend Correct Answers - 10 points Request unsuccessful. Everything else is beyond your control 0 0 11/18/13--12:16: Re: Any reason for painfully slow transfer rates with VMWare Converter?

If you make a post and then can't find it, it might have been snatched away. have a peek at these guys

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 Restore will create the VM (all the settings, like RAM, can be tuned) and also will take care of OS settings and drivers. Covered by US Patent.

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 It's not recommended?   @Aiden1, thanks. Join Now For immediate help use Live now! so stop any MSSQL services before converting. 0 This discussion has been inactive for over a year.

This is from another thread, credit to leonhardtla     leonhardtla wrote:   Checks this KB: VMware KB: vCenter Converter fails to import machine at 1%   Resolution   To resolve About Advertising Privacy Terms Help Sitemap × Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up Incapsula incident ID: 277000430067888066-284690197836530361 Request unsuccessful.

Help Desk » Inventory » Monitor » Community » Forums Search Forums Recent Posts Members Notable Members Current Visitors Recent Activity New Profile Posts Search Log in or Sign up Menu

How could I tell?

Converter does not report all disks and volumes present on the system while converting a powered-on source machine running Windows operating system This issue is caused by a bug in 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 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.

On 5.0 and 5.1 I have disabled SSL Encryption and while doing a local P2V from the physical machine or a P2V from a remote machine (all on a Gigabit LAN I had to roll back a version or two. check below post If vcenter and 2003 servers are in different subnets over firewall, then follow steps in below article 0 LVL 117 Overall: Level 117 VMware 109 this content Connect with top rated Experts 14 Experts available now in Live!