Microsoft KB Archive/915340

From BetaArchive Wiki

Article ID: 915340

Article Last Modified on 11/2/2007



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
  • Microsoft SQL Server 2000 Personal Edition



Bug #: 310 (SQL Hotfix)

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

Consider the following scenario. In Microsoft SQL Server 2000, you add a SQL Server Agent job, or you update a SQL Server Agent job. At the same time, another connection tries to delete a SQL Server Agent job. In this scenario, a deadlock occurs when the scheduled SQL Server Agent job that you add or that you update is running.

If you troubleshoot the deadlock by enabling trace flag 1204, you notice that the following error message is logged in the SQL Server error log file:

Deadlock encountered .... Printing deadlock information …
Date Time SPID Node:1

Date Time SPID SPID: 77 ECID: 0 Statement Type: DELETE Line #: 124
Date Time SPID Input Buf: Language Event: EXECUTE msdb.dbo.sp_delete_job @job_id = 0x9D8193BA4AB3E84381F15C1701991638

Date Time SPID Node:2

Date Time SPID SPID: 52 ECID: 0 Statement Type: SELECT Line #: 19
Date Time SPID Input Buf: Language Event: EXECUTE msdb.dbo.sp_sqlagent_refresh_job @job_id = 0x44C826041DA74947A7BFD1365474B5FB
Date Time SPID Victim Resource Owner:
Date Time SPID ResType:LockOwner Stype:'OR' Mode: S SPID:52 ECID:0 Ec:(0x36829558) Value:0x5b7084a0 Cost:(0/0)

CAUSE

This problem occurs because SQL Server Agent does not schedule the SQL Server Agent job to run in the job cache. When SQL Server Agent runs the scheduled SQL Server Agent job, SQL Server Agent uses the sp_sqlagent_refresh_job stored procedure to update the job cache. If another connection tries to delete a SQL Server Agent job, a deadlock occurs.

RESOLUTION

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 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:

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

  • Microsoft SQL Server 2000 Service Pack 4 (SP4)

    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

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

File name File version File size Date Time Platform
Spupdsvc.exe 6.2.24.0 22,752 01-Jun-2005 11:43 x86
Tempcatsign.cdf Not Applicable 1,796 09-Mar-2006 09:51 Not Applicable
80sp4-tools.sql Not Applicable 134,628 18-Feb-2006 09:40 Not Applicable
Dtsui.dll 2000.80.2187.0 1,593,344 09-Mar-2006 04:47 x86
Impprov.dll 2000.80.2187.0 102,400 09-Mar-2006 04:47 x86
Msgprox.dll 2000.80.2187.0 94,208 09-Mar-2006 04:47 x86
Msrpjt40.dll 4.10.9424.0 188,473 23-Jan-2006 16:13 x86
Mssdi98.dll 8.11.50523.0 239,104 06-Jun-2005 06:46 x86
Ntwdblib.dll 2000.80.2187.0 290,816 09-Mar-2006 04:47 x86
Odsole70.dll 2000.80.2187.0 69,632 09-Mar-2006 04:47 x86
Osql.exe 2000.80.2187.0 57,344 09-Mar-2006 02:37 x86
Pfclnt80.dll 2000.80.2187.0 430,080 09-Mar-2006 04:47 x86
Procsyst.sql Not Applicable 552,068 16-Jun-2005 08:15 Not Applicable
Replmerg.exe 2000.80.2187.0 163,840 09-Mar-2006 02:46 x86
Replmerg.sql Not Applicable 1,151,450 09-Mar-2006 02:22 Not Applicable
Replprov.dll 2000.80.2187.0 237,568 09-Mar-2006 04:47 x86
Replrec.dll 2000.80.2187.0 315,392 09-Mar-2006 04:47 x86
Replsub.dll 2000.80.2187.0 270,336 09-Mar-2006 04:47 x86
Repltran.sql Not Applicable 1,000,634 02-Feb-2006 05:59 Not Applicable
Semexec.dll 2000.80.2187.0 856,064 09-Mar-2006 04:47 x86
Sp4_serv_qfe.sql Not Applicable 18,810 16-Jun-2005 08:15 Not Applicable
Sqlagent.exe 2000.80.2187.0 323,584 09-Mar-2006 02:26 x86
Sqldiag.exe 2000.80.2187.0 118,784 09-Mar-2006 03:22 x86
Sqldmo.dll 2000.80.2187.0 4,362,240 09-Mar-2006 04:47 x86
Sqlevn70.rll 2000.80.2187.0 45,056 09-Mar-2006 04:47 Not Applicable
Sqlfth75.dll 2000.80.2187.0 102,400 09-Mar-2006 02:35 x86
Sqlservr.exe 2000.80.2187.0 9,162,752 09-Mar-2006 04:45 x86
Sqlsort.dll 2000.80.2187.0 589,824 09-Mar-2006 04:47 x86
Stardds.dll 2000.80.2187.0 176,128 09-Mar-2006 04:47 x86
Svrnetcn.dll 2000.80.2187.0 110,592 09-Mar-2006 04:47 x86
Ums.dll 2000.80.2187.0 35,328 09-Mar-2006 04:47 x86
Osql.exe 2000.80.2187.0 57,344 09-Mar-2006 02:37 x86
Sqlse.rll 1.1.2032.0 45,056 22-Feb-2006 06:50 Not Applicable
Sqlstpcustomdll.dll 1.1.2032.0 1,846,784 22-Feb-2006 06:50 x86
Sqlstpcustomdll.rll 1.1.2032.0 12,288 22-Feb-2006 06:50 Not Applicable
Updspapi.dll 6.2.24.0 371,424 01-Jun-2005 11:45 x86


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 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


For more information about trace flag 1204, visit the following Microsoft Developer Network (MSDN) Web site:

Keywords: kbfix kbexpertiseadvanced kbpubtypekc kbqfe kbhotfixserver KB915340