Subjective:EVENT ID: 12289 - Source: VSS Volume Shadow Copy Service error: Unexpected error VSS_E_WRITER_STATUS_NOT_AVAILABLE. An older active writer session state is being overwritten by a newer session. The most common cause is that the number of parallel backups has exceeded the maximum supported limit. hr = 0x80042409. Objective:Shadow copies succeed but the error indicates that after 64 "uses" either the Writer unnecessarily keeps 64 sessions or that the session counter is broken. Reproduced on multiple production systems and on clean DVD installs of Windows 2008 R1 (regardless of SP level). Not reproduced on 2008 R2. Sessions are reset after server reboot and the counter continues to 64. 65th shadow copy produces this error because the writer arrived at the limit of 64 sessions and is forced to get rid of the oldest session in order to serve the newest shadow copy request. Writers usually involved are WMI Writer and TermServLicensing, but multiple others seem to participate at times. My Question:Would anyone know whether there is a hotfix for 2008 R1 that provides a VSS "facelift" and would address this problem?FYI, the problem is easily reproducible by creating 65 shadow copies on any 2008 R1 box we have - you can keep track of sessions by looking up the shadow copy number in ESENT info events in the app log. With a script we can go from reboot to error in 20 minutes.

HiTo resolve this issue. Refer the below article . It has the similar issue.http://technet.microsoft.com/en-us/l.../cc734302.aspxAlso refer the below articles:http://forum.storagecraft.com/Commun...6321.aspx#6321http://msdn.microsoft.com/en-us/libr...8VS.85%29.aspx Thanks...Deva --Self-trust is the first secret of success.

Hi MiloPG ,Thank you for posting in windows server forums, Deva the article http://technet.microsoft.com/en-us/l.../cc734302.aspx refers to the event id 12293 . Please refer to the below technet article and follow the troubleshooting steps defined and reply back if it resolved the issue http://technet.microsoft.com/en-us/library/ee264206(WS.10).aspxsainath !analyze

Hello,Apologies for leaving this thread for so long without confirmation. I have checked the link you posted and it does not lead me any closer to a solution or explanation. 1. The one check in the link suggesting to make sure the VSS service is enabled is confirmed. VSS service is enabled, starting and running as it should. 2. The VSS Event appearing in the Application log has a link called "More: Event Log Online" which naively searches the MS site for the event and it does not come up with anything. (Pasting in the outcome of following the link) Results for: Microsoft Product: Windows Operating System; Version: 6.0.6002.18005; Event ID: 12289; Event Source: VSS; No results were found for your query. Please see Search Help for suggestions. 3. There is no third party vendor involved. I have originally experienced the error event with Veritax NetBackup but in testing I reduced the repro to not using any third party tools. Only taking a shadow copy of system state is enough to reproduce the problem - with any backup program. I am unmarking your reply as Answer. Would you have any other suggestions?thanks

We are having the same problems with multiple 2008 servers that we support as well. When we use the Storagecraft provider for backups everything works fine, but when we use the VSS provider to complete the end-of-day/last of day backups we receive these 12289, 12302 and 13 errors.Our primary concern is that we do not yet have a definitive answer telling us whether or not these errors can/should be ignored or are a larger problem. Here are some of the event logs for the problem: Volume Shadow Copy Service error: Error creating the Shadow Copy Provider COM class with CLSID {e4eb5095-f587-4159-a1d8-2710692fd243} [0x80070424]. Operation: Obtain a callable interface for this provider Check If Volume Is Supported by Provider Add a Volume to a Shadow Copy Set Context: Provider ID: {24602736-bed9-4619-91b0-243447c6409c} Class ID: {00000000-0000-0000-0000-000000000000} Snapshot Context: 4194306 Execution Context: Coordinator Provider ID: {24602736-bed9-4619-91b0-243447c6409c} Volume Name: \\?\Volume{5aa0833c-e8ec-11de-abc3-0026b9435d07}\ Execution Context: Coordinator Volume Shadow Copy Service information: The COM Server with CLSID {e4eb5095-f587-4159-a1d8-2710692fd243} and name SW_PROV cannot be started. [0x80070424] Operation: Obtain a callable interface for this provider Check If Volume Is Supported by Provider Add a Volume to a Shadow Copy Set Context: Provider ID: {24602736-bed9-4619-91b0-243447c6409c} Class ID: {00000000-0000-0000-0000-000000000000} Snapshot Context: 4194306 Execution Context: Coordinator Provider ID: {24602736-bed9-4619-91b0-243447c6409c} Volume Name: \\?\Volume{5aa0833c-e8ec-11de-abc3-0026b9435d07}\ Execution Context: Coordinator Volume Shadow Copy Service information: The COM Server with CLSID {e4eb5095-f587-4159-a1d8-2710692fd243} and name SW_PROV cannot be started. [0x80070424] Operation: Obtain a callable interface for this provider Check If Volume Is Supported by Provider Add a Volume to a Shadow Copy Set Context: Provider ID: {24602736-bed9-4619-91b0-243447c6409c} Class ID: {00000000-0000-0000-0000-000000000000} Snapshot Context: 16 Execution Context: Coordinator Provider ID: {24602736-bed9-4619-91b0-243447c6409c} Volume Name: \\?\Volume{5aa0833c-e8ec-11de-abc3-0026b9435d07}\ Execution Context: Coordinator Volume Shadow Copy Service error: Error creating the Shadow Copy Provider COM class with CLSID {e4eb5095-f587-4159-a1d8-2710692fd243} [0x80070424]. Operation: Obtain a callable interface for this provider Check If Volume Is Supported by Provider Add a Volume to a Shadow Copy Set Context: Provider ID: {24602736-bed9-4619-91b0-243447c6409c} Class ID: {00000000-0000-0000-0000-000000000000} Snapshot Context: 16 Execution Context: Coordinator Provider ID: {24602736-bed9-4619-91b0-243447c6409c} Volume Name: \\?\Volume{5aa0833c-e8ec-11de-abc3-0026b9435d07}\ Execution Context: Coordinator

Hi MiloPG,Please check to see if this KB article is helpful.VSS error "0x80042409" is logged in the Application log when a VSS restore operation is performedhttp://support.microsoft.com/kb/978773/en-usThanks.This posting is provided "AS IS" with no warranties, and confers no rights.

We are having the exact same problem on our SBS2k8 server using the built in backup system. I don't understand how the "answer" proposed by David Shen (and marked as an answer by him as well) can possibly address this issue since the article he points to is a completely different version of this event.