FIX: The password that you specify in a BACKUP statement appears in the SQL Server Errorlog file or in the Application event log if the BACKUP statement does not run in SQL Server 2000

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

On This Page

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

Consider the following scenario. In SQL Server 2000, you use the BACKUP statement to back up up a database, a transaction log, files, or filegroups. Additionally, you specify a password in the BACKUP statement. You run the BACKUP statement. In this scenario, the statement does not run. When you open the SQL Server Errorlog file or if you open Event ID 17055 in the Application event log, you notice that the password that you specified in the BACKUP statement appears.

RESOLUTION

The installer does not install this hotfix correctly on x64-based systems. This installation issue occurs when the following conditions are true:
  • The system uses the Advanced Micro Devices (AMD) AMD64 processor architecture or the Intel Extended Memory 64 Technology (EM64T) processor architecture.

    Note This issue does not occur on systems that use the Intel Itanium processor architecture.
  • The system is running a 64-bit version of the Microsoft Windows Server operating system.
  • The system is running a 32-bit version of SQL Server 2000.
We have corrected this installation issue in later builds of SQL Server 2000, starting with version 8.00.2244. When a customer who is running SQL Server 2000 on an x64-based system requests this hotfix, we will provide a build that includes this hotfix and that can be installed correctly on an x64-based system. The build that we provide will be version 8.00.2244 or a later version.

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft SQL Server 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must have Microsoft SQL Server 2000 Service Pack 4 (SP4) installed before you apply this hotfix.

