Quantcast
Channel: VMware Communities: Message List - Converter Standalone
Viewing all articles
Browse latest Browse all 8478

Failed Conversion - Possible controlsetXXX issue?

$
0
0

I'm having an issue P2Ving a machine and I think I have finally traced back my issue and just wanted to throw this out to everyone.  I have had a ticket open for awhile now with VMWare.

 

My currentcontrolset points to controlset015 instead of 001 (or 002) due to some issues with this particular server some time in late 2008.  My VMWare Converter fails every time at 98% and the VM is non-bootable with a BSOD STOP error of 7b.   A re-run of the configuration also fails.  I have been struggling to figure out why and stumbled onto a fix to get the machine to at least boot, partially.  I injected the SAS drivers and then enabled them to start in ControlSet015 (in lieu of most KB articles which say 001 or 002).  That booted the machine but it was still non-functional since the other drivers did not exist. 

 

I began to really dig into the logs and found this: 

 

2014-02-20T10:26:56.150-05:00 [07204 warning 'Default'] ERROR 2 opening key mntApi69177312230355024\ControlSet0015.


Note the key is ControlSet0015, not ControlSet015.  This got me to thinking, maybe Converter is taking the Select keys and adding 'ControlSet00' to the number listed, thereby adding too many 0s when a controlset number has two digits.  I did a test and changed the default controlset to 31 and re-ran a configuration and was greeted with:


2014-03-10T14:25:39.439-04:00 [12060 warning 'Default'] ERROR: Unable to open key mntApi33130316230358670\ControlSet0031.


Aha, so I think that this is it.  Anyone have any ideas and/or workarounds?  Obviously I'd like to just ditch this server and start fresh but that isn't an option, I'm afraid.


Viewing all articles
Browse latest Browse all 8478

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>