I am getting log shipping errors referring to a database that has been deleted

Posted on 2014-02-25
Last Modified: 2014-03-29
I have been given an existing MS SQL 2008 R2 database to oversee. IN the event log, I keep getting this error.

The log shipping primary database ACI-SQL1.ACI_Test has backup threshold of 60 minutes and has not performed a backup log operation for 221465 minutes. Check agent log and logshipping monitor information.
Error: 14420, Severity: 16, State: 1.

I was told that the ACI_Text database was deleted. How do I stop the server from trying to do log shipping on a non-existing database?


Question by:dcadler
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
LVL 27

Accepted Solution

Zberteoc earned 500 total points
ID: 39886520

Author Comment

ID: 39887598
Zberteoc - The database, ACI_Test, had been deleted by the admin before me. So, I can't right-click on it and select properties, as the Technet article suggests. That is the reason I am seeking help on this forum. I do not know why I am getting the error message when the database is not in the list of databases. I assume that there is a reference in a system database I need to manually remove.

Any other ideas?


LVL 27

Expert Comment

ID: 39888448
Read to the bottom the "Using Transact-SQL" section. There are other links there.

Author Comment

ID: 39899355
Zberteoc - Using the T-SQL commands did not fix the issue.

I think that there is an entry in a system table for log shipping on the database that has been deleted. The database doesn't exist, but the Log Shipping Alert job, which has the step;

exec sys.sp_check_log_shipping_monitor_alert

against the master database, is generating the error.

So, is there a way to manually remove the record from the master database so that the alert does not get tripped? If so, which table(s) do I need to look at.

Or is there some kind of orphaned database cleanup utility that will remove the orphaned records in the master table when a user database is not properly deleted?


LVL 27

Expert Comment

ID: 39900575
Exactly that was supposed to do the stored procedures in the link. Similar situations happens with replication but when you execute remove replication db every trace is removed.

Did you run the queries on both sides?

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article explains how to reset the password of the sa account on a Microsoft SQL Server.  The steps in this article work in SQL 2005, 2008, 2008 R2, 2012, 2014 and 2016.
For both online and offline retail, the cross-channel business is the most recent pattern in the B2C trade space.
Via a live example, show how to shrink a transaction log file down to a reasonable size.
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…

710 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question