Weird SQL Server 2000 behavior
I was able to successfully create a database maintenance plan for SQL Server 2000 Transaction Log Shipping for a few databases a few weeks ago. Yesterday, I created a few more but to my surprise, I can no longer do it. I can create a maintenance plan but the job it creates does not start even if I force the job to start. I did exactly the same thing as what I did (as I document everything I do) before but no luck.
Has anybody had this experience before?
Can you go into the Enterprise Manager, drill into Management->SQL Server Agent->Jobs, and then look at the job history for the failing job?
If you check the "Show Step Details" box, you should be able to see error messages from the step that failed (probably the last one unless you had error handling).
You should also be able to see errors in the system appication event log.
If you can post the errors here, we can help figure out what's going on.
Hi Kevin,
Thanks for your reply. Unfortunately, I do not have any job history coz the job doesn't even start...even if I manually start the it. Anyway, I got it all working now. I just restart the service and it works now. The only problem I have now is cleaning up all log shipping related tables on the standby server. I cannot create a new log shipping plan for a database as it pops up Error 14261. I already did the workaround found in http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q298/7/43.asp&NoWebContent=1 but still no luck. So now I am doing everything manually - selecting the plan in the sysdbmaint*, log_shipping_* tables and deleting them on the standby server.
Can you give me a guide on how to manually clean up the log shipping related tables in the standby server? I am just making a guess by analyzing the relationships between the log_shipping_* and sysdbmaint* tables. But I don't know if I am doing it correctly.
