Groups | Blog | Home
all groups > dotnet component services > november 2005 >

dotnet component services : Please help - COM+ Application is in unstable state...


Bob
11/24/2005 12:00:00 AM
Hi,

I have been getting this kind of event log messages since I have upgraded to
Framework 2 with VS2005 and is wondering if someone can tell me more about
this. I have search the net and a few article points to difference between
the attributes and the COM+ Catalog's settings. I checked them both and they
do not differ.

This is what I did (in NUnit):
1) Call test method in an ES component to insert a bad data to the database
and this throw an exception as expected
2) Call a method to insert a good record and this proceed.
and then Call this same method to insert the same record. The SQL2000
indicated duplicated index and threw and exception as expected.
4) When return to the client side, I always dispose the ES component. I
noticed that it was hung on the IDisposable.Dispose().

Why is that?

I did not see this kind of problem in beta 2 of VS2005.

Any idea? Many thanks.

Bob
=====================================
Event Type: Error
Event Source: COM+
Event Category: (98)
Event ID: 4822
Date: 25/11/2005
Time: 1:52:03 AM
User: N/A
Computer: LEON-PC
Description:
A condition has occurred that indicates this COM+ application is in an
unstable state or is not functioning correctly. Assertion Failure:
m_pTxResPool == NULL

Server Application ID: {05E8D6AD-92AB-4C2A-A1C6-828AC5576893}
Server Application Instance ID:
{C9263F6F-A85C-4163-85BC-6795CF80F959}
Server Application Name: Demo Server
The serious nature of this error has caused the process to terminate.
COM+ Services Internals Information:
File: d:\qxp_slp\com\com1x\src\comsvcs\txprop\txstream.cpp, Line: 608
Comsvcs.dll file version: ENU 2001.12.4414.308 shp

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.



Stefan Glock
12/27/2005 12:42:20 PM
Hi,

is there any solution availabe for this problem?

[quoted text, click to view]

Stefan Glock
12/27/2005 9:29:52 PM
I only have this error if i am updating a Windows XP Workstation with the
latest patches.

[quoted text, click to view]

Stefan Glock
12/28/2005 2:45:11 PM
I fixed (or better say workaround) this by simply disabling the Object
Pooling in the Library Application.

[quoted text, click to view]

AddThis Social Bookmark Button