VMware Converter requests SCSIPORT.SYS, but does not accept it

When virtualizing a Windows 2000 server using VMware Converter, you may receive a message stating that the version of SCSIPORT.SYS on the source system must be upgraded. The Converter requests version requested is 5.0.2195.7017, however even after providing this version of the file, the converter complains that you may encounter problems with that version and will not proceed. Likewise, if you supply earlier versions (e.g. 5.0.2195.6713) or later version (e.g. 5.0.2195.7059) it may complain that these versions will cause problems and you will be unable to convert the source system.

In order to progress beyond this point, we found that the SCSIPORT.SYS file from a Windows XP Professional SP2 workstation (version 5.1.2600.2180) was accepted by the Converter. This file can be found in C:\Windows\System32\Drivers.

In our testing, the source server already had the version 7017 driver installed (which made it even stranger that it was complaininga bout it). After the conversion, the server booted fine, and when we checked the file it was not the XP version (obviously), but rather the original 7017 file was still there and the server seemed to be running fine.

Whatever the outcome, after the conversion is complete, it is recommended that you replace the driver with the version from the Service Pack 4 Update Rollup 1 V2. The version of this file is 5.0.2195.7059.

To replace the file:

If you don't already have a copy of the right version of SCSIPORT.SYS, download it (KB891861). Run the executable from a command-prompt with the /X:pathname to extract the files without installing.
Add the newly converted vmdk temporarily as a secondary disk to an existing Windows virtual machine.
Start the existing virtual machine. Browse the secondary drive (the mounted vmdk file from the converted server) to %WINDIR%\System32\Drivers and copy in version 7059 of the SCSIPORT.SYS file.
Shut down the temporary machine, remove the secondary hard drive mapping and start up the original converted server.

Author: ASAK
Created: Oct 26 2007
Categories: VMware ESX Server
TechByte #158

Warning: By visiting this site and/or by using any information contained herein, you agree to the Techbytes.ca terms of use.

Comment posted by 'les rigolos' on Feb 7 2008 @ 11:57:36
Thanks a lot for your help... It works fine.... Bye from france...
Comment posted by 'Justin' on Feb 11 2008 @ 19:15:27
Thanks ASAK - works for me too and saved me some time
Comment posted by 'Anonymous' on Mar 28 2008 @ 20:16:55
This worked once I installed another vmware player XP image, might put that you i manually edited the vmx file with 2 lines to get it to see the second Virtual Machine as a second drive.
Comment posted by 'DaveT' on Apr 20 2008 @ 15:30:53
Thanks, slight variation: Converter wanted 5.0.2195.7017, mine is 5.00.2195.7017 (note 00, maybe that is problem?). I used 5.1.2600.2180 from my XP (SP?) machine, it accepted that in converter, have not tried to run it.
Comment posted by 'Virtual MDK' on Jun 5 2008 @ 03:06:50
This driver may cause issues however; let's face fact's, fix the problem at it's root and fix the service pack situation first and foremost. Either fix it in the physical realm, or AFTER the fact. To fix the blue screen - simply choose the 2nd repair option. Thanks Bill.