Results 1 to 3 of 3

Thread: VSS Writer Status does not reset

  1. #1
    chris_aim@hotmail.com Guest

    VSS Writer Status does not reset

    Hello,

    We are running EMC/Legato Networker 7.4with Sp2 to backup our Windows
    Server 2008 (64-bit) server, and very other day we hit a problem where
    the backup fails for no apparent reason.

    When the problem occurs, the backup logs show the following

    savegrp: suppressed 2 lines of verbose output
    C:\windows\help\windows\en-us\ocsp.h1s
    C:\windows\inf\oem12.inf
    System Writer - Get file attributes returned error 2 for VSS file
    Error! Hyperlink reference not valid.
    System Writer - ERROR: Failed to save filegr files, writer = S
    System Writer - Error saving writer System Writer
    System Writer - ERROR: Aborting backup of saveset VSS SYSTEM FILESET:
    because of the error with writer System Writer.
    System Writer - Error saving
    39078:save: RPC error: RPC cannot encode arguments

    Also, vssadmin show the following..

    Writer name: 'System Writer'
    Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
    Writer Instance Id: {965d6ebb-c9eb-4f48-a1e0-93f31b662690}
    State: [1] Stable
    Last error: No error

    Writer name: 'ASR Writer'
    Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
    Writer Instance Id: {c69904a5-bb1d-4766-822c-4966b2106b28}
    State: [1] Stable
    Last error: No error

    Writer name: 'COM+ REGDB Writer'
    Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
    Writer Instance Id: {8c30427a-0fd4-4f80-b8ad-b1e9fa2a016d}
    State: [1] Stable
    Last error: No error

    Writer name: 'Registry Writer'
    Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
    Writer Instance Id: {3d17395b-cdda-4471-afeb-34cf9c566f4c}
    State: [1] Stable
    Last error: No error

    Writer name: 'BITS Writer'
    Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
    Writer Instance Id: {b45898a7-4ce3-47c2-9d7e-1fe8c397377c}
    State: [5] Waiting for completion
    Last error: No error

    Writer name: 'SPSearch VSS Writer'
    Writer Id: {57af97e4-4a76-4ace-a756-d11e8f0294c7}
    Writer Instance Id: {a9ee16bb-263a-4baf-bf86-b350de103df8}
    State: [5] Waiting for completion
    Last error: No error

    Writer name: 'IIS Config Writer'
    Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
    Writer Instance Id: {afdcbebc-c741-4f6e-a8a4-a850c5eebbd9}
    State: [5] Waiting for completion
    Last error: No error

    Writer name: 'IIS Metabase Writer'
    Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
    Writer Instance Id: {2f1374f7-ebe9-4582-b856-96a1695f86ff}
    State: [5] Waiting for completion
    Last error: No error

    Writer name: 'WMI Writer'
    Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
    Writer Instance Id: {d7798284-cc01-488d-a9f7-d8f75108b05e}
    State: [5] Waiting for completion
    Last error: No error

    Previously, we have had to reboot the server as a workaround, but this
    is not a tenable long-term solution. All my findings only refer to VSS
    updates for Windows 2003. I have not seen any that refers to Windows
    2008, so would be grateful if someone can assist with getting this
    resolved.

    Thanks
    Chris

  2. #2
    chris_aim@hotmail.com Guest

    Re: VSS Writer Status does not reset

    On May 28, 12:31*pm, "Thee Chicago Wolf (MVP)" <.@.> wrote:
    > >We are running EMC/Legato Networker 7.4with Sp2 to backup our Windows
    > >Server 2008 (64-bit) server, and very other day we hit a problem where
    > >the backup fails for no apparent reason.

    >
    > >When the problem occurs, the backup logs show the following

    >
    > >savegrp: suppressed 2 lines of verbose output
    > >C:\windows\help\windows\en-us\ocsp.h1s
    > >C:\windows\inf\oem12.inf
    > >System Writer - Get file attributes returned error 2 for VSS file
    > >Error! Hyperlink reference not valid.
    > >System Writer - ERROR: Failed to save filegr files, writer = S
    > >System Writer - Error saving writer System Writer
    > >System Writer - ERROR: Aborting backup of saveset VSS SYSTEM FILESET:
    > >because of the error with writer System Writer.
    > >System Writer - Error saving
    > >39078:save: RPC error: RPC cannot encode arguments

    >
    > >Also, vssadmin show the following..

    >
    > >Writer name: 'System Writer'
    > > * Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
    > > * Writer Instance Id: {965d6ebb-c9eb-4f48-a1e0-93f31b662690}
    > > * State: [1] Stable
    > > * Last error: No error

    >
    > >Writer name: 'ASR Writer'
    > > * Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
    > > * Writer Instance Id: {c69904a5-bb1d-4766-822c-4966b2106b28}
    > > * State: [1] Stable
    > > * Last error: No error

    >
    > >Writer name: 'COM+ REGDB Writer'
    > > * Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
    > > * Writer Instance Id: {8c30427a-0fd4-4f80-b8ad-b1e9fa2a016d}
    > > * State: [1] Stable
    > > * Last error: No error

    >
    > >Writer name: 'Registry Writer'
    > > * Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
    > > * Writer Instance Id: {3d17395b-cdda-4471-afeb-34cf9c566f4c}
    > > * State: [1] Stable
    > > * Last error: No error

    >
    > >Writer name: 'BITS Writer'
    > > * Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
    > > * Writer Instance Id: {b45898a7-4ce3-47c2-9d7e-1fe8c397377c}
    > > * State: [5] Waiting for completion
    > > * Last error: No error

    >
    > >Writer name: 'SPSearch VSS Writer'
    > > * Writer Id: {57af97e4-4a76-4ace-a756-d11e8f0294c7}
    > > * Writer Instance Id: {a9ee16bb-263a-4baf-bf86-b350de103df8}
    > > * State: [5] Waiting for completion
    > > * Last error: No error

    >
    > >Writer name: 'IIS Config Writer'
    > > * Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
    > > * Writer Instance Id: {afdcbebc-c741-4f6e-a8a4-a850c5eebbd9}
    > > * State: [5] Waiting for completion
    > > * Last error: No error

    >
    > >Writer name: 'IIS Metabase Writer'
    > > * Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
    > > * Writer Instance Id: {2f1374f7-ebe9-4582-b856-96a1695f86ff}
    > > * State: [5] Waiting for completion
    > > * Last error: No error

    >
    > >Writer name: 'WMI Writer'
    > > * Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
    > > * Writer Instance Id: {d7798284-cc01-488d-a9f7-d8f75108b05e}
    > > * State: [5] Waiting for completion
    > > * Last error: No error

    >
    > >Previously, we have had to reboot the server as a workaround, but this
    > >is not a tenable long-term solution. All my findings only refer to VSS
    > >updates for Windows 2003. I have not seen any that refers to Windows
    > >2008, so would be grateful if someone can assist with getting this
    > >resolved.

    >
    > >Thanks
    > >Chris

    >
    > I know it's a bit early to suggest it but have you maybe thought of
    > updating to the recently released SP2 for 2K8? The only VSS stuff I
    > see if for 2K3 server as well.
    >
    > Here's a link to the download:http://www.microsoft.com/downloads/d...D=a4dd31d5-f90...
    >
    > I'm showing a few VSS related fixes in the SP2 for 2K8 hotfix list
    > here:http://go.microsoft.com/fwlink/?LinkId=143706- Hide quoted text -
    >
    > - Show quoted text -


    Thank you for the response. Unfortunately, any service pack upgrade
    will have to go through testing which, even if approved, will take
    roughly 6-12 weeks to implement. I was looking more alomg the lines of
    either obtaining a "standalone" VSS hotfix, or preferably a quicker
    resolution via making configuration changes.

  3. #3
    chris_aim@hotmail.com Guest

    Re: VSS Writer Status does not reset

    On May 28, 3:40*pm, "Thee Chicago Wolf (MVP)" <.@.> wrote:
    > >Thank you for the response. Unfortunately, any service pack upgrade
    > >will have *to go through testing which, even if approved, will take
    > >roughly 6-12 weeks to implement. I was looking more alomg the lines of
    > >either obtaining a "standalone" VSS hotfix, or preferably a quicker
    > >resolution via making configuration changes.

    >
    > I totally understand. SP2 is to new to throw on a production machine.
    >
    > I looked more closely at the hotfixes for VSS related stuff on 2K8
    > server and you may want to apply them and see if them help or not.
    > Certainly a hotfix would be less damaging than a full on service pack.
    >
    > Taken from the 2K8 Hotfix Speadsheet at:http://go.microsoft.com/fwlink/?LinkId=143706
    >
    > These are all the VSS related hotfixes in SP2 for 2K8 server you may
    > want to try/look at (even if it's not 100% specific to your issue).
    >
    > http://support.microsoft.com/kb/9566....com/kb/959978
    >
    > Let me know if any of them help.


    Thank you very much. I will look into these and let you know how
    things pan out. Thanks again.

Similar Threads

  1. status disk? status.msi
    By GanGadUtt in forum Windows XP Support
    Replies: 7
    Last Post: 01-04-2012, 02:18 AM
  2. Replies: 7
    Last Post: 15-03-2012, 01:37 PM
  3. Apple TV hard reset and soft reset troubleshoot fixed
    By McKenzie! in forum Monitor & Video Cards
    Replies: 8
    Last Post: 01-10-2011, 01:17 AM
  4. UMD writer
    By Aaron o in forum Portable Devices
    Replies: 3
    Last Post: 22-07-2010, 05:22 PM
  5. Reset CMOS password requires reset bios?
    By Aditya kumar in forum Operating Systems
    Replies: 2
    Last Post: 04-08-2009, 05:27 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •