FIX: You may receive an error message when you manually define a Back Up Database task in SQL Server 2005 to back up the transaction log

Article translations Article translations
Article ID: 921003 - View products that this article applies to.
Bug #: 853 (SQL Hotfix)
Bug #: 436155 (SQLBUDT)
Bug #: 437989 (SQLBUDT)
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.
Expand all | Collapse all

SUMMARY

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

SYMPTOMS

If you manually define a Back Up Database task in SQL Server 2005 to back up the transaction log, you may receive an error message that resembles the following:
Maintenance Plan Wizard
The selected database does not have the Recovery Model property set to full. This is required in order to back up the transaction log.
When this problem occurs, you experience the following behavior:
  • The SQL Server 2005 Management Studio does not let you back up the transaction log of a database in the bulk-logged recovery model.
  • If you manually define a maintenance plan, the transaction log of the database in the bulk-logged recovery model is not backed up.

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.

Prerequisites

You must have Microsoft SQL Server 2005 Service Pack 1 (SP1) installed to apply this hotfix.

For more information about how to obtain SQL Server 2005 Service Pack 1, 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

Restart information

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

Registry information

You do not have to change the registry.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.

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.
SQL Server 2005 hotfix, 32-bit
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Ms.ss.mgdsqldumper.dll2005.90.2164.075,55215-Jun-200603:29Not Applicable
Msgprox.dll2005.90.2164.0197,92015-Jun-200603:29Not Applicable
Replprov.dll2005.90.2164.0547,61615-Jun-200603:31Not Applicable
Replrec.dll2005.90.2164.0782,11215-Jun-200603:32Not Applicable
Sbmsmdlocal.dll9.0.2164.015,661,85615-Jun-200603:33Not Applicable
Sqlaccess.dll2005.90.2164.0347,93615-Jun-200603:31Not Applicable
Sqlservr.exe2005.90.2164.028,950,87215-Jun-200603:33Not Applicable
SQL Server 2005 hotfix, 64-bit
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Ms.ss.mgdsqldumper.dll2005.90.2164.075,55215-Jun-200603:29Not Applicable
Ms.ss.mgdsqldumper.dll2005.90.2164.091,42415-Jun-200604:10Not Applicable
Msgprox.dll2005.90.2164.0259,36015-Jun-200604:10Not Applicable
Replprov.dll2005.90.2164.0745,24815-Jun-200604:12Not Applicable
Replrec.dll2005.90.2164.01,008,41615-Jun-200604:12Not Applicable
Sbmsmdlocal.dll9.0.2164.015,661,85615-Jun-200603:33Not Applicable
Sqlaccess.dll2005.90.2164.0355,10415-Jun-200604:11Not Applicable
Sqlservr.exe2005.90.2164.039,251,23215-Jun-200604:13Not Applicable
SQL Server 2005 hotfix, 64-bit for Itanium processors
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Ms.ss.mgdsqldumper.dll2005.90.2164.075,55215-Jun-200603:29Not Applicable
Ms.ss.mgdsqldumper.dll2005.90.2164.0163,10415-Jun-200603:29Not Applicable
Msgprox.dll2005.90.2164.0542,49615-Jun-200603:28Not Applicable
Replprov.dll2005.90.2164.01,617,18415-Jun-200603:29Not Applicable
Replrec.dll2005.90.2164.02,141,47215-Jun-200603:29Not Applicable
Sbmsmdlocal.dll9.0.2164.048,733,98415-Jun-200603:30Not Applicable
Sqlaccess.dll2005.90.2164.0349,47215-Jun-200603:28Not Applicable
Sqlservr.exe2005.90.2164.072,208,67215-Jun-200603:30Not Applicable

WORKAROUND

To work around this problem, back up the transaction log by using Transact-SQL commands. Use a Transact-SQL command that resembles the following:
BACKUP LOG [AdventureWorks] TO  DISK = N'C:\AdventureWorks_backup_200608031547.trn'

STATUS

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

MORE INFORMATION

For more information, 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: 921003 - Last Review: October 9, 2011 - Revision: 2.0
APPLIES TO
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Developer Edition
Keywords: 
kbautohotfix kbsql2005sp1fix kbbug kbfix kbtshoot kbHotfixServer kbqfe KB921003

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