SQL Server Q&A

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=10Note 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)”
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 tocreate a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support(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.

DateTimeVersionSizeFile name———————————————-09-17-20032000.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?(http://support.microsoft.com/kb/839801/) FIX: Hotfixes are available for MDAC 2.8

Symptoms
If you use Bcp.exe to export a table to a flat file, the process may fail with an exception error if you use a format file to change the order of the columns during the export. The exception error occurs within the Bcp.exe file and the following error message appears:

The instruction at “memory_address” referenced memory at “memory_address”.
The memory could not be “written”.The output file is created but no rows are exported.
Resolution
Use a view to change the order of the columns to export. Then, use the view when you perform the bulk copy program and have the format file match the order of the columns in the view.

Symptoms
When you try to install a version of MicrosoftSQL Server 2005 that has been downloaded from the Microsoft Web site, you receive the following error message:

Could not find a package to install on the installation media.Additionally, error messages that resemble the following may be logged in the SQLSetupNumber_ServerName_Core(local).log file:

2005/9/30 10:5:19Error: Action “DeterminePackageTransformsAction” threw an exception during execution.
Failed to open package to determine installing product code : 110NotesThe SQLSetupNumber_ServerName _Core(local).log file is located in the C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files folder.Number is a placeholder for a number that increases for every installation of SQL Server 2005. The log file that has the largest value for Number in the file name is the log file for the most recent installation of SQL Server 2005.
Resolution
This problem occurs because a Sqlrun_*.msi file in the Setup folder on the SQL Server 2005 Setup media is corrupted. For example, the Sqlrun_NS.msi file is corrupted. Therefore, the Setup program cannot open the corrupted package during the installation and returns error code 110.

Symptoms
When you restore a database, recovery of logical file names of the database can fail, and the logical file names that correspond to the database in the master..sysaltfiles and the <Database_name>..sysfiles tables may differ.
Resolution
When you perform a backup and restore operation with a database that is in full recovery mode, this problem occurs if you modify the logical file names in the database after you back up the database but before you back up the transaction log.

Symptoms
For a database with two or more file groups, if a clustered index is created on a table in each filegroup, an attempt to back up any individual file group may fail with the following 3029 error message:

Server: Msg 3029, Level 16, State 1, Line 2
Database file ‘DB_DataA’ is subject to logical recovery and must be among the files to be backed up as part of the file or filegroup backup.
Server: Msg 3029, Level 16, State 1, Line 2
Database file ‘DB_DataB’ is subject to logical recovery and must be among the files to be backed up as part of the file or filegroup backup.
Server: Msg 3013, Level 16, State 1, Line 2
Backup or restore operation terminating abnormally.
Resolution
Perform a full database backup before you attempt to make file or file group backups. After the full backup, you can back up individual file groups.

Symptoms
When you try to restore a snapshot-based database backup from a file or from a file group in Microsoft SQL Server 2005, the restore process may fail. Additionally, you may receive one or more of the following error messages:
Error message 1

Successfully completed data transfer.
Error message 2

Msg 3283, SevLevel 16, State 1The file “MyDBLog” failed to initialize correctly. Examine the error logs for more details.
Error message 3

Msg 3013, SevLevel 16, State 1RESTORE DATABASE is terminating abnormally.
Error message 4

Errors resulted in failure of the command
Resolution
This issue occurs because of a change in SQL Server 2005.
SQL Server 2000 required the following multiple-step restore process: Restore the file or the file group from the full database backup.The database remains in a restoring state. Restore the transaction log or logs from the log backup chain. SQL Server 2005 tries to restore the log files and the data files in a single step. Some third-party snapshot backup utilities do not support the single-step approach.