Log Shipping does not have server access

[djj55]

In SQL 2000 we have four instances of log shipping setup. On Sunday we stopped the monitor server and the secondary server to move the boxes to a new room. When we brought these back up the log shipping for the two small databases worked find the log shipping for the two large database did not recover. We are receiving the error:

The job failed. The owner () of job Log Shipping copy for myDatabase.my_logshipping does not have server access.

on the secondary server for both the copy and the restore jobs for the log shipping. These jobs were working before the server move but not know. Notice that it does not give an owner.

I would prefer to change a permission rather than have to rebuild. We have a back up from Friday night and the log files but it still takes some effort to rebuild.

Thank you for your time,
djj

 

[djj55]

Never mind. I changed the owner from myself to the administrator and it worked. Now why it worked before the move and not after, I do not know.
djj

 

[mrdenny]

This is a funky thing with SQL Agent in SQL 2000. Everyonce in a while it will decide that it doesn't know who owns the job. Even though if you look into the sysjobs table the owner does show up correctly.

All you have to do is what you did, change the job owner and change it back.

It's very stupid.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

My Blog

 

[djj55]

Must be a Microsoft product.
djj