none
VSS error 8193

    Question

  • I am getting three VSS errors when WS2008 backup executes.  I have no idea where to begin to look for the problem.
    The error (Event 8193) is:
    Volume Shadow Copy Service error: Unexpected error calling routine ConvertStringSidToSid.  hr = 0x80070539.

    Operation:
       OnIdentify event
       Gathering Writer Data

    Context:
       Execution Context: Shadow Copy Optimization Writer
       Writer Class Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Name: Shadow Copy Optimization Writer
       Writer Instance ID: {b7e9a7ca-db70-47c8-922b-0fa15f064b10}

    The other two are duplications of this error.
    Can anyone help me find a solution to this error?
    Here is a snapshot of the Application Events when the backup executes.

    Information    12/16/2008 2:27:58 AM    VSS    8224    None
    Information    12/16/2008 2:25:00 AM    Backup    754    None
    Error    12/16/2008 2:24:55 AM    VSS    8193    None
    Information    12/16/2008 2:00:23 AM    ESENT    103    General
    Information    12/16/2008 2:00:23 AM    ESENT    302    Logging/Recovery
    Information    12/16/2008 2:00:22 AM    ESENT    301    Logging/Recovery
    Information    12/16/2008 2:00:21 AM    ESENT    300    Logging/Recovery
    Information    12/16/2008 2:00:20 AM    ESENT    102    General
    Information    12/16/2008 2:00:17 AM    ESENT    2006    ShadowCopy
    Information    12/16/2008 2:00:17 AM    ESENT    2003    ShadowCopy
    Information    12/16/2008 2:00:17 AM    ESENT    2006    ShadowCopy
    Information    12/16/2008 2:00:17 AM    ESENT    2006    ShadowCopy
    Information    12/16/2008 2:00:17 AM    ESENT    2003    ShadowCopy
    Information    12/16/2008 2:00:17 AM    ESENT    2003    ShadowCopy
    Information    12/16/2008 2:00:15 AM    ESENT    2001    ShadowCopy
    Information    12/16/2008 2:00:15 AM    ESENT    2001    ShadowCopy
    Information    12/16/2008 2:00:15 AM    ESENT    2001    ShadowCopy
    Information    12/16/2008 2:00:15 AM    ESENT    2001    ShadowCopy
    Information    12/16/2008 2:00:15 AM    ESENT    2005    ShadowCopy
    Information    12/16/2008 2:00:15 AM    ESENT    2005    ShadowCopy
    Information    12/16/2008 2:00:15 AM    ESENT    2005    ShadowCopy
    Error    12/16/2008 2:00:11 AM    VSS    8193    None
    Error    12/16/2008 2:00:10 AM    VSS    8193    None
    Information    12/16/2008 2:00:00 AM    Backup    753    None
    Tuesday, December 16, 2008 2:36 PM

Answers

  •  

    Hi,

     

    According to the research, the issue may be caused by an invalid entry inside the following registry sub tree.

     

    HKey_Local_Machine\Software\Microsoft\Windows NT\CurrentVersion\ProfileList

     

    Please open the registry editor with regedit.

     

    Expand and local to the subtree, check if there is an entry that has a ".bak" value appended. If so, this may be cause the failure when trying to resolve the SID of the writer.

     

    Please backup the registry key first, and then delete that entry with the extra ".bak"

     

    Then you may reboot the problematic server to check if it the issue can be fixed.

     

    Hope it helps.


    David Shen - MSFT
    • Marked as answer by David Shen Monday, December 22, 2008 2:33 AM
    Thursday, December 18, 2008 3:36 AM

