The message was not found in the Message Box or the Tracking databases. This may be caused by one of the following conditions: (1) message tracking is not enabled; (2) the message(s) is no longer referenced by a running or suspended service instance; (3) the Message Box tracking tables have been automatically purged; or (4) the SQL Server agent is not running on the Message Box servers.
The message posted to a dynamic port had an incorrect URL format:"%1". The format should be in the following form: "protocol://address". ...
The message produced by the receive pipeline: "%1" for receive location: "%2" has an invalid value(%3) for a message context ...
The message size cannot be bigger than 4 GB (approximately 4,294,967,295 in bytes). Please specify a smaller message and ...
The message was not decrypted because the decoder could not find the decryption certificate in the "Current User\Personal" ...
The message was not found in the Message Box or the Tracking databases. This may be caused by one of the following conditions: ...
The message was routed to a subscription based upon a non-unique correlation set. Please either clean up the data before ...
The MessageBox cannot be deleted because it may still contain incomplete instances. Ensure that there are no incomplete instances ...
The MessageBox cannot be deleted because it still contains tracking data. Restart the tracking host to move the data to the ...
The MessageBox object is successfully deleted from the Management database but not all of the SQL replication configuration ...