1 person found this helpful
During the conversion of a Windows 2000 SP4 server to a virtual machine, VMware Converter reports that the version of SCSIPORT.SYS may cause problems with a message similar to the following:
"Warning the versions of scsiport.sys on disk (5.0.2195.7017) is inconsistent with that of its replacement. System reconfiguration may not be successful"
If this warning is dismissed and the conversion completes without updating the driver, on boot up the resulting virtual machine will display a blue screen with a STOP 0x1E error (KMODE_EXCEPTION_NOT_HANDLED).
To address this problem, install Microsoft Update Rollup 1 for Windows 2000 SP4 1 Version 2 (Microsoft KB891861). This version was released after the initial release of SRP1 for Windows 2000. A flaw in the original SRP1 package introduces a problematic version of SCSIPORT.SYS on some systems. VMware Converter detects the problematic versions of this driver on the source to prevent the STOP 0x1E error on the resulting virtual machine. Installing the version 2 release or SRP1 will apply the corrected driver to the physical server. After updating SCSIPORT.SYS, you can restart the conversion process without the error.
Reference the following URLs for additional information on the STOP error, and to download Security Rollup Package 1, Version 2:
I am going to check this fix now, and wll let you know by monday as I have my move this weekend.
Thanks for your help and time buddy
VCP on VI3
I also had this issue.
when attempting to import a physical server to clone ( DL380 G1, win2000 adv. sp4) i got the error : "Warning the versions of scsiport.sys on disk (5.0.2195.7017) is inconsistent
I used a scsiport.sys from a winPE CD ie : i386\system32\drivers\
was able to continue with the clone but on boot of the new vm instance i get a blue screen
finally fixed the guest instance by booting it into WinPE and saw C:\winnt\system32\driver\scsiport.sys and C:\winnt\system32\driver\scsiport.bak
I renamed the ,sys to old and the .bak to .sys and was able to boot without issue.
you'r right , this was related to the SCSI port driver.....
I change to LSI Logic from BUS logic and that resolved the issue...... just before changing i need to update the driver first ...
what version of the scsiport.sys file did you use?