You are currently offline, waiting for your internet to reconnect

FIX: COM+ Access Violation Error Occurs with BizTalk Server WMI Pseudo Provider

This article was previously published under Q302435
This article has been archived. It is offered "as is" and will no longer be updated.
When BizTalk Server 2000 is running under a high load condition, the following error may be generated in the Application event log:
Event Type:	ErrorEvent Source:	COM+Event Category:	SVCEvent ID:	         4194Date:		6/13/2001Time:		1:34:47 AMUser:		N/AComputer:	         BIZTALKSERVERDescription:The system has called a custom component and that component has failed and generated an exception. This indicates a problem with the custom component. Notify the developer of this component that a failure has occurred and provide them with the information below. Component Prog ID: Server Application ID: {6ECD95AC-3C06-4A9B-9D43-4565C1BD3319}Server Application Name: BizTalk Server Internal UtilitiesException: C0000005Address: 0x6922B9A3Call Stack: ciscore!GetQueueSemaphore(void) + 0x14866ciscore!CleanUp(void) + 0x4455CISENGINE!GetNewStateEngine(struct IInterchangeStateEngine * *) + 0x8C8CISENGINE!LKRhash::CLKRHashTable::End(void) + 0x7563TxfAux + 0x34FC1ole32!CoQueryProxyBlanket + 0x293Aole32!CoQueryProxyBlanket + 0x2B8Fole32!CoQueryProxyBlanket + 0x2F6CTxfAux!CoGetInterceptorForOle32 + 0x2FA7MSCIS!SchedulerRunning(void) + 0x1DD8KERNEL32!SetFilePointer + 0x18A					
The error in the BizTalk Messaging Service Windows Management Instrumentation (WMI) Pseudo Provider is caused by the Windows 2000 WMI Provider unloading prematurely. When the WMI provider unloads, all BizTalk Server WMI Events fail, which causes an Access Violation in BizTalk Server.
To resolve this problem, obtain the latest service pack for Microsoft BizTalk Server 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
299664 INFO: How to Obtain the Latest BizTalk Server 2000 Service Pack
Microsoft has confirmed that this is a problem in Microsoft BizTalk Server 2000. This problem was first corrected in Microsoft BizTalk Server 2000 Service Pack 1a.

Article ID: 302435 - Last Review: 10/24/2013 06:58:27 - Revision: 3.1

Microsoft BizTalk Server 2000 Service Pack 1

  • kbnosurvey kbarchive kbbiztalk2000sp1afix kbbug kbfix KB302435