Could not start SQL Agent

Hello.
I have SQL Server MSDE running Windows 2000.
When I start SQL Agent gives me the following error:"Could not start
the SQLAgent$SPSQL service on Local Computer. The service did not
return an error..."
An
Can anyone help me?
Thanks.
ticha
Posted via http://www.webservertalk.com
View this thread: http://www.webservertalk.com/message930459.html
Hi
Look in the Windows Event Log and the Agent log file in the LOGs directory.
You may get more information there.
Regards
Mike
"ticha" wrote:

> Hello.
> I have SQL Server MSDE running Windows 2000.
> When I start SQL Agent gives me the following error:"Could not start
> the SQLAgent$SPSQL service on Local Computer. The service did not
> return an error..."
> An
> Can anyone help me?
> Thanks.
>
> --
> ticha
> Posted via http://www.webservertalk.com
> View this thread: http://www.webservertalk.com/message930459.html
>

Could not load the package "\MSDB\....."

Hi,

I have a intermittent problem with my ssis packages. I have a couple of packages running on a schedule with SQL Server Agent wich sometimes gives me the following errors in agent history:

Message
Executed as user: MyDomain\SQLAgentServiceAccount. Microsoft (R) SQL Server Execute Package Utility Version 9.00.1399.06 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 21:05:00 Could not load package "\MSDB\MyPackageName" because of error 0x80040E37. Description: Table/view either does not exist or contains errors. Source: Microsoft SQL Native Client Started: 21:05:00 Finished: 21:05:00 Elapsed: 0.047 seconds. Process Exit Code 5. The step failed.

When the package does'nt fails it gives me the following message:

Message
Executed as user: MyDomain\SQLAgentServiceAccount. Microsoft (R) SQL Server Execute Package Utility Version 9.00.1399.06 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 21:10:00 DTExec: The package execution returned DTSER_SUCCESS (0). Started: 21:10:00 Finished: 21:10:02 Elapsed: 1.312 seconds. Process Exit Code 0. The step succeeded.

The jobs moves data between the sql server that executes the code and a SQL 2000 database on another server. Does anyone recognize this error?

http://www.eggheadcafe.com/forumarchives/SQLServerdts/Nov2005/post24522953.asp

This is the same error, but not necessarily the same problem. Does your package reference tables that might need to be wrapped with [] or prefixed with the schema?

Could not find stored procedure 'sp_MSins_<table_name>'.

Error message for a Distribution Agent:
"Could not find stored procedure 'sp_MSins_<table_name>'."
Elham,
looks like you have set up things manually. You can still create the stored
procedure scripts and apply them at the subscriber, or alternatively allow
the snapshot to create everything (inc data files) and reinitialize. To
manually create the scripts, use sp_scriptpublicationcustomprocs. There are
details in this article:
http://support.microsoft.com/default...;EN-US;299903.
HTH,
Paul Ibison

Could not find stored procedure 'sp_MSin_<TableName>'

Hi,
Just completed the transactional replication and when tried to test the
changes made in the publisher data it (Distribution Agent) failed with the
following error:
Could not find stored procedure 'sp_MSupd_ACCOUNT'.
(Source: PARISDB2 (Data source); Error number: 2812)
Checked the sysobjects and all these procedures (sp_MSins, sp_MSupd etc) are
present in the database.
Current Configuration is: 1 Publisher, 1 Subscriber, Distributor database is
on the Publisher server, SQLServer 2000 (SP4), Windows 2003)
Please help me out....need to know the reason and the solution
Thanks & Regards
Sangra
Hi Sangra
This problem will happen when the snapshot schema is not applied on the
subscriber.
You can generate the scripts manually using the following procedure
exec sp_scriptinsproc 'articleid'
exec sp_scriptdelproc 'articleid'
exec sp_scriptmappedupdproc 'articleid'
Apply this script on the subscriber.
For getting the articleid check sysarticles table.
P. Srinivasan MCDBA
Consultant
C-13/1,GF,Tulip Garden, Ardee City,
Sector-52,
Gurgaon-122003
India
Mobile:+91-9810321551
"Sangra" <Sangra@.discussions.microsoft.com> wrote in message
news:1A700079-F991-4D00-82A6-756AF23CC16E@.microsoft.com...
> Hi,
> Just completed the transactional replication and when tried to test the
> changes made in the publisher data it (Distribution Agent) failed with the
> following error:
> Could not find stored procedure 'sp_MSupd_ACCOUNT'.
> (Source: PARISDB2 (Data source); Error number: 2812)
> Checked the sysobjects and all these procedures (sp_MSins, sp_MSupd etc)
> are
> present in the database.
> Current Configuration is: 1 Publisher, 1 Subscriber, Distributor database
> is
> on the Publisher server, SQLServer 2000 (SP4), Windows 2003)
> Please help me out....need to know the reason and the solution
> Thanks & Regards
> Sangra

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 execute sp_replcmds on server - need help

