Event ID 10006: COM+ activation failed
Jake
We're trying to figure out a sporadic issue in the office here that only
seems to be happening on one server. During this time, all apps using this
component fail, but the duration of the outage is typically around 15-20
minutes before it just resolves itself. This is the only repeating entry we
have been able to find in the System Event log:
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10006
Date: 6/22/2009
Time: 3:31:02 PM
User: N/A
Computer: COMPSERV1
Description:
DCOM got error "COM+ activation failed because the activation could not be
completed in the specified amount of time. " from the computer COMPSERV2 when
attempting to activate the server:
{7B86A4F5-199F-441B-9EA1-2B91F13E70AB}
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
I've been able to find very little on this error message. I'm not sure if
this is pointing to the cause of our issue or if this is just a victom of an
underlying issue.
Any help would be appreciated.
Brian Muth
"Jake" <Ja...@discussions.microsoft.com> wrote in message
news:704AC4DB-94A6-431F...@microsoft.com...
It means the COM+ object couldn't be activated. A typical scenario is an STA
object that is busy or in a hung state.
Other than that, there isn't nearly enough information in your post to be
more helpful. How many components? What language are they written in? STA vs
MTA? COM+ settings?
Jake
I will do my best to answer. This is a single component and its the same one
each time, although it runs fine on the other servers in the farm. The
component was written in C++ and hasn't been updated since 2006. As far as
STA/MTA, COM+ indicates MTA, but I don't have access to the source code to
verify. I'm not sure which COM+ settings you're looking for (global or this
component), but this component is setup as a proxy on COMPSERV1 and the
remote server where it is installed is COMPSERV2.
Settings on the component are:
Transaction Support - Not Supported
Enforce component level access checks - Unchecked
Minimum Pool Size - 1
Maximum Pool Size - 50
Creation Timeout - 10000
Don't force activation context - Checked
Component supports events and statistics - Checked
Enable Just In Time Activation - Checked
Synchronization Support - Required
If you need additional info, let me know.
Brian Muth
That helps a bit.
Can you reproduce the problem? When the problem occurs, what does "View,
Status" show? Do you see the executable instantiated on the remote server?
"Jake" <Ja...@discussions.microsoft.com> wrote in message
news:93038C9E-49DC-4246...@microsoft.com...
Jake
This is where we run into issues. It is only happening in our production
environment and aside from happening in the afternoon on this specific
server, there doesn't seem to be any pattern to when it happens. Typically
by the time we are notified of the issue and log into the server, the issue
has already cleared.
John Lan
http://technet.microsoft.com/en-us/library/cc774289(WS.10).aspx,
http://msdn.microsoft.com/en-us/library/aa374351(VS.85).aspx,
Extend RPC Error Information may report more details about this issue,
typically this is caused by resource limitation or lock issue.
"Jake" <Ja...@discussions.microsoft.com> 写入消息
news:E471B28F-E963-4411...@microsoft.com...
Brian Muth
I feel the pain.
These are amongst the most difficult problems to solve. In my experience,
the key to solving this is in recreating the issue in the QA or development
environment. I can't give you much guidance in this regard because this
depends on the particulars of your application. Is it related to number of
clients? The workload? The type of data being processed? These are the
things to think about in order to reproduce the conditions needed to
precipitate the problem.
No that this is the situation in or case, but I've seen this scenario in the
past on more than one occasion when projects were pushed into production
prematurely, and there was not adequate load testing in the QA phase.
Best of luck,
Brian