We have on rare occasions experienced this exception on the manager machine:
"The CLR has been unable to transition from COM context 0x1b7ae0f0 to COM context
0x1b7ae340 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 op-
eration 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.".
It seems to mainly have been thread-deadlocking that has caused it,
and we have not been able to consistently recreate it. The exception is rare, but we think it is from the coming from the UI.
We have on rare occasions experienced this exception on the manager machine:
"The CLR has been unable to transition from COM context 0x1b7ae0f0 to COM context 0x1b7ae340 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 op- eration 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.".
It seems to mainly have been thread-deadlocking that has caused it, and we have not been able to consistently recreate it. The exception is rare, but we think it is from the coming from the UI.