VSS 8194 Event ID Error

I am receiving the above error from VSS in my application logs when I try to
backup with Mozy and Retrospect....

I was on the phone with Mozy support trying to debug the probelm with no
luck. We've tried reregistering the vss dlls and restarting services with no
luck.

As soon as Mozy reports it is doing the shadow copy I get the log entry
below. After reboot it is clear.

Vssadmin list writers always displays this after the bad shadow copy also:

Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {8ee71f5a-4c1a-4822-8f0a-7886bde8880b}
State: [1] Stable
Last error: Non-retryable error

Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {d2e8cc32-aea9-4388-aa65-c0099f2a46f2}
State: [5] Waiting for completion
Last error: No error

Writer name: 'MSSearch Service Writer'
Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
Writer Instance Id: {4dd49e66-f99d-44bc-af18-121ecc7add85}
State: [5] Waiting for completion
Last error: No error

Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {b41f32fa-c40f-4e33-860c-876c7c086e43}
State: [5] Waiting for completion
Last error: No error

Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {414ff5ca-5788-4ab7-bf0b-43d4b31635c0}
State: [5] Waiting for completion
Last error: No error

Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {21dccfed-4e1f-4286-81d8-a0aee02ed7d4}
State: [5] Waiting for completion
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {a90a98db-6ecc-4df0-98e9-eddc610f7874}
State: [5] Waiting for completion
Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {8c2e2e36-1030-41a1-be03-43f9312b864c}
State: [5] Waiting for completion
Last error: No error


Here is the copy from the event log details:


- System

- Provider

[ Name] VSS

- EventID 8194

[ Qualifiers] 0

Level 2

Task 0

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2009-06-29T04:56:56.000Z

EventRecordID 6756

Channel Application

Computer MAIN

Security


- EventData

0x80070005
Operation: Gathering Writer Data Context: Writer Class Id:
{e8132975-6f93-4464-a53e-1050253ae220} Writer Name: System Writer Writer
Instance ID: {af302b14-01a6-44a8-996d-39283fdb7ac2}

2D20436F64653A20575254575254494330303030313038382D2043616C6C3A20575254575254494330303030313035362D205049443A202030303030313232382D205449443A202030303030343832342D20434D443A2020433A5C57696E646F77735C73797374656D33325C737663686F73742E657865202D6B204E6574776F726B53657276696365202020202020202D20557365723A204E5420415554484F524954595C4E4554574F524B2053455256494345202020202D205369643A2020532D312D352D3230


--------------------------------------------------------------------------------

Binary data:


In Words

0000: 6F43202D 203A6564 57545257 43495452
0008: 30303030 38383031 6143202D 203A6C6C
0010: 57545257 43495452 30303030 36353031
0018: 4950202D 20203A44 30303030 38323231
0020: 4954202D 20203A44 30303030 34323834
0028: 4D43202D 20203A44 575C3A43 6F646E69
0030: 735C7377 65747379 5C32336D 68637673
0038: 2E74736F 20657865 4E206B2D 6F777465
0040: 65536B72 63697672 20202065 20202020
0048: 7355202D 203A7265 4120544E 4F485455
0050: 59544952 54454E5C 4B524F57 52455320
0058: 45434956 20202020 6953202D 20203A64
0060: 2D312D53 30322D35


In Bytes

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 31 30 38 38 00001088
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 31 30 35 36 00001056
0030: 2D 20 50 49 44 3A 20 20 - PID:
0038: 30 30 30 30 31 32 32 38 00001228
0040: 2D 20 54 49 44 3A 20 20 - TID:
0048: 30 30 30 30 34 38 32 34 00004824
0050: 2D 20 43 4D 44 3A 20 20 - CMD:
0058: 43 3A 5C 57 69 6E 64 6F C:\Windo
0060: 77 73 5C 73 79 73 74 65 ws\syste
0068: 6D 33 32 5C 73 76 63 68 m32\svch
0070: 6F 73 74 2E 65 78 65 20 ost.exe
0078: 2D 6B 20 4E 65 74 77 6F -k Netwo
0080: 72 6B 53 65 72 76 69 63 rkServic
0088: 65 20 20 20 20 20 20 20 e
0090: 2D 20 55 73 65 72 3A 20 - User:
0098: 4E 54 20 41 55 54 48 4F NT AUTHO
00a0: 52 49 54 59 5C 4E 45 54 RITY\NET
00a8: 57 4F 52 4B 20 53 45 52 WORK SER
00b0: 56 49 43 45 20 20 20 20 VICE
00b8: 2D 20 53 69 64 3A 20 20 - Sid:
00c0: 53 2D 31 2D 35 2D 32 30 S-1-5-20

