Unable to create a VSS snapshot

[MatiasHJ]

Hey!



I'm converting a physical machine into a virtuel.

However each time i start convert it, it's stuck at 1% for quite some time followed by



FAILED: Unable to create a VSS snapshot of the source volume(s). Error code:
2147754774 (0x80042316).



I've been crawling the net trying to fix this for some days now and tried several fixes - non of them worked.

Here's what i've tried:

Changing states on Volume Shadow Copy & Microsoft Software Shadow Copy Provider service to Automatic (also tried manual "up")

Reregister .DLL's

(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)

Disabled Synchronization

Tried changing Volume C:´s storage area to Emore space) and enabled volumes(which fails)

I've tried downloading and installing several hotfixes(latest was KB940349)

Also im sure that theres enough space on the destination.



Also restarted the server when needed(after .dll reregistration etc)



The most success i've have had has been that the estimated time has gone from "1 hour and 3 minutes" and staying there for a while before failing - to the estimated time of "1 hour" and failing after just a couple of secs(Still same errror code).



Specs:

Server to virtualize:

Microsoft Windows Server 2003R2

Standard Edition

Service Pack2



vCenter Converter:

vCenter Converter Standalone Client

v. 4.3.0 build 292238





Attached log from the Converter and here's from the event-viewer:

Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 12310
Date: 9/6/2012
Time: 9:32:55 AM
User: N/A
Computer: APPSRV01
Description:
Volume Shadow Copy Service error: The shadow copy could not be committed - operation timed out. Error context: DeviceIoControl(\\?\Volume{034eeaab-b772-11df-90df-806e6f6e6963} - 0000018C,0x0053c010,0003E310,0,00AA0048,4096,[0]).



Data:
0000: 2d 20 43 6f 64 65 3a 20 - Code:
0008: 49 4e 43 49 43 48 4c 48 INCICHLH
0010: 30 30 30 30 30 34 35 39 00000459
0018: 2d 20 43 61 6c 6c 3a 20 - Call:
0020: 53 50 52 51 53 4e 50 43 SPRQSNPC
0028: 30 30 30 30 30 32 33 35 00000235
0030: 2d 20 50 49 44 3a 20 20 - PID:
0038: 30 30 30 30 31 33 39 32 00001392
0040: 2d 20 54 49 44 3a 20 20 - TID:
0048: 30 30 30 30 35 38 35 36 00005856
0050: 2d 20 43 4d 44 3a 20 20 - CMD:
0058: 43 3a 5c 57 49 4e 44 4f C:\WINDO
0060: 57 53 5c 53 79 73 74 65 WS\Syste
0068: 6d 33 32 5c 73 76 63 68 m32\svch
0070: 6f 73 74 2e 65 78 65 20 ost.exe
0078: 2d 6b 20 73 77 70 72 76 -k swprv
0080: 2d 20 55 73 65 72 3a 20 - User:
0088: 4e 54 20 41 55 54 48 4f NT AUTHO
0090: 52 49 54 59 5c 53 59 53 RITY\SYS
0098: 54 45 4d 20 20 20 20 20 TEM
00a0: 2d 20 53 69 64 3a 20 20 - Sid:
00a8: 53 2d 31 2d 35 2d 31 38 S-1-5-18





Thanks in advance and im looking forward to see what i've might have missed
(vss writers:

http://speedy.sh/qWF7e/Writers.txt

)

 

[MortenBergmann]

This is how I resolved this issue:

Resolution
This issue occurs if Volume Shadow Copy Service (VSS) has problems performing a snapshot of disks, which can occur if multiple providers are associated with the operating system.

To check if there are multiple providers and delete the second provider:

Click Start > Run, type cmd, and press Enter.
Run the command:

vssadmin list writers

This command should not return errors.

Check the providers associated with the operating system with the command:

vssadmin list providers

If the command returns more than one provider, remove the key of the second provider from the Windows registry:
Click Start > Run, type regedit, and press Enter.
Browse the registry to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers.
Back up the registry location. Right-click on the key and choose Export.
Remove the key for the second provider. It looks like HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\<GUID>.

Note: Keep the Microsoft provider key. It looks like HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\{b5946137-7b9f-4925-af80-51abd60b20d5}.

Reboot the physical host.