Prcess could not execute 'sp_MSadd_repl_commands27hp'

Hello all,
Our log reader agent is failing at times with the error "The process could
not execute 'sp_MSadd_repl_commands27hp' on 'DistributorServerName'...
We have custom distribution agents that have -CommitBatchSize = 500 and
-CommitBatchThreshold = 1000...
I'm also noticing that our distribution agent cleanup agent progressively
takes longer through our peak. From 10 minutes to close to an hour...
So I'm thinking we are having contention between the distribution db cleanup
and maybe our -CommitBatchSize...
Any recommendations?
Thanks!
Stop the distribution agent and run the log reader agent again. You may need
to enable logging and post the results back here if the condition does not
clear.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"BATMAN" <BATMAN@.discussions.microsoft.com> wrote in message
news:8A5EB566-D904-4335-ABF8-9BA387671F73@.microsoft.com...
> Hello all,
> Our log reader agent is failing at times with the error "The process could
> not execute 'sp_MSadd_repl_commands27hp' on 'DistributorServerName'...
> We have custom distribution agents that have -CommitBatchSize = 500 and
> -CommitBatchThreshold = 1000...
> I'm also noticing that our distribution agent cleanup agent progressively
> takes longer through our peak. From 10 minutes to close to an hour...
> So I'm thinking we are having contention between the distribution db
> cleanup
> and maybe our -CommitBatchSize...
> Any recommendations?
> Thanks!
|||OK... Here is what is in the log... It goes from working fine to throwing
errors to working fine again:
...
Status: 16384, code: 20007, text: 'No replicated transactions are available.'.
Status: 2, code: 1003, text: 'The process could not execute
'sp_MSadd_repl_commands27hp' on 'DistServerName'.'.
The process could not execute 'sp_MSadd_repl_commands27hp' on
'DistServerName'.
Status: 2, code: 1003, text: 'Timeout expired'.
Status: 0, code: 22020, text: 'Batches were not committed to the
Distributor.'.
The agent failed with a 'Retry' status. Try to run the agent at a later time.
Status: 4096, code: 20024, text: 'Initializing'.
Status: 4, code: 20051, text: 'Delivering replicated transactions'.
Status: 2, code: 1003, text: 'The process could not execute
'sp_MSadd_repl_commands27hp' on 'DistServerName'.'.
The process could not execute 'sp_MSadd_repl_commands27hp' on
'DistServerName'.
Status: 2, code: 1003, text: 'Timeout expired'.
Status: 0, code: 2000, text: 'IDistPut Interface has been shut down.'.
The agent failed with a 'Retry' status. Try to run the agent at a later time.
Status: 4096, code: 20024, text: 'Initializing'.
Status: 4, code: 20051, text: 'Delivering replicated transactions'.
...
Thanks!
Michael
"Hilary Cotter" wrote:

> Stop the distribution agent and run the log reader agent again. You may need
> to enable logging and post the results back here if the condition does not
> clear.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "BATMAN" <BATMAN@.discussions.microsoft.com> wrote in message
> news:8A5EB566-D904-4335-ABF8-9BA387671F73@.microsoft.com...
>
>
|||At the time the below error occured, the "Distribution clean up:
distribution" job was running:
...
Status: 2, code: 1003, text: 'The process could not execute
'sp_MSadd_repl_commands27hp' on 'ANETREPUBVSQL1F'.'.
The process could not execute 'sp_MSadd_repl_commands27hp' on
'DistServerName'.
Status: 2, code: 1003, text: 'Timeout expired'.
Status: 0, code: 22020, text: 'Batches were not committed to the
Distributor.'.
The agent failed with a 'Retry' status. Try to run the agent at a later time.
...
As I noticed before, our distribution cleanup takes 30-50 minutes to
complete during peak traffic.
Thanks,
Michael
"Hilary Cotter" wrote:

> Stop the distribution agent and run the log reader agent again. You may need
> to enable logging and post the results back here if the condition does not
> clear.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "BATMAN" <BATMAN@.discussions.microsoft.com> wrote in message
> news:8A5EB566-D904-4335-ABF8-9BA387671F73@.microsoft.com...
>
>
|||Stop the distribution clean up task until your log reader has processed all
of your commands in the log. Set readbatchsize to 500 and the querytimeout
and log timeout to something large - I would try 300. These settings are for
your log reader agent.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"BATMAN" <BATMAN@.discussions.microsoft.com> wrote in message
news:F303B3EA-3B82-4F6B-AF9B-23386530C0F9@.microsoft.com...[vbcol=seagreen]
> At the time the below error occured, the "Distribution clean up:
> distribution" job was running:
> ----
> ...
> Status: 2, code: 1003, text: 'The process could not execute
> 'sp_MSadd_repl_commands27hp' on 'ANETREPUBVSQL1F'.'.
> The process could not execute 'sp_MSadd_repl_commands27hp' on
> 'DistServerName'.
> Status: 2, code: 1003, text: 'Timeout expired'.
> Status: 0, code: 22020, text: 'Batches were not committed to the
> Distributor.'.
> The agent failed with a 'Retry' status. Try to run the agent at a later
> time.
> ...
> ----
> As I noticed before, our distribution cleanup takes 30-50 minutes to
> complete during peak traffic.
> Thanks,
> Michael
>
>
> "Hilary Cotter" wrote:
|||The default Log Reader agent profile has a -ReadBatchSize of 500 and a
-QueryTimeout of 300 already...
So when you say "log timeout to something large - I would try 300", are you
meaning the QueryTimeout? Again, FYI... This is SQL 2000.
Anyway, I upped the QueryTimeout to 600 and I'm still getting the timeout...
Thanks,
Michael
"Hilary Cotter" wrote:

