Windows Server

Jon · Guest

I am getting VSS errors in the event log of my cluster. These errors
occur on both nodes. I am not trying to cluster Volume Shadow Copy. I
have tried what is suggested in KB 812877 to no avail. Any ideas?

Thanks,

Jon

Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 8194
Date: 11/10/2005
Time: 1:28:10 AM
User: N/A
Computer: SERVER1
Description:
Volume Shadow Copy Service error: Unexpected error querying for the
IVssWriterCallback interface. hr = 0x80070005.

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 57 52 54 49 43 WRTWRTIC
0010: 30 30 30 30 30 37 38 35 00000785
0018: 2d 20 43 61 6c 6c 3a 20 - Call:
0020: 57 52 54 57 52 54 49 43 WRTWRTIC
0028: 30 30 30 30 30 37 35 35 00000755
0030: 2d 20 50 49 44 3a 20 20 - PID:
0038: 30 30 30 30 30 33 35 36 00000356
0040: 2d 20 54 49 44 3a 20 20 - TID:
0048: 30 30 30 30 32 35 37 32 00002572
0050: 2d 20 43 4d 44 3a 20 20 - CMD:
0058: 43 3a 5c 57 49 4e 44 4f C:\WINDO
0060: 57 53 5c 43 6c 75 73 74 WS\Clust
0068: 65 72 5c 63 6c 75 73 73 er\cluss
0070: 76 63 2e 65 78 65 20 20 vc.exe
0078: 2d 20 55 73 65 72 3a 20 - User:
0080: 00 00 00 00 00 00 00 00 DOM1\clu
0088: 73 74 65 72 20 20 20 20 ster
0090: 2d 20 53 69 64 3a 20 20 - Sid:
0098: 00 00 00 00 00 00 00 00 S-1-5-12
00a0: 00 00 00 00 00 00 00 00 -1234567
00a8: 00 00 00 00 00 00 00 00 89-12345
00b0: 00 00 00 00 00 00 00 00 67890-12
00b8: 00 00 00 00 00 00 00 00 3456789-
00c0: 00 00 00 00 00 00 00 00 1234

Jon · Guest

Forgot to mention it is Windows Server 2003

Mike Rosado [MSFT] · Guest

Hi Jon,

Not saying the following hotifx will resolve the issue you're seeing, but
may prevent other VSS issues you haven't encountered just yet.

887827 A Volume Shadow Copy Service (VSS) update-2 package is available
http://support.microsoft.com/?id=887827

The error you're seeing in the Application Event log, are typically when
using a 3rd party backup program that utilizes Windows 2003 VSS and has
it's
own requestor. If you run the vssadmin list writers command after a backup
failure, one of the writers may show the last error as Non-Retryable Error
as seen below:

Writer name: 'Cluster Service Writer'
Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
Writer Instance Id: {a23970d8-f802-4e5d-92f5-db428a6c5613}
State: [1] Stable
Last error: Non-retryable error

In the above case: It looks like the requestor (the backup application)
does not allow the cluster writer to call back into their process. Most
likely you call
CoInitializeSecurity with wrong parameters or no call to
CoInitializeSecurity at all.

Technical details: The event message above is coming from the cluster
service process, hosting the cluster writer. At this moment, this is the
only writer that
is running under an administrative account which is not Local System. But
COM disables access by default to everybody except "SELF" (the current
logon session) and Local SYSTEM. This is why you are getting the callback
error event, and the failed cluster writer state.

Please see the following link for more details.
http://msdn.microsoft.com/library/en-us/vss/base/security_considerations_for
_requestors.asp

Explicitly Controlling User Account Access to a Requestor

There are cases where restricting access to a requestor to processes
running as Local System, or under the local Administrators or local Backup
Operators groups, may be too restrictive.

For example, a given writer process (perhaps a third-party non-system
writer) might not ordinarily need to be run under an Administrator or
Backup Operator account. For security reasons, it would be best not to
artificially promote the processes privileges to support VSS.

In these cases, a secure registry location needs to be modified to instruct
VSS that a given user is safe to run a VSS writer.

The following example grants access to the "MyDomain\MyUser" account:

HKEY_LOCAL_MACHINE
SYSTEM
CurrentControlSet
Services
VSS
VssAccessControl <--- ADD KEY
MyDomain\MyUser = 1 <--- ADD VALUE

However - Ultimetly the the OEM backup vendor will need to fix their
requestor to adhere to the standards outlined in the above link.

--------------------
Hope this helps,
Mike Rosado
Windows 2000 MCSE + MCDBA
Microsoft Enterprise Platform Support
Windows NT/2000/2003 Cluster Technologies

====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.
<http://www.microsoft.com/info/cpyright.htm>

simonpearson · Joined: 12 Dec 2005 Posts: 1 Location: NZ

Hi all,

I'm experiencing exactly the same message within Eventvwr (VSS Event 8194), so am keen to add the additional Registry Key and Value that you mention - but what TYPE of Value am I to use for the Domain\Username Value?

Thanks in advance.

	Windows Server Forum Index -> Clustering	All times are GMT
Page 1 of 1