VMware Cloud Community
KOFMF
Contributor
Contributor

Converter unable to create a VSS snapshot of the source volume Error code 2147754776 (0x80042318)

During conversion P2V after 42 minutes 95% the conversion failed as shown in the subject? I tried twice and I obtained the same information at the same time and at the same %

Someone know why it is impossible to create a VSS snapshot at what means the error 2147754776

I attached the log too

Thanks for the help

15 Replies
jokke
Expert
Expert

This is not an explanation of why you experience vss errors, but if you have access to a version 3.x iso you can coldclone your system. You will in effect have eliminated that kind of error as vss only applies to hotcloning.

Joakim

Reply
0 Kudos
KOFMF
Contributor
Contributor

Thanks

I found solution at

The problem was Visio 11

sh0t
Contributor
Contributor

Confirmed

same vss error caused by dud Visio entry - visio removed from build and replaced with viewer root cause

delete registry key as per article

Reply
0 Kudos
shepnasty
Contributor
Contributor

Wow this post saved me hours of work! Thanks so much!!

Reply
0 Kudos
whoisthanhnghi
Contributor
Contributor

Hi All

I have got the same problem. My case is different that My OS is windows 2k3 R2 x64, just install Exchange server, no visio. Please help me

Thanks

Reply
0 Kudos
DJScorpion
Contributor
Contributor

Hi your solution solved my issue!

It seems that there was Visio on it but the uninstallation wasn't really clean Smiley Wink

Reply
0 Kudos
longroy
Contributor
Contributor

I solved my issue by installing the latest version of vmware vcenter converter. (4.3) seems to fix the issues with Windows 7 and possibly Visio I was seeing earlier.

Reply
0 Kudos
LPLAdmin
Enthusiast
Enthusiast

Same here. Old Visio entry in the registry. Removed as per the MS article.

Reply
0 Kudos
calladd
Enthusiast
Enthusiast

If the above does not help try this solution as well..... http://support.microsoft.com/kb/940184#LetMeFixItMyselfAlways

Important This article is not for use with Windows Vista, with  Windows Server 2008, or with later Windows operating systems. Starting  with Windows Vista and with Windows Server 2008, Windows component  installation is manifest-based. Trying to manually register specific  components, as described in the following steps, can have unexpected  results that may require you to reinstall Windows to resolve.

To resolve this problem, follow these steps:

  1. Click Start, click Run, type Regedit, and then click OK.
  2. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions
  3. On the Edit menu, click Delete, and then click Yes to confirm that you want to delete the subkey.
  4. Exit Registry Editor.
  5. Click Start, click Run, type services.msc, and then click OK.
  6. Right-click the following services one at a time. For each service,  click Restart
    • COM+ Event System
    • COM+ System Application
    • Microsoft Software Shadow Copy Provider
    • Volume Shadow Copy
  7. Click Start, click Run, type cmd, and then click OK.
  8. At the command prompt, type vssadmin list writers, and then press ENTER.
  9. If the VSS writers are now listed, close the Command Prompt window. You do not have to complete the remaining steps.

    If the VSS writers are not listed, type the following commands at the  command prompt. Press ENTER after each command.
    • cd /d %windir%\system32
    • net stop vss
    • net stop swprv
    • regsvr32 ole32.dll
    • regsvr32 oleaut32.dll
    • regsvr32 /i eventcls.dll
    • regsvr32 vss_ps.dll
    • vssvc /register
    • regsvr32 /i swprv.dll
    • regsvr32 es.dll
    • regsvr32 stdprov.dll
    • regsvr32 vssui.dll
    • regsvr32 msxml.dll
    • regsvr32 msxml3.dll
    • regsvr32 msxml4.dll
    Note The last command may not run successfully.
  10. At the command prompt, type vssadmin list writers, and then press ENTER.
  11. Confirm that the VSS writers are now listed.
Reply
0 Kudos
hodders
Contributor
Contributor

Another confirmation that removal of a Visio subkey in the registry fixed this for me.

(I also had to start the MS Software Shadow Copy Provider service using net start SwPrv).

Reply
0 Kudos
dobo1
Contributor
Contributor

Wow - so glad this post was made. I was about to get a hammer to very permanently fix the issue. Visio reg entry was indeed the culprit here. Worked for me.

Thanks !!

Reply
0 Kudos
Kamuela
Contributor
Contributor

Found that Windows 2008 R2 seems to work best using Vmware converter 5. Other versions constantly gave me VSS snapshot problems but with v5 was able to P2V several 2008 R2 systems that I could not P2V before.

Nodnarb
Enthusiast
Enthusiast

Solved my problem as well. The Visio key was the issue. Thanks!

Reply
0 Kudos
AlexTheGreat
Contributor
Contributor


I had the same problem as Kamuela.

Win 2008 R2 did not convert to an ESXi host.

After installing VMware-converter-all-5.0.0-470252.exe, convertion is now working fine so far.

Thanks!

Reply
0 Kudos
PIARAY
Contributor
Contributor

I had the same error doing a P2V of an XP machine. I tried what was suggested earlier in this thread with no success. I eventually started a vcenter converter install on the PC I was trying to virtualise and it failed to install with error 1704 an installation of Mcafee is currently suspended. I then manually uninstalled Mcafee using... How to manually remove McAfee Agent 5.x  

After Mcafee was gone I was able to using vmware converter successfully from the host. 

Reply
0 Kudos