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: After you detach a Microsoft SQL Server 2005 database that resides on network-attached storage, you cannot reattach the SQL Server database

FIX: After you detach a Microsoft SQL Server 2005 database that resides on network-attached storage, you cannot reattach the SQL Server database

View products that this article applies to.

BUG #: 442810 (SQLBUDT)
BUG #: 1057 (SQL Hotfix)

↑ Back to the top

Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.

↑ Back to the top

Summary

This article describes the following about this hotfix release:
  • The issues that are fixed by this hotfix package
  • The prerequisites for applying this hotfix package
  • Information about whether you must restart the computer after you apply this hotfix package
  • Information about whether this hotfix package is replaced by any other hotfix package
  • The files that are contained in this hotfix package

↑ Back to the top

Symptoms

After you detach a Microsoft SQL Server 2005 database that resides on network-attached storage, you cannot reattach the SQL Server database. Additionally, a message that resembles the following may be logged in the Application log:
Msg 5120, Level 16, State 101, Line 1 Unable to open the physical file "\\servername\sharename\filename.mdf". Operating system error 5: (Access is denied.).

↑ Back to the top

Cause

This problem occurs because SQL Server 2005 resets the file permissions when the database is detached. When you try to reattach the database, it cannot be attached because of limited share permissions.

↑ Back to the top

Resolution

Service pack information

To resolve this problem, obtain the latest service pack for SQL Server 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
913089 How to obtain the latest service pack for SQL Server 2005

Hotfix information

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.

Prerequisites


There are no prerequisites for this hotfix.

Restart information


You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information


This hotfix is not replaced by any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) 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 item in Control Panel.
File nameFile versionFile sizeDateTimePlatform
Logread.exe2005.90.1551.0397,08819-Jul-200623:40Not Applicable
Microsoft.sqlserver.replication.dll2005.90.1551.01,608,48019-Jul-200623:36Not Applicable
Microsoft.sqlserver.smo.dll9.0.1551.01,559,32819-Jul-200623:36Not Applicable
Microsoft.sqlserver.sqlenum.dll9.0.1551.0895,77619-Jul-200623:36Not Applicable
Osql.exe2005.90.1551.051,48819-Jul-200623:35Not Applicable
Replrec.dll2005.90.1551.0781,08819-Jul-200623:35Not Applicable
Msmdlocal.dll9.0.1551.015,626,52819-Jul-200623:37Not Applicable
Msmdredir_dll9.0.1551.03,929,88819-Jul-200623:37Not Applicable
Sqlaccess.dll2005.90.1551.0349,47219-Jul-200623:40Not Applicable
Sqldiag.exe2005.90.1551.0960,28819-Jul-200623:36Not Applicable
Sqlservr.exe2005.90.1551.028,791,12819-Jul-200623:37Not Applicable

↑ 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. This problem was first corrected in Microsoft SQL Server 2005 Service Pack 2.

↑ Back to the top

More Information

To change the behavior in SQL Server 2005 after you apply this hotfix, follow these steps:
  1. Use the -T startup option to start SQL Server. Use this startup option to turn on trace flag 1802 in SQL Server Configuration Manager. For more information about how to change the startup parameters, visit the following Microsoft Developer Network (MSDN) Web site:
    http://msdn2.microsoft.com/en-us/library/ms190737.aspx
  2. Use the following command to detach the database.
    exec sp_detach_db DatabaseName go
  3. Use the following command to reattach the database.
    exec sp_attach_db DatabaseName, '\\Network-attached storage_Path\DatabaseMDFFile.mdf', '\\Network-attached storage_Path\DatabaseLDFFile.ldf' go

↑ Back to the top

Keywords: kb, kbautohotfix, kbsql2005sp2fix, kbsql2005presp2fix, kbsql2005engine, kbtshoot, kbfix, kbentirenet, kbhotfixserver, kbqfe, kbpubtypekc

↑ Back to the top

Article Info
Article ID : 922804
Revision : 1
Created on : 1/7/2017
Published on : 10/9/2011
Exists online : False
Views : 584