A non marshalable COM component is being used from a different apartment/context then the one where it first entered the CLR. Since the component is non marshalable, it will be called directly from the current apartment/context. This may cause corruption or data loss if the component does not support being accessed from multiple threads at once. This is most likely caused by a faulty IMarshal implementation on the part of the COM component.
A navigation property of type '{0}' is not valid. '{1}' or a single implementation of '{2}' was expected, but '{3}' was found. ...
A navigation property that returns an EntityCollection cannot be changed if the existing EntityCollection contains items ...
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found ...
A newly accepted connection did not receive initialization data from the sender within the configured ChannelInitializationTimeout ...
A non marshalable COM component is being used from a different apartment/context then the one where it first entered the ...
A non-critical error or warning occurred in the MetadataExchangeClient during WSDL Import This could result in some endpoints ...
A non-null {0} implementation is required for services marked with {1}. Either programmatically add one by setting the PersistenceProvider ...
A non-static member cannot be accessed with the class name;;The non-static member '{0}' cannot be accessed with the class ...
A null Message (signalling end of channel) was received from a datagram channel, but the channel is still in the Opened state. ...