Support > Knowledge Base
Knowledge Base

Search the Knowledge Base: |
Search the Knowledge Base: |
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:
-
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) .
-
Confirm that the VMware Converter related services are started on the source operating system.
To ensure the VMware related services are started:
-
Open a command prompt. For more information, see Opening a command or shell prompt (1003892) .
-
Run the following commands:
net start vstor2-p2v30
net start ufad-p2v
net start "tcp/ip netbios helper service"
net start stcp2v30
-
-
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:
-
Click Start > Run.
-
Type eventvwr and press Enter.
-
Check for errors from these sources: rpcss, com, dcom, Service Control Manager, vstor2-p2v30, ufad-p2v.
-
- For Windows 2000:
-
Click Start > Control Panel > Administrative Tools > Event Viewer.
-
Check for errors from these sources: COM, DCOM, or Service Control Manager (SCM), VMware Converter.
- For Windows NT:
-
Restart the source server. This may restore the functionality of certain OS components.
Windows XP and 2003
-
Update the disk controller driver to the latest version.
-
Confirm that the VMware Converter related services are started on the source operating system.
To ensure the VMware related services are started:
-
Open a command prompt. For more information, see Opening a command or shell prompt (1003892) .
-
Run the following commands:
net start vstor2-p2v30
net start ufad-p2v
net start "tcp/ip netbios helper"
net start swprv
net start vss
-
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.
-
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.
-
Re-register Volume Shadow Copy Services (VSS)
-
Open a command prompt. For more information, see Opening a command or shell prompt (1003892) .
-
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
-
Restart the server.
-
Verify that the VSS writers are working correctly.
-
Open a command prompt. For more information, see Opening a command or shell prompt (1003892) .
-
Type:
vssadmin list writers -
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. -
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:
-
Error events are generated when you try to perform a system state backup on a Windows Server 2003-based computer (http://support.microsoft.com/kb/941956)
- Microsoft Hotfix 826936 for Windows Server 2003 ( http://support.microsoft.com/kb/826936 )
- Microsoft Hotfix 833167 for Windows Server 2003 ( http://support.microsoft.com/kb/833167 )
- Microsoft Hotfix 891957 for Windows Server 2003 SP1 ( http://support.microsoft.com/kb/891957 )
- Best practices for troubleshooting VMware Converter (1004588)
- Converting a physical blade server fails (1000508)
Feedback
Actions
- KB Article: 1006489
- Updated: Aug 14, 2009
- Products:
VMware Converter
VMware vCenter Converter
VMware vCenter Converter Standalone - Product Versions:
VMware Converter 3.0.x
VMware vCenter Converter 4.0.x
VMware vCenter Converter Standalone 4.0.x

