This post is more than 5 years old
84 Posts
0
236306
VSS event ID 8194 after installing HIT 4.6
I have seen this with a few separate customers now. Event ID Error 8194 appears on Hyper-V 2012 hosts with the HIT installed. Has anyone seen this?
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied.
. This is often caused by incorrect security settings in either the writer or requestor process.
Operation:
Gathering Writer Data
Context:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {c4cafe6b-9e92-49e6-b95e-35b7cd4c0cac}
The forum below intimates this has been seen before and points to the HIT.
austin-t
84 Posts
2
January 28th, 2014 08:00
It would appear a working solution is to configure removing access to the network service account, what it actually does is to stop the call to VSS, hence no access denied error is reported. The double \\ is the output from the registry export and is required.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl]
"NT Authority\\NetworkService"=dword:00000000
austin-t
84 Posts
0
January 16th, 2014 04:00
This did not work :(
austin-t
84 Posts
0
January 16th, 2014 04:00
Found this after I posted. Can anyone confirm this is a fix?
workinghardinit.wordpress.com/.../dell-compellent-hardware-vss-provider-commvault-on-windows-server-2012-hyper-v-nodes-volume-shadow-copy-service-error-unexpected-error-querying-for-the-ivsswritercallback-interface-hr-0x80
Dev Mgr
9.3K Posts
0
January 17th, 2014 12:00
Are you using 2012 or 2012 R2? The hitkit 4.6 is not compatible with 2012 R2 (ASM doesn't recognize the VSS writers from what I can tell (but MPIO seems to work)).
austin-t
84 Posts
0
January 18th, 2014 01:00
Thanks for responding.
Windows 2012 not R2
mirko.schnellba
25 Posts
0
January 21st, 2014 06:00
Yes, I see this on my clustered hosts. Stopping "EqualLogic Auto-Snapshot Manager Agent" on all nodes gets rid of the events (which themselves are ok to be ignored). This will have no impact on MPIO or hardware VSS provider, but obviously Auto-Snapshot Manager won't work.
As this is a known issue in cluster environments, I hope HIT 4.7 (whenever that hits) will have a work around.
Zer0kbps
3 Posts
1
June 5th, 2014 02:00
Thanks for this Austin, I had a 4 node hyper-v cluster logging these events constantly, it's been driving me mad for a year, so far so good.
Kind Regards,
Austen.
A.W
63 Posts
0
July 19th, 2014 06:00
HIT 4.7 does not fix the known issue...
but, HIT 4.7 running on 2008r2 cluster does not have the same issue...
A.W
63 Posts
0
July 19th, 2014 06:00
HIT 4.7 does not fix the known issue...
ScruffyChancer
2 Posts
0
December 8th, 2014 09:00
Worked for me - thanks Austin-T.
CAVRaza
10 Posts
0
December 8th, 2014 15:00
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl]
"NT Authority\\NetworkService"=dword:00000000
Do not change to zero as above but u can add another account without any harm. if u change default account to zero, Host will start giving blue screen during heavy load. I have tested that and rolled back!
pyasuda
3 Posts
0
December 30th, 2014 13:00
CAVRaza, please give an example. Add a NT Authority\System with dword= 0x0? So the VssAccountControl key will have 2 values?
Craigondrums
32 Posts
0
March 9th, 2016 15:00
Hey Austin - I upgraded our HIT from 4.5 to 4.8 tonight and faced this issue. Happy to have found this article. The reg edit fixed it. We don't use the ASM anyway ;)