The metadata could not be determined because statement '%1!s!' in procedure '%2!s!' contains dynamic SQL. Consider using the WITH RESULT SETS clause to explicitly describe the result set.
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. ...
The metadata could not be determined because statement '%1!s!' in procedure '%2!s!' invokes a CLR procedure. Consider using ...
The metadata could not be determined because statement '%1!s!' in procedure '%2!s!' invokes an extended stored procedure. ...
The metadata could not be determined because statement '%1!s!' in procedure '%2!s!' uses an undeclared parameter in a context ...