kcwallace Posted December 16, 2008 Posted December 16, 2008 Does anyone have a english translation for this? More specifically, how can I prevent it. It happens when I am running a series of database record inserts. The CLR has been unable to transition from COM context 0x2f1cb0 to COM context 0x2f1e20 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. Quote Go Beavs!!!
Administrators PlausiblyDamp Posted December 17, 2008 Administrators Posted December 17, 2008 (edited) What database are you using? What drivers are you going through (sqlclient, oledb etc)? Edited December 18, 2008 by PlausiblyDamp Quote Posting Guidelines FAQ Post Formatting Intellectuals solve problems; geniuses prevent them. -- Albert Einstein
kcwallace Posted December 17, 2008 Author Posted December 17, 2008 I am using SQL 2005 and using the SQLClient via C# .Net 3.5 Quote Go Beavs!!!
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.