locked
VSS Error Event id 8193 - 0x80070539 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

     

    I keep getting VSS Error with event id 8193 for several weeks now:

    ConvertStringSidToSid
    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:
    {bd32726a-3d40-4c27-9282-2af7d5cff0a5}

    Any ideas?
    Saturday, July 26, 2008 12:23 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Checking registered writers with "vssadmin list writers" does not list the "Shadow Copy Optimization Writer".

    Is there a way of re-registering this writer with VSS? I guess this would stop the error.

     

    Tuesday, August 12, 2008 8:36 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I am having the same problem and it is VERY frustrating.  I was told at Dell tech support to reinstall Vista SP 1.  What did you do?  Thanks.
    Saturday, August 16, 2008 9:06 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Noting much just hoping somebody with the right knowledge is going to give me a light ...

    All public VSS resolutions relate to Server 2003 and hence do not work here.

     

    Also I have reformulated the issue slightly:

     

     

    Vista SP1 - VSSadmin List Writers reveals one writer missing:

    Shadow Copy Optimization Writer is not listed.

     

    Creating a restore point causes VSS Error with event id 8193

     

    >> ConvertStringSidToSid
    >> 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:
    >> {bd32726a-3d40-4c27-9282-2af7d5cff0a5}

     

    However, restore point creation is succesful.

     

    There must be another way but reinstalling the entire OS and everything else on top from scratch ...

    • Proposed as answer by akermitb Wednesday, June 3, 2009 5:35 PM
    Saturday, August 16, 2008 9:25 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    try this : http://seer.entsupport.symantec.com/docs/312068.htm

    i have not tried it for now but its will be done soon
    mcp
    Wednesday, June 3, 2009 5:36 PM
  • Question
    Sign in to vote
    9
    Sign in to vote

    This post seemed to solve the issue for me:

    http://blogs.technet.com/jonjor/archive/2010/02/18/scvmm-p2v-fails-with-at-40-percent-with-0x809933bb-or-0x80070539.aspx

    Followed steps in 'KB947242 - A temporary profile is loaded after you log on to a Windows Vista-based system' to resolve issue where customer's profile was deleted from the system (in this case the profile was simply corrupt).

    1.  
      1. Open regedit and locate 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList'
      2. Under the ProfileList subkey, delete any subkey that is named SID.bak.
    Jeff Graves, ORCS Web, Inc.
    • Proposed as answer by Pedmil Wednesday, November 30, 2011 4:34 PM
    Thursday, April 8, 2010 1:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Deleting the registry key resolved my similar issue.
    Friday, January 18, 2013 6:04 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    This post seemed to solve the issue for me:

    http://blogs.technet.com/jonjor/archive/2010/02/18/scvmm-p2v-fails-with-at-40-percent-with-0x809933bb-or-0x80070539.aspx

    Followed steps in 'KB947242 - A temporary profile is loaded after you log on to a Windows Vista-based system' to resolve issue where customer's profile was deleted from the system (in this case the profile was simply corrupt).

    1.  
      1. Open regedit and locate 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList'
      2. Under the ProfileList subkey, delete any subkey that is named SID.bak.
    Jeff Graves, ORCS Web, Inc.

    Worked for me!
    Monday, December 1, 2014 3:17 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    Thanks Jeff !
    Tuesday, December 2, 2014 10:46 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Worked for me too. I was able to reproduce the VSS error by performing the vssadmin list writers command; the error would show (in eventviewer) the first profile entry with the .bak extension. After removing this entry, the vssadmin command would trigger an event log error with the next profile entry. After removing all entries with tne .bak extension, performing the vssadmin command produces no more errors in event log. 
    Friday, April 24, 2015 11:29 AM