FIX: You may receive an error message when you perform transactional replication in SQL Server 2000 (900470)


The information in this article applies to:

  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000 Personal Edition
BUG #: 474381 (SQL Server 8.0)
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.

SUMMARY

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

SYMPTOMS

When you perform transactional replication in Microsoft SQL Server 2000, you may receive the following error message from the Replication Log Reader Agent utility:
Status: 0, code: 18767, text: 'The specified begin LSN (00008ab0:00002feb:0001) for replication log scan occurs before replbeginlsn (00008ab0:00002feb:0002).'.
This error message is reported by the sp_replcmds stored procedure. This error message is also reported by the sp_repltrans stored procedure.

For a list of all publicly released SQL Server 2000 post-Service Pack 4 hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:

894905 Cumulative list of the hotfixes that are available for SQL Server 2000 SP4

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it 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 SQL Server 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product 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

To apply this hotfix, you must have SQL Server 2000 Service Pack 4 (SP4) installed on the computer. For information about how to obtain SQL Server 2000 SP4, 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.

File information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain 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 tool in Control Panel.SQL Server 2000 32-bit versions
File nameFile versionFile sizeDateTimePlatform
Mssdi98.dll8.11.50523.0239,10406-Jun-200522:46x86
Osql.exe2000.80.1025.057,90417-May-200501:51x86
Pfclnt80.dll2000.80.2148.0430,08012-Jul-200517:24x86
Procsyst.sqlNot Applicable552,06817-Jun-200500:15Not Applicable
Sp4_serv_qfe.sqlNot Applicable18,81017-Jun-200500:15Not Applicable
Sqlagent.exe2000.80.2148.0323,58408-Jul-200501:50x86
Sqldiag.exe2000.80.2148.0118,78408-Jul-200502:51x86
Sqlfth75.dll2000.80.2148.0102,40008-Jul-200502:09x86
Sqlservr.exe2000.80.2148.09,154,56008-Jul-200516:07x86
SQL Server 2000 64-bit version
File nameFile versionFile sizeDateTimePlatform
Mssdi98.dll8.11.50523.0239,10406-Jun-200522:46x86
Osql.exe2000.80.1025.057,90417-May-200501:51x86
Pfclnt80.dll2000.80.2148.0430,08012-Jul-200517:24x86
Procsyst.sqlNot Applicable552,06817-Jun-200500:15Not Applicable
Sp4_serv_qfe.sqlNot Applicable18,81017-Jun-200500:15Not Applicable
Sqlagent.exe2000.80.2148.0323,58408-Jul-200501:50x86
Sqldiag.exe2000.80.2148.0118,78408-Jul-200502:51x86
Sqlfth75.dll2000.80.2148.0102,40008-Jul-200502:09x86
Sqlservr.exe2000.80.2148.09,154,56008-Jul-200516:07x86

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

Modification Type:MinorLast Reviewed:7/25/2006
Keywords:kbBug kbfix kbHotfixServer kbQFE kbpubtypekc KB900470 kbAudDeveloper kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.