Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'

I have started getting this new error after installing SQL 2005 service pack 1 whenever I start the SQL agent :

Log SQL Agent (Current - 6/5/2006 12:28:00 AM)
Message
[298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)

I don;t see any problems because of it but would like to fix it because it is an error and might be affecting something I don't know about.

Thank you.

please post this question to the "SQL Server Tools General" forum, as someone should be able to help you there.

Thanks,

Peter

|||

I had the same issue. Solved it by excluding the system databases (like msdb) from the backups made in the SQL Maintenance plans executed by the SQL Server Agent / Integration Services.

Hope this helps,

Ries Vriend

http://www.amsterdamsoftware.com

|||I am not backing up any of the system databases and still getting this error.|||

I too am getting an error about the xp_sqlagent_notify in the SQLAgent log. Neither am I backing up the master, msdb nor model. Nor am I trying to send an email notification, just writing to the log.

The backup is running and I'm seeing the backup files, but the errors are troubling.

I'm running 32 bit SP1. SQL Server 9.0.2047

|||This error is showing up in our logs too. And we're not backing up MSDB or any system databases on this dev box.|||

I don't know if this has *anything* to do with your situation, but see if Agent extended procedures are enabled ...

select value, value_in_use from sys.configurations where name = 'Agent XPs'

|||yeah it is enabled. Still then Im getting the error.|||

I am also having a problem with this:

