SQL Native Client - SQL Server Forums

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.

All Forums

SQL Server 2000 Forums

SQL Server Administration (2000)

SQL Native Client

Author

Topic

jonathan4465
Starting Member

5 Posts

Posted - 2006-11-15 : 11:02:38

I'm not sure if this is where this belongs, but here it goes:

We have a Windows 2003 Server with SQL 2000 SP3a installed which runs a Sharepoint database. I came into work today and found out another admin "mistakenly" installed the SQL 2005 native client on the Windows 2003\SQL 2000 server. Now, when you try to run a backup VSS wont work! Here are the errors:

SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=420. Thread=8616. Client. Instance=MSFW. VD=Global\{9FB9355D-9BD4-433D-B1CD-028C82E5A4EF}1.

Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft OLE DB Provider for SQL Server
Error message: BACKUP DATABASE is terminating abnormally.

None of this happened until the 2005 native client was installed. I'm not very good with SQL, so I'm asing if this 2005 native client overwrote the 2000 client or something of that nature? I think he ralized what he did right away, and didnt restart the server yet. At the moment, sharepoint is working so we aren't going to try anything until we are sure of what to do. Should we uninstall the 2005 native client? What 2000 components could have been upgraded to cause this? Any suggestions would be great!

mcrowley
Aged Yak Warrior

771 Posts

Posted - 2006-11-15 : 11:19:25

The SQL Server native client >should< not harm anything. I believe it is a separate install from the OLEDB provider. Can this be replicated at will, or was this a one-off error?

jonathan4465
Starting Member

5 Posts

Posted - 2006-11-15 : 11:22:32

Just as a test I try to backup the system state and then the errors above are logged in the event viewer. One thing I noticed was in the first error "Instance=MSFW" shows up. This is the MSDE instance for ISA 2004 firewall. Strange...

jonathan4465
Starting Member

5 Posts

Posted - 2006-11-15 : 11:43:54

Oh, and this is the error in the backup log:

Volume shadow copy creation: Attempt 1.
"MSDEWriter" has reported an error 0x800423f4. This is part of System State. The backup cannot continue.

Error returned while creating the volume shadow copy:800423f4
Aborting Backup.

mcrowley
Aged Yak Warrior

771 Posts

Posted - 2006-11-15 : 11:47:04

So the sharepoint instance is out of the picture, and can be backed up normally?

jonathan4465
Starting Member

5 Posts

Posted - 2006-11-15 : 11:53:21

Yes, if I go into enterprise manager and select "backup database" it works fine. But, the issue for me is I can't do a normal backup of the system. (system state, etc.)

mcrowley
Aged Yak Warrior

771 Posts

Posted - 2006-11-15 : 13:29:40

What is trying to do the normal backup? A maintenance plan, a backup package like Veritas, or Legato?

jonathan4465
Starting Member

5 Posts

Posted - 2006-11-15 : 16:15:26

I'm just trying to use NTBACKUP to back up the system state.

antti
Starting Member

1 Post

Posted - 2006-11-17 : 01:54:01

Uh, I have exactly same problem with Windows 2003 server std (not Small Busines Server) + SQL Server 2005 + Ntbackup. As hardware I use HP ML310 SCSI model with HP Storageworks 20/40Gt DAT drive attached with USB. Only have one partition as C drive where all databases and system files are installed.

When I fisrst installed SQL server all backups were fine. But after software provider (some financial software) installed his databases to sql server, backups started to fail with exactly same errors. All these databases have recovery model as Full.

If I check System State as one option for my backup, backup fails totally and is not backing up anything (not even regular files which are in same job). If I leave System state out of the backup, system log is still filled with errors (at the bottom of this message) but it eventually backs up regular files.

My 2 humble guestions are:

1. Why Ntbackup is trying to do some kind of Online Backup from my sql server even if I don't want to? (I have always used maintenance plans and take only database dumps + tranaction logs on tape with ntbackup.)

2. Can I somehow disable this strange SQL Online Backup feature from Ntbackup.

Have you guys any idea what to do. At this moment, I cannot do backup...

Here are some errors from my application eventlog (when System State option is disabled)

1.st marking in my log after backup starts:
Event ID: 8018
Source: Ntbackup

Begin Operation

2.nd
Source: MSSQLSERVER
Event ID: 3041
Category:(6)

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

3.rd
Source: SQLVDI
Event ID: 1

SQLVDI: Loc=SVDS::Close. Desc=Open devices!. ErrorCode=(0). Process=484. Thread=9896. Server. Instance=MSSQLSERVER. VD=Global\{BBC14E0E-D34A-4BF4-A38A-B6CC243FC473}135.

4.th
Source: VSS
Event ID: 6013

Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft OLE DB Provider for SQL Server
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3224
Error state: 1, Severity: 16
Source: Microsoft OLE DB Provider for SQL Server
Error message: Cannot create worker thread.

5.th
Source: MSSQLSERVER
Event ID: 18210
Category:(2)

BackupMedium::ReportIoError: write failure on backup device '{BBC14E0E-D34A-4BF4-A38A-B6CC243FC473}16'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).

planckscale
Starting Member

1 Post

Posted - 2009-09-30 : 12:56:23

I'm experiencing this same issue, using a maintenance plan. Did you find a solution to this issue?

quote:
Originally posted by antti

Uh, I have exactly same problem with Windows 2003 server std (not Small Busines Server) + SQL Server 2005 + Ntbackup. As hardware I use HP ML310 SCSI model with HP Storageworks 20/40Gt DAT drive attached with USB. Only have one partition as C drive where all databases and system files are installed.

When I fisrst installed SQL server all backups were fine. But after software provider (some financial software) installed his databases to sql server, backups started to fail with exactly same errors. All these databases have recovery model as Full.

If I check System State as one option for my backup, backup fails totally and is not backing up anything (not even regular files which are in same job). If I leave System state out of the backup, system log is still filled with errors (at the bottom of this message) but it eventually backs up regular files.

My 2 humble guestions are:

1. Why Ntbackup is trying to do some kind of Online Backup from my sql server even if I don't want to? (I have always used maintenance plans and take only database dumps + tranaction logs on tape with ntbackup.)

2. Can I somehow disable this strange SQL Online Backup feature from Ntbackup.

Have you guys any idea what to do. At this moment, I cannot do backup...

Here are some errors from my application eventlog (when System State option is disabled)

1.st marking in my log after backup starts:
Event ID: 8018
Source: Ntbackup

Begin Operation

2.nd
Source: MSSQLSERVER
Event ID: 3041
Category:(6)

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

3.rd
Source: SQLVDI
Event ID: 1

SQLVDI: Loc=SVDS::Close. Desc=Open devices!. ErrorCode=(0). Process=484. Thread=9896. Server. Instance=MSSQLSERVER. VD=Global\{BBC14E0E-D34A-4BF4-A38A-B6CC243FC473}135.

4.th
Source: VSS
Event ID: 6013

Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft OLE DB Provider for SQL Server
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3224
Error state: 1, Severity: 16
Source: Microsoft OLE DB Provider for SQL Server
Error message: Cannot create worker thread.

5.th
Source: MSSQLSERVER
Event ID: 18210
Category:(2)

BackupMedium::ReportIoError: write failure on backup device '{BBC14E0E-D34A-4BF4-A38A-B6CC243FC473}16'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).

MCSE 2003: Security

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources