Error Connecting to SQL 2000

I am using Visual Studio 2005 with SQL Server 2000. I'm having an issue where I can build my website just fine for long periods of time, and then for what appears to be no reason, my site errors out when trying to connect to the database with the message below -- the thing is I don't want to use a SQL Server 2005 database, nor do I have Server 2005 or Server Express loaded. How can I unhook this and make it use SQL 2000?

"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.) "

This does not seem to be related to SSIS. You might get a better answer if you try to post this message into a more appropriate forum.

Error Connecting to SQL 2000

I am using Visual Studio 2005 withSQL Server 2000. I'm having an issue where I can build my website just fine for long periods of time, and then for what appears to be no reason, my site errors out when trying to connect to the database with the message below -- the thing is I don't want to use a SQL Server 2005 database, nor do I have Server 2005 or Server Express loaded. How can I unhook this and make it use SQL 2000?

"An error has occurred while establishing a connection to theserver. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.) "

This is the standard message for failing to connect to the server, even if it is SQL Server 2000.

The message talks about 2005, but if you're using 2000, you may ignore this addition.

The important sentence here is: "No connection could be made because the target machine actively refused it".

One thing you could try is just refresh the page and try again.

Jos

|||

Hi i gues u need to restart ur services including SQL services as well n yes it a common error so dont worry about it may it helps u

|||

I've tried restarting my SQL services and rebooting repeatedly but it doesn't help.

|||

Hi tjherman,

Did you made any modifications to your connection string before? Check it.

Besides, I also tend to believe that the problem is related to your database engine.Make sure you sql sever service is started(Since you said that you have restared your sql server2000, i would suggest you to also check if the database service is started), you can first connect to your database using Management Studio and see what happened

Hope my suggestion helps

|||

ya Bo Chen is rite u should first try it using Enterprise Manager n see ur DB is working fi9 or

Error After SQL Server 2005 SP1

SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003 Server SP1
When I start the SQL Server service I get:
[298] SQL Server Error: 2812, Could not find stored procedure
'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
Any ideas?
Thanks,
Bryansp1 build is 2047. you must have installed the post sp1 hotfix rollup.
please follow http://support.microsoft.com/Default.aspx?id=918222 to ensure
you have properly install the hotfix in the specified order.
-oj
"BDB" <bdb@.reply.to.group.com> wrote in message
news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...
> SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003 Server
> SP1
>
> When I start the SQL Server service I get:
> [298] SQL Server Error: 2812, Could not find stored procedure
> 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
>
> Any ideas?
> Thanks,
> Bryan
>|||sp1 build is 2047. you must have installed the post sp1 hotfix rollup.
please follow http://support.microsoft.com/Default.aspx?id=918222 to ensure
you have properly install the hotfix in the specified order.
-oj
"BDB" <bdb@.reply.to.group.com> wrote in message
news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...
> SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003 Server
> SP1
>
> When I start the SQL Server service I get:
> [298] SQL Server Error: 2812, Could not find stored procedure
> 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
>
> Any ideas?
> Thanks,
> Bryan
>|||Hi, Thank you for your post.
We were aware and followed KB918222 prior to bringing the build to 2153. It
does not appear to be related.
"oj" <nospam_ojngo@.home.com> wrote in message
news:%233htVgRkGHA.4304@.TK2MSFTNGP03.phx.gbl...[vbcol=seagreen]
> sp1 build is 2047. you must have installed the post sp1 hotfix rollup.
> please follow http://support.microsoft.com/Default.aspx?id=918222 to
> ensure you have properly install the hotfix in the specified order.
> --
> -oj
> "BDB" <bdb@.reply.to.group.com> wrote in message
> news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...|||Take a closer look at msdb..sp_sqlagent_notify stored procedure. The
execution line should be:
EXECUTE @.retval = master.dbo.xp_sqlagent_notify @.op_type, @.job_id,
@.schedule_id, @.alert_id, @.action_type, @.nt_user_name, @.error_flag,
@.@.trancount, @.wmi_namespace, @.wmi_query
-oj
"BDB" <bdb@.reply.to.group.com> wrote in message
news:%23sVMFlVkGHA.5108@.TK2MSFTNGP02.phx.gbl...
> Hi, Thank you for your post.
> We were aware and followed KB918222 prior to bringing the build to 2153.
> It does not appear to be related.
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:%233htVgRkGHA.4304@.TK2MSFTNGP03.phx.gbl...
>|||Hi, Thank you for your post.
We were aware and followed KB918222 prior to bringing the build to 2153. It
does not appear to be related.
"oj" <nospam_ojngo@.home.com> wrote in message
news:%233htVgRkGHA.4304@.TK2MSFTNGP03.phx.gbl...[vbcol=seagreen]
> sp1 build is 2047. you must have installed the post sp1 hotfix rollup.
> please follow http://support.microsoft.com/Default.aspx?id=918222 to
> ensure you have properly install the hotfix in the specified order.
> --
> -oj
> "BDB" <bdb@.reply.to.group.com> wrote in message
> news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...|||Take a closer look at msdb..sp_sqlagent_notify stored procedure. The
execution line should be:
EXECUTE @.retval = master.dbo.xp_sqlagent_notify @.op_type, @.job_id,
@.schedule_id, @.alert_id, @.action_type, @.nt_user_name, @.error_flag,
@.@.trancount, @.wmi_namespace, @.wmi_query
-oj
"BDB" <bdb@.reply.to.group.com> wrote in message
news:%23sVMFlVkGHA.5108@.TK2MSFTNGP02.phx.gbl...
> Hi, Thank you for your post.
> We were aware and followed KB918222 prior to bringing the build to 2153.
> It does not appear to be related.
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:%233htVgRkGHA.4304@.TK2MSFTNGP03.phx.gbl...
>|||Hi, Thanks for following up! On inspection of msdb.dbo.sp_sqlagent_notify
source the calling semantics of master.dbo.xp_sqlagent_notify are the same
as what you specified.
"oj" <nospam_ojngo@.home.com> wrote in message
news:uJB6qmWkGHA.3588@.TK2MSFTNGP02.phx.gbl...[vbcol=seagreen]
> Take a closer look at msdb..sp_sqlagent_notify stored procedure. The
> execution line should be:
> EXECUTE @.retval = master.dbo.xp_sqlagent_notify @.op_type, @.job_id,
> @.schedule_id, @.alert_id, @.action_type, @.nt_user_name, @.error_flag,
> @.@.trancount, @.wmi_namespace, @.wmi_query
> --
> -oj
> "BDB" <bdb@.reply.to.group.com> wrote in message
> news:%23sVMFlVkGHA.5108@.TK2MSFTNGP02.phx.gbl...|||Hi, Thanks for following up! On inspection of msdb.dbo.sp_sqlagent_notify
source the calling semantics of master.dbo.xp_sqlagent_notify are the same
as what you specified.
"oj" <nospam_ojngo@.home.com> wrote in message
news:uJB6qmWkGHA.3588@.TK2MSFTNGP02.phx.gbl...[vbcol=seagreen]
> Take a closer look at msdb..sp_sqlagent_notify stored procedure. The
> execution line should be:
> EXECUTE @.retval = master.dbo.xp_sqlagent_notify @.op_type, @.job_id,
> @.schedule_id, @.alert_id, @.action_type, @.nt_user_name, @.error_flag,
> @.@.trancount, @.wmi_namespace, @.wmi_query
> --
> -oj
> "BDB" <bdb@.reply.to.group.com> wrote in message
> news:%23sVMFlVkGHA.5108@.TK2MSFTNGP02.phx.gbl...|||there must be a process/procedure that calls 'msdb.dbo.xp_sqlagent_notify'.
run this to see if anything returns.
exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from
?.sys.sql_modules where definition like '%msdb.dbo.xp_sqlagent_notify%'"
-oj
"BDB" <bdb@.reply.to.group.com> wrote in message
news:uFvh$UXkGHA.2200@.TK2MSFTNGP05.phx.gbl...
> Hi, Thanks for following up! On inspection of
> msdb.dbo.sp_sqlagent_notify source the calling semantics of
> master.dbo.xp_sqlagent_notify are the same as what you specified.
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:uJB6qmWkGHA.3588@.TK2MSFTNGP02.phx.gbl...
>

Error After SQL Server 2005 SP1

SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003 Server SP1
When I start the SQL Server service I get:
[298] SQL Server Error: 2812, Could not find stored procedure
'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
Any ideas?
Thanks,
Bryansp1 build is 2047. you must have installed the post sp1 hotfix rollup.
please follow http://support.microsoft.com/Default.aspx?id=918222 to ensure
you have properly install the hotfix in the specified order.
--
-oj
"BDB" <bdb@.reply.to.group.com> wrote in message
news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...
> SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003 Server
> SP1
>
> When I start the SQL Server service I get:
> [298] SQL Server Error: 2812, Could not find stored procedure
> 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
>
> Any ideas?
> Thanks,
> Bryan
>|||Hi, Thank you for your post.
We were aware and followed KB918222 prior to bringing the build to 2153. It
does not appear to be related.
"oj" <nospam_ojngo@.home.com> wrote in message
news:%233htVgRkGHA.4304@.TK2MSFTNGP03.phx.gbl...
> sp1 build is 2047. you must have installed the post sp1 hotfix rollup.
> please follow http://support.microsoft.com/Default.aspx?id=918222 to
> ensure you have properly install the hotfix in the specified order.
> --
> -oj
> "BDB" <bdb@.reply.to.group.com> wrote in message
> news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...
>> SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003 Server
>> SP1
>> When I start the SQL Server service I get:
>> [298] SQL Server Error: 2812, Could not find stored procedure
>> 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
>>
>> Any ideas?
>> Thanks,
>> Bryan|||Take a closer look at msdb..sp_sqlagent_notify stored procedure. The
execution line should be:
EXECUTE @.retval = master.dbo.xp_sqlagent_notify @.op_type, @.job_id,
@.schedule_id, @.alert_id, @.action_type, @.nt_user_name, @.error_flag,
@.@.trancount, @.wmi_namespace, @.wmi_query
-oj
"BDB" <bdb@.reply.to.group.com> wrote in message
news:%23sVMFlVkGHA.5108@.TK2MSFTNGP02.phx.gbl...
> Hi, Thank you for your post.
> We were aware and followed KB918222 prior to bringing the build to 2153.
> It does not appear to be related.
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:%233htVgRkGHA.4304@.TK2MSFTNGP03.phx.gbl...
>> sp1 build is 2047. you must have installed the post sp1 hotfix rollup.
>> please follow http://support.microsoft.com/Default.aspx?id=918222 to
>> ensure you have properly install the hotfix in the specified order.
>> --
>> -oj
>> "BDB" <bdb@.reply.to.group.com> wrote in message
>> news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...
>> SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003 Server
>> SP1
>> When I start the SQL Server service I get:
>> [298] SQL Server Error: 2812, Could not find stored procedure
>> 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
>>
>> Any ideas?
>> Thanks,
>> Bryan
>|||Hi, Thanks for following up! On inspection of msdb.dbo.sp_sqlagent_notify
source the calling semantics of master.dbo.xp_sqlagent_notify are the same
as what you specified.
"oj" <nospam_ojngo@.home.com> wrote in message
news:uJB6qmWkGHA.3588@.TK2MSFTNGP02.phx.gbl...
> Take a closer look at msdb..sp_sqlagent_notify stored procedure. The
> execution line should be:
> EXECUTE @.retval = master.dbo.xp_sqlagent_notify @.op_type, @.job_id,
> @.schedule_id, @.alert_id, @.action_type, @.nt_user_name, @.error_flag,
> @.@.trancount, @.wmi_namespace, @.wmi_query
> --
> -oj
> "BDB" <bdb@.reply.to.group.com> wrote in message
> news:%23sVMFlVkGHA.5108@.TK2MSFTNGP02.phx.gbl...
>> Hi, Thank you for your post.
>> We were aware and followed KB918222 prior to bringing the build to 2153.
>> It does not appear to be related.
>> "oj" <nospam_ojngo@.home.com> wrote in message
>> news:%233htVgRkGHA.4304@.TK2MSFTNGP03.phx.gbl...
>> sp1 build is 2047. you must have installed the post sp1 hotfix rollup.
>> please follow http://support.microsoft.com/Default.aspx?id=918222 to
>> ensure you have properly install the hotfix in the specified order.
>> --
>> -oj
>> "BDB" <bdb@.reply.to.group.com> wrote in message
>> news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...
>> SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003 Server
>> SP1
>> When I start the SQL Server service I get:
>> [298] SQL Server Error: 2812, Could not find stored procedure
>> 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
>>
>> Any ideas?
>> Thanks,
>> Bryan|||there must be a process/procedure that calls 'msdb.dbo.xp_sqlagent_notify'.
run this to see if anything returns.
exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from
?.sys.sql_modules where definition like '%msdb.dbo.xp_sqlagent_notify%'"
-oj
"BDB" <bdb@.reply.to.group.com> wrote in message
news:uFvh$UXkGHA.2200@.TK2MSFTNGP05.phx.gbl...
> Hi, Thanks for following up! On inspection of
> msdb.dbo.sp_sqlagent_notify source the calling semantics of
> master.dbo.xp_sqlagent_notify are the same as what you specified.
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:uJB6qmWkGHA.3588@.TK2MSFTNGP02.phx.gbl...
>> Take a closer look at msdb..sp_sqlagent_notify stored procedure. The
>> execution line should be:
>> EXECUTE @.retval = master.dbo.xp_sqlagent_notify @.op_type, @.job_id,
>> @.schedule_id, @.alert_id, @.action_type, @.nt_user_name, @.error_flag,
>> @.@.trancount, @.wmi_namespace, @.wmi_query
>> --
>> -oj
>> "BDB" <bdb@.reply.to.group.com> wrote in message
>> news:%23sVMFlVkGHA.5108@.TK2MSFTNGP02.phx.gbl...
>> Hi, Thank you for your post.
>> We were aware and followed KB918222 prior to bringing the build to 2153.
>> It does not appear to be related.
>> "oj" <nospam_ojngo@.home.com> wrote in message
>> news:%233htVgRkGHA.4304@.TK2MSFTNGP03.phx.gbl...
>> sp1 build is 2047. you must have installed the post sp1 hotfix rollup.
>> please follow http://support.microsoft.com/Default.aspx?id=918222 to
>> ensure you have properly install the hotfix in the specified order.
>> --
>> -oj
>> "BDB" <bdb@.reply.to.group.com> wrote in message
>> news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...
>> SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003
>> Server SP1
>> When I start the SQL Server service I get:
>> [298] SQL Server Error: 2812, Could not find stored procedure
>> 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
>>
>> Any ideas?
>> Thanks,
>> Bryan
>|||Okay, I ran this and I found no references. I think what might be happening
is that xp_sqlagent_notify is called in the wrong database context. So the
intention is that it is called in master but is instead called in msdb.
However, when I search for just xp_sqlagent_notify, it is only called from
msdb..sp_delete_job
and msdb..sp_sqlagent_notify. BTW, clever code!
"oj" <nospam_ojngo@.home.com> wrote in message
news:OiAGECekGHA.4044@.TK2MSFTNGP03.phx.gbl...
> there must be a process/procedure that calls
> 'msdb.dbo.xp_sqlagent_notify'.
> run this to see if anything returns.
> exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n
> from ?.sys.sql_modules where definition like
> '%msdb.dbo.xp_sqlagent_notify%'"
> --
> -oj
> "BDB" <bdb@.reply.to.group.com> wrote in message
> news:uFvh$UXkGHA.2200@.TK2MSFTNGP05.phx.gbl...
>> Hi, Thanks for following up! On inspection of
>> msdb.dbo.sp_sqlagent_notify source the calling semantics of
>> master.dbo.xp_sqlagent_notify are the same as what you specified.
>> "oj" <nospam_ojngo@.home.com> wrote in message
>> news:uJB6qmWkGHA.3588@.TK2MSFTNGP02.phx.gbl...
>> Take a closer look at msdb..sp_sqlagent_notify stored procedure. The
>> execution line should be:
>> EXECUTE @.retval = master.dbo.xp_sqlagent_notify @.op_type, @.job_id,
>> @.schedule_id, @.alert_id, @.action_type, @.nt_user_name, @.error_flag,
>> @.@.trancount, @.wmi_namespace, @.wmi_query
>> --
>> -oj
>> "BDB" <bdb@.reply.to.group.com> wrote in message
>> news:%23sVMFlVkGHA.5108@.TK2MSFTNGP02.phx.gbl...
>> Hi, Thank you for your post.
>> We were aware and followed KB918222 prior to bringing the build to
>> 2153. It does not appear to be related.
>> "oj" <nospam_ojngo@.home.com> wrote in message
>> news:%233htVgRkGHA.4304@.TK2MSFTNGP03.phx.gbl...
>> sp1 build is 2047. you must have installed the post sp1 hotfix rollup.
>> please follow http://support.microsoft.com/Default.aspx?id=918222 to
>> ensure you have properly install the hotfix in the specified order.
>> --
>> -oj
>> "BDB" <bdb@.reply.to.group.com> wrote in message
>> news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...
>> SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003
>> Server SP1
>> When I start the SQL Server service I get:
>> [298] SQL Server Error: 2812, Could not find stored procedure
>> 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
>>
>> Any ideas?
>> Thanks,
>> Bryan
>>
>|||hmm...something must be calling this. there is definitely a bug here (if
it's not user code, then it's probably ms) because it references the wrong
database.
-oj
"BDB" <bdb@.reply.to.group.com> wrote in message
news:uDaA$76kGHA.3304@.TK2MSFTNGP03.phx.gbl...
> Okay, I ran this and I found no references. I think what might be
> happening is that xp_sqlagent_notify is called in the wrong database
> context. So the intention is that it is called in master but is instead
> called in msdb. However, when I search for just xp_sqlagent_notify, it is
> only called from msdb..sp_delete_job
> and msdb..sp_sqlagent_notify. BTW, clever code!
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:OiAGECekGHA.4044@.TK2MSFTNGP03.phx.gbl...
>> there must be a process/procedure that calls
>> 'msdb.dbo.xp_sqlagent_notify'.
>> run this to see if anything returns.
>> exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n
>> from ?.sys.sql_modules where definition like
>> '%msdb.dbo.xp_sqlagent_notify%'"
>> --
>> -oj|||look like it's ms bug.
"Ciprian Gerea [MSFT]" <Ciprian.Gerea@.online.microsoft.com> wrote in message
news:%23kozju%23kGHA.1244@.TK2MSFTNGP05.phx.gbl...
> Hi Adrian,
> The error about the call to xp_sqlagent_notify is a benign startup error,
> and we're looking at fixing it for the next service pack. Without more
> information I can't tell why agent is failing, but I believe that the job
> history error that you're mentioning might give us a clue.
-oj
"oj" <nospam_ojngo@.home.com> wrote in message
news:%23eUC$ODlGHA.4200@.TK2MSFTNGP05.phx.gbl...
> hmm...something must be calling this. there is definitely a bug here (if
> it's not user code, then it's probably ms) because it references the wrong
> database.
>
> --
> -oj
>
> "BDB" <bdb@.reply.to.group.com> wrote in message
> news:uDaA$76kGHA.3304@.TK2MSFTNGP03.phx.gbl...
>> Okay, I ran this and I found no references. I think what might be
>> happening is that xp_sqlagent_notify is called in the wrong database
>> context. So the intention is that it is called in master but is instead
>> called in msdb. However, when I search for just xp_sqlagent_notify, it is
>> only called from msdb..sp_delete_job
>> and msdb..sp_sqlagent_notify. BTW, clever code!
>> "oj" <nospam_ojngo@.home.com> wrote in message
>> news:OiAGECekGHA.4044@.TK2MSFTNGP03.phx.gbl...
>> there must be a process/procedure that calls
>> 'msdb.dbo.xp_sqlagent_notify'.
>> run this to see if anything returns.
>> exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n
>> from ?.sys.sql_modules where definition like
>> '%msdb.dbo.xp_sqlagent_notify%'"
>> --
>> -oj
>|||Thanks so much for your help!
"oj" <nospam_ojngo@.home.com> wrote in message
news:%23as6ORDlGHA.1320@.TK2MSFTNGP04.phx.gbl...
> look like it's ms bug.
> "Ciprian Gerea [MSFT]" <Ciprian.Gerea@.online.microsoft.com> wrote in
> message news:%23kozju%23kGHA.1244@.TK2MSFTNGP05.phx.gbl...
>> Hi Adrian,
>> The error about the call to xp_sqlagent_notify is a benign startup error,
>> and we're looking at fixing it for the next service pack. Without more
>> information I can't tell why agent is failing, but I believe that the job
>> history error that you're mentioning might give us a clue.
>
> --
> -oj
>
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:%23eUC$ODlGHA.4200@.TK2MSFTNGP05.phx.gbl...
>> hmm...something must be calling this. there is definitely a bug here (if
>> it's not user code, then it's probably ms) because it references the
>> wrong database.
>>
>> --
>> -oj
>>
>> "BDB" <bdb@.reply.to.group.com> wrote in message
>> news:uDaA$76kGHA.3304@.TK2MSFTNGP03.phx.gbl...
>> Okay, I ran this and I found no references. I think what might be
>> happening is that xp_sqlagent_notify is called in the wrong database
>> context. So the intention is that it is called in master but is instead
>> called in msdb. However, when I search for just xp_sqlagent_notify, it
>> is only called from msdb..sp_delete_job
>> and msdb..sp_sqlagent_notify. BTW, clever code!
>> "oj" <nospam_ojngo@.home.com> wrote in message
>> news:OiAGECekGHA.4044@.TK2MSFTNGP03.phx.gbl...
>> there must be a process/procedure that calls
>> 'msdb.dbo.xp_sqlagent_notify'.
>> run this to see if anything returns.
>> exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n
>> from ?.sys.sql_modules where definition like
>> '%msdb.dbo.xp_sqlagent_notify%'"
>> --
>> -oj
>>
>