Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: General network error when you try to back up or restore a SQL Server database on a computer that is running Windows Server 2003

FIX: General network error when you try to back up or restore a SQL Server database on a computer that is running Windows Server 2003

View products that this article applies to.

Symptoms

When you try to back up a Microsoft SQL Sever database on a computer that is running Microsoft Windows Server 2003, you may receive an error message that is similar to the following:
Processed <Number of Pages> pages for database '<databaseName>', file '<databaseName>' on file 1.
100 percent backed up.
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Processed 1 pages for database '<databaseName>', file '<fileName>' on file 1.
However, the backup device file is created successfully and the backup data is valid.

A similar problem may also occur when try to restore a SQL Server database on a computer that is running Microsoft Windows Server 2003, and you may receive an error message that is similar to the following:
Processed <Number of Pages> pages for database '<databaseName>', file '<fileName>' on file 1.
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Processed 1 pages for database '<databaseName>', file '<fileName>' on file 1.
ODBC: Msg 0, Level 16, State 1
Communication link failure
Generally, the backup device file is still created. However, the file may not be valid depending on when the failure occurred. Also, when this problem occurs, an error such as the following is typically logged in the SQL Server error log:
2004-05-26 09:44:16.77 backup BACKUP failed to complete the command backup database testdb to disk='c:\temp\testdb.bak' with init, stats=10
Note This problem may occur when the SQL Server connection uses the Named Pipes Net-Library.

When the Sqlmaint.exe utility runs the RESTORE VERIFYONLY command, you may notice an error message that is similar to the following in the SQL Server error log:
BackupDiskFile::OpenMedia: Backup device 'C:\MSSQL\db_200401261900.BAK' failed to open. Operating system error = 32(The process cannot access the file because it is being used by another process.).
Also, you may notice an error message that is similar to the following in the SQL Server maintenance plan output file:
Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backup device 'C:\MSSQL\db_200401261900.BAK'. Device error or device off-line. See the SQL Server error log for more details. [Microsoft][ODBC SQL Server Driver][SQL Server]VERIFY DATABASE is terminating abnormally. End of maintenance plan 'ABC Maintenance Plan' on 1/26/2004 7:00:08 PM SQLMAINT.EXE Process Exit Code: 1 (Failed)"

↑ Back to the top

Resolution

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. 
   Date      Time   Version          Size       File name
   ----------------------------------------------
   09-17-2003      2000.85.1022.42 28,672 bytes dbnmpntw.dll
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

Note For a list of all the hotfixes available for MDAC 2.8, click the following article number to view the article in the Microsoft Knowledge Base:
839801 FIX: Hotfixes are available for MDAC 2.8


↑ Back to the top

Workaround

To work around the problem, use the TCP/IP Net-Library instead of the Named Pipes Net-Library to connect to the SQL Server database, and then back up or restore the database.

For the exact steps to set the TCP/IP network library on the client where you are performing the backup or the restore operation, see the "How to configure a client to use TCP/IP (Client Network Utility)" chapter in SQL Server 2000 Books Online.

When you connect to an instance of SQL Server by using SQL Query Analyzer, you can force the connection to use the TCP/IP Net-Library. To do this, type the name of the instance of SQL Server with the tcp prefix in the SQL Server text box in the Connect to SQL Server dialog box. This appears as follows:
tcp:SQL Server Name

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

Keywords: kbdatabase, kbserver, kbbackup, kbtsql, kbhotfixserver, kbnetwork, kbqfe, kbfix, kbautohotfix, kbclientserver, KB827452

↑ Back to the top

Article Info
Article ID : 827452
Revision : 13
Created on : 11/15/2007
Published on : 11/15/2007
Exists online : False
Views : 499