ollybuba
asked on
SBS 2011 Event ID 8194
I have a 7 month old SBS 2011 Standard with SP 1. When checking the event logs I get an Event ID 8194. I ran "vssadmin list writers" in cmd and the only thing listed with an error is:
Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8
Writer Instance Id: {af84cb4d-591c-4fb0-9883-6
State: [8] Failed
Last error: Retryable error
The error only occurs when the server is performing a backup. I use Cobian backup to backup all of my servers and it seems to work well. I also receive warnings 8230 and 13567 pertaining to the file services role quite often. More so the 8230 warning than the 13567.
Any thoughts?
Thanks
Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8
Writer Instance Id: {af84cb4d-591c-4fb0-9883-6
State: [8] Failed
Last error: Retryable error
The error only occurs when the server is performing a backup. I use Cobian backup to backup all of my servers and it seems to work well. I also receive warnings 8230 and 13567 pertaining to the file services role quite often. More so the 8230 warning than the 13567.
Any thoughts?
Thanks
ASKER
I'm not sure how to bring the Vsswriter into stable state.
Restart Information STore service
once done open Command prompt and type the below command and hit enter
vssadmin list writers
- Rancy
once done open Command prompt and type the below command and hit enter
vssadmin list writers
- Rancy
ASKER
It says that it is stable. Now do I just wait and let my backup run tonight and check and see if I get the retryable error in the morning?
Yes sir thats what you need to do and ensure that before backup all writers are stable or your backups will fail
- Rancy
- Rancy
ASKER
What if they say "waiting for completion"?
Thats isnt good as well so all should be stable for others you might have to restart the server as well
- Rancy
- Rancy
you need to check for the vss related updated files for your server for example:
ntfs.sys
volsnap.sys
swprv.dll
also check the drive where exchange database or logs exist for chkdsk errors
if errors persists then first fix it with chkdsk/f/r and then update these files with
their latest versions and then check this will most probably resolve the issue,
ntfs.sys
volsnap.sys
swprv.dll
also check the drive where exchange database or logs exist for chkdsk errors
if errors persists then first fix it with chkdsk/f/r and then update these files with
their latest versions and then check this will most probably resolve the issue,
ASKER
My 2008 R2 Terminal Server is having the same problems when I run the vssadmin list writers command. It doesn't show it as having any errors but it does say that a bunch of writers states are [5] Waiting for completion. Could this be problem caused by my backup software? I am using Cobian 11.2.0.580.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The problem was with Cobian backup. If I disabled the Cobian backup and Cobian VSS service and restarted the server it would work fine.
DO you bring the Vsswriter into stable state before backup ?
- Rancy