I recently had the job of figuring out why a Windows 2000 Server would blue screen after a P2V. Usually this is from a stop error 0x7B where Windows cannot “see” the boot drive. This one was a 0x1E which is a bit different. When I worked for VMware I use to get this call a lot, so here is the fast instruction set on how to fix it and move on with your day.
Go to a happy Windows 2000 Server that is already booted on VMware ESX and running. IF you have one. [IF not see the post notes.]
Get SCSIPORT.SYS from C:WINNTSYSTEM32drivers and copy it to your desktop.
Boot the failed Win2k VM to Ubuntu 9.04 iso w/network enabled.
Mount the VM’s system drive and create a SMB share with full access.
Rename the old SCSIPORT.SYS to SCSIPORT.SYS.FAIL
Copy the fresh version to your Ubuntu share from your desktop.
Shutdown Ubuntu and boot to new happy Win2k VM. Easy peasy.
MS fracked up the Win2kSP4 rollup and released another version without too many people knowing. But if you were one of the lucky ones that updated early, you got this bad SCSIPORT.SYS file. It was all good until people started P2Ving machines. They would’ve gotten away with it, if it weren’t for those pesky VM kids.
Here is the difference in Build numbers for SCSIPORT.SYS:
Good version: 5.00.2195.7059
Bad version: 5.00.2195.7017
If you do not have a functioning Win2K server VM you will need to apply a hotfix from Microsoft before you convert the physical machine to a VM. Here is the link to the hotfix: http://support.microsoft.com/kb/904374
Here is the VMware KB:
Error Message About SCSIPORT.SYS Version or STOP 0x1E Error on
Resulting Windows 2000 SP4 Virtual Machine