Solved

VSS Service stops with no Event ID logged.

Posted on 2008-10-09
3
375 Views
Last Modified: 2012-06-27
I have a customer with Wndows Server 2003 SBS.
We run nightly NTBackup jobs for Exchange and other data.
We get an alert from our monitoring software that Volume Shadow Copy Service has stopped. But there is nothing in system or application event logs indicating that the service stopped.
The alarm is reported about 20 minutes after NTbackup logs show the backup completing.
0
Comment
Question by:RichSRV2Win
  • 2
3 Comments
 
LVL 18

Expert Comment

by:sk_raja_raja
ID: 22681076
0
 

Author Comment

by:RichSRV2Win
ID: 22688789
Thanks for the Response sk_raja_raja,
The First link provided goes to an event ID, but that's part of the problem. Even though the monitoring software sees that the VSS service has stopped; there are absolutely NO event ID's logged concerning VSS or Volume Shadow Copy in the event logs.
This is what concerns me. No Event ID's at all? Something has to be wrong.

I did find something from the second link; I have several writers in the Failed state, and Acronis is installed as a provider but that's what we use as a backup of the C: drive of the server in case the server completely crashes.
I checked but can't seem to find a VSS Rollup that applies to 2003 SBS, only for Standard.

Here's what I got from VSSadmin
C:\Documents and Settings\Administrator>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {dfdda699-1e7f-4be9-9c7c-fbbb6d0136c2}
   State: [10] Failed
   Last error: No error

Writer name: 'MSDEWriter'
   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
   Writer Instance Id: {94ddc7d7-852a-49f9-b241-646d70bb5d90}
   State: [1] Stable
   Last error: No error

Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {e2d445cf-f471-4ca4-a61b-05d070954f49}
   State: [10] Failed
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {91c639f1-15e8-448f-b27c-d84e9631ee87}
   State: [1] Stable
   Last error: No error

Writer name: 'WINS Jet Writer'
   Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741}
   Writer Instance Id: {db79f3ad-2638-4f09-b555-f300deff7047}
   State: [10] Failed
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {009bc5d7-26b3-48c3-bba1-235a224a518c}
   State: [10] Failed
   Last error: No error

Writer name: 'Event Log Writer'
   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
   Writer Instance Id: {e0d46395-630f-4e51-9e7f-13771de66e85}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {c15c6703-7c9f-4250-ab19-26449aef8383}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {c17ed71e-e1ee-4d11-bbef-671d8b46ab96}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {b48c0178-053c-4025-9ac0-19ec99121dbb}
   State: [10] Failed
   Last error: No error

Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {6b8a086e-591f-4b67-93e5-116876e6b2cb}
   State: [10] Failed
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {57117aed-4947-4e4f-ba24-70830d416ed9}
   State: [10] Failed
   Last error: No error

Providers:
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7

Provider name: 'Acronis VSS HW Provider'
   Provider type: Hardware
   Provider Id: {f5dbcc43-b847-494e-8083-f030501da611}
   Version: 1.0

Thanks in advance for your help.
0
 

Accepted Solution

by:
RichSRV2Win earned 0 total points
ID: 23066212
I never did find a solution to this issue but after restarting VSS at one point I didn't have the failed writers. This had been performed before but didn't clear the failed state.
0

Featured Post

NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Introduction At 19:33 (UST) on Tuesday 21st September the long awaited email arrived with the subject title of “ANNOUNCING THE AVAILABILITY OF WINDOWS SBS 7 PREVIEW”.  It was time to drop whatever I was doing and dedicate as much bandwidth as possi…
Scenerio: You have a server running Server 2003 and have applied a retail pack of Terminal Server Licenses.  You want to change servers or your server has crashed and you need to reapply the Terminal Server Licenses. When you enter the 16-digit lic…
In a recent question (https://www.experts-exchange.com/questions/28997919/Pagination-in-Adobe-Acrobat.html) here at Experts Exchange, a member asked how to add page numbers to a PDF file using Adobe Acrobat XI Pro. This short video Micro Tutorial sh…

821 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question