Damn agent.internal.fault.PlatformError.summary.

[martinm242]

Hi all,

I try to convert a Win2003 Enterprise Server to a virtual machine using VMware vCenter Converter Standalone Client & Server 4.0.0 Build 146302.

Every single attempt fails and the following error is shown: FAILED: agent.internal.fault.PlatformError.summary

It seems that this is a know issue: http://www.vmware.com/support/converter/doc/releasenotes_conv40.html#knownissues

--

Consecutive conversions of powered-on machines running Windows Server 2000 fail every other time

If you try to convert a powered-on machine running Windows Server

2000 several consecutive times, every second conversion task fails with

the following error in Converter Standalone logs:

agent.internal.fault.PlatformError.summary

.

Workaround: If the conversion task fails, right-click the task in the task list, select Copy As New to create a new conversion task, and run it again.

--

I did so (copied it as new 5 times now) and it does not work at all.

Is there anything I might be overseeing?

Thanks,

Martin

[martinm242]

Hi,

allow me to reply to myself...

The problem was in the firewalls between the physical system to be converted and the ESXi server... with the needed ports opened everything works just fine.

Sorry for the noise!

Cheers,

Martin

[squirrelking]

Thanks for the info, got me thinking when I got this message. For this environment I'm working on, they are not on a domain so name resolution was the issue.

The "Status" of the failed migration says: FAILED: agent.internal.fault.PlatformError.summary

When you look at the exported Converter logs under:

Zip File\Windows\Temp\vmware-temp\vmware-system\agent-task-1.zip\Documents and Settings\All Users\Application Data\VMware\VMware vCenter Converter Standalone\logs\vmware-converter-agent-0.log

You'll see the error "Error: Host address lookup for server" with your ESX server that you were using as the target for the conversion.

Once I put the ESX servers into the Windows host file (on the server I'm trying to clone), the migration kicked off/worked great.

[roccotosaf]

Hi,

same problem converting from phisical machine XP Pro SP2 from a remote vmware server 2.x.

I tried stopping firewalls/antivirus, placing destination on a different network share, running converter directly on the source machine...

Any other suggestions?

Thanks

Rocco

[roccotosaf]

Now it's all right. A problem with vstor2-driver stopped the P2V task.

[ketelhuis]

Thanks,

I got the same error. I was indeed a DNS issue.

grtz,

Arnout