| Event Id | 14442 |
| Source | MSSQLServer |
| Description | Role change failed. |
| Event Information | "According to Microsoft Cause: One of the following has occurred: 1.The primary server name or database name specified in sp_change_monitor_role does not match a current server or database name of a primary server or database in msdb.dbo.log_shipping_primaries on the monitoring instance. 2.The secondary server name or database name specified in sp_change_monitor_role does not match a current server or database name of a secondary server or database in msdb.dbo.log_shipping_secondaries on the monitoring instance. Scenarios where this could occur: 1.You have passed the wrong values for the primary and secondary server names. 2.The primary or secondary server was registered in SQL Enterprise Manager by the keyword ""(local)"" or by ""."" instead of by the actual server\instance name at the time log shipping was originally configured. The name used to register the server in SQL Enterprise Manager is the name propagated to the system tables, and there is now a mismatch with the actual server\instance name. 3.The instance is case sensitive, and the parameters you passed to sp_change_monitor_role do not match what is stored as the server\instance name and/or database name in the system tables. 4.You did not choose ""Allow database to assume primary role"" when you configured the secondary database. Resolution: 1.Verify that the value for @primary_server is the name of the primary server being replaced, not the name of server that will become the primary server. Verify that the value for @secondary_server is the name of the secondary server being replaced, not the name of server that will become the secondary server. 2.Verify that the value stored in log_shipping_primaries.primary_server_name is the actual primary server name and not ""(local)"", ""."" or some other value such as an alias or an IP address. 3.If the server is case sensitive, verify that the values you pass to sp_change_monitor_role are exactly the same case as the corresponding values stored in msdb.dbo.log_shipping_primaries and msdb.dbo.log_shipping_secondaries. 4.If you did not choose ""Allow database to assume primary role"" when you configured the secondary database, you will need to remove log shipping and reconfigure it from the beginning." |
| Reference Links | Event Id:14442 of Source Id:MSSQLServer |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.