Any help would be greatly appreciated!!!! (This error is occuring on my
custom built desktop and my HP laptop both with Vista 64 Bit Ultimate
installed. I have Service Pack 2 installed)
 

Question Info


Last updated February 25, 2019 Views 14,792 Applies to:

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Hello jyeager28,

 Thank you for using Microsoft Windows Vista Forums.

 Have you been able to perform a back up with Mozy and Retrospect successfully in the past?  I have added a link below with some information with this error.  Please let us know status.  Thanks!

Microsoft TechNet:
Event ID 8194 — Volume Shadow Copy Service Operations
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = %1. This is often caused by incorrect security settings in either the writer or requestor process. %2
 

To troubleshoot this error condition, you first need to determine what caused it by using the VssAdmin command line tool. After determining the cause of the error condition, follow the steps indicated for each possible cause.

http://technet.microsoft.com/en-us/library/cc734235(WS.10).aspx


James Microsoft Answers Support Engineer Visit our Microsoft Answers Feedback Forum and let us know what you think.

2 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I have tried all means of fixing this. I have even been on with Mozy 2nd level support. They cannot determine the problem. The error occurs with Retrospect, Mozy and Diskeeper with VSS defrag enabled.

I need to schedule a time with a 2nd level support person for he/she to access my system to look at what is going on. The Mozy support person wants to be on remotely as well.

Please let me know whena support person can be on M-F 10:00 AM - 4:00 PM EDT....

2 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I also have a VSS trace file. Is there any way to upload it here?

2 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I've also been plagued by this problem by Mozy on my SBS 2003 R2 server. It's identical to yours, except my path is pointing Sharepoint's mssearch.exe rather than svchost.exe. You might want to find out which service within your svchost.exe is the offending party (use Process Explorer). Bottom line is that 8194 appears every time Mozy runs.

Interestingly, there are long stretches where it gets into a good phase and doesn't do it. For example, it was good for a couple months until I installed SP2 for Sharepoint 3.0, and then it started happening again. Perhaps it's whichever is installed last, I don't know.

In any case, I thought the fix here (Registry mod at the end) helped, at least for a while, but I'm not sure. In my case, I added the account that the Sharepoint service uses. If you haven't tried it already, do.
http://msdn.microsoft.com/en-us/library/aa384604(VS.85).aspx

Incidentally, there are messages going back years tying Mozy (and some other programs) to this. It's time they fixed it.

2 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I've tried your registry fix and no change.

This error occurs with Mozy, Retrospect and Diskeeper with VSS defrag enabled however, the builtin backup program runs fine.

I've also wiped my machine and reloaded windows and then installed Mozy and tried a backup, same error.

I've installed Vista SP2 and subsequent post fixes with no luck either.

MICRSOFT, PLEASE FIX THIS!!!!!!!!

2 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I've tried your registry fix and no change.

This error occurs with Mozy, Retrospect and Diskeeper with VSS defrag enabled however, the builtin backup program runs fine.

I've also wiped my machine and reloaded windows and then installed Mozy and tried a backup, same error.

I've installed Vista SP2 and subsequent post fixes with no luck either.

MICRSOFT, PLEASE FIX THIS!!!!!!!!

2 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

jyeager28,
We would like to get a better understanding of this issue so we can better assist not only you but other users with similar problems as well. 

Please send an email to *** Email address is removed for privacy *** with your direct contact information and a time frame you are able to work on this issue.  A support engineer will contact you within 24 business hours. Once a resolution has been found we will return to this post to document the resolution that was found.

Thank you,


Gloria
Microsoft Answers Support Engineer
Visit our Microsoft Answers Feedback Forum and let us know what you think.

2 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

If you need any further assistance on my end, I'm available.

I did contact Mozy again about this, and they assured me they're on the case. It's unclear whether the fault lies with the individual vendors or MS.

2 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I am also seeing these errors in my logs.   However, it is not clear from these posts if the Mozy backups are really impacted due to this error.  Can someone confirm that there is an issue with the actual data backup?  Everything appears to backup from what I am seeing in Mozy.

Thanks,
Gerry

2 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

That's right, there's no impact at all. It's just one of those things that's been cluttering up logs for years and that should stop.

2 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.