CLR (MDA) Error at Runtime

Question

0.00/5 (No votes)

See more:

I'm in the process of calling a function repeatedly for transferring data from one server to another. However, I get the following error message. The error is not occurred on a particular line; so , it is hard to debug.

The CLR has been unable to transition from COM context 0x1b1e78 to COM
context 0x1b1fe8 for 60 seconds. The thread that owns the
destination context/apartment is most likely either doing a
non pumping wait or processing a very long running operation
without pumping Windows messages. This situation
generally has a negative performance impact and may
even lead to the application becoming non responsive
or memory usage accumulating continually over time. To
avoid this problem, all single threaded apartment (STA)
threads should use pumping wait primitives (such as
CoWaitForMultipleHandles) and routinely pump messages
during long running operations.

Posted 11-Aug-11 1:10am

Rakesh Meel

Updated 11-Aug-11 1:11am

v2

Add a Solution

2 solutions

Solution 1

I think this is 10th question, that's answer is first result of Google search[^].

OK here you go

http://blog.wpfwonderland.com/2007/08/16/clr-has-been-unable-to-transition-from-com-context-for-60-seconds/[^]

Posted 11-Aug-11 1:39am

Suresh Suthar

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Rakesh Meel · Accepted Answer · 2011-08-11T03:27:00

Solution 2

Thanks Dear for kind reply....But little bit more hard problem is there...i Use visual studio 2008 and there no option that suggested by you....
Debug -> Exceptions -> Managed Debug Assistants
so what to do more if any idea plz specify.

Posted 11-Aug-11 3:27am

Rakesh Meel

Comments

Suresh Suthar 12-Aug-11 0:36am

Hi Rakesh, There is an option under Debug menu or Press Ctrl+D+E Exception dialog will open...

And please don't post your question in solution just add a comment to existing question or solution....

[no name] 12-Aug-11 2:10am

Thanks dear now my problem resolved......once again thanks for kind help