I have been getting this message in the past couple of hours. I
rebooted publisher and subscriber. Even if I restart the agent - it
doesn't help. I rebuilt transactional replication from scratch and I
still got this error message. I set for the agent to output to the
file and this is what I get
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:10:53 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:10:53 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
on 'KOCL384017SQL'.'.
The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.
Disconnecting from Publisher 'KOCL384017SQL'
The agent failed with a 'Retry' status. Try to run the agent at a
later time.
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:16:54 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:16:54 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
on 'KOCL384017SQL'.'.
The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.
Disconnecting from Publisher 'KOCL384017SQL'
The agent failed with a 'Retry' status. Try to run the agent at a
later time.
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:22:55 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:22:55 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
>>The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.<<
Try creating a new Profile for your log reader agent with a smaller number
for the -ReadBatchSize parameter, and/or a longer -LoginTimeout value
Could be you have a very large transaction stuck in the t-log of the
published database
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"tolcis" <nytollydba@.gmail.com> wrote in message
news:70357b88-b169-4b21-83b4-ddc5a00b6ad0@.q77g2000hsh.googlegroups.com...
>I have been getting this message in the past couple of hours. I
> rebooted publisher and subscriber. Even if I restart the agent - it
> doesn't help. I rebuilt transactional replication from scratch and I
> still got this error message. I set for the agent to output to the
> file and this is what I get
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:10:53 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:10:53 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
> Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
> on 'KOCL384017SQL'.'.
> The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
> Status: 2, code: 0, text: 'Timeout expired'.
> Disconnecting from Publisher 'KOCL384017SQL'
> The agent failed with a 'Retry' status. Try to run the agent at a
> later time.
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:16:54 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:16:54 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
> Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
> on 'KOCL384017SQL'.'.
> The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
> Status: 2, code: 0, text: 'Timeout expired'.
> Disconnecting from Publisher 'KOCL384017SQL'
> The agent failed with a 'Retry' status. Try to run the agent at a
> later time.
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:22:55 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:22:55 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}

could not execute sp_replcmds on server - need help

I have been getting this message in the past couple of hours. I
rebooted publisher and subscriber. Even if I restart the agent - it
doesn't help. I rebuilt transactional replication from scratch and I
still got this error message. I set for the agent to output to the
file and this is what I get
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:10:53 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:10:53 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
on 'KOCL384017SQL'.'.
The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.
Disconnecting from Publisher 'KOCL384017SQL'
The agent failed with a 'Retry' status. Try to run the agent at a
later time.
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:16:54 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:16:54 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
on 'KOCL384017SQL'.'.
The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.
Disconnecting from Publisher 'KOCL384017SQL'
The agent failed with a 'Retry' status. Try to run the agent at a
later time.
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:22:55 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:22:55 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}>>The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.<<
Try creating a new Profile for your log reader agent with a smaller number
for the -ReadBatchSize parameter, and/or a longer -LoginTimeout value
Could be you have a very large transaction stuck in the t-log of the
published database
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"tolcis" <nytollydba@.gmail.com> wrote in message
news:70357b88-b169-4b21-83b4-ddc5a00b6ad0@.q77g2000hsh.googlegroups.com...
>I have been getting this message in the past couple of hours. I
> rebooted publisher and subscriber. Even if I restart the agent - it
> doesn't help. I rebuilt transactional replication from scratch and I
> still got this error message. I set for the agent to output to the
> file and this is what I get
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:10:53 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:10:53 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
> Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
> on 'KOCL384017SQL'.'.
> The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
> Status: 2, code: 0, text: 'Timeout expired'.
> Disconnecting from Publisher 'KOCL384017SQL'
> The agent failed with a 'Retry' status. Try to run the agent at a
> later time.
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:16:54 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:16:54 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
> Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
> on 'KOCL384017SQL'.'.
> The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
> Status: 2, code: 0, text: 'Timeout expired'.
> Disconnecting from Publisher 'KOCL384017SQL'
> The agent failed with a 'Retry' status. Try to run the agent at a
> later time.
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:22:55 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:22:55 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}

could not execute sp_replcmds on server - need help

I have been getting this message in the past couple of hours. I
rebooted publisher and subscriber. Even if I restart the agent - it
doesn't help. I rebuilt transactional replication from scratch and I
still got this error message. I set for the agent to output to the
file and this is what I get
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:10:53 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:10:53 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
on 'KOCL384017SQL'.'.
The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.
Disconnecting from Publisher 'KOCL384017SQL'
The agent failed with a 'Retry' status. Try to run the agent at a
later time.
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:16:54 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:16:54 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
on 'KOCL384017SQL'.'.
The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.
Disconnecting from Publisher 'KOCL384017SQL'
The agent failed with a 'Retry' status. Try to run the agent at a
later time.
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:22:55 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:22:55 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}>>The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.<<
Try creating a new Profile for your log reader agent with a smaller number
for the -ReadBatchSize parameter, and/or a longer -LoginTimeout value
Could be you have a very large transaction stuck in the t-log of the
published database
--
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"tolcis" <nytollydba@.gmail.com> wrote in message
news:70357b88-b169-4b21-83b4-ddc5a00b6ad0@.q77g2000hsh.googlegroups.com...
>I have been getting this message in the past couple of hours. I
> rebooted publisher and subscriber. Even if I restart the agent - it
> doesn't help. I rebuilt transactional replication from scratch and I
> still got this error message. I set for the agent to output to the
> file and this is what I get
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:10:53 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:10:53 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
> Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
> on 'KOCL384017SQL'.'.
> The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
> Status: 2, code: 0, text: 'Timeout expired'.
> Disconnecting from Publisher 'KOCL384017SQL'
> The agent failed with a 'Retry' status. Try to run the agent at a
> later time.
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:16:54 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:16:54 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
> Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
> on 'KOCL384017SQL'.'.
> The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
> Status: 2, code: 0, text: 'Timeout expired'.
> Disconnecting from Publisher 'KOCL384017SQL'
> The agent failed with a 'Retry' status. Try to run the agent at a
> later time.
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:22:55 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:22:55 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}