Service broker dialog '%1!s!' could not be closed because the database with id '%2!s!' is not available. Consider closing the dialogs manually once the database is available again.
Server user '%1!s!' is not a valid user in database '%2!s!'. Add the user account or 'guest' user account into the database ...
Server-level event notifications can not be delivered. Either Service Broker is disabled in msdb, or msdsb failed to start. ...
Service Broker could not upgrade conversation session keys in database '%1!s!' to encrypted format (Error: %2!s!). The Service ...
Service Broker could not upgrade conversation with conversation_handle '%1!s!'. Use END CONVERSATION . WITH CLEANUP to delete ...
Service broker dialog '%1!s!' could not be closed because the database with id '%2!s!' is not available. Consider closing ...
Service broker dialog '%1!s!' could not be closed due to a broker error in database with id '%2!s!' because of the following ...
Service broker failed to clean up conversation endpoints on database '%1!s!'. Another problem is preventing SQL Server from ...
Service Broker in database '%1!s!' has a pending conversation upgrade operation. A database master key in the database is ...
Service Broker message delivery is not enabled in this database. Use the ALTER DATABASE statement to enable Service Broker ...