FIX: An "Error 17883" error message may be logged, and SQL Server 2000 or SQL Server 7.0 may stop responding when you run an application that creates COM objects by using the sp_OACreate function (835581)


The information in this article applies to:

  • Microsoft SQL Server 2000 Desktop Engine (MSDE)
  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Personal Edition
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000 Workgroup Edition
  • Microsoft SQL Server 7.0
BUG #: 469097 (SQL Server 8.0)SQL Server 8.0:469097
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 run an application that creates Microsoft COM objects by using the sp_OACreate function within Transact-SQL code, Microsoft SQL Server 2000 or Microsoft SQL Server 7.0 may stop responding (hang). Additionally, the following error message may be logged in the SQL Server error log:
Error: 17883, Severity: 1, State: 0
server Process 162:0 (0) UMS Context 0x11DE8B68 appears to be non-yielding on Scheduler 1
Note This error message may also be logged for other reasons.

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

810185 SQL Server 2000 hotfix update for SQL Server 2000 Service Pack 3 and 3a

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for 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

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.

Note No hotfix is currently available for SQL Server 7.0.

Prerequisites

  • Microsoft SQL Server 2000 Service Pack 3 (SP3)

    For more information about how to obtain SQL Server 2000 SP3, 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 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
   Date         Time   Version        Size        File name
   -------------------------------------------------------------------
   31-May-2003  18:45  2000.80.818.0      78,400  Console.exe
   28-Oct-2003  04:21  2000.80.873.0     315,968  Custtask.dll
   02-Oct-2003  20:59  2000.80.867.0      33,340  Dbmslpcn.dll
   25-Apr-2003  02:12                    786,432  Distmdl.ldf
   25-Apr-2003  02:12                  2,359,296  Distmdl.mdf
   30-Jan-2003  01:55                        180  Drop_repl_hotfix.sql
   12-Sep-2003  03:26  2000.80.859.0   1,905,216  Dtspkg.dll
   26-Aug-2003  20:16  2000.80.854.0     528,960  Dtspump.dll
   23-Jun-2003  22:40  2000.80.837.0   1,557,052  Dtsui.dll
   23-Jun-2003  22:40  2000.80.837.0     639,552  Dtswiz.dll
   24-Apr-2003  02:51                    747,927  Instdist.sql
   10-Oct-2003  18:52                    745,961  Instmsdb.sql
   03-May-2003  01:56                      1,581  Inst_repl_hotfix.sql
   08-Feb-2003  06:40  2000.80.765.0      90,692  Msgprox.dll
   01-Apr-2003  02:07                      1,873  Odsole.sql
   05-Apr-2003  01:46  2000.80.800.0      62,024  Odsole70.dll
   07-May-2003  20:41  2000.80.819.0      25,144  Opends60.dll
   07-May-2003  18:47                    132,096  Opends60.pdb
   02-Apr-2003  21:48  2000.80.796.0      57,904  Osql.exe
   02-Apr-2003  23:15  2000.80.797.0     279,104  Pfutil80.dll
   04-Aug-2003  18:17                    550,780  Procsyst.sql
   12-Sep-2003  00:37                     12,305  Qfe469315.sql
   22-May-2003  22:57                     19,195  Qfe469571.sql
   20-Jan-2004  00:45                  1,090,380  Replmerg.sql
   06-Sep-2003  07:18  2000.80.858.0     221,768  Replprov.dll
   16-Jan-2004  01:24  2000.80.908.0     307,784  Replrec.dll
   16-Jan-2004  01:13  2000.80.908.0     159,813  Replres.rll
   06-Sep-2003  00:00                  1,087,150  Replsys.sql
   13-Aug-2003  16:28                    986,603  Repltran.sql
   02-Jan-2004  19:42  2000.80.904.0     287,304  Rinitcom.dll
   22-Oct-2003  00:08  2000.80.871.0      57,916  Semnt.dll
   29-Jul-2003  20:13  2000.80.819.0     492,096  Semobj.dll
   31-May-2003  18:27  2000.80.818.0     172,032  Semobj.rll
   02-Jan-2004  19:42  2000.80.904.0      53,832  Snapshot.exe
   09-Dec-2003  20:07                    117,834  Sp3_serv_uni.sql
   16-Jan-2004  01:23  2000.80.908.0      28,672  Sqlagent.dll
   16-Jan-2004  01:24  2000.80.908.0     311,872  Sqlagent.exe
   07-Jan-2004  22:38  2000.80.905.0     126,976  Sqlakw32.dll
   01-Jun-2003  01:01  2000.80.818.0   4,215,360  Sqldmo.dll
   07-Apr-2003  17:44                     25,172  Sqldumper.exe
   19-Mar-2003  18:20  2000.80.789.0      28,672  Sqlevn70.rll
   27-Sep-2003  04:42  2000.80.865.0     180,792  Sqlmap70.dll
   03-Sep-2003  02:56  2000.80.857.0     188,992  Sqlmmc.dll
   02-Sep-2003  23:03  2000.80.857.0     479,232  Sqlmmc.rll
   22-Oct-2003  00:08  2000.80.871.0     401,984  Sqlqry.dll
   08-Feb-2003  06:40  2000.80.765.0      57,920  Sqlrepss.dll
   16-Jan-2004  01:24  2000.80.908.0   7,610,449  Sqlservr.exe
   16-Jan-2004  01:26                 12,780,544  Sqlservr.pdb
   25-Jul-2003  21:44  2000.80.845.0     590,396  Sqlsort.dll
   08-Feb-2003  06:40  2000.80.765.0      45,644  Sqlvdi.dll
   02-Oct-2003  20:59  2000.80.867.0      33,340  Ssmslpcn.dll
   01-Jun-2003  01:01  2000.80.818.0      82,492  Ssnetlib.dll
   01-Jun-2003  01:01  2000.80.818.0      25,148  Ssnmpn70.dll
   28-Oct-2003  04:21  2000.80.873.0     123,456  Stardds.dll
   01-Jun-2003  01:01  2000.80.818.0     158,240  Svrnetcn.dll
   31-May-2003  18:59  2000.80.818.0      76,416  Svrnetcn.exe
   30-Apr-2003  23:52  2000.80.816.0      45,132  Ums.dll
   30-Apr-2003  23:52                    132,096  Ums.pdb
   02-Jul-2003  00:19  2000.80.834.0      98,816  Xpweb70.dll
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

WORKAROUND

This problem occurs if an attempt to destroy a COM object stops responding (hangs). Sometimes you can help prevent this problem by avoiding code in the COM object that might delay object termination. In Microsoft Visual Basic, you can do this by not putting blocking calls in the Class_Terminate routine. If the COM object makes a loopback connection to the computer that is running SQL Server and that is hosting the COM object, you can help prevent this problem by avoiding loopback connections to SQL Server.

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 the terminology that Microsoft uses when Microsoft corrects 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

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