COM+ application is in an unstable state

[MR]

(apologies for the multiple post)
We developed a component that uses enterprise services. the component seems
to run fine. we don't see any memory leaks.
it seems that after running for a period of time (several hours), and after
several thousands of calls (maybe even tens of thousands of calls) the
application that calls the component crashes.
the parent program and component are written in C# and run on a Windows
2003.
We have tried many things and the only thing that works is to remove the
derivation from enterprise services. but this removes the scalability that
we had hoped to achieve.
we are stumped by this. has anyone else experienced this problem? what is
the cause of it? could we be doing something wrong? is there a solution or
workaround.?
thanks for your help
m

Event Type: Error
Event Source: COM+
Event Category: (98)
Event ID: 4822
Date: 11/29/2004
Time: 3:50:11 AM
User: N/A
Computer: SERVER
Description:
A condition has occurred that indicates this COM+ application is in an
unstable state or is not functioning correctly. Assertion Failure:
new_cCalls > 0

Server Application ID: {61EEB7E0-E6CD-4146-9488-8C07E4827FBE}
Server Application Instance ID:
{D9A0B0EC-EE62-4EEA-B243-670478CE05A2}
Server Application Name: ProcessMessage
The serious nature of this error has caused the process to terminate.
COM+ Services Internals Information:
File: d:\nt\com\complus\src\comsvcs\tracker\trkprop\trkprop.cpp, Line: 476
Comsvcs.dll file version: ENU 2001.12.4720.130 shp

 

[Peter Huang [MSFT]]

Hi

The 4822 event is a general error which may be caused by many possibility.
So far I did not find any known issue is exactly the same as what you have
show.
Here is a KB, you may take a look.

PRB: Some Functionalities of a COM+ Application Do Not Change If You Change
the Corresponding Settings in the COM+ Catalog
http://support.microsoft.com/?id=322630

Because the attributes on your code may not be corresponding to the setting
in the MMC which may cause problem, you may have a check and ensure they
have the match setting and make a test problem to generat a lot of function
call to see if that works.

Also since this is not easy reproduce problem, it is hard to handle in the
newsgroup, I strongly recommend you submit a service request to the MS PSS,
which will do dump analysis which will be helpful in this scenario.

You may reach MSPSS via the link below.
http://support.microsoft.com

Hope this helps.


Best regards,

Perter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Yan-Hong Huang[MSFT]]

Hi MR,

I agree with Peter on it. For this type of crash issues, it is better for
us to get a crash dump and then start from it to isolate the problem. This
should be the most efficient way for troubleshooting. Microsoft product
support service should be the correct source for you to seek for support.
http://www.microsoft.com/services/microsoftservices/supp.mspx

Thanks for your understanding.

Best regards,
Yanhong Huang
Microsoft Community Support

Get Secure! ¨C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
-http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.as
p&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.