Quantcast
Channel: Backup – Windows and Windows Server forum
Viewing all articles
Browse latest Browse all 1854

VSS writers timeout Server2008 R2

$
0
0

Hello everyone

I have been having continual issue with IIS, WMI and System writers on Windows Server2008 R2

Using Symantec BE, jobs keep failing and the writer status's keep reverting to timeouts state after/during a jobs running.

Doing a restart on the server brings all the states to stable, but then when the job runs and fails, the writers are timed-out.

I can't seem to find any solution to this issue on server2008 besides the good old restart, which isn't cutting it anymore.

Anyway to update/reinstall system writers?

Any solution/tips are appreciated!

Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {fcbf184f-1e94-4a36-8091-edfe015d1fe4}
   State: [9] Failed
   Last error: Timed out

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {2501958d-028c-45a2-856b-4b29900e8857}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {4def43fe-5338-4e59-b145-041535251577}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {bb5d49bc-8368-46cf-9c98-4be19c800925}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {a5802642-22eb-434a-b906-0cc6cdb383fe}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {8001258e-65af-4fd1-8269-ae03d4db44ac}
   State: [9] Failed
   Last error: Timed out

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {fbcae7e1-2575-4a12-a657-59242e480b8e}
   State: [9] Failed
   Last error: Timed out

EVENT VIEWER LOG

Log Name:      Application
Source:        VSS
Date:          07/11/2013 7:09:04 PM
Event ID:      8224
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      !!!!!!!!
Description:
The VSS service is shutting down due to idle timeout.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="VSS" />
    <EventID Qualifiers="0">8224</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-07-11T23:09:04.000000000Z" />
    <EventRecordID>13213</EventRecordID>
    <Channel>Application</Channel>
    <Computer>!!!!!.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>
    </Data>
    <Binary>2D20436F64653A2020434F525356434330303030303737332D2043616C6C3A2020434F525356434330303030303735352D205049443A202030303030343330342D205449443A202030303030323335322D20434D443A2020433A5C57696E646F77735C73797374656D33325C76737376632E6578652020202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>
  </EventData>
</Event>


Viewing all articles
Browse latest Browse all 1854

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>