Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Monday, November 21, 2005 1:51 AM
Whenever I start my SQL Express 2005 database, I get the following in the logs :
<SNIP>
2005-11-20 19:04:11.92 spid8s Starting up database 'tempdb'.
2005-11-20 19:04:11.99 spid5s Error: 8355, Severity: 16, State: 1.
2005-11-20 19:04:11.99 spid5s Service Broker is disabled in MSDB or MSDB failed to start. Server level event notifications can not be delivered. Event notifications with FAN_IN in other databases could be affected as well.
2005-11-20 19:04:11.99 spid11s The Service Broker protocol transport is disabled or not configured.
2005-11-20 19:04:11.99 spid5s Recovery is complete. This is an informational message only. No user action is required.
2005-11-20 19:04:11.99 spid11s The Database Mirroring protocol transport is disabled or not configured.
2005-11-20 19:04:12.04 spid11s Service Broker manager has started.
</SNIP>
I also get "Service Broker is disabled in MSDB or MSDB failed to start. Server level event notifications can not be delivered. Event notifications with FAN_IN in other databases could be affected as well." in the event logs.
This is on a Windows 2003 SP1 server, and was an upgrade to an existing MSDE 2000 database.
Does anyone have any ideas what causes this, and how to fix it?
Monday, November 21, 2005 2:21 AM ✅Answered | 7 votes
If you don't care about Service Broker functionality or any other functionality dependent on it (Event Notifications, Query Notifications, SqlDependency, SQL database mail etc) then you can simply ignore the message.
If you need Service Broker functionality, you should enable back the broker in MSDB:
ALTER DATABASE [msdb] SET ENABLE_BROKER;
HTH,
~ Remus
Monday, November 21, 2005 3:27 AM
Thanks for the quick reply! Everything seems to be working despite this message, meaning my application can connect to the database and query/update it, so I think I'll just ignore the message for now. If something starts acting up, I'll enable it to see if that helps.
Tuesday, June 5, 2007 9:40 AM
If i want to exchange message between two different instances or databases in two different servers, then I have to enable the transport protocol which wil be disabled by default in service broker.I read in some article that some registry settings has to be changed.So can someone suggest on the same.
Tuesday, June 5, 2007 7:51 PM
When I try to execute this statement, the query just continues to run and run. If I use the GUI, it instantly hangs the task. Any thoughts as to why and how to fix would be great. Thx, Cin
Thursday, August 2, 2007 3:57 PM | 2 votes
You need to stop SQL Agent for this statement to complete.
Thursday, November 11, 2010 7:15 PM
from this post http://social.msdn.microsoft.com/Forums/en/sqlservicebroker/thread/97f6a441-50e3-47f5-a4b0-8df68653a56d
You need exclusive lock on the Database, use this.
ALTER DATABASE TEST SET SINGLE_USER WITH ROLLBACK IMMEDIATE
ALTER DATABASE TEST SET
ENABLE_BROKER
ALTER DATABASE TEST SET MULTI_USER
worked a champ for me, but because the post was locked couldnt thank the guy! ;)
Simon
Friday, May 6, 2011 3:12 PM
from this post http://social.msdn.microsoft.com/Forums/en/sqlservicebroker/thread/97f6a441-50e3-47f5-a4b0-8df68653a56d
You need exclusive lock on the Database, use this.
ALTER DATABASE TEST SET SINGLE_USER WITH ROLLBACK IMMEDIATE
ALTER DATABASE TEST SET ENABLE_BROKER ALTER DATABASE TEST SET MULTI_USER
worked a champ for me, but because the post was locked couldnt thank the guy! ;)
Simon
make sense, "lock" part, will try, thanks
Friday, December 30, 2011 4:01 PM
THIS WORKS ON ME!!!! PERFECT!!
Monday, January 9, 2012 3:15 PM
If I stop the SQL Agent and run the following command, what exactly is going to happen? What harm could be done if any? I get this message when restarting my SQL server 2005 machine but everything seems to work fine anyway.
ALTER DATABASE [MSDB] SET NEW_BROKER WITH ROLLBACK IMMEDIATE