https://www.betaarchive.com/wiki/index.php?title=Microsoft_KB_Archive/835581&feed=atom&action=history
Microsoft KB Archive/835581 - Revision history
2024-03-28T13:55:51Z
Revision history for this page on the wiki
MediaWiki 1.39.3
https://www.betaarchive.com/wiki/index.php?title=Microsoft_KB_Archive/835581&diff=202841&oldid=prev
3155ffGd: importing KB archive
2020-07-18T17:13:12Z
<p>importing KB archive</p>
<p><b>New page</b></p><div><div id="nsbanner"><br />
<br />
<div id="bannerrow1"><br />
<br />
{|<br />
| Knowledge Base<br />
|<br />
|}<br />
<br />
<br />
</div><br />
<div id="TitleRow"><br />
<br />
= <span id="KB835581"></span>FIX: An &quot;Error 17883&quot; 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 =<br />
<br />
<br />
</div><br />
<br />
</div><br />
<div id="nstext" valign="BOTTOM"><br />
<br />
Article ID: 835581<br />
<br />
Article Last Modified on 11/2/2007<br />
<br />
<br />
-----<br />
<br />
APPLIES TO<br /><br />
<br /><br />
<br />
* Microsoft SQL Server 2000 Desktop Engine (Windows)<br />
* Microsoft SQL Server 2000 Developer Edition<br />
* Microsoft SQL Server 2000 Enterprise Edition<br />
* Microsoft SQL Server 2000 Personal Edition<br />
* Microsoft SQL Server 2000 Standard Edition<br />
* Microsoft SQL Server 2000 Workgroup Edition<br />
* Microsoft SQL Server 7.0 Standard Edition<br />
<br />
<br />
-----<br />
<br />
<div class="notice_section"><br />
<br />
BUG #: 469097 (SQL Server 8.0)<br />
<br />
</div><br />
<div class="notice_section"><br />
<br />
''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.''<br />
<br />
</div><br />
<div class="summary_section"><br />
<br />
== SUMMARY ==<br />
<br />
This article describes the following about this hotfix release:<br />
* The issues that are fixed by the hotfix package<br />
* The prerequisites for installing the hotfix package<br />
* Whether you must restart the computer after you install the hotfix package<br />
* Whether the hotfix package is replaced by any other hotfix package<br />
* Whether you must make any registry changes<br />
* The files that are contained in the hotfix package<br />
<br />
<br />
</div><br />
<div class="symptoms_section"><br />
<br />
== SYMPTOMS ==<br />
<br />
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:<br />
<div class="errormessage"><br />
<br />
Error: 17883, Severity: 1, State: 0<br /><br />
server Process 162:0 (0) UMS Context 0x11DE8B68 appears to be non-yielding on Scheduler 1<br />
<br />
</div><br />
'''Note''' This error message may also be logged for other reasons.<br /><br />
<br /><br />
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:<br />
<div class="indent"><br />
<br />
[[../810185|810185]] SQL Server 2000 hotfix update for SQL Server 2000 Service Pack 3 and 3a<br />
<br />
<br />
</div><br />
<br />
</div><br />
<div class="resolution_section"><br />
<br />
== RESOLUTION ==<br />
<br />
=== Service pack information ===<br />
<br />
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:<br />
<div class="indent"><br />
<br />
[[../290211|290211]] How to obtain the latest SQL Server 2000 service pack<br />
<br />
<br />
</div><br />
=== Hotfix information ===<br />
<br />
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.<br /><br />
<br /><br />
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:<br />
<div class="indent"><br />
<br />
http://support.microsoft.com/contactus/?ws=support<br />
<br />
<br />
</div><br />
'''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.<br /><br />
<br /><br />
'''Note''' No hotfix is currently available for SQL Server 7.0.<br />
==== Prerequisites ====<br />
<br />
<ul><br />
<li>Microsoft SQL Server 2000 Service Pack 3 (SP3)<br /><br />
<br /><br />
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:<br />
<div class="indent"><br />
<br />
<p>[[../290211|290211]] How to obtain the latest SQL Server 2000 service pack</p><br />
<br />
</div></li></ul><br />
<br />
==== Restart information ====<br />
<br />
You do not have to restart the computer after you apply this hotfix.<br />
==== Registry information ====<br />
<br />
You do not have to change the registry.<br />
==== Hotfix file information ====<br />
<br />
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.<br /><br />
<br /><br />
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.<br />
===== SQL Server 2000 32-bit versions =====<br />
<br />
<pre class="fixed_text"> Date Time Version Size File name<br />
-------------------------------------------------------------------<br />
31-May-2003 18:45 2000.80.818.0 78,400 Console.exe<br />
28-Oct-2003 04:21 2000.80.873.0 315,968 Custtask.dll<br />
02-Oct-2003 20:59 2000.80.867.0 33,340 Dbmslpcn.dll<br />
25-Apr-2003 02:12 786,432 Distmdl.ldf<br />
25-Apr-2003 02:12 2,359,296 Distmdl.mdf<br />
30-Jan-2003 01:55 180 Drop_repl_hotfix.sql<br />
12-Sep-2003 03:26 2000.80.859.0 1,905,216 Dtspkg.dll<br />
26-Aug-2003 20:16 2000.80.854.0 528,960 Dtspump.dll<br />
23-Jun-2003 22:40 2000.80.837.0 1,557,052 Dtsui.dll<br />
23-Jun-2003 22:40 2000.80.837.0 639,552 Dtswiz.dll<br />
24-Apr-2003 02:51 747,927 Instdist.sql<br />
10-Oct-2003 18:52 745,961 Instmsdb.sql<br />
03-May-2003 01:56 1,581 Inst_repl_hotfix.sql<br />
08-Feb-2003 06:40 2000.80.765.0 90,692 Msgprox.dll<br />
01-Apr-2003 02:07 1,873 Odsole.sql<br />
05-Apr-2003 01:46 2000.80.800.0 62,024 Odsole70.dll<br />
07-May-2003 20:41 2000.80.819.0 25,144 Opends60.dll<br />
07-May-2003 18:47 132,096 Opends60.pdb<br />
02-Apr-2003 21:48 2000.80.796.0 57,904 Osql.exe<br />
02-Apr-2003 23:15 2000.80.797.0 279,104 Pfutil80.dll<br />
04-Aug-2003 18:17 550,780 Procsyst.sql<br />
12-Sep-2003 00:37 12,305 Qfe469315.sql<br />
22-May-2003 22:57 19,195 Qfe469571.sql<br />
20-Jan-2004 00:45 1,090,380 Replmerg.sql<br />
06-Sep-2003 07:18 2000.80.858.0 221,768 Replprov.dll<br />
16-Jan-2004 01:24 2000.80.908.0 307,784 Replrec.dll<br />
16-Jan-2004 01:13 2000.80.908.0 159,813 Replres.rll<br />
06-Sep-2003 00:00 1,087,150 Replsys.sql<br />
13-Aug-2003 16:28 986,603 Repltran.sql<br />
02-Jan-2004 19:42 2000.80.904.0 287,304 Rinitcom.dll<br />
22-Oct-2003 00:08 2000.80.871.0 57,916 Semnt.dll<br />
29-Jul-2003 20:13 2000.80.819.0 492,096 Semobj.dll<br />
31-May-2003 18:27 2000.80.818.0 172,032 Semobj.rll<br />
02-Jan-2004 19:42 2000.80.904.0 53,832 Snapshot.exe<br />
09-Dec-2003 20:07 117,834 Sp3_serv_uni.sql<br />
16-Jan-2004 01:23 2000.80.908.0 28,672 Sqlagent.dll<br />
16-Jan-2004 01:24 2000.80.908.0 311,872 Sqlagent.exe<br />
07-Jan-2004 22:38 2000.80.905.0 126,976 Sqlakw32.dll<br />
01-Jun-2003 01:01 2000.80.818.0 4,215,360 Sqldmo.dll<br />
07-Apr-2003 17:44 25,172 Sqldumper.exe<br />
19-Mar-2003 18:20 2000.80.789.0 28,672 Sqlevn70.rll<br />
27-Sep-2003 04:42 2000.80.865.0 180,792 Sqlmap70.dll<br />
03-Sep-2003 02:56 2000.80.857.0 188,992 Sqlmmc.dll<br />
02-Sep-2003 23:03 2000.80.857.0 479,232 Sqlmmc.rll<br />
22-Oct-2003 00:08 2000.80.871.0 401,984 Sqlqry.dll<br />
08-Feb-2003 06:40 2000.80.765.0 57,920 Sqlrepss.dll<br />
16-Jan-2004 01:24 2000.80.908.0 7,610,449 Sqlservr.exe<br />
16-Jan-2004 01:26 12,780,544 Sqlservr.pdb<br />
25-Jul-2003 21:44 2000.80.845.0 590,396 Sqlsort.dll<br />
08-Feb-2003 06:40 2000.80.765.0 45,644 Sqlvdi.dll<br />
02-Oct-2003 20:59 2000.80.867.0 33,340 Ssmslpcn.dll<br />
01-Jun-2003 01:01 2000.80.818.0 82,492 Ssnetlib.dll<br />
01-Jun-2003 01:01 2000.80.818.0 25,148 Ssnmpn70.dll<br />
28-Oct-2003 04:21 2000.80.873.0 123,456 Stardds.dll<br />
01-Jun-2003 01:01 2000.80.818.0 158,240 Svrnetcn.dll<br />
31-May-2003 18:59 2000.80.818.0 76,416 Svrnetcn.exe<br />
30-Apr-2003 23:52 2000.80.816.0 45,132 Ums.dll<br />
30-Apr-2003 23:52 132,096 Ums.pdb<br />
02-Jul-2003 00:19 2000.80.834.0 98,816 Xpweb70.dll</pre><br />
'''Note''' Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.<br />
<br />
</div><br />
<div class="workaround_section"><br />
<br />
== WORKAROUND ==<br />
<br />
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.<br />
<br />
</div><br />
<div class="status_section"><br />
<br />
== STATUS ==<br />
<br />
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.<br />
<br />
</div><br />
<div class="moreinformation_section"><br />
<br />
== MORE INFORMATION ==<br />
<br />
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:<br />
<div class="indent"><br />
<br />
[[../822499|822499]] New naming schema for Microsoft SQL Server software update packages<br />
<br />
<br />
</div><br />
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:<br />
<div class="indent"><br />
<br />
[[../824684|824684]] Description of the standard terminology that is used to describe Microsoft software updates<br />
<br />
<br />
</div><br />
<br />
</div><br />
<br /><br />
<br />
Additional query words: scheduler hang hung sp_OA sp_OADestroy<br />
<br />
Keywords: kbhotfixserver kbqfe kbsqlserv2000presp4fix kbqfe kbfix kbbug kbpubtypekc KB835581<br />
<br />
<div class="footer"><br />
<br />
<br /><br />
<br />
<br />
-----<br />
<br />
[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]<br />
<br />
<span>© Microsoft Corporation. All rights reserved.</span><br />
<br />
<br />
</div><br />
<br />
</div></div>
3155ffGd