Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Minesalatte
Starting Member
10 Posts |
 Posted - 2010-01-19 : 07:19:12
|
| Windows 2003 Enterprise SP2SQL 2005 Standard Edition 9.0.4035Trying to backup my databases using VSS and am getting "SqlServerWriter" has reported an error 0x800423f4. This is accompanied with a variety of errors in the event log (below). I seem to be bouncing around a bit trying to find the root cause and subsequent resolution, TechNet mentions installing a VSS hotfix but this seems to not apply to Windows 2003 SP2, TechNet in the SQL section lead nowhere so I'm asking more in the heart of SQL community.Example event log entries:###SQLVDI: Loc=BufferAreaManager::MapBuffers. Desc=Out Of Address Space. ErrorCode=(8)Not enough storage is available to process this command.. Process=1468. Thread=8124. Server. Instance=MSSQLSERVER. VD=Global\{B898A689-46FE-4166-8CE8-697917FADB2F}111_SQLVDIMemoryName_0. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.SQLVDI: Loc=SVDS::Close. Desc=Open devices!. ErrorCode=(0). Process=1468. Thread=8124. Server. Instance=MSSQLSERVER. VD=Global\{B898A689-46FE-4166-8CE8-697917FADB2F}111_SQLVDIMemoryName_0. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=1468. Thread=8124. Server. Instance=MSSQLSERVER. VD=Global\{B898A689-46FE-4166-8CE8-697917FADB2F}111_SQLVDIMemoryName_0. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.SQLVDI: Loc=SVDS::Open. Desc=Map(Control). ErrorCode=(8)Not enough storage is available to process this command.. Process=1468. Thread=9148. Server. Instance=MSSQLSERVER. VD=Global\{B898A689-46FE-4166-8CE8-697917FADB2F}108_SQLVDIMemoryName_0. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.BackupVirtualDeviceSet::Initialize: Request large buffers failure on backup device '{B898A689-46FE-4166-8CE8-697917FADB2F}111'. Operating system error 0x8007000e(Not enough storage is available to complete this operation.).For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.Cannot open backup device '{B898A689-46FE-4166-8CE8-697917FADB2F}108'. Operating system error 0x80070008(Not enough storage is available to process this command.).For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013Error state: 1, Severity: 16Source: Microsoft SQL Native ClientError message: BACKUP DATABASE is terminating abnormally.SQLSTATE: 42000, Native Error: 18210Error state: 1, Severity: 16Source: Microsoft SQL Native ClientError message: BackupVirtualDeviceSet::Initialize: Request large buffers failure on backup device '{B898A689-46FE-4166-8CE8-697917FADB2F}111'. Operating system error 0x8007000e(Not enough storage is available to complete this operation.).For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.###The errors relating to not having enough storage is available is bizarre since there's plenty of space >80% Free on same disk as databases. A lot of my searches keep pointing at virtual memory blocks rather than actual storage space but this is more around the Red Gate community, with talk of using EXEC master..sqbmemory to help find if my virtual memory blocks are used up. I don't use Red Gate so can't install master..sqbmemory (http://www.red-gate.com/supportcenter/Content.aspx?c=knowledgebase\SQL_Backup\KB200707000057.htm&p=SQL%20Backup). For the last error I came across an interesting MS KB article (http://support.microsoft.com/kb/919023Without understanding the root cause I don't want to start making any of the suggested changes, has anyone has seen and hopefully resolved these issues, any points the right direction would be appreciated.Thanks. |
|
|
Minesalatte
Starting Member
10 Posts |
Posted - 2010-01-22 : 05:42:30
|
| Not really a fix, more a work around. I stopped the SqlServerWriter service and switched to MSDEWriter in the registry, MSDEVersionChecking =0as per this article:[url]http://wiki.r1soft.com/pages/viewpage.action?pageId=4459836[/url]It looks to have got rid of the errors. |
 |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2010-01-22 : 07:24:29
|
| we don't use VSS for SQL, but you ARE taking MSSQL backups too right? |
|
|
|
Minesalatte
Starting Member
10 Posts |
Posted - 2010-01-22 : 09:31:57
|
| I'm actually using R1soft for backing up the server which then uses VSS, I thought it was a VSS issue as I got the problem when running it independently of R1soft. I was a bit quick on the draw as I now get "'MSDEWriter' is in failed state" with R1 (VSS manually is fine), which I'll take up with R1 as first point.I use a maintenance plan to backup the system databases, but rely on R1soft for the rest. R1 has never previously failed us, but I wouldn't be so confident with the current issues I am seeing. I've previously used a maintenance plan to backup all databases to a mounted NFS share, I'm considering going back to this until I get this resolved. |
|
|
|
|
|
|
|
|
SqlServerWriter error using VSS