FIX: You receive the "Could not find stored procedure" error message when you perform transactional replication with queued updating in SQL Server 2000 (884854)


The information in this article applies to:

  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Personal Edition
  • Microsoft SQL Server 2000 Enterprise Evaluation Edition
  • Microsoft SQL Server 2000 Workgroup Edition
  • Microsoft SQL Server 2000 Desktop Engine (MSDE)
  • Microsoft SQL Server 2000 Developer Edition 64 bit
  • Microsoft SQL Server 2000 Enterprise Edition 64-bit
  • Microsoft SQL Server 2000 Enterprise Edition SP3
  • Microsoft SQL Server 2000 Enterprise Evaluation Edition SP3
  • Microsoft SQL Server 2000 Developer Edition SP3

SUMMARY

Microsoft distributes 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.

Article Contents

SUMMARY

This article describes the following about this hotfix:
  • The issues that are fixed by this hotfix package.
  • The prerequisites for installing the hotfix package.
  • Whether you must restart your 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.
back to the top

Introduction

Issues that are fixed by this hotfix package

The following issue is fixed in this Microsoft SQL Server 2000 hotfix package:

When you perform transactional replication with queued updating in Microsoft SQL Server 2000, you may experience one of the following symptoms:
  • The Queue Reader Agent service may fail with an Access Violation.
  • You may receive an error message that is similar to the following:
    Server: ServerName, Database DatabaseName:
    ODBC Error: Could not find stored procedure ''<garbage characters>''.
  • You may also find some transactions in the MSreplication_queue table that are never processed. Typically, this behavior occurs under high load conditions.
For a list of previous hotfixes, see the "Microsoft SQL Server 2000 Post-Service Pack 3" hotfix section and the "Microsoft SQL Server 2000 Post-Service Pack 3a" hotfix section in the following Microsoft Knowledge Base article:

290211 How to obtain the latest SQL Server 2000 service pack

back to the top

MORE INFORMATION

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For more information, 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

Hotfix information

Prerequisites

This hotfix requires SQL Server 2000 Service Pack 3 (SP3). For more information about how to obtain SQL Server 2000 Service Pack 3, 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

Before you install this hotfix, follow these steps:
  1. Back up system databases.
  2. Reinstall SQL Server 2000.
  3. Install this hotfix.
  4. Restore system databases.
back to the top

Restart information

You must restart your computer after you apply this hotfix.

back to the top

Registry information

None

back to the top

Hotfix file information

This hotfix contains only the files that are required to correct the issue that is described in this article. 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 tool in Control Panel.
   Date         Time           Version           Size    File name
   --------------------------------------------------------------
   18-Aug-2004  01:55  2000.80.970.0      664,128 Autoplt.dll 
   18-Aug-2004  01:55  2000.80.970.0      332,352 Ctasksui.dll 
   18-Aug-2004  01:55  2000.80.970.0      315,968 Custtask.dll 
   18-Aug-2004  01:55  2000.80.970.0       33,340 Dbmslpcn.dll 
   18-Aug-2004  01:55  2000.80.970.0    1,905,216 Dtspkg.dll 
   18-Aug-2004  01:55  2000.80.970.0      528,960 Dtspump.dll 
   18-Aug-2004  01:55  2000.80.970.0    1,557,052 Dtsui.dll 
   18-Aug-2004  01:55  2000.80.970.0      639,552 Dtswiz.dll 
   18-Aug-2004  01:55  2000.80.970.0       90,692 Msgprox.dll 
   19-May-2004  23:43  8.11.40209.0       209,408 Mssdi98.dll 
   18-Aug-2004  01:55  2000.80.970.0       62,024 Odsole70.dll 
   18-Aug-2004  01:56  2000.80.970.0       25,144 Opends60.dll 
   18-Aug-2004  01:55  2000.80.970.0      279,104 Pfutil80.dll 
   18-Aug-2004  01:55  2000.80.970.0      221,768 Replprov.dll 
   18-Aug-2004  01:55  2000.80.970.0      307,784 Replrec.dll 
   18-Aug-2004  00:46  2000.80.970.0      159,813 Replres.rll
   18-Aug-2004  01:55  2000.80.970.0      287,304 Rinitcom.dll 
   18-Aug-2004  01:55  2000.80.970.0       78,416 Sdiclnt.dll 
   18-Aug-2004  01:55  2000.80.970.0       66,112 Semmap.dll 
   18-Aug-2004  01:55  2000.80.970.0       57,916 Semnt.dll 
   18-Aug-2004  01:55  2000.80.970.0      492,096 Semobj.dll 
   18-Aug-2004  01:20  2000.80.970.0      172,032 Semobj.rll
   18-Aug-2004  01:54  2000.80.970.0       28,672 Sqlagent.dll 
   18-Aug-2004  01:54  2000.80.970.0      168,001 Sqlakw32.dll 
   18-Aug-2004  01:55  2000.80.970.0       33,344 Sqlctr80.dll 
   18-Aug-2004  01:55  2000.80.970.0    4,215,360 Sqldmo.dll 
   18-Aug-2004  00:35  2000.80.970.0       28,672 Sqlevn70.rll
   18-Aug-2004  01:55  2000.80.970.0      180,792 Sqlmap70.dll 
   18-Aug-2004  01:55  2000.80.970.0      188,992 Sqlmmc.dll 
   18-Aug-2004  01:15  2000.80.970.0      479,232 Sqlmmc.rll
   18-Aug-2004  01:55  2000.80.970.0      401,984 Sqlqry.dll 
   18-Aug-2004  01:55  2000.80.970.0       57,920 Sqlrepss.dll 
   18-Aug-2004  01:55  2000.80.970.0      590,396 Sqlsort.dll 
   18-Aug-2004  01:55  2000.80.970.0       45,644 Sqlvdi.dll 
   18-Aug-2004  01:55  2000.80.970.0      106,588 Sqsrvres.dll 
   18-Aug-2004  01:55  2000.80.970.0       33,340 Ssmslpcn.dll 
   18-Aug-2004  01:55  2000.80.970.0       82,492 Ssnetlib.dll 
   18-Aug-2004  01:55  2000.80.970.0       25,148 Ssnmpn70.dll 
   18-Aug-2004  01:55  2000.80.970.0      123,456 Stardds.dll 
   18-Aug-2004  01:55  2000.80.970.0      158,240 Svrnetcn.dll 
   18-Aug-2004  01:55  2000.80.970.0       49,228 Ums.dll 
   18-Aug-2004  01:55  2000.80.970.0       98,872 Xpweb70.dll
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

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 2000 Service Pack 4.

back to the top

REFERENCES

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 the terminology that Microsoft uses when correcting software after it is released, 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

back to the top
Modification Type:MinorLast Reviewed:6/1/2006
Keywords:kbbug kbfix kbSQLServ2000preSP4fix kbHotfixServer kbQFE KB884854 kbAudDeveloper kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.