Join Now For immediate help use Live now! For more information about this message, see Microsoft Knowledge Base article 329133. Possibly the system date or time was modified on the one of them. Thanks, Dave 0 LVL 26 Overall: Level 26 MS SQL Server 21 MS SQL Server 2008 15 Windows Server 2008 2 Message Active 5 days ago Expert Comment by:Zberteoc ID: have a peek here
The backup threshold is the number of minutes that are allowed to elapse between log-shipping backup jobs before an alert is generated. See example of private comment Links: ME329133, Microsoft event 14420 from source MSSQLServer Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links... Check agent log and logshipping monitor information.At 9:00 AM, Rebuild indexes Maintenance task job is running, and its taking 1hr 20 mins to complete that job. Instead, this message might indicate one of the following problems: The backup job is not running.
Possible causes for this include the following: the SQL Server Agent service on the primary server instance is not running, the job is disabled, or the job's schedule has been changed. You cannot post new polls. This message does not necessarily indicate a problem with log shipping.
I assume that there is a reference in a system database I need to manually remove. Enter the product name, event source, and event ID. If you change the frequency of the backup job after log shipping is configured and functional, you must update the value of the backup alert threshold accordingly. There are several possible reasons why the alert message was generated.
Error: 14420, Severity: 16, State: 1. You cannot post events. You cannot edit your own topics. http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=SQL+Server&ProdVer=2000.80.760.0&EvtID=14420&EvtSrc=MSSQLServer&LCID=1033 Note: Different time zones for the two server instances should not cause a problem.
Explanation Log shipping is out of synchronization beyond the backup threshold. You’ll be auto redirected in 1 second. Ideally, you must set this value to at least three times the frequency of the backup job. Learning resources Microsoft Virtual Academy Channel 9 MSDN Magazine Community Forums Blogs Codeplex Support Self support Programs BizSpark (for startups) Microsoft Imagine (for students) United States (English) Newsletter Privacy & cookies
You may have set an incorrect value for the "Backup Alert" threshold. Our log shipping backup job occurs every 1 hr. IN the event log, I keep getting this error. This may also generate alert messages.
The message indicates that the difference between the time of the last backed up file and the current time on the monitor server is greater than the time that is set navigate here The backup alert threshold might have an incorrect value. In the secondary server dbo.log_shipping_monitor_primary has two rows and gives the threshhold_alert 14420. Version: 9.0 Component: SQLEngine Symbolic Name: SQLErrorNum14420 Message: The log shipping primary database %s.%s has backup threshold of %d minutes and has not performed a backup log operation for %d minutes.
This could be caused by an authentication problem between the monitor server instance and the primary server instance. Feedback: Send comments or solutions - Notify me when updated Printer friendly Subscribe Subscribe to EventID.Net now!Already a subscriber? Comments No comments yet. Check This Out So, is there a way to manually remove the record from the master database so that the alert does not get tripped?
I know I have to delete some rows in the msdb table because I created, deleted and re-enabled logshipping and I am getting the event log error: The log shipping primary Possible causes for this include the following: the SQL Server Agent service on the primary server instance is not running, the job is disabled, or the job's schedule has been changed. There are several possible reasons why the alert message was generated.
Possibly the system date or time was modified on the one of them. Enter the product name, event source, and event ID. So, I can't right-click on it and select properties, as the Technet article suggests. As hourly is quite a low frequency I would go for just over twice the backup frequency. --------------------------------------------------------------------- Post #812658 gary1gary1 Posted Monday, November 2, 2009 5:15 PM Say Hey Kid
Cause: WMI is unable to query the backend database for server configuration. To update the monitor tables with the latest data for the primary database, run sp_refresh_log_shipping_monitor on the primary server instance. In this case, check the job history for the backup job to see a reason for the failure. this contact form This could be caused by an authentication problem between the monitor server instance and the primary server instance.
Look into separating up your reindex job, doing different tables at different times. Stats Reported 5 years ago 0 Comments 1,064 Views Other sources for 14420 MSSQLSERVER MSSQL$HARZGUSS_EASY MSSQL$SQL MSSQL$UATSQL MSSQL$CORESGS MSSQL$SPZ MSSQL$NOBIAWEB MSSQL$DBA See More IT's easier with help Join millions of IT The alert message 14420 indicates that the difference between the current time and the time indicated by the last_backup_filename value in the log_shipping_primaries table on the monitor server is greater than When the monitor server instance goes offline and then comes back online, the log_shipping_monitor_primary table is not updated with the current values before the alert message job runs.
When the monitor server instance goes offline and then comes back online, the log_shipping_monitor_primary table is not updated with the current values before the alert message job runs. When the monitor server is offline and then comes back online, the fields in the log_shipping_primaries table are not updated with the current values before the alert message job runs. You cannot post topic replies.