FIX: Error message when you use log shipping in SQL Server 2008: "During startup of warm standby database '<Database Name>' (database ID <N>), its standby file ('<File Name>') was inaccessible to the RESTORE statement"

Article translations Article translations
Article ID: 962008 - View products that this article applies to.
Microsoft distributes Microsoft SQL Server 2008 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 2008 fix release.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • You have three servers that are in the same domain. For example, you have server A, server B, and server C.
  • You install Microsoft SQL Server 2008 on server A and on server B.
  • The startup account of the SQL Server service and of the SQL Server Agent is a domain account.
  • You create two shared directories on server C. For example, the folders are named D1 and D2. The startup account does not have the administrator permission on server C. However, the startup account has the full control permission for the two directories.
  • You configure log shipping between server A and server B. For the primary server, you specify the transaction log backup folder to use the network path of the directory D1. For the secondary server, you specify the destination folder to use the network path of the directory D2.
  • On the secondary server, you set the STANDBY mode for the secondary database.
In this scenario, you may find that log shipping does not work. Additionally, the following error message is logged in the SQL Server 2005 Errorlog file:
During startup of warm standby database 'Database Name' (database ID N), its standby file ('File Name') was inaccessible to the RESTORE statement. The operating system error was '5(Access is denied.)'. Diagnose the operating system error, correct the problem, and retry startup. RESTORE LOG is terminating abnormally.

Note This issue does not occur in Microsoft SQL Server 2005.

RESOLUTION

Cumulative update information for the release version of SQL Server 2008

The fix for this issue was first released in Cumulative Update 4 for the release version of SQL Server 2008. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
963036 Cumulative update package 4 for SQL Server 2008
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
956909 The SQL Server 2008 builds that were released after SQL Server 2008 was released

Cumulative update information for SQL Server 2008 Service Pack 1

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 Service Pack 1. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
969099 Cumulative update package 1 for SQL Server 2008 Service Pack 1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released

STATUS

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

MORE INFORMATION

Notes
  • After you apply the fix for this issue, the .TUF (Transaction Undo File) file is created on the secondary server in the same folder where the database’s MDF file is located. Previously, the Transaction Undo File was created on the secondary server in the same location where the database’s Transaction log backup files are copied. 
  • This fix only updates the SqlLogShip.exe and SqlManagerUI.dll files. These files are the Tools components that support Log Shipping. Therefore, updating these files also affects the release versions of SQL Server 2008 and of SQL Server 2008 Service Pack 1. This is because, even though you may have only one instance of SQL Server 2008 for which this fix is applied, the shared components are automatically updated for all the instances.


More information about cumulative update package 4 for SQL Server 2008

For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:
963036 Cumulative update package 4 for SQL Server 2008

More information about cumulative update package 1 for SQL Server 2008 Service Pack 1

For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:
969099 Cumulative update package 1 for SQL Server 2008 Service Pack 1

REFERENCES

For more information about the list of builds that are available after the release of SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
956909 The SQL Server 2008 builds that were released after SQL Server 2008 was released
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 962008 - Last Review: June 6, 2011 - Revision: 3.0
APPLIES TO
  • Microsoft SQL Server 2008 Workgroup
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Standard
Keywords: 
kbsurveynew kbexpertiseadvanced kbqfe kbfix KB962008

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com