Announcement

Collapse
No announcement yet.

SBS 2008 VSS errors

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • SBS 2008 VSS errors

    SYSTEM
    Current Exchange 2007 Version: 08.03.0245.001 (rollup 6 SP3)
    Current SBS2008 Version: Update Rollup 5


    PROBLEM

    Hi All,

    Have been having issues with SBS2008 and VSS backups using Windows Backup over the past few months. Strangely, the backup is successful, no VSS writers are failed however the exchange transaction logs suggest that exchange is not being backed up (seems very hit and miss, will work every now and then but mostly fails).

    ADDITIONAL INFORMATION

    Event Log Error 1:

    Log Name: Application
    Source: VSS
    Date: 18/09/2012 1:30:43 AM
    Event ID: 8193
    Task Category: None
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: Server.domain.local

    Description:
    Volume Shadow Copy Service error: Unexpected error calling routine IEventSystem::Store. hr = 0x80070005.
    Event Xml:

    Event Log Error 2:

    Log Name: Application
    Source: VSS
    Date: 18/09/2012 1:30:41 AM
    Event ID: 12289
    Task Category: None
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: Server.domain.local
    Description:
    Volume Shadow Copy Service error: Unexpected error RegOpenKeyExW(-2147483646,System\CurrentControlSet\Services\Event Log\Application\VSS,...). hr = 0x80070005.

    VSS WRITERS

    Writer name: 'ASR Writer'
    Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
    Writer Instance Id: {c3cdc5cb-7f45-4609-a3b4-5ca39b93ed5a}
    State: [1] Stable
    Last error: No error

    Writer name: 'FRS Writer'
    Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
    Writer Instance Id: {b7d53f7f-110f-471e-94c9-a0793d310118}
    State: [1] Stable
    Last error: No error

    Writer name: 'Registry Writer'
    Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
    Writer Instance Id: {228b12ff-0b2c-48c0-8ea9-6f236adaea16}
    State: [1] Stable
    Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
    Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
    Writer Instance Id: {ebae6107-19f9-4ece-9b54-c0a73cd1c387}
    State: [1] Stable
    Last error: No error

    Writer name: 'Dhcp Jet Writer'
    Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
    Writer Instance Id: {9066bcba-f48d-4508-9d2f-8bdd99e9b61d}
    State: [1] Stable
    Last error: No error

    Writer name: 'COM+ REGDB Writer'
    Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
    Writer Instance Id: {2d31c06f-bba1-4e9e-b97a-f919fe8a4349}
    State: [1] Stable
    Last error: No error

    Writer name: 'BITS Writer'
    Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
    Writer Instance Id: {cc1eee46-c378-4c25-b2c7-cf86dfd2daf2}
    State: [1] Stable
    Last error: No error

    SHADOW STORAGE
    I completed cleared out shadow storage - as it was something i had read up on however this got me no where.

    Shadow Copy Storage association
    For volume: (C\\?\Volume{b562a5dd-8246-11de-a75b-806e6f6e6963}\
    Shadow Copy Storage volume: (C\\?\Volume{b562a5dd-8246-11de-a75b-806e6f6e69
    Used Shadow Copy Storage space: 0 B
    Allocated Shadow Copy Storage space: 0 B
    Maximum Shadow Copy Storage space: 14.875 GB
    Shadow Copy Storage association
    For volume: (D\\?\Volume{68c8478f-82de-11de-91aa-002481d1c8b0}\
    Shadow Copy Storage volume: (D\\?\Volume{68c8478f-82de-11de-91aa-002481d1c8
    Used Shadow Copy Storage space: 0 B
    Allocated Shadow Copy Storage space: 0 B
    Maximum Shadow Copy Storage space: 69.846 GB
    Shadow Copy Storage association
    For volume: (\\?\Volume{bd3b6ffb-def9-11e1-bee4-002481d1c8b0}\)\\?\Volume{bd3
    Shadow Copy Storage volume: (\\?\Volume{bd3b6ffb-def9-11e1-bee4-002481d1c8b0}
    Used Shadow Copy Storage space: 0 B
    Allocated Shadow Copy Storage space: 0 B
    Maximum Shadow Copy Storage space: UNBOUNDED

    OTHER SOLUTIONS
    1. Reregistered the dll's (stopped all required services, reregistered the dll's and start the services back up).
    Pretty much turned it into a script:

    et stop "File Replication Service"
    net stop "DHCP Server"
    net stop "DFS Replication"
    net stop "Background Intelligent Transfer Service"
    net stop "System Event Notification Service"
    net stop "Background Intelligent Transfer Service"
    net stop "COM+ Event System"
    net stop "Microsoft Software Shadow Copy Provider"
    net stop "Volume Shadow Copy"

    cd /d %windir%\system32

    net stop vss
    net stop swprv
    regsvr32 /s ole32.dll
    regsvr32 /s oleaut32.dll
    regsvr32 /s vss_ps.dll
    vssvc /register
    regsvr32 /s /i swprv.dll
    regsvr32 /s /i eventcls.dll
    regsvr32 /s es.dll
    regsvr32 /s stdprov.dll
    regsvr32 /s vssui.dll
    regsvr32 /s msxml.dll
    regsvr32 /s msxml4.dll
    regsvr32 /s msxml3.dll

    net start "COM+ Event System"
    net start "System Event Notification Service"
    net start "Microsoft Software Shadow Copy Provider"
    net start "Volume Shadow Copy"
    net start "File Replication Service"
    net start "DHCP Server"
    net start "DFS Replication"
    net start "Background Intelligent Transfer Service"

    2. Deleted Reg key forcing VSS writers to be rebuilt
    Deleted the HKLM\Software\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions key

    3. Ran sharepoint wizard
    4. Run check disk (no errors)
    5. Followed instructions to assure their was no setup 'initiating' during backup
    - Go to the Registry Editor and locate HKEY_LOCAL_MACHINE\SYSTEM\Setup
    - Ensure that the following registry values are set to 0:
    -SystemSetupInProgress
    -UpgradeInProgress

    6. Gave full permission to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\servic es\VSS registry key.

    Only thing I haven't tried is a repair on the COM+ component from suggestions I've seen on the net. Anyone seen this before? Please don't hesitate to ask for additional information.

  • #2
    Re: SBS 2008 VSS errors

    If its any consilation I get the same problem with VSS errors and backup exec - havent managed to find a solution yet.

    As you said - hit and miss, I can run nightly exchange backups and its fine and other times the vss writer will time out (or atleast thats the erorr I get) and when I look in vssadmin list writers all is stable so I just manually run the backup again.

    Ive changed the schedule time to see if its conflicting with anything and again - still sometimes works and others not. Bit of a cop out but Ive just accepted it and moved on.

    Comment


    • #3
      Re: SBS 2008 VSS errors

      Originally posted by 5habbaranks View Post
      If its any consilation I get the same problem with VSS errors and backup exec - havent managed to find a solution yet.

      As you said - hit and miss, I can run nightly exchange backups and its fine and other times the vss writer will time out (or atleast thats the erorr I get) and when I look in vssadmin list writers all is stable so I just manually run the backup again.

      Ive changed the schedule time to see if its conflicting with anything and again - still sometimes works and others not. Bit of a cop out but Ive just accepted it and moved on.
      To isolate, try to attempt a Full backup of Exchange Information Store only. Configure the job as below
      1. Turn off AOFO. Job Properties->Advanced Open File->Unselect this if it has been selected.
      2. Ensure that you perform a Full backup (not Copy) Job Properties->Exchange and use the Drop Down to select Full backup.

      See if you get any event IDs on the Exchange server regarding Log/Recovery. This should give you an idea if Backup is attempting any log truncation.

      As for the backup not working with Windows backup - Look in the Event Viewer for any alerts correcponding to the time of backup. Typically while performing a backup of exchange with any backup solution, the VSS events will get generated giving you information and warning/alert. Also as these backups are dependent on VSS completly the writers need to be in steady state.

      Comment


      • #4
        Re: SBS 2008 VSS errors

        Originally posted by jaydeepsathe View Post
        To isolate, try to attempt a Full backup of Exchange Information Store only. Configure the job as below
        1. Turn off AOFO. Job Properties->Advanced Open File->Unselect this if it has been selected.
        2. Ensure that you perform a Full backup (not Copy) Job Properties->Exchange and use the Drop Down to select Full backup.

        See if you get any event IDs on the Exchange server regarding Log/Recovery. This should give you an idea if Backup is attempting any log truncation.

        As for the backup not working with Windows backup - Look in the Event Viewer for any alerts correcponding to the time of backup. Typically while performing a backup of exchange with any backup solution, the VSS events will get generated giving you information and warning/alert. Also as these backups are dependent on VSS completly the writers need to be in steady state.
        Information i have provided already suggests that the VSS writer status is stable. Also posted what is generated in the event logs, have researched those errors but all fixes so far have not been successful

        Comment


        • #5
          Re: SBS 2008 VSS errors

          man, i got the same issue. the only way i got this fix is by :
          1- create a Task Scheduler to stop SQLWriter (before the back up start)
          2- start the backup
          3- give it 3 - 4 hours until the back up finish and set up another Task Scheduler to start SQLWriter.


          it's the best fix i could come up with.

          Comment

          Working...
          X