sql writer is causing my backup's to fail

Question

We recently installed a new virtual server to run our sql standard 2008 sp2 server. So naturally what any it guy do is to take a backup of the virtual server. First night we tried to take a backup of our virtual hard disk the backup failed.   So naturally we thought that it was Symantec’s fault. We have a Symantec hyper-v license purchased. So we contacted Symantec support and it came up that SqlServerWriter was the cause the backup failed. So we tried to take a full backup of virtual server white Windows server backup. And again the SqlServerWriter was the cause the backup failed. So the very big question is that what setting do I have to put on my server that I am cable of doing nightly backup of my virtual server what is running sql standard server 2008, white out shutting the virtual server down.

 

Under here is some specs of our work environment:

Operating System= Windows Server 2008 R2

Virtual Server Software = Hyper-V Version: 6.1.7600.16385

Program = SQL 2008 sp2 Standard

Backup Software = Symantec Exec 2010

 

And this is the errors what we are getting in the events viewer:

Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 10.0
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3202
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 10.0
Error message: Write on "{05F79733-9897-4BCB-BD4A-DF7D24BF6901}55" failed: 995(failed to retrieve text for this error. Reason: 15105)

event id: 24583

 

2:

A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error.  If the backup process is retried,
the error is likely to reoccur.
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.

Operation:
   PrepareForSnapshot Event

Context:
   Execution Context: Writer
   Writer Class Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Name: SqlServerWriter
   Writer Instance Name: SQL Server 2008:SQLWriter
   Writer Instance ID: {6b1aa3b7-8ca5-4cc6-8195-f10840026b02}
   Command Line: "C:\Program Files\Microsoft SQL Server\90\Shared\sqlwriter.exe"
   Process ID: 1764

SQLVDI: Loc=SVDS::Open. Desc=Open(Control). ErrorCode=(2)The system cannot find the file specified.
. Process=1548. Thread=9392. Server. Instance=MYSQLSERVERSQL. VD=Global\{05F79733-9897-4BCB-BD4A-DF7D24BF6901}449_SQLVDIMemoryName_0.

event id: 8229

3.

Cannot open backup device '{3A3B9929-3BCF-4860-9331-45D490F4DE4A}504'. Operating system error 0x80070002(failed to retrieve text for this error. Reason: 15105).

event id: 3201

 

4.

BACKUP failed to complete the command BACKUP DATABASE c8150_kpt. Check the backup application log for detailed messages.,

event id: 3041

 

5.

BackupIoRequest::ReportIoError: write failure on backup device '{3A3B9929-3BCF-4860-9331-45D490F4DE4A}349'. Operating system error 995(failed to retrieve text for this error. Reason: 15105).

event id: 18210

 

Solution what we have tried is:

 

Registering

 

Run FIXVSS.BAT to reset VSS configuration.
rem FILENAME: FIXVSS03.BAT
rem
net stop "System Event Notification"
net stop "COM+ Event System"
net stop "Microsoft Software Shadow Copy Provider "
net stop "Volume Shadow Copy"
cd /d %windir%\system32
net stop vss
net stop swprv
regsvr32 /s ole32.dll
regsvr32 /s oleaut32.dll
regsvr32 /s vss_ps.dll
vssvc /register
regsvr32 /s /i swprv.dll
regsvr32 /s /i eventcls.dll
regsvr32 /s es.dll
regsvr32 /s stdprov.dll
regsvr32 /s vssui.dll
regsvr32 /s msxml.dll
regsvr32 /s msxml3.dll
regsvr32 /s msxml4.dll
Cd /d %systemroot%\syswow64
regsvr32 /s ole32.dll
regsvr32 /s vss_ps.dll
regsvr32 /s es.dll
regsvr32 /s stdprov.dll
regsvr32 /s msxml3.dll
regsvr32 /s msxml.dll
regsvr32 /s msxml4.dll
net start "COM+ Event System"

doesn't work

 from this site: http://social.technet.microsoft.com/Forums/en-US/winserverfiles/thread/9cf42e8a-2a33-47c5-a797-269330e9ba1a

 

Sow my big question is how do i get my backup's again to work?

 

Sorry if i posted this on the wrong section on the forum. and if anybody needs more information i haven't provided i am happy to give more.

 

 

 

Answer 1

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

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

Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {24525b48-a6ca-497c-86f6-f71ad8e4278d}
   State: [8] Failed
   Last error: Non-retryable error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {6932d8b9-a517-49e0-bf7e-ffaaf11a6859}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {be8b20ed-d54b-4267-8c21-f73d734f5a03}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {7f31edd8-0663-40a2-b685-3274974fa256}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {8f8c3e14-e02c-41aa-bfda-43655a4ff373}
   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: {0e6d8abf-8565-46d8-bc81-7a2da735c7cc}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {64d87d3c-a70f-44e4-a574-814f3f132030}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {c10a7c6a-9cd3-4368-93fe-b6179882674e}
   State: [5] Waiting for completion
   Last error: No error


C:\Users\administrator.myserver>

Answer 2

Hi Skullsoldier,

 

Please try stopping SQL Server VSS Writer from “services.msc” and try again.

---

Regards,
Tom Li

Answer 3

Hi Skullsoldier,

 

Please try stopping SQL Server VSS Writer from “services.msc” and try again.

---

Regards,
Tom Li

hmm i have heard that it's not sow safe to modify services settings

Answer 4

Hello Tom,

I had this same error as the original poster and tried your suggestion of stopping the SQL server VSS writer service, and running the backup again (we use DPM 2010).  It worked after stopping the SQL VSS writer service.   Although this is a fine work around, DPM runs backups on this virtual nightly, so having to stop the service each time we wish to run a backup is not feasable.  Is there a fix available for the reason the VSS writer service is causing backups to fail?   Any suggestions on how to fix the problem?  Or is it save to disable the SQL service VSS writer service permantely?  I'm not certain what role this service plays in our server (it's a WSUS server).

Thanks,

Ted Larsen

Answer 5

Hello Ten Larsen

Restart the SQL Server VSS Writer Service and try again.

I hope this resolved issue.

Answer 6

Check this blog  http://sql-blogs.com/2012/01/17/troubleshooting-vss-writer-issues/ and see if that helps.

 

 

---

Kind regards| Harsh Chawla | Personal Blog:- SQL-blogs
|Team Blog:- Team Blog

Answer 7

The above blog worked for me.

Specifically:

"please check the service logon which is mostly Nt authority/system or any user which you have mentioned as service logon, is added in SQL server as sysadmin privileges or not. If it’s not there then please make it as syadmin"

---

not so lean, not so mean, programming machine

Answer 8

i have completly forgoten this already been fixed from mine part. Harsh Chawla fix worked for me. thanks again. this can be now marked as answred

Answer 9

Can you point which solution worked for you? I have tried all of them but none worked.. thank you..