The CLR has been unable to transition from COM context 0x%1$x to COM context 0x%2$x 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.
The ClockController.Seek method was called with arguments that describe a seek destination with a negative value. The seek ...
The close operation did not complete within the allotted timeout of {0}. The time allotted to this operation may have been ...
The close status description '{0}' is too long. The UTF8-representation of the status description must not be longer than ...
The CloseSequence request's reply message must carry a final acknowledgement. This is a violation of the WS-ReliableMessaging ...
The CLR has been unable to transition from COM context 1$x to COM context 2$x for 60 seconds. The thread that owns the destination ...
The CLR marshaler encountered an error while attempting to associate a SafeHandle with an unmanaged resource. This may cause ...
The CLR marshaler encountered an error while attempting to release the reference to a SafeHandle it acquired in order to ...
The CLR marshaler encountered an error while attempting to restore the thread culture after a call from unmanaged to managed ...
The CLR Type '{0}' could not be loaded during service compilation. Verify that this type is either defined in a source file ...