SQL 2005

I receive this error everytime I restart the server and have no clue what it
means.

Event Type:	Error
Event Source:	MSSQLSERVER
Event Category:	(2)
Event ID:	8355
Date:		1/28/2006
Time:		9:04:49 PM
User:		N/A
 Computer:	NETCORWEB0
1
Description:
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.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: a3 20 00 00 10 00 00 00   £ ......
0008: 0c 00 00 00 4e 00 45 00   ....N.E.
0010: 54 00 43 00 4f 00 52 00   T.C.O.R.
0018: 57 00 45 00 42 00 30 00   W.E.B.0.
0020: 31 00 00 00 07 00 00 00   1.......
0028: 6d 00 61 00 73 00 74 00   m.a.s.t.
0030: 65 00 72 00 00 00         e.r...

Any help is greatly appreciated.

Event notifications, as well as query notifications, use Service Broker to
deliver the notifications. Server level event notification use MSDB and if
Service Broker is disabled in MSDB, they will not be delivered. That what
the message means.
Service Broker is usually disabled as a result of a database restore or
attach operation. To enable it back, use ALTER DATABASE ... SET
ENABLE_BROKER;
SQL Server Database mail funcitonality also requires Service Broker to be
enabled in msdb.
If you don't need any of these functionalities, you can safely ignore the
message.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

HTH,
~ Remus Rusanu

SQL Service Broker
http://msdn2.microsoft.com/en-us/library/ms166043(en-US,SQL.90).aspx


"mlnetcor" < mlnetcor@discussions
.microsoft.com> wrote in message
news:A3C68E79-64C3-4784-967B- 8490255C4CA0@microso
ft.com...
>I receive this error everytime I restart the server and have no clue what
>it
> means.
>
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 8355
> Date: 1/28/2006
> Time: 9:04:49 PM
> User: N/A
> Computer: NETCORWEB01
> Description:
> 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.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: a3 20 00 00 10 00 00 00   £ ......
> 0008: 0c 00 00 00 4e 00 45 00   ....N.E.
> 0010: 54 00 43 00 4f 00 52 00   T.C.O.R.
> 0018: 57 00 45 00 42 00 30 00   W.E.B.0.
> 0020: 31 00 00 00 07 00 00 00   1.......
> 0028: 6d 00 61 00 73 00 74 00   m.a.s.t.
> 0030: 65 00 72 00 00 00         e.r...
>
> Any help is greatly appreciated.

Thanks for the info.

How long does this query take to run?

I used:

ALTER DATABASE MSDB
SET ENABLE_BROKER

Query has been executing for over 7 minutes.

"Remus Rusanu [MSFT]" wrote:

> Event notifications, as well as query notifications, use Service Broker to
> deliver the notifications. Server level event notification use MSDB and if
> Service Broker is disabled in MSDB, they will not be delivered. That what
> the message means.
> Service Broker is usually disabled as a result of a database restore or
> attach operation. To enable it back, use ALTER DATABASE ... SET
> ENABLE_BROKER;
> SQL Server Database mail funcitonality also requires Service Broker to be
> enabled in msdb.
> If you don't need any of these functionalities, you can safely ignore the
> message.
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
> HTH,
> ~ Remus Rusanu
>
> SQL Service Broker
> http://msdn2.microsoft.com/en-us/library/ms166043(en-US,SQL.90).aspx
>
>
> "mlnetcor" < mlnetcor@discussions
.microsoft.com> wrote in message
> news:A3C68E79-64C3-4784-967B- 8490255C4CA0@microso
ft.com... 
>
>
>

It needs exclusive access on the msdb database. Make sure you close any
other user connection on msdb first.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

HTH,
~ Remus Rusanu

SQL Service Broker
http://msdn2.microsoft.com/en-us/library/ms166043(en-US,SQL.90).aspx


"mlnetcor" < mlnetcor@discussions
.microsoft.com> wrote in message
news:48FC9661-19CA-4743-AF3E- 29961805BF04@microso
ft.com...
> Thanks for the info.
>
> How long does this query take to run?
>
> I used:
>
> ALTER DATABASE MSDB
> SET ENABLE_BROKER
>
> Query has been executing for over 7 minutes.
>
> "Remus Rusanu [MSFT]" wrote:
> 

And  make sure agent isn't running - agent opens connections to msdb.

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Remus Rusanu [MSFT]" <Remus.Rusanu.NoSpam@microsoft.com.nowhere.moon> w
rote
in message news:%23sS3JDRJGHA.528@TK2MSFTNGP12.phx.gbl...
> It needs exclusive access on the msdb database. Make sure you close any
> other user connection on msdb first.
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> HTH,
> ~ Remus Rusanu
>
> SQL Service Broker
> http://msdn2.microsoft.com/en-us/library/ms166043(en-US,SQL.90).aspx
>
>
> "mlnetcor" < mlnetcor@discussions
.microsoft.com> wrote in message
> news:48FC9661-19CA-4743-AF3E- 29961805BF04@microso
ft.com... 
>
>