Context 0x%1$x' is disconnected. Releasing the interfaces from the current context (context 0x%2$x). This may cause corruption or data loss. To avoid this problem, please ensure that all contexts/apartments stay alive until the application is completely done with the RuntimeCallableWrappers that represent COM components that live inside them.
Contains a list of categories associated with the table header (read by screen readers). The categories can be any string ...
Content model validation resulted in a large number of states, possibly due to large occurrence ranges. Therefore, content ...
Content not valid. The conceptual side Member or Property '{0}' specified as part of this MSL does not exist in MetadataWorkspace. ...
Context 1$x is disconnected. No proxy will be used to service the request on the COM component. This may cause corruption ...
Context 1$x' is disconnected. Releasing the interfaces from the current context (context 2$x). This may cause corruption ...
Context 1$x' is disconnected. Releasing the interfaces from the current context (context 2$x).This may cause corruption or ...
Context cached at the channel cannot be set or retrieved when the context management is disabled at the channel layer. Ensure ...
Context channel received a message with context which does not match the current context cached at the channel. Ensure service ...
Context protocol was unable to parse the context header. Nodes disallowed by the context header schema were found inside ...