Parallels Transporter Failure

I'm try to convert several MS Virtual PC systems. These systems run find under MS VPC. When I use Parallels Transporter, the .vhd file seems to convert ok and I get to the Hard Disk Role screen. See attached picture1.png.

I select bootable disk and Transporter correctly identifies the OS type. See attached picture3.png.

Then Transporter crashes (picture4.png).

Here are the first few lines of the Apple report:

Process: Parallels Transporter [1518]
Path: /Applications/Parallels/Parallels Transporter.app/Contents/MacOS/Parallels Transporter
Identifier: com.parallels.server.transporter
Version: ??? (3540)
Build Info: Parallels-3540.209168~4.0.3540.209168
Code Type: X86 (Native)
Parent Process: launchd [258]

Date/Time: 2008-12-03 11:56:59.275 -0700
OS Version: Mac OS X 10.5.5 (9F33)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000024
Crashed Thread: 12


Any ideas?

Paul

 

1. Please check
http://kb.parallels.com/en/5663
2. If Virtual Machine feets to version please put here

<home>/Library/Logs/Parallels/transporter_cl.log

 

OK, John, it is supported. The source is a MS Virtual Server 2005 system.

Attached is the log.

Paul

 

Any news on this?

Paul

 

Thank you
Case was submitted to developers

 

Thanks, John.

Paul

 

Developers replied
1. Please check file system in virtual machine you are trying to migrate using chkdsk
2. Shutdown it correctly using Start -Shutdown
3. Try to migrate again
4. If it fails please send us crash report for Parallels Transporter from ~/Library/Logs/CrashReporter
5. Also please let me know , you wrote that crash is for all Virtual machine, could you please clarify this

 

Will do! Please stand by.

Paul

 

Hi John,

I have some very good news. The same three VMs that failed previously are now working. I've been scratching my head to figure out why and can only come up with one difference. I am using the same computer (Macbook Pro), but the first time I tried to use Transported on these VMs it failed and now it does not. However, the first time was an upgrade of V3 to V4 3522 and then V4 3540. In between, I removed V4 on this laptop, loaded V3, tested V3, then loaded V4 3540 directly (skipping 3522).

I did perform a chkdsk as you suggested and did not notice any errors but I cannot be absolutely sure there were none.

Perhaps this gives you a clue why it works now, but I'm pretty happy.

Thank you.

Paul

 

Glad to here that problem is resolved
Merry Christmas & Happy Holidays!