error when convert MS Virtual Server

[mla_]

I try to convert MS VIrtual Server 2005 machine to VMWARE.

The converter is latest 3.0.3

msxml parser is v.6 but I installed v.3 just to try.

The error:

"VPC config file could not be parsed"

Is it something known or I have to install converter in Virtual and convert as physical.

Thanks,

Michael.

[paragsha]

Could you attach the .vmc file that you are pointing to?

[paragsha]

Also I hope you restarted the system after installing MSXML v3. Converter requires MSXML v 2.6 or 3 or 4 to import VPC VMs.

[mla_]

yes I restarted the server.

please see attach....

thanks,

Michael.

[paragsha]

I installed Converter 3.0.3 GA (same build) on a XP machine with MSXML 3 installed on it. I changed your vpc file to point it to a VHD that I have locally on my machine and everything worked fine. This should be a setup issue on your computer. My guess is still that converter is not seeing the appropiate version of MSXML installed on your system (maybe due problems with the installation?). If you attach the converter logs I can confirm this.

Also there are tools/scripts that can tell you the versions of MSXML installed on your system. Try one of these to ensure that MSXML 2.6 or 3 or 4 is installed on your system.

http://support.microsoft.com/kb/278674

http://www.thescripts.com/forum/thread553198.html

[mla_]

Thank you very much for your time.

I will check MSXML and will try again. I will be on the site in question Thursday.

Converter and MSXML installation I did remotely.

Thanks again.

[mla_]

see zip please.

May be you can find something...

thanks.

[paragsha]

These do not have the converter agent logs (only the client logs are present). Use converter to collect the logs and it will include both the agent and client logs.

[theanykey]

vmware-client.log (capture a record on the source)

- Contains actions taken on the Converter application are written here.

- Does NOT contain import/reconfiguration information

- Is stored under the user’s (the user who ran the Converter Application) temp directory.

vmware-converter.log (capture a record on the system where Converter is installed)

- Contains information regarding the import/reconfiguration steps taken by the agent when converting the physical/virtual machine.

- Is available in the Source Physical Machine OS’s temp directory (C:\Windows\Temp\vmware-temp)

When you do a remote conversion, the log package (file->export logs) may not include the vmware-converter.log files. If this is the case, you will need to manually grab them from the source machine.

[mla_]

Here is a converter log.

I copied folder with MS virtual machine to alternate pc and trying to convert locally.

Appreciate your help.

Michael.

[theanykey]

Impersonating user mabramovich

source:(sysimage.VPCSourceVMSpec)

vmcFilePath = "F:\!BES backup\BES\BlackBerry Server\BlackBerry Server.vmc"

Using temp dir C:\WINDOWS\TEMP\vmware-temp\vmware-mabramovich-1220\temp-wrapper.0

CoCreateInstance XML Document failed hr: -2147221164

InitMSXML failed hr: -2147221164

Could not parse the VMC configuration file

You can try moving the vmc image to another directory that does not contain ! in the path.

If that fails, try powering the vmc image on and ensure it is powered off (not suspended)

Alternatively, simply power on the VMC image, install converter inside the running VM and convert it as you would convert a physical machine.

[paragsha]

Hi Michael,

Like I mentioned earlier, this is a setup issue with your MSXML 3.0 not registered properly. The error code -2147221164 (0x80040154) confirms this. I am not an expert on MSXML installation/registration but I am sure that MSXML is what's causing your problem. It is not un-common that installations of COM components (in our case MSXML) failing partially/siliently due to various anti-virus softwares.

You might want to try

a. A different system

b. Uninstall, re-install MSXML 3. Disable anti-virus while installing, make sure you have admin privileges.

c. Try other versions of MSXML (maybe 4.0)

Also having ! in your directory name would not be an issue.