For more information about how to obtain SQL Server 2000 Service Pack 4, click the following article number to view the article in the Microsoft Knowledge Base:
290211 How to obtain the latest SQL Server 2000 service pack

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 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.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Updatelauncher.exe5.2.3790.12888,70416-Jan-200603:15x86
_sfx_manifest_Not Applicable4925-Jan-200605:58Not Applicable
Spupdsvc.exe6.1.22.525,82419-Jan-200601:03x64
Tempcatsign.cdfNot Applicable1,65325-Jan-200605:05Not Applicable
Dtsui.dll2000.80.2180.01,593,34425-Jan-200604:01x86
Impprov.dll2000.80.2180.0102,40025-Jan-200604:01x86
Msgprox.dll2000.80.2180.094,20825-Jan-200604:01x86
Msrpjt40.dll4.10.9424.0188,47323-Jan-200616:13x86
Mssdi98.dll8.11.50523.0239,10406-Jun-200506:46x86
Ntwdblib.dll2000.80.2180.0290,81625-Jan-200604:01x86
Odsole70.dll2000.80.2180.069,63225-Jan-200604:01x86
Osql.exe2000.80.2039.057,34403-May-200512:32x86
Pfclnt80.dll2000.80.2180.0430,08025-Jan-200604:01x86
Procsyst.sqlNot Applicable552,06816-Jun-200508:15Not Applicable
Replmerg.exe2000.80.2180.0163,84024-Jan-200623:04x86
Replprov.dll2000.80.2180.0237,56825-Jan-200604:01x86
Replrec.dll2000.80.2180.0315,39225-Jan-200604:01x86
Replsub.dll2000.80.2180.0270,33625-Jan-200604:01x86
Semexec.dll2000.80.2180.0856,06425-Jan-200604:01x86
Sp4_serv_qfe.sqlNot Applicable18,81016-Jun-200508:15Not Applicable
Sqlagent.exe2000.80.2180.0323,58424-Jan-200622:51x86
Sqldiag.exe2000.80.2180.0118,78424-Jan-200623:29x86
Sqldmo.dll2000.80.2180.04,362,24025-Jan-200604:01x86
Sqlevn70.rll2000.80.2180.045,05625-Jan-200604:01Not Applicable
Sqlfth75.dll2000.80.2180.0102,40024-Jan-200622:56x86
Sqlservr.exe2000.80.2180.09,162,75225-Jan-200604:00x86
Sqlsort.dll2000.80.2180.0589,82425-Jan-200604:01x86
Stardds.dll2000.80.2180.0176,12825-Jan-200604:01x86
Svrnetcn.dll2000.80.2180.0110,59225-Jan-200604:01x86
Ums.dll2000.80.2180.035,32825-Jan-200604:01x86
Osql.exe2000.80.2039.057,34403-May-200512:32x86
Sqlse.rll1.1.2010.045,56812-Jan-200608:54Not Applicable
Sqlstpcustomdll.dll1.0.128.01,367,04019-Jan-200601:02x64
Sqlstpcustomdll.rllNot Applicable25,08819-Jan-200601:02Not Applicable
Updspapi.dll6.1.22.5462,56019-Jan-200601:03x64
Spupdsvc.exe6.1.22.522,75219-Jan-200601:03x86
Tempcatsign.cdfNot Applicable1,65325-Jan-200604:55Not Applicable
Dtsui.dll2000.80.2180.01,593,34425-Jan-200604:01x86
Impprov.dll2000.80.2180.0102,40025-Jan-200604:01x86
Msgprox.dll2000.80.2180.094,20825-Jan-200604:01x86
Msrpjt40.dll4.10.9424.0188,47323-Jan-200616:13x86
Mssdi98.dll8.11.50523.0239,10406-Jun-200506:46x86
Ntwdblib.dll2000.80.2180.0290,81625-Jan-200604:01x86
Odsole70.dll2000.80.2180.069,63225-Jan-200604:01x86
Osql.exe2000.80.2039.057,34403-May-200512:32x86
Pfclnt80.dll2000.80.2180.0430,08025-Jan-200604:01x86
Procsyst.sqlNot Applicable552,06816-Jun-200508:15Not Applicable
Replmerg.exe2000.80.2180.0163,84024-Jan-200623:04x86
Replprov.dll2000.80.2180.0237,56825-Jan-200604:01x86
Replrec.dll2000.80.2180.0315,39225-Jan-200604:01x86
Replsub.dll2000.80.2180.0270,33625-Jan-200604:01x86
Semexec.dll2000.80.2180.0856,06425-Jan-200604:01x86
Sp4_serv_qfe.sqlNot Applicable18,81016-Jun-200508:15Not Applicable
Sqlagent.exe2000.80.2180.0323,58424-Jan-200622:51x86
Sqldiag.exe2000.80.2180.0118,78424-Jan-200623:29x86
Sqldmo.dll2000.80.2180.04,362,24025-Jan-200604:01x86
Sqlevn70.rll2000.80.2180.045,05625-Jan-200604:01Not Applicable
Sqlfth75.dll2000.80.2180.0102,40024-Jan-200622:56x86
Sqlservr.exe2000.80.2180.09,162,75225-Jan-200604:00x86
Sqlsort.dll2000.80.2180.0589,82425-Jan-200604:01x86
Stardds.dll2000.80.2180.0176,12825-Jan-200604:01x86
Svrnetcn.dll2000.80.2180.0110,59225-Jan-200604:01x86
Ums.dll2000.80.2180.035,32825-Jan-200604:01x86
Osql.exe2000.80.2039.057,34403-May-200512:32x86
Sqlse.rll1.1.2010.045,05612-Jan-200608:06Not Applicable
Sqlstpcustomdll.dll1.0.128.0943,10419-Jan-200601:02x86
Sqlstpcustomdll.rllNot Applicable24,57619-Jan-200601:02Not Applicable
Updspapi.dll6.1.22.5371,93619-Jan-200601:03x86

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 about the naming schema for Microsoft 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: 913789 - Last Review: June 19, 2007 - Revision: 1.2
APPLIES TO
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000, Workgroup Edition
  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Enterprise Edition
Keywords: 
kbexpertiseadvanced kbtshoot kbprb KB913789

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