SQL Server Errors or Failures from Error: 32024 to Error: 32043

SQLServerF1

Error: 32024, Severity: 16, An entry for primary server %s, primary database %s already exists.

Error: 32025, Severity: 16, Primary Server %s, Database %s has active log shipping secondary database(s) on the secondary. Drop the secondary database(s) first.
Error: 32026, Severity: 10, Log shipping Primary Server Alert.
Error: 32027, Severity: 10, Log shipping Secondary Server Alert.
Error: 32028, Severity: 16, Invalid value = %d for parameter @threshold_alert was specified.
Error: 32029, Severity: 10, Log shipping backup agent [%s] has verified log backup file ‘%s.wrk’ and renamed it as ‘%s.trn’. This is an informational message only. No user action is required.
Error: 32030, Severity: 10, Could not query monitor information for log shipping primary %s.%s from monitor server %s.

Error: 32031, Severity: 10, Could not query monitor information for log shipping secondary %s.%s from monitor server %s.
Error: 32032, Severity: 16, Invalid value ‘%d’ for update period. Update period should be between 1 and 120 minutes.
Error: 32033, Severity: 16, The update job for the database mirroring monitor already exists. To change the update period, use sys.sp_dbmmonitorchangemonitoring
Error: 32034, Severity: 16, An internal error occurred when setting up the database mirroring monitoring job.
Error: 32035, Severity: 16, An internal error occurred when modifying the database mirroring monitoring job.
Error: 32036, Severity: 16, Parameter(s) out of range.
Error: 32037, Severity: 16, The units for the update period for the database mirroring monitor job have been changed.
Error: 32038, Severity: 16, An internal error has occurred in the database mirroring monitor.
Error: 32039, Severity: 16, The database ‘%s’ is not being mirrored. No update of the base table was done.
Error: 32040, Severity: 16, The alert for ‘oldest unsent transaction’ has been raised. The current value of ‘%d’ surpasses the threshold ‘%d’.
Error: 32041, Severity: 16, The database mirroring monitor base tables have not been created. Please run sys.sp_dbmmonitorupdate to create them.

Error: 32042, Severity: 16, The alert for ‘unsent log’ has been raised. The current value of ‘%d’ surpasses the threshold ‘%d’.
Error: 32043, Severity: 16, The alert for ‘unrestored log’ has been raised. The current value of ‘%d’ surpasses the threshold ‘%d’.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

Leave a Reply

Your email address will not be published. Required fields are marked *