VMware vSphere

 View Only
  • 1.  Converter sysprep error Read failed, error = 2

    Posted Jul 02, 2008 08:56 AM

    Hello

    I am running vmware converter to duplicate a VM to another VM, I have issues with the sysprep part.

    The conversion seems to run fine until step 3 : Preparing target virtual machine, converter says ERROR : Unkown error returned by VMware Converter agent.

    Agent log shows :

    Setting param Unattended.InstallFilesPath to value \sysprep\i386

    Setting param GuiUnattended.OemSkipWelcome to value 1

    Setting param GuiUnattended.OEMSkipRegional to value 1

    Setting param Networking.InstallDefaultComponents to value Yes

    Setting param GuiUnattended.AdminPassword to value xxxxx

    Setting param GuiUnattended.TimeZone to value 105

    Setting param UserData.FullName to value arkema

    Setting param UserData.OrgName to value arkema

    Setting param UserData.ComputerName to value ACHC1STMP1VMVM7

    Setting param Identification.JoinDomain to value INT

    Setting param Identification.DomainAdmin to value a1017084

    Setting param Identification.DomainAdminPassword to value xxxxx

    Setting param LicenseFilePrintData.AutoMode to value PerServer

    Setting param LicenseFilePrintData.AutoUsers to value 5

    Added nic setting cmd guestcustutil.exe setupNic -o 1 -t 0

    Added custom command guestcustutil.exe cleanBootExecute

    Sysprep output dir: C:/WINNT/TEMP/vmware-temp/sysprep, verify unattended: true

    All supporting files copied successfully

    Copied file Resources\bootrun.exe to directory C:/WINNT/TEMP/vmware-temp/sysprep/i386/$OEM$

    Copied file Resources\bootrunMsg.dll to directory C:/WINNT/TEMP/vmware-temp/sysprep/i386/$OEM$

    Copied file Resources\finalizationsetup.bat to directory C:/WINNT/TEMP/vmware-temp/sysprep/i386/$OEM$

    Copied file Resources\guestcustutil.exe to directory C:/WINNT/TEMP/vmware-temp/sysprep/i386/$OEM$

    Copied file Resources\loginblocker.exe to directory C:/WINNT/TEMP/vmware-temp/sysprep/i386/$OEM$

    Copied file Resources\imgcust-reboot.exe to directory C:/WINNT/TEMP/vmware-temp/sysprep/i386/$OEM$

    Copied custom command files successfully.

    sysprepDeployRoot: C:\sysprep\2003SP2

    sysprepOptions: -quiet -reboot -mini -reseal

    Create sysprep file package. Params:

    file = C:\WINNT\TEMP\vmware-temp\deployPkg.cab

    binary dir = Resources

    options = -quiet -reboot -mini -reseal

    config = C:\WINNT\TEMP\vmware-temp\sysprep

    sysprep = C:\sysprep\2003SP2

    tools =

    native =

    nativeArgs =

    Successfully created file C:\WINNT\TEMP\imc37.tmp

    Creating cab file imc37.tmp

    Getting temp file C:\WINNT\TEMP\41

    Opening C:\WINNT\TEMP\41...

    Getting temp file C:\WINNT\TEMP\18467

    Opening C:\WINNT\TEMP\18467...

    Getting temp file C:\WINNT\TEMP\6334

    Opening C:\WINNT\TEMP\6334...

    Getting temp file C:\WINNT\TEMP\26500

    Opening C:\WINNT\TEMP\26500...

    Getting temp file C:\WINNT\TEMP\19169

    Opening C:\WINNT\TEMP\19169...

    Adding Resources\guestcustutil.exe as guestcustutil.exe

    Read failed, error = 2

    Read failed, error = 2

    Adding Resources\imgcust-reboot.exe as imgcust-reboot.exe

    Read failed, error = 2

    Read failed, error = 2

    Adding C:\WINNT\TEMP\vmware-temp\sysprep\i386\$OEM$\bootrun.exe as sysprep\i386\$OEM$\bootrun.exe

    Read failed, error = 2

    Read failed, error = 2

    Adding C:\WINNT\TEMP\vmware-temp\sysprep\i386\$OEM$\bootrunMsg.dll as sysprep\i386\$OEM$\bootrunMsg.dll

    Read failed, error = 2

    Read failed, error = 2

    Adding C:\WINNT\TEMP\vmware-temp\sysprep\i386\$OEM$\cmdlines.txt as sysprep\i386\$OEM$\cmdlines.txt

    Read failed, error = 2

    Read failed, error = 2

    Adding C:\WINNT\TEMP\vmware-temp\sysprep\i386\$OEM$\finalizationsetup.bat as sysprep\i386\$OEM$\finalizationsetup.bat

    Read failed, error = 2

    Read failed, error = 2

    Adding C:\WINNT\TEMP\vmware-temp\sysprep\i386\$OEM$\finalize.bat as sysprep\i386\$OEM$\finalize.bat

    Read failed, error = 2

    Read failed, error = 2

    Adding C:\WINNT\TEMP\vmware-temp\sysprep\i386\$OEM$\guestcustutil.exe as sysprep\i386\$OEM$\guestcustutil.exe

    Read failed, error = 2

    Read failed, error = 2

    Adding C:\WINNT\TEMP\vmware-temp\sysprep\i386\$OEM$\imgcust-reboot.exe as sysprep\i386\$OEM$\imgcust-reboot.exe

    Read failed, error = 2

    Read failed, error = 2

    Adding C:\WINNT\TEMP\vmware-temp\sysprep\i386\$OEM$\loginblocker.exe as sysprep\i386\$OEM$\loginblocker.exe

    Read failed, error = 2

    Read failed, error = 2

    Adding C:\WINNT\TEMP\vmware-temp\sysprep\sysprep.inf as sysprep\sysprep.inf

    Read failed, error = 2

    Read failed, error = 2

    Adding C:\sysprep\2003SP2\setupcl.exe as deploy\setupcl.exe

    Read failed, error = 2

    Read failed, error = 2

    Adding C:\sysprep\2003SP2\sysprep.exe as deploy\sysprep.exe

    Read failed, error = 2

    Read failed, error = 2

    Flushing...

    Getting temp file C:\WINNT\TEMP\15724

    Opening C:\WINNT\TEMP\15724...

    Getting temp file C:\WINNT\TEMP\11478

    Opening C:\WINNT\TEMP\11478...

    Read failed, error = 2

    Added file guestcustutil.exe

    Added file imgcust-reboot.exe

    Added file sysprep\i386\$OEM$\bootrun.exe

    Added file sysprep\i386\$OEM$\bootrunMsg.dll

    Added file sysprep\i386\$OEM$\cmdlines.txt

    Added file sysprep\i386\$OEM$\finalizationsetup.bat

    Added file sysprep\i386\$OEM$\finalize.bat

    Read failed, error = 2

    Added file sysprep\i386\$OEM$\guestcustutil.exe

    Read failed, error = 2

    Added file sysprep\i386\$OEM$\imgcust-reboot.exe

    Read failed, error = 2

    Added file sysprep\i386\$OEM$\loginblocker.exe

    Read failed, error = 2

    Added file sysprep\sysprep.inf

    Read failed, error = 2

    Added file deploy\setupcl.exe

    Read failed, error = 2

    Added file deploy\sysprep.exe

    Read failed, error = 2

    Deleting C:\WINNT\TEMP\41...

    Deleting C:\WINNT\TEMP\18467...

    Opening C:\WINNT\TEMP\imc37.tmp...

    Read failed, error = 2

    Read failed, error = 2

    Read failed, error = 2

    Read failed, error = 2

    Read failed, error = 2

    Deleting C:\WINNT\TEMP\6334...

    Deleting C:\WINNT\TEMP\26500...

    Deleting C:\WINNT\TEMP\19169...

    Getting temp file C:\WINNT\TEMP\29358

    Opening C:\WINNT\TEMP\29358...

    Getting temp file C:\WINNT\TEMP\26962

    Opening C:\WINNT\TEMP\26962...

    Getting temp file C:\WINNT\TEMP\24464

    Opening C:\WINNT\TEMP\24464...

    Deleting C:\WINNT\TEMP\15724...

    Deleting C:\WINNT\TEMP\11478...

    Deleting C:\WINNT\TEMP\29358...

    Deleting C:\WINNT\TEMP\26962...

    Deleting C:\WINNT\TEMP\24464...

    Successfully deleted file/directory C:\WINNT\TEMP\imc37.tmp

    1 volumes found

    Ant hint ?



  • 2.  RE: Converter sysprep error Read failed, error = 2

    Posted Jul 02, 2008 08:32 PM

    the error=2 lines on a sysprep function is normal. please attach the entire log file please.



  • 3.  RE: Converter sysprep error Read failed, error = 2

    Posted Jul 03, 2008 09:31 AM

    Here is the full log file



  • 4.  RE: Converter sysprep error Read failed, error = 2

    Posted Jul 03, 2008 03:17 PM

    Live OS version: Windows 2000 edition: Workstation/Professional root:WINNT SrvPack:4 SMP:1 64:0 Ver:5.0

    Tells me the source is Windows 2000-sp4

    sysprepDeployRoot: C:\sysprep\2003SP2

    Tells me chances are you are using windows 2003-sp2 sysprep binaries. This means you have applied the wrong sysprep files to the source OS.

    http://support.microsoft.com/kb/820196

    The Windows 2000 Resource Kit Deployment Tools are not automatically installed when you install Windows 2000 SP4. The updated Deployment Tools are available in the Support\Tools\Deploy.cab file on the Windows 2000 SP4 CD-ROM. To download this file, visit the following Microsoft Web site:

    http://technet.microsoft.com/en-us/windowsserver/2000/bb735341.aspx

    Important Do not run these tools on Windows 2000 Datacenter Server without first consulting your Original Equipment Manufacturer (OEM).



  • 5.  RE: Converter sysprep error Read failed, error = 2

    Posted Jul 04, 2008 07:16 AM

    I don't think so, I am running Converter on a windows 2000 host. From this host I convert a 2K3 VM to another VM and the sysprep dies at the end of the conversion.

    Is it problem ? Do I need at least a 2K3 to convert a 2K3 image ?

    Thanks



  • 6.  RE: Converter sysprep error Read failed, error = 2
    Best Answer

    Posted Jul 07, 2008 02:37 PM

    Just to make sure I follow ...

    you have installed converter onto a windows 2000 physical host?

    you are converting a windows 2003 VM to a new VM?

    If so, you need to install converter onto an OS of the same value or newer. So in order to convert 2003, you need to have converter either installed within the 2003 VM directly or on another 2003. Using windows XP should be fine in this case but the best practice would be to install converter directly onto the machine you are converting.

    also make note of the following...

    http://www.vmware.com/support/converter/doc/releasenotes_conv303.html

    Customization is not applied if a virtual machine is manually restarted after running the Configure Machine option

    The process for customization occurs in this order:

    1. Customize the virtual machine image with Converter and wait for 100 percent completion.

    2. Power on the virtual machine.

    3. Wait for it to reboot automatically.

    4. Sysprep processes the customizations.

    5. Sysprep reboots the virtual machine.

    6. The Windows operating system loads, and the network configurations occur.

    If you manually reboot the virtual machine after step 2, without waiting for it to automatically reboot, the customization process will break. If Windows discovers new hardware and asks you to reboot and you select YES, the customization process will also break. In both scenarios, customization settings are not applied to the virtual machine. You must wait for the machine to automatically reboot twice before the customization settings are applied and you can safely log on.