All replies

  •  

    Hi,

     

    According to the research, the issue may be caused by an invalid entry inside the following registry sub tree.

     

    HKey_Local_Machine\Software\Microsoft\Windows NT\CurrentVersion\ProfileList

     

    Please open the registry editor with regedit.

     

    Expand and local to the subtree, check if there is an entry that has a ".bak" value appended. If so, this may be cause the failure when trying to resolve the SID of the writer.

     

    Please backup the registry key first, and then delete that entry with the extra ".bak"

     

    Then you may reboot the problematic server to check if it the issue can be fixed.

     

    Hope it helps.


    David Shen - MSFT
    • Marked as answer by David Shen Monday, December 22, 2008 2:33 AM
    Thursday, December 18, 2008 3:36 AM
  • Hi David,

    Your answer solved the problem after reboot.  I do appreciate your help.  Have a Merry Christmas and super New Year.

    Lee
    • Proposed as answer by NEWMG-Spencer Friday, October 01, 2010 4:49 PM
    Sunday, December 21, 2008 7:53 PM
  •  Merry Christmas and happy new year.
    David Shen - MSFT
    Monday, December 22, 2008 2:32 AM
  • Hi


    On my Vista Enterprise SP2 i had to delete all the '.bak' keys from the 'ProfileList' to get bak the 'Shadow Copy Optimization Writer' listed with 'vssadmin list writers' on a command prompt and having resolved the 8193 VSS error.


    Cheers markus
    Thursday, December 10, 2009 4:26 PM
  • Was getting this error on windows 7 as well, a SID for a non-existent user had be renamed to *.bak

    Google of the error brought me straight here and the fix worked first time..

    Love it when that happens..

    Thanks.
    Friday, January 01, 2010 10:43 PM
  • I had this error in Vista Home Premium SP2 all hotfixes done.

    THIS POST FIXED IT! - the dreaded .bak files

    This sounds like a long-standing Windows bug. Apparently the system is trying to use a backup copy of a profile to perform Shadow Copy functions.

    I believe my .bak file was created by Windows when I deleted a user from my system.  As I recall, I also told the delete to not save any files for that user.

    Hope this helps as there are many, many posts on forums where people are trying to solve VSS and Shadow Copy Writer problems. This adds up to thousands of unproductive hours searching for a solution

    Wednesday, January 06, 2010 12:35 AM
  • This absolutely fixed the issue.  Thanks for tracking down the root cause of this problem!  Helped me a bunch with my DPM 2007 deployment.  It was failing when I was trying to back up SharePoint.
    Tuesday, June 15, 2010 1:28 PM
  • I just performed those steps on my Server 2008 R2 DC.  Fixed the problem.

    Thanks!!!

    Friday, September 10, 2010 1:46 PM
  • I ran into this problem on several different machines.  Two were running Server 2003, and the other one running XP Professional.

    I finally came across something related to this for Server 2008 that finally led me in the right direction to finding a solution.


    The article talks about recreating the "TypeLib" registry value.  NOTE, in Server 2008, this value is of type REG_EXPAND_SZ while in Server 2003 and XP it is REG_SZ.

    After comparing the registry values on the machines that were having problems with the registry values of machines that were working fine, I found that the values were wrong for a couple of the registry keys.  Also, there were a couple of extra unneeded keys that I could get rid of.

    Basically, it is under the following section of the registry:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\EventClasses\{FAF53CC4-BD73-4E36-83F1-2B23F46E513E}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}

    The values for OwnerSID and TypeLib are probably wrong.

    Correct values are as follows:

    OwnerSID (REG_SZ):  S-1-5-18
    TypeLib (REG_SZ):  C:\WINDOWS\system32\EVENTCLS.DLL

    After you set these values as shown, you will need to reboot the system before VSS will work properly again.


    • Edited by NEWMG-Spencer Friday, October 01, 2010 9:06 PM Fixed Typo
    • Proposed as answer by NEWMG-Spencer Monday, October 04, 2010 10:40 PM
    Friday, October 01, 2010 4:54 PM
  • Thanks David

    Your solution worked a treat when we were experiencing this problem on our Windows 2008 R2 server.

    Wednesday, November 23, 2011 2:33 PM
  • The registry trick fixed our issue too !!! Thank you David Shen

    We are backing up a few servers including a Win 2008 R2 SP1 server for awhile and suddenly out of nowhere this error surfaced. The actual event text is very confusing since it talk about HDD out of space. After modifying the registry as David Shen insturcted,a reboot after that, and everything is working now.

    Best,

    E.

    Wednesday, December 28, 2011 4:58 PM
  • Hello DAVID,

    I am also getting the same Errors in Event Viewer of my windows server 2008 R2 Terminal server. I searched the Registry value, but I found that instead of .bak entry I have .old entry. Should I make it remove? Will it work?

    Thanks for the reply.

    Pankaj

    • Proposed as answer by Pankaj.gupta Friday, April 13, 2012 10:26 AM
    Wednesday, March 14, 2012 7:30 AM
  • Yes, you should. Any other text added to it (.old) will make Windows fail parsing the string properly.
    Wednesday, August 01, 2012 4:56 PM
  • This is how we FIXED this problem and there are many fixes listed here:

    a) Our Fix:

    - Login to the server where Windows Server Backup runs

    - Check the Event Viewer Logs under Application Services -> Backup  (Operations)

    - If you have Hyper-V running, then go to the Hyper-V section under Application Services -> Hyper-V VMS (Operations).

    - In that log, it will states which VM is causing the error.

    - Login to that VM and check the Event Viewer logs. In our case it was SQLWriter causing it.

    - Solution is simple, batch a simple script on that VM and add it to Task Scheduler to stop SQLWriter few minutes before the backup starts and then start it up few minutes afterwards. (net stop sqlwriter , net start sqlwriter)

    - If you have a local SQL server on the server you're doing Windows backup, then this may need to be done.

     

    b) Other fixes reported by users:

    - from command prompt type: diskpart

    - from command prompt type: automount  and check if automount is enabled/disabled, it need to be enabled

     

    c) Another fix (not recommended in my opinion) only works if you have Hyper-V installed:

    - Disable VSS Writer for Hyper-V using the following:

    goto registry on the server running windows backup: 

    1. hklm\software\microsoft\windowsNT\currentversion\spp
    2. Add a new key as type reg_Multi_SZ
    3. Name for new key: DisabledWriters
    4. Value for new key: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de} (remember that yours may be different - run a vssadmin list writers to determine your value for the key)
    5. net stop wbengine
    6. net start wbengine
    Monday, December 03, 2012 12:54 AM
  • We receive the similar errors which cause our server lots of confusion.

    Using EMC's Replication manager, there are several disk devices cloned, mounted and unmounted on a daily basis.

    As such it's quite common for us to receive the errors listed above.

    The fix works great but I was wondering if there is a quick / easy way to simply clear the entire cache / memory of what disks a server has. Simply selecting clear cache in Disk Manager is not sufficient.

    many thanks and if you can help that would be greatly appreciated.

    Dino

    Wednesday, March 13, 2013 9:21 AM
  • David, you're the man. This solution saved the day, five years later! Thank you for your expertise!


    Dan

    Wednesday, August 28, 2013 8:28 PM
  • Hi David! Do you know whether or not this solution has a KB related to it? Thanks!
    Thursday, September 26, 2013 6:18 PM
  • I renamed .bak file as .bak_old in place of deleting the same file. I restated the System but error did not resolve. I want to ask that is it necessary to delete only?

    Monday, February 17, 2014 10:03 AM
  • Thank You it works. In my windows Vista.
    Monday, March 03, 2014 5:00 PM
  • Is it necessary to delete all the entry or only the .bak or .old text of the entry?

    Thanks

    Thursday, March 06, 2014 8:38 AM