The metadata could not be determined because every code path results in an error; see previous errors for some of these.
The message received was sent by the initiator of the conversation, but the message type '%1!s!' is marked SENT BY TARGET ...
The message string being posted by the managed error infrastructure contains a bad format specification. This is an internal ...
The message with default language Id of destination is not present in destination and hence attempting to transfer the same ...
The message {0}:{1} on conversation {2}:{3} from service {4} and broker instance {5} to service {6} and broker instance {7} ...
The metadata could not be determined because every code path results in an error; see previous errors for some of these. ...
The metadata could not be determined because remote metadata discovery failed for statement '%1!s!' in procedure '%2!s!'. ...
The metadata could not be determined because statement '%1!s!' contains dynamic SQL. Consider using the WITH RESULT SETS ...
The metadata could not be determined because statement '%1!s!' in procedure '%2!s!' contains dynamic SQL. Consider using ...
The metadata could not be determined because statement '%1!s!' in procedure '%2!s!' does not support metadata discovery. ...