VMware
 

Knowledge Base

Search the Knowledge Base:

Products:
Search In:
 

Troubleshooting damaged operating system components that cause conversion failure

Symptoms

  • The free disk space or used disk space reported in the New Conversion wizard is incorrect.
  • The conversion fails almost immediately after clicking Finish in the New Conversion wizard
  • You receive the following errors:
    • Failed to take snapshot of the source volume
    • Error opening disk device: Incorrect function (1)
    • Failed to get capacity for \\.\PhysicalDrive0 : error opening disk device: Incorrect function (1)
    • sysimage.fault.OsVersionNotFound
    • Warning: no attached disks were detected.
    • The COM Server with CLSID {65ee1dba-8ff4-4a58-ac1c-3470ee2f376a} and name SW_PROV cannot be started. [0x80070422]

Resolution

Windows NT and Windows 2000

To troubleshooting damaged operating system components that cause a conversion failure in Windows NT and Windows 2000:

  1. Update the disk controller driver to the latest version. For related information, see Conversion fails on a source running Windows NT with a Dell PERC 3 or 4 disk controller (1001559) .
  2. Confirm that the VMware Converter related services are started on the source operating system.

    To ensure the VMware related services are started:

    1. Open a command prompt. For more information, see Opening a command or shell prompt (1003892) .
    2. Run the following commands:

      net start vstor2-p2v30
      net start ufad-p2v
      net start "tcp/ip netbios helper service"
      net start stcp2v30
  3. Confirm that there are no errors in the system Event Log. Check for errors during the time period when the conversion was attempted.
    • For Windows NT:
      1. Click Start > Run.
      2. Type eventvwr and press Enter.
      3. Check for errors from these sources: rpcss, com, dcom, Service Control Manager, vstor2-p2v30, ufad-p2v.
    • For Windows 2000:
    1. Click Start > Control Panel > Administrative Tools > Event Viewer.
    2. Check for errors from these sources: COM, DCOM, or Service Control Manager (SCM), VMware Converter.

  4. Restart the source server. This may restore the functionality of certain OS components.

Windows XP and 2003

  1. Update the disk controller driver to the latest version.
  2. Confirm that the VMware Converter related services are started on the source operating system.

    To ensure the VMware related services are started:

    1. Open a command prompt. For more information, see Opening a command or shell prompt (1003892) .
    2. Run the following commands:

      net start vstor2-p2v30
      net start ufad-p2v
      net start "tcp/ip netbios helper"
      net start swprv
      net start vss

    3. Confirm that there are no errors in the system Event Log from these sources: VSS, COM, DCOM, or Service Control Manager (SCM), VMware Converter. Check for errors during the time period when the conversion was attempted.

      To view the Event Log, click Start > Control Panel > Administrative Tools > Event Viewer.

    4. Verify that there are no effective Group Policies (GPOs) which are restricting the Volume Shadow Copy services from running.

      Click Start > Run. Type rsop.msc . If you are unsure of the GPOs in place, try removing the source server from the domain. This should disable the GPOs in effect from Active Directory.

    5. Re-register Volume Shadow Copy Services (VSS)

      1. Open a command prompt. For more information, see Opening a command or shell prompt (1003892) .
      2. Run the following commands:

        cd %systemroot%\system32
        net stop vss
        net stop swprv
        regsvr32 ole32.dll
        regsvr32 vss_ps.dll
        vssvc /Register
        regsvr32 /i swprv.dll
        regsvr32 /i eventcls.dll
        regsvr32 es.dll
        regsvr32 stdprov.dll
        regsvr32 vssui.dll
        regsvr32 msxml.dll
        regsvr32 msxml3.dll
        regsvr32 msxml4.dll
      3. Restart the server.
      4. Verify that the VSS writers are working correctly.

        1. Open a command prompt. For more information, see Opening a command or shell prompt (1003892) .
        2. Type:
          vssadmin list writers
        3. If you encounter an error, see Error message when you run the "vssadmin list writers" command on a Windows Server 2003-based computer: "Error: 0x8000FFFF" (http://support.microsoft.com/kb/940184)
          Note: Link valid August 11/08. If you find the link to be broken, provide feedback and a VMware employee will update the article.
        4. Follow the Microsoft knowledgebase articles list in the "Additional Information" section of this article, or contact Microsoft support for further assistance.

Additional Information

For additional or related troubleshooting information, see:

Feedback

Rating: 1 - Lowest 2 3 4 5 - Highest (4 Ratings)   

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (2000 or fewer characters)
Submit
Rating: 1 - Lowest 2 3 4 5 - Highest (4 Ratings)   
Actions