Hi,

RalfP had a similar problem (seehere), try to delete the WINNT\$NtUpdateRollupPackUninstall$ folder on the W2K-server and try the import again. Has something to do with the injection of the scsi-driver.

Message was edited by:
HanzdeVries

Hi,

yes, the import started, but I experienced the same thing as Kris.

Import failed at 100%, vm is ready, after booting I got BSOD saying "inaccessible boot device".

Ralf

Did you edit the old import or did you start a new one?

I could edit and restart the old convert but with the same result, failed at 100%.

Which options did you use during the convert (disk size management, disk space allocation). I tried to resize and set the space dynamic growth.

Will try again with same disk size and direct allocation.

Ralf

The last messages are the following:

IVmdbPipe2Impl operation completed with error: The pipe was ended (translated from Die Pipe wurde beendet).

'Shutting down VMDB service...
'Unregistering callback...
'...done
'[p2vSupport,141] Shutting down App

That's it....

During conversion a lot of

'[imageProcessingTaskWrapper,657] (Re)Start waiting for property updates from VmiReconfigTask::task{3}

'ERROR_MORE_DATA received

and after a while the same [task,234] as descibed by HanzdeVries.

Ralf

I have never seen this behaviour. Did you select "Import all disks and maintain size" or did you select the volumes you wanted to import?


This error is ignorable. Its not related to the import.

This is also explained by the fact that the system disk was not imported.