ERROR: VMware Converter Agent System Error

[The-Dragon]

I’m having problems trying to convert 2 physical machines

attached the error log

[IamTHEvilONE]

The-Dragon,

Welcome to the Forums!

There are too many ways to get the NFC errors you are seeing. One might be that you require double the amount of space on the target data store, others point to duplex settings on the network path being misaligned.

There are a couple documents (http://kb.vmware.com to search) that highlight the NFC Errors you are getting ... take a look at these as the explain better than I can in one post:

An NFC connection fault can occur during a block-level cloning operation

http://kb.vmware.com/kb/1006999/

Checking networking connections between Converter end points

http://kb.vmware.com/kb/1006607/

Investigating network devices and device settings as a cause of VMware Converter failures

http://kb.vmware.com/kb/1004615/

Regards,

EvilOne

1 - Check the documents

2 - Search the forums

3 - Post Question

And remember to award points to those who assist you.

[The-Dragon]

Here is another error log

Please help to fix anyone

[IamTHEvilONE]

You are still getting the NFC Errors. the other problem is that the first partition is taking way too long to convert. I think our connection will time out after an hour. it took about 2 hours for the first drive to finish, which is probably way too long. the nfc errors occur directly between the 2 discs.

There is one lesser known document about something like this:

Cloning fails when source has multiple partitions or disks using the BlockClone method to ESX host

http://kb.vmware.com/kb/1002587/

EvilOne

NOTE: If your problem or questions has been resolved, please mark this thread as answered and award points accordingly.

[The-Dragon]

According to the article

[http://kb.vmware.com/kb/1002587/]

it is easy but my problem is I can’t find “vpxd.cfg or config.xml or source xml file”

Can u please specify where can I find those files.

[The-Dragon]

Common guys a month now and no one answered me on this !!

[theanykey · Accepted solution]

SOAP related timeouts (will be seen as NFC errors in p2v logs but does not answer every "type" of NFC error). This happens if a next physical disk in line to convert is started well after 60 minutes from starting the 1st physical disk of the source machine. For example:

Disk1 - C:\ and D:\

Disk2 - E:\

Disk3 - F:\ G:\

Suppose we started C:\ at 12:00pm. E:\ starts at 12:45pm and F:\ starts at 1:05pm. F:\ would fail since the SOAP session would of timed out at 1:00pm. The results would appear as NFC errors when immediately starting to clone from the F:\ drive. However, if F:\ starts at 12:58pm then the G:\ drive would also complete because we only authenticate per each "physical" disk and not per each partition.

On ESX the file is /etc/vmware/hostd/config.xml

On VC the file is C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\vpxd.cfg

Edit the config.xml and/or vpxd.cfg file to increase the default timeout value. Include a section similar to:

service mgmt-vmware restart