Translator
      English flagItalian flagKorean flagChinese (Simplified) flagChinese (Traditional) flagPortuguese flagGerman flagFrench flag
      Spanish flagJapanese flagArabic flagRussian flagGreek flagDutch flagBulgarian flagCzech flag
      Croatian flagDanish flagFinnish flagHindi flagPolish flagRomanian flagSwedish flagNorwegian flag
      Catalan flagFilipino flagHebrew flagIndonesian flagLatvian flagLithuanian flagSerbian flagSlovak flag
      Slovenian flagUkrainian flagVietnamese flagAlbanian flagEstonian flagGalician flagMaltese flagThai flag
      Turkish flagHungarian flagBelarus flagIrish flagIcelandic flagMacedonian flagMalay flagPersian flag
    Tag Cloud
    Sponsors
    Recent Comments
      Link with us

      IT Solutions Knowledge Base

      Copyright Protected
      256-bit Secured



Volume Shadow Copy operation failed with error code
Home » Backup, Hyper-V, Windows Server 2008 » Volume Shadow Copy operation failed with error code 2155348001
By | 5 CommentsLeave a Comment
Last updated: Thursday, November 6, 2008

This is a known microsoft bug found on Windows 7 and its being also report in Windows Server 2008. There will be a fix from microsoft around this when they release Service Pack 2. If you encounter the following issue the only workable solution is to put all Hyper-V images to save state and then run the Windows Backup.

It seem that although there are some workaround solutions, none of them is really working.

Some solutions that might work for you before attempting the save state are the following:

1) Disable any Forefront or Trendmicro Antivirus solutions

2) Backup the following registry key:
HKLM\Software\Microsoft\EventSystem and then delete:
HKLM\Software\Microsoft\EventSystem\{26c409cc-ae86-11d1b616-00805fc79216}\Subscriptions
and restart the server. This will cause the VSS Entries to rebuild when the writer initializes
(Note: Do not delete the EventClasses Key)

3) Create a batch file with the following code to re-register the DLL’s and restart the VSS service:

cd /d %windir%\system32
Net stop vss
Net stop swprv
regsvr32 ole32.dll
regsvr32 oleaut32.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

4) Make sure your Windows Server is fully updated with all the latest patches.

5) Make sure that all your drivers and firmware are up to date.

6) Make sure you have at least 15GB of space available

If you have already done the following and your backup still fails your only way that will cause some downtime is to save the state of Hyper-V VHD Images and run the backup or wait until Microsoft releases SP2 for Windows Server 2008.

Comments

5 comments
  1. Ewdev
    December 12, 2008

    Thanks Glafkos, very timely information, however I am getting a few problems running the batch program and I wondered if you knew whether this could be a problem with my setup?
    1. When registering eventscls.dll I get ‘The module “eventscls.dll” was loaded but the call to DllInstall failed with error code 0x8000ffff’
    2. When registering es.dll I get ‘The module “es.dll” was loaded but the entry-point DllRegisterServer was not found.’
    3. When registering msxml.dll I get ‘The specified module could not be found’ an obvious one perhaps but should it be there?
    4. When registering msxml4.dll I get ‘The specified module could not be found’ also obvious but I am wondering why these modules are not present? Is there something I have not installed that is required by backup or vss etc?

    Thx

    [Reply]

    Leave a reply
  2. Glafkos Charalambous
    December 12, 2008

    Hello Ewdev,

    1) What OS?
    2) Can you verify that the files exist?
    3) Did you try to run each command line by line in a command prompt?

    The above script should work without issues on Windows 2003/2008

    [Reply]

    Leave a reply
  3. Sorin
    April 9, 2009

    Hello Glafkos.
    I encounter the same messages as Ewdev on Win server 2008. I believe that the failure of backup is due to a virus (saliti) because yesterday I found that virus on my server, and incidentally I notice the failure of scheduled backup. Until yesterday the backup works fine. I do not made any changes on server, that could justify the backup failure. This is the reason for that I suppose the virus is guilty for that.

    [Reply]

    Leave a reply
  4. Glafkos Charalambous
    April 9, 2009

    Hello,

    For Windows x64 bit please replace c:\windows\system32 with c:\windows\SysWOW64 and execute:

    regsvr32 ole32.dll
    regsvr32 vss_ps.dll
    regsvr32 es.dll
    regsvr32 stdprov.dll
    regsvr32 msxml3.dll
    regsvr32 msxml.dll
    regsvr32 msxml4.dll

    As I had researched the issue it seems that the above errors are common for lot of people.

    Reference:
    http://social.microsoft.com/Forums/en-US/whssoftware/thread/5057969b-3f2a-40a7-9865-dd6ada05962e
    http://social.technet.microsoft.com/Forums/en-US/winserverfiles/thread/e2f86247-6a77-4bf3-a4f8-be7687c181b7
    http://social.microsoft.com/Forums/en-US/winservergen/thread/aa3f3f73-b81c-4d16-a47a-5e7c9248d970

    Thanks
    Glafkos

    [Reply]

    Leave a reply
  5. James
    February 5, 2010

    Glafkos,

    Thank you so much for your input for the x64 system path change. I was desperately trying to fix this error but to no avail. I tried registering the dll files and changing registry entries for hours. When I saw your entry about changing the path for a 64bit OS it finally hit me that I was registering the dll’s in the wrong location. It seems silly for me to have overlooked this in hindsight, but your information helped me realize the issue. I hope your post can help others.

    Thanks again

    James

    [Reply]

    Leave a reply

Leave a Comment

Add your picture!
Join Gravatar and upload your avatar. C'mon, it's free!