> Stop the distribution clean up task until your log reader has processed all
> of your commands in the log. Set readbatchsize to 500 and the querytimeout
> and log timeout to something large - I would try 300. These settings are for
> your log reader agent.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "BATMAN" <BATMAN@.discussions.microsoft.com> wrote in message
> news:F303B3EA-3B82-4F6B-AF9B-23386530C0F9@.microsoft.com...
>
>
|||OK... I upped the QueryTimout to 1800 and I got the error "The agent is
suspect. No response within last 10 minutes."...
Thanks,
Michael
"BATMAN" wrote:
[vbcol=seagreen]
> The default Log Reader agent profile has a -ReadBatchSize of 500 and a
> -QueryTimeout of 300 already...
> So when you say "log timeout to something large - I would try 300", are you
> meaning the QueryTimeout? Again, FYI... This is SQL 2000.
> Anyway, I upped the QueryTimeout to 600 and I'm still getting the timeout...
> Thanks,
> Michael
>
> "Hilary Cotter" wrote:

Possible To Start Agent Job from ASP or asp.net

I have a long running process that i would like to have started via a web
application. I suppose I have a few options and im not sure if #1 is
possible.
#1 - Start A Job via ASP or ASP.NET
#2 - Set a Flag that a job checks when it runs on a repeating schedule so
it will take action instead of just repeating again next time the schedule
hits.
#3 - Make sure all is ready for the job which occurs at a known time (a bad
idea)
Anyone know if #1 has a solution?You can start a sql job by calling this stored procedure.
e.g.
exec msdb..sp_start_job 'your_job'
-oj
"Erik Jensen" <ErikJensen@.discussions.microsoft.com> wrote in message
news:D1D61D84-36C5-40C9-8990-B4D8D11D2677@.microsoft.com...
>I have a long running process that i would like to have started via a web
> application. I suppose I have a few options and im not sure if #1 is
> possible.
> #1 - Start A Job via ASP or ASP.NET
> #2 - Set a Flag that a job checks when it runs on a repeating schedule so
> it will take action instead of just repeating again next time the schedule
> hits.
> #3 - Make sure all is ready for the job which occurs at a known time (a
> bad
> idea)
> Anyone know if #1 has a solution?
>

Possible to alert on SQL Server Agent Error Log?

We have one SQL server where the mail may disconnect from time to time with
the SQL Server Agent.
Is it possible to flag an alert to notify when the SQL Server Agent produces
an error in the SQL Server Agent Error Log?Hi
"ssciarrino" wrote:

> We have one SQL server where the mail may disconnect from time to time wit
h
> the SQL Server Agent.
> Is it possible to flag an alert to notify when the SQL Server Agent produc
es
> an error in the SQL Server Agent Error Log?
You don't give your SQL Server version number or whether SQL Agent is still
running and it is just mail that is not getting though? What message is put
in the log?
Have you looked at creating an ALERT for this if you can trap the error
level or number? You would have to use a method other than emails to send th
e
information! You could look at using MOM to check the log files for this.
A common cause of email stopping is issues connecting to the email server.
If you have network issues you may want to sort them out. SMTP email tends t
o
be less prone to this to use this with SQL 2000 you can use xp_smtp
http://www.sqldev.net/xp/xpsmtp.htm and include extra steps in the jobs to
send the sucess/failure emails. SQL 2005 has SMTP inbuilt with database mail
.
John|||Hi John
Thanks for the insight I will look into this...at the moment we are SQl
2000 but as you mention SQL 2005 doesn't have this problem. We are currentl
y
migrating to SQL 2005, may not have to visit this after upgrade.
I was looking for any type of log message that was error (red) but it
appears I have to narrow down via alert via error number/message
"John Bell" wrote:

> Hi
> "ssciarrino" wrote:
>
> You don't give your SQL Server version number or whether SQL Agent is stil
l
> running and it is just mail that is not getting though? What message is pu
t
> in the log?
> Have you looked at creating an ALERT for this if you can trap the error
> level or number? You would have to use a method other than emails to send
the
> information! You could look at using MOM to check the log files for this.
> A common cause of email stopping is issues connecting to the email server.
> If you have network issues you may want to sort them out. SMTP email tends
to
> be less prone to this to use this with SQL 2000 you can use xp_smtp
> http://www.sqldev.net/xp/xpsmtp.htm and include extra steps in the jobs to
> send the sucess/failure emails. SQL 2005 has SMTP inbuilt with database ma
il.
> John

Possible to alert on SQL Server Agent Error Log?

Hi
"ssciarrino" wrote:

> We have one SQL server where the mail may disconnect from time to time with
> the SQL Server Agent.
> Is it possible to flag an alert to notify when the SQL Server Agent produces
> an error in the SQL Server Agent Error Log?
You don't give your SQL Server version number or whether SQL Agent is still
running and it is just mail that is not getting though? What message is put
in the log?
Have you looked at creating an ALERT for this if you can trap the error
level or number? You would have to use a method other than emails to send the
information! You could look at using MOM to check the log files for this.
A common cause of email stopping is issues connecting to the email server.
If you have network issues you may want to sort them out. SMTP email tends to
be less prone to this to use this with SQL 2000 you can use xp_smtp
http://www.sqldev.net/xp/xpsmtp.htm and include extra steps in the jobs to
send the sucess/failure emails. SQL 2005 has SMTP inbuilt with database mail.
John
Hi John
Thanks for the insight I will look into this...at the moment we are SQl
2000 but as you mention SQL 2005 doesn't have this problem. We are currently
migrating to SQL 2005, may not have to visit this after upgrade.
I was looking for any type of log message that was error (red) but it
appears I have to narrow down via alert via error number/message
"John Bell" wrote:

> Hi
> "ssciarrino" wrote:
>
> You don't give your SQL Server version number or whether SQL Agent is still
> running and it is just mail that is not getting though? What message is put
> in the log?
> Have you looked at creating an ALERT for this if you can trap the error
> level or number? You would have to use a method other than emails to send the
> information! You could look at using MOM to check the log files for this.
> A common cause of email stopping is issues connecting to the email server.
> If you have network issues you may want to sort them out. SMTP email tends to
> be less prone to this to use this with SQL 2000 you can use xp_smtp
> http://www.sqldev.net/xp/xpsmtp.htm and include extra steps in the jobs to
> send the sucess/failure emails. SQL 2005 has SMTP inbuilt with database mail.
> John

Possible to alert on SQL Server Agent Error Log?

We have one SQL server where the mail may disconnect from time to time with
the SQL Server Agent.
Is it possible to flag an alert to notify when the SQL Server Agent produces
an error in the SQL Server Agent Error Log?Hi
"ssciarrino" wrote:
> We have one SQL server where the mail may disconnect from time to time with
> the SQL Server Agent.
> Is it possible to flag an alert to notify when the SQL Server Agent produces
> an error in the SQL Server Agent Error Log?
You don't give your SQL Server version number or whether SQL Agent is still
running and it is just mail that is not getting though? What message is put
in the log?
Have you looked at creating an ALERT for this if you can trap the error
level or number? You would have to use a method other than emails to send the
information! You could look at using MOM to check the log files for this.
A common cause of email stopping is issues connecting to the email server.
If you have network issues you may want to sort them out. SMTP email tends to
be less prone to this to use this with SQL 2000 you can use xp_smtp
http://www.sqldev.net/xp/xpsmtp.htm and include extra steps in the jobs to
send the sucess/failure emails. SQL 2005 has SMTP inbuilt with database mail.
John|||Hi John
Thanks for the insight I will look into this...at the moment we are SQl
2000 but as you mention SQL 2005 doesn't have this problem. We are currently
migrating to SQL 2005, may not have to visit this after upgrade.
I was looking for any type of log message that was error (red) but it
appears I have to narrow down via alert via error number/message
"John Bell" wrote:
> Hi
> "ssciarrino" wrote:
> > We have one SQL server where the mail may disconnect from time to time with
> > the SQL Server Agent.
> >
> > Is it possible to flag an alert to notify when the SQL Server Agent produces
> > an error in the SQL Server Agent Error Log?
> You don't give your SQL Server version number or whether SQL Agent is still
> running and it is just mail that is not getting though? What message is put
> in the log?
> Have you looked at creating an ALERT for this if you can trap the error
> level or number? You would have to use a method other than emails to send the
> information! You could look at using MOM to check the log files for this.
> A common cause of email stopping is issues connecting to the email server.
> If you have network issues you may want to sort them out. SMTP email tends to
> be less prone to this to use this with SQL 2000 you can use xp_smtp
> http://www.sqldev.net/xp/xpsmtp.htm and include extra steps in the jobs to
> send the sucess/failure emails. SQL 2005 has SMTP inbuilt with database mail.
> John