2006-10-26 08:52:42 - ! [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'.

The againt will not even start.

Anyone have any luck with this please let me know.

Thanks

Stacey

|||

We have heard a lot of feedback on this issue. Two bugs were filed in Microsoft Connect (http://connect.microsoft.com/SQLServer/). You can see the results here:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=206727
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=142208

This item should be fixed in the next service pack (Service Pack 2). Please let us know if it is not.

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||These links don't seem to go anywhere...is there a work around or fix? Post the answer, no links please :)|||

So, when will SP2 or a hotfix be released? It would be nice to have database mail working.

Thanks.

|||

SQL 2005 Service Pack 2 CTP fixed this on my server.

http://www.microsoft.com/sql/ctp.mspx#E2

|||Is this a show stopper for Database mail not to work? I can send test mail. but if I configure to send a mail when replication fails, it does not work and this seems to be the only error in the log|||

I had a problem like this with SQL Server 2005 and WSS 2.0. The server name has a dash in it, and when SharePoint created its databases, dashes were inserted. When running the following SQL command:

exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from ?.sys.sql_modules where definition like
'%msdb.dbo.xp_sqlagent_notify%'"

the query failed when it reached the database name that contained a dash. After renaming the database and doing all necessary changes to get SharePoint running again, I took the offending db offline and restarted server agent with no error.

Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'

I have started getting this new error after installing SQL 2005 service pack 1 whenever I start the SQL agent :

Log SQL Agent (Current - 6/5/2006 12:28:00 AM)
Message
[298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)

I don;t see any problems because of it but would like to fix it because it is an error and might be affecting something I don't know about.

Thank you.

please post this question to the "SQL Server Tools General" forum, as someone should be able to help you there.

Thanks,

Peter

|||

I had the same issue. Solved it by excluding the system databases (like msdb) from the backups made in the SQL Maintenance plans executed by the SQL Server Agent / Integration Services.

Hope this helps,

Ries Vriend

http://www.amsterdamsoftware.com

|||I am not backing up any of the system databases and still getting this error.|||

I too am getting an error about the xp_sqlagent_notify in the SQLAgent log. Neither am I backing up the master, msdb nor model. Nor am I trying to send an email notification, just writing to the log.

The backup is running and I'm seeing the backup files, but the errors are troubling.

I'm running 32 bit SP1. SQL Server 9.0.2047

|||This error is showing up in our logs too. And we're not backing up MSDB or any system databases on this dev box.|||

I don't know if this has *anything* to do with your situation, but see if Agent extended procedures are enabled ...

select value, value_in_use from sys.configurations where name = 'Agent XPs'

|||yeah it is enabled. Still then Im getting the error.|||

I am also having a problem with this:

2006-10-26 08:52:42 - ! [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'.

The againt will not even start.

Anyone have any luck with this please let me know.

Thanks

Stacey

|||

We have heard a lot of feedback on this issue. Two bugs were filed in Microsoft Connect (http://connect.microsoft.com/SQLServer/). You can see the results here:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=206727
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=142208

This item should be fixed in the next service pack (Service Pack 2). Please let us know if it is not.

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||These links don't seem to go anywhere...is there a work around or fix? Post the answer, no links please :)|||

So, when will SP2 or a hotfix be released? It would be nice to have database mail working.

Thanks.

|||

SQL 2005 Service Pack 2 CTP fixed this on my server.

http://www.microsoft.com/sql/ctp.mspx#E2

|||Is this a show stopper for Database mail not to work? I can send test mail. but if I configure to send a mail when replication fails, it does not work and this seems to be the only error in the log|||

I had a problem like this with SQL Server 2005 and WSS 2.0. The server name has a dash in it, and when SharePoint created its databases, dashes were inserted. When running the following SQL command:

exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from ?.sys.sql_modules where definition like
'%msdb.dbo.xp_sqlagent_notify%'"

the query failed when it reached the database name that contained a dash. After renaming the database and doing all necessary changes to get SharePoint running again, I took the offending db offline and restarted server agent with no error.

Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'

I have started getting this new error after installing SQL 2005 service pack 1 whenever I start the SQL agent :

Log SQL Agent (Current - 6/5/2006 12:28:00 AM)
Message
[298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)

I don;t see any problems because of it but would like to fix it because it is an error and might be affecting something I don't know about.

Thank you.

please post this question to the "SQL Server Tools General" forum, as someone should be able to help you there.

Thanks,

Peter

|||

I had the same issue. Solved it by excluding the system databases (like msdb) from the backups made in the SQL Maintenance plans executed by the SQL Server Agent / Integration Services.

Hope this helps,

Ries Vriend

http://www.amsterdamsoftware.com

|||I am not backing up any of the system databases and still getting this error.|||

I too am getting an error about the xp_sqlagent_notify in the SQLAgent log. Neither am I backing up the master, msdb nor model. Nor am I trying to send an email notification, just writing to the log.

The backup is running and I'm seeing the backup files, but the errors are troubling.

I'm running 32 bit SP1. SQL Server 9.0.2047

|||This error is showing up in our logs too. And we're not backing up MSDB or any system databases on this dev box.|||

I don't know if this has *anything* to do with your situation, but see if Agent extended procedures are enabled ...

select value, value_in_use from sys.configurations where name = 'Agent XPs'

|||yeah it is enabled. Still then Im getting the error.|||

I am also having a problem with this:

2006-10-26 08:52:42 - ! [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'.

The againt will not even start.

Anyone have any luck with this please let me know.

Thanks

Stacey

|||

We have heard a lot of feedback on this issue. Two bugs were filed in Microsoft Connect (http://connect.microsoft.com/SQLServer/). You can see the results here:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=206727
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=142208

This item should be fixed in the next service pack (Service Pack 2). Please let us know if it is not.

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||These links don't seem to go anywhere...is there a work around or fix? Post the answer, no links please :)|||

So, when will SP2 or a hotfix be released? It would be nice to have database mail working.

Thanks.

|||

SQL 2005 Service Pack 2 CTP fixed this on my server.

http://www.microsoft.com/sql/ctp.mspx#E2

|||Is this a show stopper for Database mail not to work? I can send test mail. but if I configure to send a mail when replication fails, it does not work and this seems to be the only error in the log|||

I had a problem like this with SQL Server 2005 and WSS 2.0. The server name has a dash in it, and when SharePoint created its databases, dashes were inserted. When running the following SQL command:

exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from ?.sys.sql_modules where definition like
'%msdb.dbo.xp_sqlagent_notify%'"

the query failed when it reached the database name that contained a dash. After renaming the database and doing all necessary changes to get SharePoint running again, I took the offending db offline and restarted server agent with no error.

Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'

I have started getting this new error after installing SQL 2005 service pack 1 whenever I start the SQL agent :

Log SQL Agent (Current - 6/5/2006 12:28:00 AM)
Message
[298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)

I don;t see any problems because of it but would like to fix it because it is an error and might be affecting something I don't know about.

Thank you.

please post this question to the "SQL Server Tools General" forum, as someone should be able to help you there.

Thanks,

Peter

|||

I had the same issue. Solved it by excluding the system databases (like msdb) from the backups made in the SQL Maintenance plans executed by the SQL Server Agent / Integration Services.

Hope this helps,

Ries Vriend

http://www.amsterdamsoftware.com

|||I am not backing up any of the system databases and still getting this error.|||

I too am getting an error about the xp_sqlagent_notify in the SQLAgent log. Neither am I backing up the master, msdb nor model. Nor am I trying to send an email notification, just writing to the log.

The backup is running and I'm seeing the backup files, but the errors are troubling.

I'm running 32 bit SP1. SQL Server 9.0.2047

|||This error is showing up in our logs too. And we're not backing up MSDB or any system databases on this dev box.|||

I don't know if this has *anything* to do with your situation, but see if Agent extended procedures are enabled ...

select value, value_in_use from sys.configurations where name = 'Agent XPs'

|||yeah it is enabled. Still then Im getting the error.|||

I am also having a problem with this:

2006-10-26 08:52:42 - ! [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'.

The againt will not even start.

Anyone have any luck with this please let me know.

Thanks

Stacey

|||

We have heard a lot of feedback on this issue. Two bugs were filed in Microsoft Connect (http://connect.microsoft.com/SQLServer/). You can see the results here:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=206727
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=142208

This item should be fixed in the next service pack (Service Pack 2). Please let us know if it is not.

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||These links don't seem to go anywhere...is there a work around or fix? Post the answer, no links please :)|||

So, when will SP2 or a hotfix be released? It would be nice to have database mail working.

Thanks.

|||

SQL 2005 Service Pack 2 CTP fixed this on my server.

http://www.microsoft.com/sql/ctp.mspx#E2

|||Is this a show stopper for Database mail not to work? I can send test mail. but if I configure to send a mail when replication fails, it does not work and this seems to be the only error in the log|||

I had a problem like this with SQL Server 2005 and WSS 2.0. The server name has a dash in it, and when SharePoint created its databases, dashes were inserted. When running the following SQL command:

exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from ?.sys.sql_modules where definition like
'%msdb.dbo.xp_sqlagent_notify%'"

the query failed when it reached the database name that contained a dash. After renaming the database and doing all necessary changes to get SharePoint running again, I took the offending db offline and restarted server agent with no error.

Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'

I have started getting this new error after installing SQL 2005 service pack 1 whenever I start the SQL agent :

Log SQL Agent (Current - 6/5/2006 12:28:00 AM)
Message
[298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)

I don;t see any problems because of it but would like to fix it because it is an error and might be affecting something I don't know about.

Thank you.

please post this question to the "SQL Server Tools General" forum, as someone should be able to help you there.

Thanks,

Peter

|||

I had the same issue. Solved it by excluding the system databases (like msdb) from the backups made in the SQL Maintenance plans executed by the SQL Server Agent / Integration Services.

Hope this helps,

Ries Vriend

http://www.amsterdamsoftware.com

|||I am not backing up any of the system databases and still getting this error.
|||

I too am getting an error about the xp_sqlagent_notify in the SQLAgent log. Neither am I backing up the master, msdb nor model. Nor am I trying to send an email notification, just writing to the log.

The backup is running and I'm seeing the backup files, but the errors are troubling.

I'm running 32 bit SP1. SQL Server 9.0.2047

|||This error is showing up in our logs too. And we're not backing up MSDB or any system databases on this dev box.|||

I don't know if this has *anything* to do with your situation, but see if Agent extended procedures are enabled ...

select value, value_in_use from sys.configurations where name = 'Agent XPs'

|||yeah it is enabled. Still then Im getting the error.|||

I am also having a problem with this:

2006-10-26 08:52:42 - ! [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'.

The againt will not even start.

Anyone have any luck with this please let me know.

Thanks

Stacey

|||

We have heard a lot of feedback on this issue. Two bugs were filed in Microsoft Connect (http://connect.microsoft.com/SQLServer/). You can see the results here:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=206727
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=142208

This item should be fixed in the next service pack (Service Pack 2). Please let us know if it is not.

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||These links don't seem to go anywhere...is there a work around or fix? Post the answer, no links please :)|||

So, when will SP2 or a hotfix be released? It would be nice to have database mail working.

Thanks.

|||

SQL 2005 Service Pack 2 CTP fixed this on my server.

http://www.microsoft.com/sql/ctp.mspx#E2

|||Is this a show stopper for Database mail not to work? I can send test mail. but if I configure to send a mail when replication fails, it does not work and this seems to be the only error in the log|||

I had a problem like this with SQL Server 2005 and WSS 2.0. The server name has a dash in it, and when SharePoint created its databases, dashes were inserted. When running the following SQL command:

exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from ?.sys.sql_modules where definition like
'%msdb.dbo.xp_sqlagent_notify%'"

the query failed when it reached the database name that contained a dash. After renaming the database and doing all necessary changes to get SharePoint running again, I took the offending db offline and restarted server agent with no error.

Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'

I have started getting this new error after installing SQL 2005 service pack 1 whenever I start the SQL agent :

Log SQL Agent (Current - 6/5/2006 12:28:00 AM)
Message
[298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)

I don;t see any problems because of it but would like to fix it because it is an error and might be affecting something I don't know about.

Thank you.

please post this question to the "SQL Server Tools General" forum, as someone should be able to help you there.

Thanks,

Peter

|||

I had the same issue. Solved it by excluding the system databases (like msdb) from the backups made in the SQL Maintenance plans executed by the SQL Server Agent / Integration Services.

Hope this helps,

Ries Vriend

http://www.amsterdamsoftware.com

|||I am not backing up any of the system databases and still getting this error.
|||

I too am getting an error about the xp_sqlagent_notify in the SQLAgent log. Neither am I backing up the master, msdb nor model. Nor am I trying to send an email notification, just writing to the log.

The backup is running and I'm seeing the backup files, but the errors are troubling.

I'm running 32 bit SP1. SQL Server 9.0.2047

|||This error is showing up in our logs too. And we're not backing up MSDB or any system databases on this dev box.|||

I don't know if this has *anything* to do with your situation, but see if Agent extended procedures are enabled ...

select value, value_in_use from sys.configurations where name = 'Agent XPs'

|||yeah it is enabled. Still then Im getting the error.|||

I am also having a problem with this:

2006-10-26 08:52:42 - ! [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'.

The againt will not even start.

Anyone have any luck with this please let me know.

Thanks

Stacey

|||

We have heard a lot of feedback on this issue. Two bugs were filed in Microsoft Connect (http://connect.microsoft.com/SQLServer/). You can see the results here:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=206727
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=142208

This item should be fixed in the next service pack (Service Pack 2). Please let us know if it is not.

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||These links don't seem to go anywhere...is there a work around or fix? Post the answer, no links please :)|||

So, when will SP2 or a hotfix be released? It would be nice to have database mail working.

Thanks.

|||

SQL 2005 Service Pack 2 CTP fixed this on my server.

http://www.microsoft.com/sql/ctp.mspx#E2

|||Is this a show stopper for Database mail not to work? I can send test mail. but if I configure to send a mail when replication fails, it does not work and this seems to be the only error in the log|||

I had a problem like this with SQL Server 2005 and WSS 2.0. The server name has a dash in it, and when SharePoint created its databases, dashes were inserted. When running the following SQL command:

exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from ?.sys.sql_modules where definition like
'%msdb.dbo.xp_sqlagent_notify%'"

the query failed when it reached the database name that contained a dash. After renaming the database and doing all necessary changes to get SharePoint running again, I took the offending db offline and restarted server agent with no error.

Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'

I have started getting this new error after installing SQL 2005 service pack 1 whenever I start the SQL agent :

Log SQL Agent (Current - 6/5/2006 12:28:00 AM)
Message
[298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)

I don;t see any problems because of it but would like to fix it because it is an error and might be affecting something I don't know about.

Thank you.

please post this question to the "SQL Server Tools General" forum, as someone should be able to help you there.

Thanks,

Peter

|||

I had the same issue. Solved it by excluding the system databases (like msdb) from the backups made in the SQL Maintenance plans executed by the SQL Server Agent / Integration Services.

Hope this helps,

Ries Vriend

http://www.amsterdamsoftware.com

|||I am not backing up any of the system databases and still getting this error.|||

I too am getting an error about the xp_sqlagent_notify in the SQLAgent log. Neither am I backing up the master, msdb nor model. Nor am I trying to send an email notification, just writing to the log.

The backup is running and I'm seeing the backup files, but the errors are troubling.

I'm running 32 bit SP1. SQL Server 9.0.2047

|||This error is showing up in our logs too. And we're not backing up MSDB or any system databases on this dev box.|||

I don't know if this has *anything* to do with your situation, but see if Agent extended procedures are enabled ...

select value, value_in_use from sys.configurations where name = 'Agent XPs'

|||yeah it is enabled. Still then Im getting the error.|||

I am also having a problem with this:

2006-10-26 08:52:42 - ! [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'.

The againt will not even start.

Anyone have any luck with this please let me know.

Thanks

Stacey

|||

We have heard a lot of feedback on this issue. Two bugs were filed in Microsoft Connect (http://connect.microsoft.com/SQLServer/). You can see the results here:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=206727
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=142208

This item should be fixed in the next service pack (Service Pack 2). Please let us know if it is not.

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||These links don't seem to go anywhere...is there a work around or fix? Post the answer, no links please :)|||

So, when will SP2 or a hotfix be released? It would be nice to have database mail working.

Thanks.

|||

SQL 2005 Service Pack 2 CTP fixed this on my server.

http://www.microsoft.com/sql/ctp.mspx#E2

|||Is this a show stopper for Database mail not to work? I can send test mail. but if I configure to send a mail when replication fails, it does not work and this seems to be the only error in the log|||

I had a problem like this with SQL Server 2005 and WSS 2.0. The server name has a dash in it, and when SharePoint created its databases, dashes were inserted. When running the following SQL command:

exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from ?.sys.sql_modules where definition like
'%msdb.dbo.xp_sqlagent_notify%'"

the query failed when it reached the database name that contained a dash. After renaming the database and doing all necessary changes to get SharePoint running again, I took the offending db offline and restarted server agent with no error.

Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'

I have started getting this new error after installing SQL 2005 service pack 1 whenever I start the SQL agent :

Log SQL Agent (Current - 6/5/2006 12:28:00 AM)
Message
[298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)

I don;t see any problems because of it but would like to fix it because it is an error and might be affecting something I don't know about.

Thank you.

please post this question to the "SQL Server Tools General" forum, as someone should be able to help you there.

Thanks,

Peter

|||

I had the same issue. Solved it by excluding the system databases (like msdb) from the backups made in the SQL Maintenance plans executed by the SQL Server Agent / Integration Services.

Hope this helps,

Ries Vriend

http://www.amsterdamsoftware.com

|||I am not backing up any of the system databases and still getting this error.|||

I too am getting an error about the xp_sqlagent_notify in the SQLAgent log. Neither am I backing up the master, msdb nor model. Nor am I trying to send an email notification, just writing to the log.

The backup is running and I'm seeing the backup files, but the errors are troubling.

I'm running 32 bit SP1. SQL Server 9.0.2047

|||This error is showing up in our logs too. And we're not backing up MSDB or any system databases on this dev box.|||

I don't know if this has *anything* to do with your situation, but see if Agent extended procedures are enabled ...

select value, value_in_use from sys.configurations where name = 'Agent XPs'

|||yeah it is enabled. Still then Im getting the error.|||

I am also having a problem with this:

2006-10-26 08:52:42 - ! [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'.

The againt will not even start.

Anyone have any luck with this please let me know.

Thanks

Stacey

|||

We have heard a lot of feedback on this issue. Two bugs were filed in Microsoft Connect (http://connect.microsoft.com/SQLServer/). You can see the results here:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=206727
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=142208

This item should be fixed in the next service pack (Service Pack 2). Please let us know if it is not.

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||These links don't seem to go anywhere...is there a work around or fix? Post the answer, no links please :)|||

So, when will SP2 or a hotfix be released? It would be nice to have database mail working.

Thanks.

|||

SQL 2005 Service Pack 2 CTP fixed this on my server.

http://www.microsoft.com/sql/ctp.mspx#E2

|||Is this a show stopper for Database mail not to work? I can send test mail. but if I configure to send a mail when replication fails, it does not work and this seems to be the only error in the log|||

I had a problem like this with SQL Server 2005 and WSS 2.0. The server name has a dash in it, and when SharePoint created its databases, dashes were inserted. When running the following SQL command:

exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from ?.sys.sql_modules where definition like
'%msdb.dbo.xp_sqlagent_notify%'"

the query failed when it reached the database name that contained a dash. After renaming the database and doing all necessary changes to get SharePoint running again, I took the offending db offline and restarted server agent with no error.

Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'

I have started getting this new error after installing SQL 2005 service pack 1 whenever I start the SQL agent :

Log SQL Agent (Current - 6/5/2006 12:28:00 AM)
Message
[298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)

I don;t see any problems because of it but would like to fix it because it is an error and might be affecting something I don't know about.

Thank you.

please post this question to the "SQL Server Tools General" forum, as someone should be able to help you there.

Thanks,

Peter

|||

I had the same issue. Solved it by excluding the system databases (like msdb) from the backups made in the SQL Maintenance plans executed by the SQL Server Agent / Integration Services.

Hope this helps,

Ries Vriend

http://www.amsterdamsoftware.com

|||I am not backing up any of the system databases and still getting this error.|||

I too am getting an error about the xp_sqlagent_notify in the SQLAgent log. Neither am I backing up the master, msdb nor model. Nor am I trying to send an email notification, just writing to the log.

The backup is running and I'm seeing the backup files, but the errors are troubling.

I'm running 32 bit SP1. SQL Server 9.0.2047

|||This error is showing up in our logs too. And we're not backing up MSDB or any system databases on this dev box.|||

I don't know if this has *anything* to do with your situation, but see if Agent extended procedures are enabled ...

select value, value_in_use from sys.configurations where name = 'Agent XPs'

|||yeah it is enabled. Still then Im getting the error.|||

I am also having a problem with this:

2006-10-26 08:52:42 - ! [298] SQLServer Error: 2812, Could not find stored procedure 'msdb.dbo.xp_sqlagent_notify'.

The againt will not even start.

Anyone have any luck with this please let me know.

Thanks

Stacey

|||

We have heard a lot of feedback on this issue. Two bugs were filed in Microsoft Connect (http://connect.microsoft.com/SQLServer/). You can see the results here:

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=206727
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=142208

This item should be fixed in the next service pack (Service Pack 2). Please let us know if it is not.

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||These links don't seem to go anywhere...is there a work around or fix? Post the answer, no links please :)|||

So, when will SP2 or a hotfix be released? It would be nice to have database mail working.

Thanks.

|||

SQL 2005 Service Pack 2 CTP fixed this on my server.

http://www.microsoft.com/sql/ctp.mspx#E2

|||Is this a show stopper for Database mail not to work? I can send test mail. but if I configure to send a mail when replication fails, it does not work and this seems to be the only error in the log|||

I had a problem like this with SQL Server 2005 and WSS 2.0. The server name has a dash in it, and when SharePoint created its databases, dashes were inserted. When running the following SQL command:

exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from ?.sys.sql_modules where definition like
'%msdb.dbo.xp_sqlagent_notify%'"

the query failed when it reached the database name that contained a dash. After renaming the database and doing all necessary changes to get SharePoint running again, I took the offending db offline and restarted server agent with no error.

Could not find stored procedure GetActivePoll?

can anyone please help me with my poll application? whenever i run it, i will comes out with this error "Could not find stored procedure 'GetActivePoll'". i've got stored procedure in my database with the name GetActivePoll', how come it cannot find the stored procedured? below are some images and codes i've attached with.

1<%@. Page Language="VB" MasterPageFile="~/MasterPage.master" AutoEventWireup="false" CodeFile="poll.aspx.vb"Inherits="Polls_poll" title="Fanzine if Liverpool FC" %>2<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server">3<div style="text-align: left">4 <span style="font-size: 30px; color: #3333ff; font-family: Verdana"><strong><span5 style="color: #000000">Please take a vote...</span><br />6 </strong></span>7 </div>8 <div style="text-align: left">9 <br />10 <table width="100%" align="center">11 <tr>12 <td style="width: 100px; border-top: thin solid; height: 20px;">13 <asp:Label ID="lblPollQuestion" runat="server" Font-Bold="True" Font-Names="Verdana"14 Font-Size="10pt" Text="Poll Question" Width="500px"></asp:Label></td>15 </tr>16 <tr>17 <td style="width: 100px">18 <asp:RadioButtonList ID="rdoPollOptionList" runat="server" Font-Names="Verdana" Font-Size="9pt" Width="500px" DataSourceID="SqlDataSource1" DataTextField="PK_PollId" DataValueField="PK_PollId">19 </asp:RadioButtonList><asp:SqlDataSource ID="SqlDataSource1" runat="server" ConnectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\Poll.mdf;Integrated Security=True;User Instance=True"20 ProviderName="System.Data.SqlClient" SelectCommand="SELECT * FROM [Polls]"></asp:SqlDataSource>21 </td>22 </tr>23 <tr>24 <td style="width: 100px; text-align: left">25 <asp:Button ID="btnVote" runat="server" Text="Vote" Width="71px" BackColor="Silver" BorderColor="Silver" BorderStyle="Solid" Font-Bold="True" ForeColor="White" /><br />26 <br />27 <asp:Label ID="lblError" runat="server" Font-Names="Verdana" Font-Size="Smaller"28 ForeColor="Red" Text="You cannot vote more than once..." Visible="False" Width="500px"></asp:Label></td>29 </tr>30 </table>31 </div>32</asp:Content>33

1Imports System.Data2Imports System.Data.SqlClient3PartialClass Polls_poll4Inherits System.Web.UI.Page5Protected Sub Page_Load(ByVal senderAs Object,ByVal eAs System.EventArgs)Handles Me.Load6If Not IsPostBackThen7 DisplayPoll()8End If9 End Sub10 Private Sub DisplayPoll()11Try12 Dim dsAs DataSet = getActivePoll()1314 lblPollQuestion.Text = ds.Tables(0).Rows(0)("Question")1516Dim iAs Integer = 017For Each drAs DataRowIn ds.Tables(1).Rows18 rdoPollOptionList.Items.Add(dr("Answer"))19 rdoPollOptionList.Items(i).Value = dr("PK_OptionId")20 rdoPollOptionList.SelectedIndex = 02122 i = i + 123Next24 Catch exAs Exception25Throw ex26End Try27 End Sub28 Private Function getActivePoll()As DataSet29Dim strConnStringAs String = System.Configuration.ConfigurationManager.ConnectionStrings.Item("ConnectionString").ToString()30Dim sqlConnAs New SqlConnection(strConnString)3132 sqlConn.Open()33Dim sqlCmdAs New SqlCommand()3435 sqlCmd.CommandText ="GetActivePoll"36 sqlCmd.CommandType = Data.CommandType.StoredProcedure37 sqlCmd.Connection = sqlConn3839Dim dsAs New DataSet40Dim daAs New SqlDataAdapter(sqlCmd)4142 da.Fill(ds)4344 sqlConn.Close()4546Return ds47End Function48 Protected Sub btnVote_Click(ByVal senderAs Object,ByVal eAs System.EventArgs)Handles btnVote.Click49If Response.Cookies("Voted")Is Nothing Then50 Response.Cookies("Voted").Value ="Voted"51 Response.Cookies("Voted").Expires = DateTime.Now.AddDays(1)5253 lblError.Visible =False5455 RecordVote()56Else57 lblError.Visible =True58 End If59 End Sub60 Private Sub RecordVote()61Dim strConnStringAs String = System.Configuration.ConfigurationManager.ConnectionStrings.Item("ConnectionString").ToString()62Dim sqlConnAs New SqlConnection(strConnString)6364 sqlConn.Open()65Dim sqlCmdAs New SqlCommand()6667 sqlCmd.CommandText ="IncrementVote"68 sqlCmd.CommandType = Data.CommandType.StoredProcedure69 sqlCmd.Connection = sqlConn7071Dim sqlParamQuestionAs New SqlParameter("@.i_OptionId", Data.SqlDbType.Int)7273 sqlParamQuestion.Value = rdoPollOptionList.SelectedValue7475 sqlCmd.Parameters.Add(sqlParamQuestion)7677 sqlCmd.ExecuteNonQuery()7879 sqlConn.Close()80End Sub81End Class

If you change line 35 to

 sqlCmd.CommandText ="[GetActivePoll]"

does it work?

|||

Are you looking in the right DB? Its a good idea to drop and recreate the proc and qualify with the owner as

CREATE PROCdbo.GetAcviePoll

Lot of times when developoers create the objects, if they are not created with the qualifier they are created under the developers credentials.