By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,575 Members | 1,968 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,575 IT Pros & Developers. It's quick & easy.

Log Shipping - false alerts, real problem...

P: n/a
Hello,

I am setting up log shipping between two SQL servers. Everything in the
setup seems to work fine. The problem I am having is that the "Log
Shipping Alert Job - Backup" job is failing, event though the tlog
backup copy & restore process is working fine. When I look at the
histories of both the backup and copy/restore jobs, they are successful
all the way through, I can make changes to the primary db, and see them
get shipped to the secondary server, so I know log shipping itself is
working. The only job that is failing is the backup alert job.

I have the secondary (destination) server setup as the monitor server.

I read that this issue may occur when the job can't access the log
shipping tables within msdb. I have verified that the account under
which log shipping runs has access to all those tables, and the db
above. The account which runs log shipping and the jobs is the same
domain account under which MSSQLServer service runs.

Here is the error message from the job history -

Executed as user: ROTELLACAPITAL\sqlserver. The log shipping source
ODSQLK02.ROTELLACAPITAL.COM.dbTradePL_LS has not backed up for 1246
minutes. [SQLSTATE 42000] (Error 14420). The step failed.

Any ideas why this might be failing? Any ideas how to fix or work around
it?

Thanks,
TGru

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Jul 23 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a

"Tim Groulx" <ti****@hotmail.com> wrote in message
news:41**********@127.0.0.1...
Hello,

I am setting up log shipping between two SQL servers. Everything in the
setup seems to work fine. The problem I am having is that the "Log
Shipping Alert Job - Backup" job is failing, event though the tlog
backup copy & restore process is working fine. When I look at the
histories of both the backup and copy/restore jobs, they are successful
all the way through, I can make changes to the primary db, and see them
get shipped to the secondary server, so I know log shipping itself is
working. The only job that is failing is the backup alert job.

I have the secondary (destination) server setup as the monitor server.

I read that this issue may occur when the job can't access the log
shipping tables within msdb. I have verified that the account under
which log shipping runs has access to all those tables, and the db
above. The account which runs log shipping and the jobs is the same
domain account under which MSSQLServer service runs.

Here is the error message from the job history -

Executed as user: ROTELLACAPITAL\sqlserver. The log shipping source
ODSQLK02.ROTELLACAPITAL.COM.dbTradePL_LS has not backed up for 1246
minutes. [SQLSTATE 42000] (Error 14420). The step failed.

Any ideas why this might be failing? Any ideas how to fix or work around
it?

Thanks,
TGru

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!


You don't mention your version and servicepack, but if you don't have SP3
yet, then this might be relevant:

http://support.microsoft.com/default...b;en-us;810969

Simon
Jul 23 '05 #2

P: n/a
thanks, I'm running enterprise sp3a.

TGru

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Jul 23 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.