Windows Backups failing due to Exchange VSS writer in Failed state

We are well versed in Windows Backup issues but this one is becoming a real pain.

Backups had been fine for months but all of a sudden they began to fail.

System: SBS 2008 Std
Updates: All updates are installed


Backups are failing due to the VSS Writers being in a failed state. Windows Backup reports "Creation of the Shared protection point timed out. With error 0x81000101"

We have so far done the following:
Registered the DLL files
Checked for a Windows.old folder
Increased "HKLM\Software\\Microsoft\Windows NT\CurrentVersion\SPP\CreateTimeoutt" to 20 mins
Run PSConfig on SharePoint
Followed instructions in http://support.microsoft.com/kb/2009272 which corrects permissions on the %windir%\winsxs folder and subsolders
Deleted the Backup logs
Deleted backup job and recreate
Removed and reinstalled Backup
Run ChkDsk over all drives
Check Value of Registry Key as describe in http://support.microsoft.com/kb/2009533
formatted the USB drives that the backup wites to and setpu backup job again.

Rebooting the server does place all VSS writers in good order. If we check the VSS writer status before a manual backup they are all fine, checking the writers after a failed backup shows the writers in the state listed below. To be fair the state below is not consistent with all the writers but the Exchange Writer is always failed. This we know will always cause the backup to fail.

This is not the only server we have seen this on and we do have another customer suffering the same thing.

Any useful "Fixes" are very welcome.

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\hollandss>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Waiting for responses.
These may be delayed if a shadow copy is being prepared.

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {ed2f1630-f9ba-4156-9804-5fdde2e22712}
   State: [9] Failed
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {e4725353-1b37-460d-8fe6-21044c624a20}
   State: [9] Failed
   Last error: No error

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {ccdefd56-59d0-41c7-9924-6dc226eac284}
   State: [9] Failed
   Last error: No error

Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {ad4ca20f-6509-4320-beee-877ddac543e0}
   State: [9] Failed
   Last error: No error

Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {26bbd6de-1f3a-4c72-a1c2-d5d1ccbc8b3b}
   State: [9] Failed
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {b598452d-46d1-4f89-a8b8-8920e85cfc78}
   State: [9] Failed
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {94d2f0ba-191f-4229-a1b0-9f6c68c77853}
   State: [9] Failed
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {a45a6b98-3043-4476-836b-2d892b9697cc}
   State: [9] Failed
   Last error: No error

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {9883d075-ddf6-4f0b-8b3c-98e608d490cf}
   State: [9] Failed
   Last error: Timed out

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {8a896fe0-382e-4c5f-9a0f-75ffd4341ea3}
   State: [9] Failed
   Last error: No error

Writer name: 'NPS VSS Writer'
   Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
   Writer Instance Id: {83de1dcf-09bc-4136-8abe-b6594ab3b89b}
   State: [9] Failed
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {8cc23956-dbeb-4cfa-b6d0-3ec442dd5a3a}
   State: [1] Stable
   Last error: No error

Writer name: 'Certificate Authority'
   Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
   Writer Instance Id: {a349e8f4-d7de-48a4-9303-6076862a1793}
   State: [9] Failed
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {8faec124-6439-4ef9-bc66-59ad3267d8b8}
   State: [9] Failed
   Last error: No error

Writer name: 'FSRM Writer'
   Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
   Writer Instance Id: {460372ef-a06f-463b-82c7-385648f515ce}
   State: [9] Failed
   Last error: No error

Writer name: 'TS Gateway Writer'
   Writer Id: {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}
   Writer Instance Id: {f181b0b7-34e3-474f-aa37-c67458465472}
   State: [9] Failed
   Last error: No error

Writer name: 'Microsoft Hyper-V VSS Writer'
   Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
   Writer Instance Id: {ac3454f0-7050-4f4d-9dcc-c7389c0cd6e3}
   State: [9] Failed
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {fe903f51-5202-4d67-8bb2-d36ab939526c}
   State: [9] Failed
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {06e675f0-6224-4ea2-9ea5-60e3c7b120d4}
   State: [9] Failed
   Last error: No error

Writer name: 'TermServLicensing'
   Writer Id: {5382579c-98df-47a7-ac6c-98a6d7106e09}
   Writer Instance Id: {a4a69d38-39ec-4d77-9a9f-61e7c4fde10d}
   State: [9] Failed
   Last error: No error
dilesAsked:
Who is Participating?
 
dilesConnect With a Mentor Author Commented:
This was the fix for the backups to become successful

Run this in an elevated command box

12.   We ran following commands and set the proper permissions:

Takeown /f %windir%\winsxs\temp\PendingRenames /a
icacls %windir%\winsxs\temp\PendingRenames /grant "NT AUTHORITY\SYSTEM:(RX)"
icacls %windir%\winsxs\temp\PendingRenames /grant "NT Service\trustedinstaller:(F)"
icacls %windir%\winsxs\temp\PendingRenames /grant BUILTIN\Users:(RX)
Takeown /f %windir%\winsxs\filemaps\* /a
icacls %windir%\winsxs\filemaps\*.* /grant "NT AUTHORITY\SYSTEM:(RX)"
icacls %windir%\winsxs\filemaps\*.* /grant "NT Service\trustedinstaller:(F)"
icacls %windir%\winsxs\filemaps\*.* /grant BUILTIN\Users:(RX)
net stop cryptsvc
net start cryptsvc

Regards
Dave
0
 
MaheshArchitectCommented:
try below

Open Sharepoint 2010 management shell (Run as administrator)
 
Paste the command: stsadm -o registerwsswriter
 
You should now able to perform windows server backup without issues

http://social.technet.microsoft.com/Forums/en-US/fde27d05-de37-4484-aebf-8e99ca126378/sbs2008-backup-error-creation-of-the-shared-protection-point-timed-out-unknown-error-0x81000101?forum=smallbusinessserver

Mahesh
0
 
dilesAuthor Commented:
This server is SBS 2008, it has V3 installed by default.

Regards
Dave
0
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

 
WORKS2011Austin Tech CompanyCommented:
How much free space do you have a snapshot requires at least 10 % of the volume to be free.
0
 
dilesAuthor Commented:
Disk space is not an issue without looking its around 100gig on the O/S Drive and around 600gig on the DATA drive.
0
 
dilesAuthor Commented:
Well this has been a challenge. In the end we involved Microsoft support. This was done last Wednesday. The backups are working but only with SQL and SharePoint services disabled. The engineer is still working on it today. I will update with the final answer when we have it. (It makes me feel a bit better that a MS engineer has found this difficult to resolve - 4th Working day now)

Anyway I had another VSSbackup issue on a different server  and found by disabling the same services as above this did not cure the issue, What I did find is that I had enabled VSS Tracing and by deleting the following key the backups have been successful. HKLM\SYSTEM\CurrentControlSet\Services\VSS\Debug\Tracing". I have left the SQL/SP Services disable for now waiting for the resolve with MS Engineer. Hoping it will be the same issue.

I will report back again about both systems when MS has resolved the issue with SQL/SP.

Regards
Dave
0
 
dilesAuthor Commented:
It fixed it.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.