Backup says unable to query writer status but all writers on target system are stable

I backup two Citrix Servers that are each running on a Windows 2003 Server with SP2 and all current Windows updates with Backup Exec 2010 R3 (Version 13.0 Rev 5204).  In the last two days the System State backups of these two servers have failed saying the VSS Writer failed.  What I find confusing is that when I run vssadmin list writers on the two servers everything comes up as Stable with no errors.

 

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: {32270a12-4de2-4164-9af7-6b8d43eaa0b5}
   State: [1] Stable
   Last error: No error

Writer name: 'MSDEWriter'
   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
   Writer Instance Id: {46707f75-5707-4004-9faa-2bf80896a1bc}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {c1ecf071-c40a-4eb5-93eb-3b48ea896877}
   State: [1] Stable
   Last error: No error

Writer name: 'Event Log Writer'
   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
   Writer Instance Id: {c2b54ef1-07f4-4231-aa2d-223bf8ecb3d9}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {e529da6a-62d1-40ca-89d0-06e8d8523e95}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {8ef303a2-1510-4a96-9338-aa6e3db57ec6}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {b57e284f-bbdb-4d4a-ae88-b8ed2772b655}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {513ab1d0-3a22-4dc4-927a-273cb08ba43b}
   State: [1] Stable
   Last error: No error

 

In the event log I see the following error:

 

Event Type:    Error
Event Source:    VSS
Event Category:    None
Event ID:    8193
Date:        4/3/2012
Time:        8:15:04 PM
User:        N/A
Computer:    LFCTX005
Description:
Volume Shadow Copy Service error: Unexpected error calling routine RegSaveKeyExW.  hr = 0x800703f8.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2d 20 43 6f 64 65 3a 20   - Code:
0008: 57 52 54 52 45 47 52 43   WRTREGRC
0010: 30 30 30 30 30 33 39 36   00000396
0018: 2d 20 43 61 6c 6c 3a 20   - Call:
0020: 57 52 54 52 45 47 52 43   WRTREGRC
0028: 30 30 30 30 30 33 31 38   00000318
0030: 2d 20 50 49 44 3a 20 20   - PID:  
0038: 30 30 30 32 35 35 38 38   00025588
0040: 2d 20 54 49 44 3a 20 20   - TID:  
0048: 30 30 30 32 34 30 31 36   00024016
0050: 2d 20 43 4d 44 3a 20 20   - CMD:  
0058: 4d 3a 5c 57 49 4e 44 4f   M:\WINDO
0060: 57 53 5c 53 79 73 74 65   WS\Syste
0068: 6d 33 32 5c 76 73 73 76   m32\vssv
0070: 63 2e 65 78 65 20 20 20   c.exe   
0078: 2d 20 55 73 65 72 3a 20   - User:
0080: 4e 54 20 41 55 54 48 4f   NT AUTHO
0088: 52 49 54 59 5c 53 59 53   RITY\SYS
0090: 54 45 4d 20 20 20 20 20   TEM     
0098: 2d 20 53 69 64 3a 20 20   - Sid:  
00a0: 53 2d 31 2d 35 2d 31 38   S-1-5-18
 

 

I know that Microsoft says to install the latest 2003 VSS Rollup packs and I have tried to do so though all of them said they are older than the versions in SP2.  I was wondering if anyone else ran into anything like this.  Could it be a Citrix issue?

I would really prefer to not reboot the servers until the weekend.

1 Solution

Accepted Solutions
Accepted Solution!

These didn't work.   I found

These didn't work.

 

I found the answer was to restart the services attached to these writers.

3 Replies

Run vssadmin list writers

Run vssadmin list writers directly after a failed backup.

Hi there,   MIght also be

Hi there,

 

MIght also be worth your while to reregister the VSS *.dlls. Check the TN below for more information:

http://www.symantec.com/business/support/index?page=content&id=TECH70486

Thanks!

Accepted Solution!

These didn't work.   I found

These didn't work.

 

I found the answer was to restart the services attached to these writers.