-
-
Save 4oo4/b27446d209d0ff4b079c1af6b7dd8a04 to your computer and use it in GitHub Desktop.
SQL AAG - Server Error Logs
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| 2021-10-23 03:08:44.57 spid143s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:08:44.57 spid143s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:08:44.72 spid143s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:08:44.72 spid143s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:08:49.66 spid143s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:08:49.66 spid143s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:08:53.27 spid143s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:08:53.27 spid143s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:08:53.33 spid43s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:08:53.33 spid43s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:08:57.01 spid143s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:08:57.01 spid143s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:08:57.61 spid143s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:08:57.61 spid143s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:08:57.64 spid143s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:08:57.64 spid143s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:08:59.16 spid220s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:08:59.16 spid220s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:09:03.12 spid220s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:09:03.12 spid220s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:09:03.20 spid211s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:09:03.20 spid211s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:09:05.00 spid220s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:09:05.00 spid220s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:09:05.64 spid209s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:09:05.64 spid209s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:09:05.70 spid220s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:09:05.70 spid220s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:09:05.75 spid220s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:09:05.75 spid220s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:09:14.12 spid143s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:09:14.12 spid143s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:09:14.24 spid143s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:09:14.24 spid143s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:09:22.13 spid143s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:09:22.13 spid143s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:09:22.25 spid143s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:09:22.25 spid143s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:09:23.11 spid211s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:09:23.11 spid211s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:09:23.14 spid143s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:09:23.14 spid143s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:09:23.49 spid143s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:09:23.49 spid143s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:09:23.55 spid142s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:09:23.55 spid142s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:09:23.86 spid142s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:09:23.86 spid142s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:09:23.91 spid142s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:09:23.91 spid142s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:09:25.75 spid23s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:09:25.75 spid23s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:09:25.79 spid23s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:09:25.79 spid23s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:09:26.50 spid23s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:09:26.50 spid23s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:09:26.63 spid23s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:09:26.63 spid23s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:10:04.34 spid23s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:10:04.34 spid23s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:10:20.93 spid15s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 604EBD17-9BC4-4480-90DF-CA446489E6B5:4 | |
| 2021-10-23 03:10:21.61 spid142s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:10:21.61 spid142s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:10:22.59 spid192s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:10:22.59 spid192s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:10:23.14 spid169s Always On Availability Groups connection with secondary database terminated for primary database 'MyDb1' on the availability replica 'db-node-secondary' with Replica ID: {604ebd17-9bc4-4480-90df-ca446489e6b5}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:10:29.54 spid143s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2714CDA-B751-4BAF-BD7D-E706DDCA874F:4 | |
| 2021-10-23 03:10:29.55 spid48s Always On Availability Groups connection with secondary database terminated for primary database 'MyDb3itoring' on the availability replica 'db-node-secondary' with Replica ID: {e2714cda-b751-4baf-bd7d-e706ddca874f}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:10:29.55 spid211s Always On Availability Groups connection with secondary database terminated for primary database 'MyDb4' on the availability replica 'db-node-secondary' with Replica ID: {e2c6d609-6b65-45a6-8027-3d1d37f6f144}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:10:29.55 spid266s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2C6D609-6B65-45A6-8027-3D1D37F6F144:4 | |
| 2021-10-23 03:10:29.74 spid273s A connection for availability group 'MyDb4' from availability replica 'db-node-primary' with id [CAD7453A-CE3E-4251-8EDA-10038D9FB820] to 'db-node-secondary' with id [E2C6D609-6B65-45A6-8027-3D1D37F6F144] has been successfully established. This is an informational message only. No user action is required. | |
| 2021-10-23 03:10:30.94 spid209s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [3B78D98A-354E-42E1-8FB1-539238E8BCEC]->[68820BCC-AD5C-40E0-9B9A-75BF95A677B5], database [MyDb2ging], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [B1FFDD41-EF78-4741-8213-15130803CA9C]: Transitioning from [PENDING] to [CHECK_IF_SEEDING_NEEDED].' | |
| 2021-10-23 03:10:30.99 spid211s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:4 | |
| 2021-10-23 03:10:31.00 spid273s Always On Availability Groups connection with secondary database terminated for primary database 'MyDb2ging' on the availability replica 'db-node-secondary' with Replica ID: {68820bcc-ad5c-40e0-9b9a-75bf95a677b5}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:10:31.23 spid278s A connection for availability group 'MyDb2' from availability replica 'db-node-primary' with id [3B78D98A-354E-42E1-8FB1-539238E8BCEC] to 'db-node-secondary' with id [68820BCC-AD5C-40E0-9B9A-75BF95A677B5] has been successfully established. This is an informational message only. No user action is required. | |
| 2021-10-23 03:10:34.83 spid70s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [3B78D98A-354E-42E1-8FB1-539238E8BCEC]->[68820BCC-AD5C-40E0-9B9A-75BF95A677B5], database [MyDb2ging], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [B1FFDD41-EF78-4741-8213-15130803CA9C]: Transitioning from [CHECK_IF_SEEDING_NEEDED] to [CATCHUP].' | |
| 2021-10-23 03:10:36.05 spid61s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [CAD7453A-CE3E-4251-8EDA-10038D9FB820]->[E2C6D609-6B65-45A6-8027-3D1D37F6F144], database [MyDb4], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [4FEE57A5-7FA5-4F3F-968F-16AA82929343]: Transitioning from [PENDING] to [CHECK_IF_SEEDING_NEEDED].' | |
| 2021-10-23 03:10:36.38 spid15s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 604EBD17-9BC4-4480-90DF-CA446489E6B5:1 | |
| 2021-10-23 03:10:36.38 spid15s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 604EBD17-9BC4-4480-90DF-CA446489E6B5:1 | |
| 2021-10-23 03:10:36.38 spid15s DbMgrPartnerCommitPolicy::SetSyncState: 604EBD17-9BC4-4480-90DF-CA446489E6B5:1 | |
| 2021-10-23 03:10:36.40 spid274s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [43DE05A5-1C5E-4BA5-BD31-CD4D8E58AD62]->[604EBD17-9BC4-4480-90DF-CA446489E6B5], database [MyDb1], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [9AD8F1C9-60FF-48DF-8BB1-96DCC5CCF4CE]: Transitioning from [PENDING] to [CHECK_IF_SEEDING_NEEDED].' | |
| 2021-10-23 03:10:36.67 spid70s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [CAD7453A-CE3E-4251-8EDA-10038D9FB820]->[E2C6D609-6B65-45A6-8027-3D1D37F6F144], database [MyDb4], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [4FEE57A5-7FA5-4F3F-968F-16AA82929343]: Transitioning from [CHECK_IF_SEEDING_NEEDED] to [CATCHUP].' | |
| 2021-10-23 03:10:36.74 spid15s A connection for availability group 'MyDb1' from availability replica 'db-node-primary' with id [43DE05A5-1C5E-4BA5-BD31-CD4D8E58AD62] to 'db-node-secondary' with id [604EBD17-9BC4-4480-90DF-CA446489E6B5] has been successfully established. This is an informational message only. No user action is required. | |
| 2021-10-23 03:10:36.74 spid143s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2714CDA-B751-4BAF-BD7D-E706DDCA874F:1 | |
| 2021-10-23 03:10:36.74 spid143s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2714CDA-B751-4BAF-BD7D-E706DDCA874F:1 | |
| 2021-10-23 03:10:36.74 spid143s DbMgrPartnerCommitPolicy::SetSyncState: E2714CDA-B751-4BAF-BD7D-E706DDCA874F:1 | |
| 2021-10-23 03:10:36.76 spid266s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2C6D609-6B65-45A6-8027-3D1D37F6F144:1 | |
| 2021-10-23 03:10:36.76 spid266s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2C6D609-6B65-45A6-8027-3D1D37F6F144:1 | |
| 2021-10-23 03:10:36.76 spid266s DbMgrPartnerCommitPolicy::SetSyncState: E2C6D609-6B65-45A6-8027-3D1D37F6F144:1 | |
| 2021-10-23 03:10:36.78 spid272s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2C6D609-6B65-45A6-8027-3D1D37F6F144:1 | |
| 2021-10-23 03:10:36.78 spid272s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2C6D609-6B65-45A6-8027-3D1D37F6F144:1 | |
| 2021-10-23 03:10:36.78 spid272s Always On Availability Groups connection with secondary database established for primary database 'MyDb4' on the availability replica 'db-node-secondary' with Replica ID: {e2c6d609-6b65-45a6-8027-3d1d37f6f144}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:10:36.79 spid16s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [8210.9A-D04D-46E8-8BEC-B7FC49CDDA43]->[E2714CDA-B751-4BAF-BD7D-E706DDCA874F], database [MyDb3itoring], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [0DEEB5F6-A1BE-40F0-954C-DF1D7B0BFF90]: Transitioning from [PENDING] to [CHECK_IF_SEEDING_NEEDED].' | |
| 2021-10-23 03:10:36.83 spid211s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:10:36.83 spid211s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:10:36.83 spid211s DbMgrPartnerCommitPolicy::SetSyncState: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:10:36.83 spid48s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:10:36.83 spid48s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:10:36.83 spid48s Always On Availability Groups connection with secondary database established for primary database 'MyDb2ging' on the availability replica 'db-node-secondary' with Replica ID: {68820bcc-ad5c-40e0-9b9a-75bf95a677b5}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:10:36.92 spid272s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2C6D609-6B65-45A6-8027-3D1D37F6F144:1 | |
| 2021-10-23 03:10:36.94 spid272s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2C6D609-6B65-45A6-8027-3D1D37F6F144:1 | |
| 2021-10-23 03:10:36.94 spid272s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2C6D609-6B65-45A6-8027-3D1D37F6F144:1 | |
| 2021-10-23 03:10:36.94 spid272s Always On Availability Groups connection with secondary database established for primary database 'MyDb4' on the availability replica 'db-node-secondary' with Replica ID: {e2c6d609-6b65-45a6-8027-3d1d37f6f144}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:10:36.97 spid48s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:10:36.97 spid48s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:10:36.97 spid48s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:10:36.97 spid48s Always On Availability Groups connection with secondary database established for primary database 'MyDb2ging' on the availability replica 'db-node-secondary' with Replica ID: {68820bcc-ad5c-40e0-9b9a-75bf95a677b5}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:10:37.02 spid272s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2C6D609-6B65-45A6-8027-3D1D37F6F144:1 | |
| 2021-10-23 03:10:37.04 spid48s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:10:37.18 spid48s A connection for availability group 'MyDb3' from availability replica 'db-node-primary' with id [8210.9A-D04D-46E8-8BEC-B7FC49CDDA43] to 'db-node-secondary' with id [E2714CDA-B751-4BAF-BD7D-E706DDCA874F] has been successfully established. This is an informational message only. No user action is required. | |
| 2021-10-23 03:10:37.31 spid266s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 604EBD17-9BC4-4480-90DF-CA446489E6B5:1 | |
| 2021-10-23 03:10:37.31 spid266s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 604EBD17-9BC4-4480-90DF-CA446489E6B5:1 | |
| 2021-10-23 03:10:37.31 spid266s Always On Availability Groups connection with secondary database established for primary database 'MyDb1' on the availability replica 'db-node-secondary' with Replica ID: {604ebd17-9bc4-4480-90df-ca446489e6b5}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:10:37.36 spid211s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2714CDA-B751-4BAF-BD7D-E706DDCA874F:1 | |
| 2021-10-23 03:10:37.36 spid211s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2714CDA-B751-4BAF-BD7D-E706DDCA874F:1 | |
| 2021-10-23 03:10:37.36 spid211s Always On Availability Groups connection with secondary database established for primary database 'MyDb3itoring' on the availability replica 'db-node-secondary' with Replica ID: {e2714cda-b751-4baf-bd7d-e706ddca874f}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:10:37.37 spid266s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 604EBD17-9BC4-4480-90DF-CA446489E6B5:1 | |
| 2021-10-23 03:10:37.40 spid211s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2714CDA-B751-4BAF-BD7D-E706DDCA874F:1 | |
| 2021-10-23 03:10:37.85 spid72s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [3B78D98A-354E-42E1-8FB1-539238E8BCEC]->[68820BCC-AD5C-40E0-9B9A-75BF95A677B5], database [MyDb2ging], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [B1FFDD41-EF78-4741-8213-15130803CA9C]: Transitioning from [CATCHUP] to [COMPLETED].' | |
| 2021-10-23 03:10:37.89 spid29s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:10:38.01 spid70s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [CAD7453A-CE3E-4251-8EDA-10038D9FB820]->[E2C6D609-6B65-45A6-8027-3D1D37F6F144], database [MyDb4], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [4FEE57A5-7FA5-4F3F-968F-16AA82929343]: Transitioning from [CATCHUP] to [COMPLETED].' | |
| 2021-10-23 03:10:38.01 spid256s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2C6D609-6B65-45A6-8027-3D1D37F6F144:1 | |
| 2021-10-23 03:10:38.22 spid29s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:4 | |
| 2021-10-23 03:10:38.22 spid29s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:4 | |
| 2021-10-23 03:10:38.22 spid29s DbMgrPartnerCommitPolicy::SetSyncState: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:4 | |
| 2021-10-23 03:10:38.25 spid272s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2714CDA-B751-4BAF-BD7D-E706DDCA874F:1 | |
| 2021-10-23 03:10:38.26 spid256s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2C6D609-6B65-45A6-8027-3D1D37F6F144:4 | |
| 2021-10-23 03:10:38.26 spid256s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2C6D609-6B65-45A6-8027-3D1D37F6F144:4 | |
| 2021-10-23 03:10:38.26 spid256s DbMgrPartnerCommitPolicy::SetSyncState: E2C6D609-6B65-45A6-8027-3D1D37F6F144:4 | |
| 2021-10-23 03:10:38.26 spid250s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 604EBD17-9BC4-4480-90DF-CA446489E6B5:1 | |
| 2021-10-23 03:10:38.47 spid272s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2714CDA-B751-4BAF-BD7D-E706DDCA874F:4 | |
| 2021-10-23 03:10:38.47 spid272s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2714CDA-B751-4BAF-BD7D-E706DDCA874F:4 | |
| 2021-10-23 03:10:38.47 spid272s DbMgrPartnerCommitPolicy::SetSyncState: E2714CDA-B751-4BAF-BD7D-E706DDCA874F:4 | |
| 2021-10-23 03:10:38.57 spid250s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 604EBD17-9BC4-4480-90DF-CA446489E6B5:4 | |
| 2021-10-23 03:10:38.57 spid250s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 604EBD17-9BC4-4480-90DF-CA446489E6B5:4 | |
| 2021-10-23 03:10:38.57 spid250s DbMgrPartnerCommitPolicy::SetSyncState: 604EBD17-9BC4-4480-90DF-CA446489E6B5:4 | |
| 2021-10-23 03:10:38.97 spid75s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [8210.9A-D04D-46E8-8BEC-B7FC49CDDA43]->[E2714CDA-B751-4BAF-BD7D-E706DDCA874F], database [MyDb3itoring], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [0DEEB5F6-A1BE-40F0-954C-DF1D7B0BFF90]: Transitioning from [CHECK_IF_SEEDING_NEEDED] to [CATCHUP].' | |
| 2021-10-23 03:10:38.97 spid74s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [43DE05A5-1C5E-4BA5-BD31-CD4D8E58AD62]->[604EBD17-9BC4-4480-90DF-CA446489E6B5], database [MyDb1], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [9AD8F1C9-60FF-48DF-8BB1-96DCC5CCF4CE]: Transitioning from [CHECK_IF_SEEDING_NEEDED] to [CATCHUP].' | |
| 2021-10-23 03:10:38.97 spid74s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [8210.9A-D04D-46E8-8BEC-B7FC49CDDA43]->[E2714CDA-B751-4BAF-BD7D-E706DDCA874F], database [MyDb3itoring], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [0DEEB5F6-A1BE-40F0-954C-DF1D7B0BFF90]: Transitioning from [CATCHUP] to [COMPLETED].' | |
| 2021-10-23 03:10:39.03 spid74s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [43DE05A5-1C5E-4BA5-BD31-CD4D8E58AD62]->[604EBD17-9BC4-4480-90DF-CA446489E6B5], database [MyDb1], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [9AD8F1C9-60FF-48DF-8BB1-96DCC5CCF4CE]: Transitioning from [CATCHUP] to [COMPLETED].' | |
| 2021-10-23 03:10:39.46 Logon Error: 17832, Severity: 20, State: 2. | |
| 2021-10-23 03:10:39.46 Logon The login packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor of the client library. [CLIENT: 10.16.1.75] | |
| 2021-10-23 03:10:39.49 spid80s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:10:39.49 spid80s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:12:26.26 Server Error: 19421, Severity: 16, State: 1. | |
| 2021-10-23 03:12:26.26 Server SQL Server hosting availability group 'MyDb4' did not receive a process event signal from the Windows Server Failover Cluster within the lease timeout period. | |
| 2021-10-23 03:12:26.26 Server Error: 19407, Severity: 16, State: 1. | |
| 2021-10-23 03:12:26.26 Server The lease between availability group 'MyDb4' and the Windows Server Failover Cluster has expired. A connectivity issue occurred between the instance of SQL Server and the Windows Server Failover Cluster. To determine whether the availability group is failing over correctly, check the corresponding availability group resource in the Windows Server Failover Cluster. | |
| 2021-10-23 03:12:26.26 Server Always On: The local replica of availability group 'MyDb4' is going offline because either the lease expired or lease renewal failed. This is an informational message only. No user action is required. | |
| 2021-10-23 03:12:26.27 Server The state of the local availability replica in availability group 'MyDb4' has changed from 'PRIMARY_NORMAL' to 'RESOLVING_NORMAL'. The state changed because the lease between the local availability replica and Windows Server Failover Clustering (WSFC) has expired. For more information, see the SQL Server error log or cluster log. If this is a Windows Server Failover Clustering (WSFC) availability group, you can also see the WSFC management console. | |
| 2021-10-23 03:12:26.29 spid250s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2C6D609-6B65-45A6-8027-3D1D37F6F144:4 | |
| 2021-10-23 03:12:26.37 Server Error: 19421, Severity: 16, State: 1. | |
| 2021-10-23 03:12:26.37 Server SQL Server hosting availability group 'MyDb3' did not receive a process event signal from the Windows Server Failover Cluster within the lease timeout period. | |
| 2021-10-23 03:12:26.37 Server Error: 19407, Severity: 16, State: 1. | |
| 2021-10-23 03:12:26.37 Server The lease between availability group 'MyDb3' and the Windows Server Failover Cluster has expired. A connectivity issue occurred between the instance of SQL Server and the Windows Server Failover Cluster. To determine whether the availability group is failing over correctly, check the corresponding availability group resource in the Windows Server Failover Cluster. | |
| 2021-10-23 03:12:26.37 Server Always On: The local replica of availability group 'MyDb3' is going offline because either the lease expired or lease renewal failed. This is an informational message only. No user action is required. | |
| 2021-10-23 03:12:26.37 Server The state of the local availability replica in availability group 'MyDb3' has changed from 'PRIMARY_NORMAL' to 'RESOLVING_NORMAL'. The state changed because the lease between the local availability replica and Windows Server Failover Clustering (WSFC) has expired. For more information, see the SQL Server error log or cluster log. If this is a Windows Server Failover Clustering (WSFC) availability group, you can also see the WSFC management console. | |
| 2021-10-23 03:12:26.72 spid28s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2714CDA-B751-4BAF-BD7D-E706DDCA874F:4 | |
| 2021-10-23 03:12:28.14 spid294 Remote harden of transaction 'UPDATE' (ID 0x000000000f35c15c 0000:12e2cc95) started at Oct 23 2021 3:12AM in database 'MyDb4' at LSN (44333:3037:3) failed. | |
| 2021-10-23 03:12:31.26 Server Error: 19421, Severity: 16, State: 1. | |
| 2021-10-23 03:12:31.26 Server SQL Server hosting availability group 'MyDb2' did not receive a process event signal from the Windows Server Failover Cluster within the lease timeout period. | |
| 2021-10-23 03:12:31.26 Server Error: 19421, Severity: 16, State: 1. | |
| 2021-10-23 03:12:31.26 Server SQL Server hosting availability group 'MyDb1' did not receive a process event signal from the Windows Server Failover Cluster within the lease timeout period. | |
| 2021-10-23 03:12:31.76 Server Error: 19407, Severity: 16, State: 1. | |
| 2021-10-23 03:12:31.76 Server The lease between availability group 'MyDb2' and the Windows Server Failover Cluster has expired. A connectivity issue occurred between the instance of SQL Server and the Windows Server Failover Cluster. To determine whether the availability group is failing over correctly, check the corresponding availability group resource in the Windows Server Failover Cluster. | |
| 2021-10-23 03:12:31.76 Server Error: 19407, Severity: 16, State: 1. | |
| 2021-10-23 03:12:31.76 Server The lease between availability group 'MyDb1' and the Windows Server Failover Cluster has expired. A connectivity issue occurred between the instance of SQL Server and the Windows Server Failover Cluster. To determine whether the availability group is failing over correctly, check the corresponding availability group resource in the Windows Server Failover Cluster. | |
| 2021-10-23 03:12:32.24 Server Always On: The local replica of availability group 'MyDb2' is going offline because either the lease expired or lease renewal failed. This is an informational message only. No user action is required. | |
| 2021-10-23 03:12:32.24 Server Always On: The local replica of availability group 'MyDb1' is going offline because either the lease expired or lease renewal failed. This is an informational message only. No user action is required. | |
| 2021-10-23 03:12:32.24 Server The state of the local availability replica in availability group 'MyDb2' has changed from 'PRIMARY_NORMAL' to 'RESOLVING_NORMAL'. The state changed because the lease between the local availability replica and Windows Server Failover Clustering (WSFC) has expired. For more information, see the SQL Server error log or cluster log. If this is a Windows Server Failover Clustering (WSFC) availability group, you can also see the WSFC management console. | |
| 2021-10-23 03:12:32.41 Server The state of the local availability replica in availability group 'MyDb1' has changed from 'PRIMARY_NORMAL' to 'RESOLVING_NORMAL'. The state changed because the lease between the local availability replica and Windows Server Failover Clustering (WSFC) has expired. For more information, see the SQL Server error log or cluster log. If this is a Windows Server Failover Clustering (WSFC) availability group, you can also see the WSFC management console. | |
| 2021-10-23 03:12:32.59 Logon Error: 18456, Severity: 14, State: 46. | |
| 2021-10-23 03:12:32.59 Logon Login failed for user 'DOMAIN\svcMyDb4'. Reason: Failed to open the database 'MyDb4' configured in the login object while revalidating the login on the connection. [CLIENT: 10.16.1.94] | |
| 2021-10-23 03:12:33.99 spid48s The availability group database "MyDb4" is changing roles from "PRIMARY" to "RESOLVING" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required. | |
| 2021-10-23 03:12:34.88 Logon Error: 18456, Severity: 14, State: 46. | |
| 2021-10-23 03:12:34.88 Logon Login failed for user 'DOMAIN\APPServer1$'. Reason: Failed to open the database 'MyDb1' configured in the login object while revalidating the login on the connection. [CLIENT: 10.16.1.99] | |
| 2021-10-23 03:12:35.33 spid20s Always On Availability Groups connection with secondary database terminated for primary database 'MyDb2ging' on the availability replica 'db-node-secondary' with Replica ID: {68820bcc-ad5c-40e0-9b9a-75bf95a677b5}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:12:35.82 spid36s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:4 | |
| 2021-10-23 03:12:35.82 spid36s The availability group database "MyDb2ging" is changing roles from "PRIMARY" to "RESOLVING" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required. | |
| 2021-10-23 03:12:35.82 spid29s Always On Availability Groups connection with secondary database terminated for primary database 'MyDb1' on the availability replica 'db-node-secondary' with Replica ID: {604ebd17-9bc4-4480-90df-ca446489e6b5}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:12:36.30 spid169s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 604EBD17-9BC4-4480-90DF-CA446489E6B5:4 | |
| 2021-10-23 03:12:36.30 spid169s The availability group database "MyDb1" is changing roles from "PRIMARY" to "RESOLVING" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required. | |
| 2021-10-23 03:12:37.24 spid96 Remote harden of transaction 'user_transaction' (ID 0x000000000f35bf35 0000:247139a7) started at Oct 23 2021 3:11AM in database 'MyDb1' at LSN (50177:55038:4) failed. | |
| 2021-10-23 03:12:37.72 spid228 Remote harden of transaction 'user_transaction' (ID 0x000000000f35bfd9 0000:247139b4) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55048:4) failed. | |
| 2021-10-23 03:12:42.39 spid184 Remote harden of transaction 'UPDATE' (ID 0x000000000f35bfb6 0000:247139b1) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55042:3) failed. | |
| 2021-10-23 03:12:44.30 spid65 Remote harden of transaction 'user_transaction' (ID 0x000000000f35c04a 0000:247139ba) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55048:9) failed. | |
| 2021-10-23 03:12:44.80 spid223 Remote harden of transaction 'user_transaction' (ID 0x000000000f35c082 0000:247139bb) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55048:10) failed. | |
| 2021-10-23 03:12:45.63 spid110 Remote harden of transaction 'user_transaction' (ID 0x000000000f35c07a 0000:247139bd) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55074:2) failed. | |
| 2021-10-23 03:12:45.66 spid214 Remote harden of transaction 'user_transaction' (ID 0x000000000f35c08b 0000:247139bc) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55048:13) failed. | |
| 2021-10-23 03:12:45.68 spid176 Remote harden of transaction 'user_transaction' (ID 0x000000000f35c0b0 0000:247139bf) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55048:21) failed. | |
| 2021-10-23 03:12:45.72 spid69 Remote harden of transaction 'user_transaction' (ID 0x000000000f35c096 0000:247139be) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55076:3) failed. | |
| 2021-10-23 03:12:45.72 spid97 Remote harden of transaction 'user_transaction' (ID 0x000000000f35bfcb 0000:247139b5) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55075:2) failed. | |
| 2021-10-23 03:12:45.73 spid159s Remote harden of transaction 'GhostCleanupTask' (ID 0x000000000f35c0d0 0000:247139c2) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55048:44) failed. | |
| 2021-10-23 03:12:45.74 spid111 Remote harden of transaction 'user_transaction' (ID 0x000000000f35c0b4 0000:247139c0) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55048:56) failed. | |
| 2021-10-23 03:12:45.74 spid220 Remote harden of transaction 'UPDATE' (ID 0x000000000f35c126 0000:247139c7) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55048:64) failed. | |
| 2021-10-23 03:12:45.99 spid90 Remote harden of transaction 'user_transaction' (ID 0x000000000f35c0d4 0000:247139c6) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55048:78) failed. | |
| 2021-10-23 03:12:46.00 spid112 Remote harden of transaction 'user_transaction' (ID 0x000000000f35c0b5 0000:247139c4) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55077:5) failed. | |
| 2021-10-23 03:12:46.00 spid213 Remote harden of transaction 'UPDATE' (ID 0x000000000f35c016 0000:247139b0) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55038:15) failed. | |
| 2021-10-23 03:12:46.08 spid283 Remote harden of transaction 'UPDATE' (ID 0x000000000f35c0c7 0000:247139c1) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55048:26) failed. | |
| 2021-10-23 03:12:46.10 spid200 Remote harden of transaction 'UPDATE' (ID 0x000000000f35c12b 0000:247139c8) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55048:67) failed. | |
| 2021-10-23 03:12:46.54 spid215 Remote harden of transaction 'UPDATE' (ID 0x000000000f35c07f 0000:247139b9) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55048:3) failed. | |
| 2021-10-23 03:12:46.69 spid180 Remote harden of transaction 'UPDATE' (ID 0x000000000f35c18a 0000:247139ce) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55048:91) failed. | |
| 2021-10-23 03:12:47.14 spid204 Remote harden of transaction 'user_transaction' (ID 0x000000000f35c09b 0000:247139c5) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55048:77) failed. | |
| 2021-10-23 03:12:47.43 spid288 Remote harden of transaction 'UPDATE' (ID 0x000000000f35c139 0000:247139ca) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55048:76) failed. | |
| 2021-10-23 03:12:47.95 spid82 Remote harden of transaction 'user_transaction' (ID 0x000000000f35c0f1 0000:247139d1) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55079:2) failed. | |
| 2021-10-23 03:12:47.96 spid209 Remote harden of transaction 'UPDATE' (ID 0x000000000f35c185 0000:247139cd) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55048:88) failed. | |
| 2021-10-23 03:12:48.13 spid224 Remote harden of transaction 'user_transaction' (ID 0x000000000f35c0ee 0000:247139cb) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55080:2) failed. | |
| 2021-10-23 03:12:48.54 spid173 Remote harden of transaction 'user_transaction' (ID 0x000000000f35c1f7 0000:247139d5) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55082:2) failed. | |
| 2021-10-23 03:12:48.54 spid123 Remote harden of transaction 'user_transaction' (ID 0x000000000f35c058 0000:247139cc) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55081:2) failed. | |
| 2021-10-23 03:12:48.72 spid190 Remote harden of transaction 'UPDATE' (ID 0x000000000f35c1e4 0000:247139d4) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55048:104) failed. | |
| 2021-10-23 03:12:48.78 spid92 Remote harden of transaction 'user_transaction' (ID 0x000000000f35c0fa 0000:247139cf) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55083:2) failed. | |
| 2021-10-23 03:12:48.80 spid134 Remote harden of transaction 'user_transaction' (ID 0x000000000f35c027 0000:247139b8) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55048:105) failed. | |
| 2021-10-23 03:12:49.34 spid158 Remote harden of transaction 'user_transaction' (ID 0x000000000f35bfef 0000:247139d2) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55048:106) failed. | |
| 2021-10-23 03:12:50.51 spid234s Always On Availability Groups connection with secondary database terminated for primary database 'MyDb3itoring' on the availability replica 'db-node-secondary' with Replica ID: {e2714cda-b751-4baf-bd7d-e706ddca874f}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:12:50.51 spid125 Error: 18056, Severity: 20, State: 46. | |
| 2021-10-23 03:12:50.51 spid125 The client was unable to reuse a session with SPID 125, which had been reset for connection pooling. The failure ID is 46. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message. | |
| 2021-10-23 03:12:51.06 spid310s The availability group database "MyDb3itoring" is changing roles from "PRIMARY" to "RESOLVING" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required. | |
| 2021-10-23 03:12:51.20 spid143s Always On Availability Groups connection with secondary database terminated for primary database 'MyDb4' on the availability replica 'db-node-secondary' with Replica ID: {e2c6d609-6b65-45a6-8027-3d1d37f6f144}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:12:51.28 spid36s State information for database 'MyDb2ging' - Hardened Lsn: '(6426:15218:1)' Commit LSN: '(6426:14355:16)' Commit Time: 'Oct 22 2021 4:00AM' | |
| 2021-10-23 03:12:51.29 spid197 Error: 18056, Severity: 20, State: 46. | |
| 2021-10-23 03:12:51.29 spid197 The client was unable to reuse a session with SPID 197, which had been reset for connection pooling. The failure ID is 46. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message. | |
| 2021-10-23 03:12:51.33 spid169s State information for database 'MyDb1' - Hardened Lsn: '(50177:55048:1)' Commit LSN: '(50166:107296:3)' Commit Time: 'Oct 22 2021 4:53AM' | |
| 2021-10-23 03:12:51.47 spid48s State information for database 'MyDb4' - Hardened Lsn: '(44333:3037:1)' Commit LSN: '(44321:5809:3)' Commit Time: 'Oct 22 2021 4:53AM' | |
| 2021-10-23 03:12:51.82 spid216 Remote harden of transaction 'user_transaction' (ID 0x000000000f35c0ed 0000:247139c9) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55084:4) failed. | |
| 2021-10-23 03:12:54.09 spid179 Remote harden of transaction 'user_transaction' (ID 0x000000000f35c1cf 0000:247139d3) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55085:2) failed. | |
| 2021-10-23 03:12:54.22 spid293 Remote harden of transaction 'user_transaction' (ID 0x000000000f35c0f2 0000:247139d0) started at Oct 23 2021 3:12AM in database 'MyDb1' at LSN (50177:55086:2) failed. | |
| 2021-10-23 03:12:55.73 Server Stopped listening on listener network name 'MyDb4' (VNN or DISTRIBUTED_NETWORK_NAME). No user action is required. | |
| 2021-10-23 03:12:55.83 spid310s State information for database 'MyDb3itoring' - Hardened Lsn: '(37808:21845:1)' Commit LSN: '(37782:15663:3)' Commit Time: 'Oct 22 2021 4:53AM' | |
| 2021-10-23 03:12:56.63 spid71s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2C6D609-6B65-45A6-8027-3D1D37F6F144:4 | |
| 2021-10-23 03:12:56.69 spid143s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:4 | |
| 2021-10-23 03:12:56.79 spid43s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 604EBD17-9BC4-4480-90DF-CA446489E6B5:4 | |
| 2021-10-23 03:12:58.02 spid310s Process ID 207 was killed by an ABORT_AFTER_WAIT = BLOCKERS DDL statement on database_id = 6, object_id = 0. | |
| 2021-10-23 03:12:58.03 spid43s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2714CDA-B751-4BAF-BD7D-E706DDCA874F:4 | |
| 2021-10-23 03:12:58.40 Server Stopped listening on listener network name 'MyDb1' (VNN or DISTRIBUTED_NETWORK_NAME). No user action is required. | |
| 2021-10-23 03:12:58.57 Server Stopped listening on listener network name 'MyDb3' (VNN or DISTRIBUTED_NETWORK_NAME). No user action is required. | |
| 2021-10-23 03:12:58.62 Server Stopped listening on listener network name 'MyDb2' (VNN or DISTRIBUTED_NETWORK_NAME). No user action is required. | |
| 2021-10-23 03:13:00.35 spid269s Remote harden of transaction 'GhostCleanupTask' (ID 0x000000000f35c28c 0000:247139d6) started at Oct 23 2021 3:13AM in database 'MyDb1' at LSN (50177:55088:2) failed. | |
| 2021-10-23 03:13:01.30 spid57 Always On: The local replica of availability group 'MyDb3' is preparing to transition to the resolving role. This is an informational message only. No user action is required. | |
| 2021-10-23 03:13:01.35 spid59 Always On: The local replica of availability group 'MyDb4' is preparing to transition to the resolving role. This is an informational message only. No user action is required. | |
| 2021-10-23 03:13:02.16 spid57 Always On: The local replica of availability group 'MyDb4' is preparing to transition to the primary role. This is an informational message only. No user action is required. | |
| 2021-10-23 03:13:02.45 spid59 Always On: The local replica of availability group 'MyDb3' is preparing to transition to the primary role. This is an informational message only. No user action is required. | |
| 2021-10-23 03:13:02.70 spid60 Always On: The local replica of availability group 'MyDb1' is preparing to transition to the primary role. This is an informational message only. No user action is required. | |
| 2021-10-23 03:13:03.73 spid63 Always On: The local replica of availability group 'MyDb2' is preparing to transition to the resolving role. This is an informational message only. No user action is required. | |
| 2021-10-23 03:13:04.55 spid63 Always On: The local replica of availability group 'MyDb2' is preparing to transition to the primary role. This is an informational message only. No user action is required. | |
| 2021-10-23 03:13:05.05 spid60 The state of the local availability replica in availability group 'MyDb1' has changed from 'RESOLVING_NORMAL' to 'PRIMARY_PENDING'. The state changed because the availability group is coming online. For more information, see the SQL Server error log or cluster log. If this is a Windows Server Failover Clustering (WSFC) availability group, you can also see the WSFC management console. | |
| 2021-10-23 03:13:05.11 Server The lease worker of availability group 'MyDb1' is now sleeping the excess lease time (141781 ms) supplied during online. This is an informational message only. No user action is required. | |
| 2021-10-23 03:13:05.23 spid59 The state of the local availability replica in availability group 'MyDb3' has changed from 'RESOLVING_NORMAL' to 'PRIMARY_PENDING'. The state changed because the availability group is coming online. For more information, see the SQL Server error log or cluster log. If this is a Windows Server Failover Clustering (WSFC) availability group, you can also see the WSFC management console. | |
| 2021-10-23 03:13:05.29 Server The lease worker of availability group 'MyDb3' is now sleeping the excess lease time (161391 ms) supplied during online. This is an informational message only. No user action is required. | |
| 2021-10-23 03:13:05.43 spid57 The state of the local availability replica in availability group 'MyDb4' has changed from 'RESOLVING_NORMAL' to 'PRIMARY_PENDING'. The state changed because the availability group is coming online. For more information, see the SQL Server error log or cluster log. If this is a Windows Server Failover Clustering (WSFC) availability group, you can also see the WSFC management console. | |
| 2021-10-23 03:13:05.60 Server The lease worker of availability group 'MyDb4' is now sleeping the excess lease time (161063 ms) supplied during online. This is an informational message only. No user action is required. | |
| 2021-10-23 03:13:05.79 Logon Error: 983, Severity: 14, State: 1. | |
| 2021-10-23 03:13:05.79 Logon Unable to access availability database 'MyDb4' because the database replica is not in the PRIMARY or SECONDARY role. Connections to an availability database is permitted only when the database replica is in the PRIMARY or SECONDARY role. Try the operation again later. | |
| 2021-10-23 03:13:05.80 spid63 The state of the local availability replica in availability group 'MyDb2' has changed from 'RESOLVING_NORMAL' to 'PRIMARY_PENDING'. The state changed because the availability group is coming online. For more information, see the SQL Server error log or cluster log. If this is a Windows Server Failover Clustering (WSFC) availability group, you can also see the WSFC management console. | |
| 2021-10-23 03:13:05.82 Server The state of the local availability replica in availability group 'MyDb1' has changed from 'PRIMARY_PENDING' to 'PRIMARY_NORMAL'. The state changed because the local replica has completed processing Online command from Windows Server Failover Clustering (WSFC). For more information, see the SQL Server error log or cluster log. If this is a Windows Server Failover Clustering (WSFC) availability group, you can also see the WSFC management console. | |
| 2021-10-23 03:13:05.88 Server The lease worker of availability group 'MyDb2' is now sleeping the excess lease time (163406 ms) supplied during online. This is an informational message only. No user action is required. | |
| 2021-10-23 03:13:05.88 spid272s The availability group database "MyDb1" is changing roles from "RESOLVING" to "PRIMARY" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required. | |
| 2021-10-23 03:13:05.90 spid272s State information for database 'MyDb1' - Hardened Lsn: '(50177:55048:1)' Commit LSN: '(50166:107296:3)' Commit Time: 'Oct 22 2021 4:53AM' | |
| 2021-10-23 03:13:05.92 spid272s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 604EBD17-9BC4-4480-90DF-CA446489E6B5:4 | |
| 2021-10-23 03:13:06.01 Server The state of the local availability replica in availability group 'MyDb3' has changed from 'PRIMARY_PENDING' to 'PRIMARY_NORMAL'. The state changed because the local replica has completed processing Online command from Windows Server Failover Clustering (WSFC). For more information, see the SQL Server error log or cluster log. If this is a Windows Server Failover Clustering (WSFC) availability group, you can also see the WSFC management console. | |
| 2021-10-23 03:13:06.07 spid71s The availability group database "MyDb3itoring" is changing roles from "RESOLVING" to "PRIMARY" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required. | |
| 2021-10-23 03:13:06.10 spid71s State information for database 'MyDb3itoring' - Hardened Lsn: '(37808:21845:1)' Commit LSN: '(37782:15663:3)' Commit Time: 'Oct 22 2021 4:53AM' | |
| 2021-10-23 03:13:06.13 spid71s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2714CDA-B751-4BAF-BD7D-E706DDCA874F:4 | |
| 2021-10-23 03:13:06.29 Server The state of the local availability replica in availability group 'MyDb4' has changed from 'PRIMARY_PENDING' to 'PRIMARY_NORMAL'. The state changed because the local replica has completed processing Online command from Windows Server Failover Clustering (WSFC). For more information, see the SQL Server error log or cluster log. If this is a Windows Server Failover Clustering (WSFC) availability group, you can also see the WSFC management console. | |
| 2021-10-23 03:13:06.30 spid310s The availability group database "MyDb4" is changing roles from "RESOLVING" to "PRIMARY" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required. | |
| 2021-10-23 03:13:06.31 spid310s State information for database 'MyDb4' - Hardened Lsn: '(44333:3037:1)' Commit LSN: '(44321:5809:3)' Commit Time: 'Oct 22 2021 4:53AM' | |
| 2021-10-23 03:13:06.33 spid310s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2C6D609-6B65-45A6-8027-3D1D37F6F144:4 | |
| 2021-10-23 03:13:06.40 spid272s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 604EBD17-9BC4-4480-90DF-CA446489E6B5:4 | |
| 2021-10-23 03:13:06.41 spid71s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2714CDA-B751-4BAF-BD7D-E706DDCA874F:4 | |
| 2021-10-23 03:13:06.48 spid310s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2C6D609-6B65-45A6-8027-3D1D37F6F144:4 | |
| 2021-10-23 03:13:06.50 spid272s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 604EBD17-9BC4-4480-90DF-CA446489E6B5:1 | |
| 2021-10-23 03:13:06.52 spid20s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [43DE05A5-1C5E-4BA5-BD31-CD4D8E58AD62]->[604EBD17-9BC4-4480-90DF-CA446489E6B5], database [MyDb1], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [62EAFF1C-1A04-4BED-8A7C-D07381D3C8BE]: Transitioning from [PENDING] to [CHECK_IF_SEEDING_NEEDED].' | |
| 2021-10-23 03:13:06.58 spid71s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2714CDA-B751-4BAF-BD7D-E706DDCA874F:1 | |
| 2021-10-23 03:13:06.61 spid169s A connection for availability group 'MyDb1' from availability replica 'db-node-primary' with id [43DE05A5-1C5E-4BA5-BD31-CD4D8E58AD62] to 'db-node-secondary' with id [604EBD17-9BC4-4480-90DF-CA446489E6B5] has been successfully established. This is an informational message only. No user action is required. | |
| 2021-10-23 03:13:06.62 spid16s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [8210.9A-D04D-46E8-8BEC-B7FC49CDDA43]->[E2714CDA-B751-4BAF-BD7D-E706DDCA874F], database [MyDb3itoring], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [21F30DC7-6175-441A-8651-045EDE08E2D9]: Transitioning from [PENDING] to [CHECK_IF_SEEDING_NEEDED].' | |
| 2021-10-23 03:13:06.64 Server The state of the local availability replica in availability group 'MyDb2' has changed from 'PRIMARY_PENDING' to 'PRIMARY_NORMAL'. The state changed because the local replica has completed processing Online command from Windows Server Failover Clustering (WSFC). For more information, see the SQL Server error log or cluster log. If this is a Windows Server Failover Clustering (WSFC) availability group, you can also see the WSFC management console. | |
| 2021-10-23 03:13:06.67 Server The Service Broker endpoint is in disabled or stopped state. | |
| 2021-10-23 03:13:06.70 spid43s A connection for availability group 'MyDb3' from availability replica 'db-node-primary' with id [8210.9A-D04D-46E8-8BEC-B7FC49CDDA43] to 'db-node-secondary' with id [E2714CDA-B751-4BAF-BD7D-E706DDCA874F] has been successfully established. This is an informational message only. No user action is required. | |
| 2021-10-23 03:13:06.70 Server Started listening on virtual network name 'MyDb4'. No user action is required. | |
| 2021-10-23 03:13:06.72 spid169s The availability group database "MyDb2ging" is changing roles from "RESOLVING" to "PRIMARY" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required. | |
| 2021-10-23 03:13:06.72 Server The Service Broker endpoint is in disabled or stopped state. | |
| 2021-10-23 03:13:06.75 spid169s State information for database 'MyDb2ging' - Hardened Lsn: '(6426:15218:1)' Commit LSN: '(6426:14355:16)' Commit Time: 'Oct 22 2021 4:00AM' | |
| 2021-10-23 03:13:06.75 Server The Service Broker endpoint is in disabled or stopped state. | |
| 2021-10-23 03:13:06.76 spid169s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:4 | |
| 2021-10-23 03:13:06.78 spid169s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:4 | |
| 2021-10-23 03:13:06.78 Server The Service Broker endpoint is in disabled or stopped state. | |
| 2021-10-23 03:13:06.79 spid310s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2C6D609-6B65-45A6-8027-3D1D37F6F144:1 | |
| 2021-10-23 03:13:06.86 spid61s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [CAD7453A-CE3E-4251-8EDA-10038D9FB820]->[E2C6D609-6B65-45A6-8027-3D1D37F6F144], database [MyDb4], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [E04C00DF-9C66-4FA0-973E-83E20F8A28CE]: Transitioning from [PENDING] to [CHECK_IF_SEEDING_NEEDED].' | |
| 2021-10-23 03:13:06.88 Server Started listening on virtual network name 'MyDb1'. No user action is required. | |
| 2021-10-23 03:13:06.94 spid48s A connection for availability group 'MyDb4' from availability replica 'db-node-primary' with id [CAD7453A-CE3E-4251-8EDA-10038D9FB820] to 'db-node-secondary' with id [E2C6D609-6B65-45A6-8027-3D1D37F6F144] has been successfully established. This is an informational message only. No user action is required. | |
| 2021-10-23 03:13:06.97 spid169s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:13:07.04 Server The Service Broker endpoint is in disabled or stopped state. | |
| 2021-10-23 03:13:07.12 Server The Service Broker endpoint is in disabled or stopped state. | |
| 2021-10-23 03:13:07.16 Server The Service Broker endpoint is in disabled or stopped state. | |
| 2021-10-23 03:13:07.19 Server The Service Broker endpoint is in disabled or stopped state. | |
| 2021-10-23 03:13:07.22 Server Started listening on virtual network name 'MyDb3'. No user action is required. | |
| 2021-10-23 03:13:07.27 Server Started listening on virtual network name 'MyDb2'. No user action is required. | |
| 2021-10-23 03:13:07.41 spid272s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 604EBD17-9BC4-4480-90DF-CA446489E6B5:1 | |
| 2021-10-23 03:13:07.41 spid272s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 604EBD17-9BC4-4480-90DF-CA446489E6B5:1 | |
| 2021-10-23 03:13:07.45 spid15s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [3B78D98A-354E-42E1-8FB1-539238E8BCEC]->[68820BCC-AD5C-40E0-9B9A-75BF95A677B5], database [MyDb2ging], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [410E84C0-C796-4BB5-A18C-E14BF4C5CAB6]: Transitioning from [PENDING] to [CHECK_IF_SEEDING_NEEDED].' | |
| 2021-10-23 03:13:07.54 spid71s A connection for availability group 'MyDb2' from availability replica 'db-node-primary' with id [3B78D98A-354E-42E1-8FB1-539238E8BCEC] to 'db-node-secondary' with id [68820BCC-AD5C-40E0-9B9A-75BF95A677B5] has been successfully established. This is an informational message only. No user action is required. | |
| 2021-10-23 03:13:07.57 spid71s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2714CDA-B751-4BAF-BD7D-E706DDCA874F:1 | |
| 2021-10-23 03:13:07.57 spid71s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2714CDA-B751-4BAF-BD7D-E706DDCA874F:1 | |
| 2021-10-23 03:13:07.91 spid48s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2C6D609-6B65-45A6-8027-3D1D37F6F144:1 | |
| 2021-10-23 03:13:07.91 spid48s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2C6D609-6B65-45A6-8027-3D1D37F6F144:1 | |
| 2021-10-23 03:13:07.97 spid29s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [43DE05A5-1C5E-4BA5-BD31-CD4D8E58AD62]->[604EBD17-9BC4-4480-90DF-CA446489E6B5], database [MyDb1], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [62EAFF1C-1A04-4BED-8A7C-D07381D3C8BE]: Transitioning from [CHECK_IF_SEEDING_NEEDED] to [CATCHUP].' | |
| 2021-10-23 03:13:08.19 spid43s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:13:08.19 spid43s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:13:08.31 spid69s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [8210.9A-D04D-46E8-8BEC-B7FC49CDDA43]->[E2714CDA-B751-4BAF-BD7D-E706DDCA874F], database [MyDb3itoring], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [21F30DC7-6175-441A-8651-045EDE08E2D9]: Transitioning from [CHECK_IF_SEEDING_NEEDED] to [CATCHUP].' | |
| 2021-10-23 03:13:08.50 spid71s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2714CDA-B751-4BAF-BD7D-E706DDCA874F:1 | |
| 2021-10-23 03:13:08.50 spid71s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2714CDA-B751-4BAF-BD7D-E706DDCA874F:1 | |
| 2021-10-23 03:13:08.50 spid71s Always On Availability Groups connection with secondary database established for primary database 'MyDb3itoring' on the availability replica 'db-node-secondary' with Replica ID: {e2714cda-b751-4baf-bd7d-e706ddca874f}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:13:08.52 spid73s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [CAD7453A-CE3E-4251-8EDA-10038D9FB820]->[E2C6D609-6B65-45A6-8027-3D1D37F6F144], database [MyDb4], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [E04C00DF-9C66-4FA0-973E-83E20F8A28CE]: Transitioning from [CHECK_IF_SEEDING_NEEDED] to [CATCHUP].' | |
| 2021-10-23 03:13:08.53 spid272s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 604EBD17-9BC4-4480-90DF-CA446489E6B5:1 | |
| 2021-10-23 03:13:08.53 spid272s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 604EBD17-9BC4-4480-90DF-CA446489E6B5:1 | |
| 2021-10-23 03:13:08.53 spid272s Always On Availability Groups connection with secondary database established for primary database 'MyDb1' on the availability replica 'db-node-secondary' with Replica ID: {604ebd17-9bc4-4480-90df-ca446489e6b5}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:13:08.61 spid71s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2714CDA-B751-4BAF-BD7D-E706DDCA874F:1 | |
| 2021-10-23 03:13:08.70 spid80s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [3B78D98A-354E-42E1-8FB1-539238E8BCEC]->[68820BCC-AD5C-40E0-9B9A-75BF95A677B5], database [MyDb2ging], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [410E84C0-C796-4BB5-A18C-E14BF4C5CAB6]: Transitioning from [CHECK_IF_SEEDING_NEEDED] to [CATCHUP].' | |
| 2021-10-23 03:13:08.75 spid272s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 604EBD17-9BC4-4480-90DF-CA446489E6B5:1 | |
| 2021-10-23 03:13:09.05 spid65s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [8210.9A-D04D-46E8-8BEC-B7FC49CDDA43]->[E2714CDA-B751-4BAF-BD7D-E706DDCA874F], database [MyDb3itoring], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [21F30DC7-6175-441A-8651-045EDE08E2D9]: Transitioning from [CATCHUP] to [COMPLETED].' | |
| 2021-10-23 03:13:09.05 spid36s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2714CDA-B751-4BAF-BD7D-E706DDCA874F:1 | |
| 2021-10-23 03:13:09.24 spid29s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [43DE05A5-1C5E-4BA5-BD31-CD4D8E58AD62]->[604EBD17-9BC4-4480-90DF-CA446489E6B5], database [MyDb1], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [62EAFF1C-1A04-4BED-8A7C-D07381D3C8BE]: Transitioning from [CATCHUP] to [COMPLETED].' | |
| 2021-10-23 03:13:09.25 spid272s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 604EBD17-9BC4-4480-90DF-CA446489E6B5:1 | |
| 2021-10-23 03:13:09.50 spid48s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2C6D609-6B65-45A6-8027-3D1D37F6F144:1 | |
| 2021-10-23 03:13:09.50 spid48s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2C6D609-6B65-45A6-8027-3D1D37F6F144:1 | |
| 2021-10-23 03:13:09.50 spid48s Always On Availability Groups connection with secondary database established for primary database 'MyDb4' on the availability replica 'db-node-secondary' with Replica ID: {e2c6d609-6b65-45a6-8027-3d1d37f6f144}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:13:09.62 spid48s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2C6D609-6B65-45A6-8027-3D1D37F6F144:1 | |
| 2021-10-23 03:13:09.81 spid43s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:13:09.81 spid43s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:13:09.81 spid43s Always On Availability Groups connection with secondary database established for primary database 'MyDb2ging' on the availability replica 'db-node-secondary' with Replica ID: {68820bcc-ad5c-40e0-9b9a-75bf95a677b5}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:13:09.95 spid43s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:13:10.09 spid84s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [CAD7453A-CE3E-4251-8EDA-10038D9FB820]->[E2C6D609-6B65-45A6-8027-3D1D37F6F144], database [MyDb4], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [E04C00DF-9C66-4FA0-973E-83E20F8A28CE]: Transitioning from [CATCHUP] to [COMPLETED].' | |
| 2021-10-23 03:13:10.09 spid65s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2C6D609-6B65-45A6-8027-3D1D37F6F144:1 | |
| 2021-10-23 03:13:10.19 spid36s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2714CDA-B751-4BAF-BD7D-E706DDCA874F:4 | |
| 2021-10-23 03:13:10.19 spid36s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2714CDA-B751-4BAF-BD7D-E706DDCA874F:4 | |
| 2021-10-23 03:13:10.19 spid36s DbMgrPartnerCommitPolicy::SetSyncState: E2714CDA-B751-4BAF-BD7D-E706DDCA874F:4 | |
| 2021-10-23 03:13:10.19 spid36s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:13:10.21 spid80s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [3B78D98A-354E-42E1-8FB1-539238E8BCEC]->[68820BCC-AD5C-40E0-9B9A-75BF95A677B5], database [MyDb2ging], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [410E84C0-C796-4BB5-A18C-E14BF4C5CAB6]: Transitioning from [CATCHUP] to [COMPLETED].' | |
| 2021-10-23 03:13:10.31 spid272s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 604EBD17-9BC4-4480-90DF-CA446489E6B5:4 | |
| 2021-10-23 03:13:10.31 spid272s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 604EBD17-9BC4-4480-90DF-CA446489E6B5:4 | |
| 2021-10-23 03:13:10.31 spid272s DbMgrPartnerCommitPolicy::SetSyncState: 604EBD17-9BC4-4480-90DF-CA446489E6B5:4 | |
| 2021-10-23 03:13:10.96 spid36s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:4 | |
| 2021-10-23 03:13:10.96 spid36s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:4 | |
| 2021-10-23 03:13:10.96 spid36s DbMgrPartnerCommitPolicy::SetSyncState: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:4 | |
| 2021-10-23 03:13:11.16 spid65s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2C6D609-6B65-45A6-8027-3D1D37F6F144:4 | |
| 2021-10-23 03:13:11.16 spid65s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2C6D609-6B65-45A6-8027-3D1D37F6F144:4 | |
| 2021-10-23 03:13:11.16 spid65s DbMgrPartnerCommitPolicy::SetSyncState: E2C6D609-6B65-45A6-8027-3D1D37F6F144:4 | |
| 2021-10-23 03:13:48.53 Server The Service Broker endpoint is in disabled or stopped state. | |
| 2021-10-23 03:13:48.69 Server The Service Broker endpoint is in disabled or stopped state. | |
| 2021-10-23 03:13:48.79 Server The Service Broker endpoint is in disabled or stopped state. | |
| 2021-10-23 03:13:48.85 Server The Service Broker endpoint is in disabled or stopped state. | |
| 2021-10-23 03:16:30.63 spid259s Always On Availability Groups connection with secondary database terminated for primary database 'MyDb2ging' on the availability replica 'db-node-secondary' with Replica ID: {68820bcc-ad5c-40e0-9b9a-75bf95a677b5}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:16:30.63 spid65s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:4 | |
| 2021-10-23 03:16:33.47 spid48s A connection for availability group 'MyDb2' from availability replica 'db-node-primary' with id [3B78D98A-354E-42E1-8FB1-539238E8BCEC] to 'db-node-secondary' with id [68820BCC-AD5C-40E0-9B9A-75BF95A677B5] has been successfully established. This is an informational message only. No user action is required. | |
| 2021-10-23 03:16:51.77 Server Error: 19421, Severity: 16, State: 1. | |
| 2021-10-23 03:16:51.77 Server SQL Server hosting availability group 'MyDb4' did not receive a process event signal from the Windows Server Failover Cluster within the lease timeout period. | |
| 2021-10-23 03:16:51.82 Server Error: 19421, Severity: 16, State: 1. | |
| 2021-10-23 03:16:51.82 Server SQL Server hosting availability group 'MyDb3' did not receive a process event signal from the Windows Server Failover Cluster within the lease timeout period. | |
| 2021-10-23 03:16:51.82 Server Error: 19407, Severity: 16, State: 1. | |
| 2021-10-23 03:16:51.82 Server The lease between availability group 'MyDb4' and the Windows Server Failover Cluster has expired. A connectivity issue occurred between the instance of SQL Server and the Windows Server Failover Cluster. To determine whether the availability group is failing over correctly, check the corresponding availability group resource in the Windows Server Failover Cluster. | |
| 2021-10-23 03:16:51.82 Server Error: 19407, Severity: 16, State: 1. | |
| 2021-10-23 03:16:51.82 Server The lease between availability group 'MyDb3' and the Windows Server Failover Cluster has expired. A connectivity issue occurred between the instance of SQL Server and the Windows Server Failover Cluster. To determine whether the availability group is failing over correctly, check the corresponding availability group resource in the Windows Server Failover Cluster. | |
| 2021-10-23 03:16:51.82 Server Always On: The local replica of availability group 'MyDb4' is going offline because either the lease expired or lease renewal failed. This is an informational message only. No user action is required. | |
| 2021-10-23 03:16:51.82 Server Always On: The local replica of availability group 'MyDb3' is going offline because either the lease expired or lease renewal failed. This is an informational message only. No user action is required. | |
| 2021-10-23 03:16:51.82 Server The state of the local availability replica in availability group 'MyDb4' has changed from 'PRIMARY_NORMAL' to 'RESOLVING_NORMAL'. The state changed because the lease between the local availability replica and Windows Server Failover Clustering (WSFC) has expired. For more information, see the SQL Server error log or cluster log. If this is a Windows Server Failover Clustering (WSFC) availability group, you can also see the WSFC management console. | |
| 2021-10-23 03:16:51.82 Server The state of the local availability replica in availability group 'MyDb3' has changed from 'PRIMARY_NORMAL' to 'RESOLVING_NORMAL'. The state changed because the lease between the local availability replica and Windows Server Failover Clustering (WSFC) has expired. For more information, see the SQL Server error log or cluster log. If this is a Windows Server Failover Clustering (WSFC) availability group, you can also see the WSFC management console. | |
| 2021-10-23 03:16:51.91 spid310s Always On Availability Groups connection with secondary database terminated for primary database 'MyDb4' on the availability replica 'db-node-secondary' with Replica ID: {e2c6d609-6b65-45a6-8027-3d1d37f6f144}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:16:52.05 Server Error: 19421, Severity: 16, State: 1. | |
| 2021-10-23 03:16:52.05 Server SQL Server hosting availability group 'MyDb1' did not receive a process event signal from the Windows Server Failover Cluster within the lease timeout period. | |
| 2021-10-23 03:16:52.27 spid300s Remote harden of transaction 'GhostCleanupTask' (ID 0x000000000f362cfb 0000:24714058) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57776:117) failed. | |
| 2021-10-23 03:16:52.27 Server Error: 19407, Severity: 16, State: 1. | |
| 2021-10-23 03:16:52.27 Server The lease between availability group 'MyDb1' and the Windows Server Failover Cluster has expired. A connectivity issue occurred between the instance of SQL Server and the Windows Server Failover Cluster. To determine whether the availability group is failing over correctly, check the corresponding availability group resource in the Windows Server Failover Cluster. | |
| 2021-10-23 03:16:52.27 Server Always On: The local replica of availability group 'MyDb1' is going offline because either the lease expired or lease renewal failed. This is an informational message only. No user action is required. | |
| 2021-10-23 03:16:52.27 Server The state of the local availability replica in availability group 'MyDb1' has changed from 'PRIMARY_NORMAL' to 'RESOLVING_NORMAL'. The state changed because the lease between the local availability replica and Windows Server Failover Clustering (WSFC) has expired. For more information, see the SQL Server error log or cluster log. If this is a Windows Server Failover Clustering (WSFC) availability group, you can also see the WSFC management console. | |
| 2021-10-23 03:16:52.72 spid335s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2C6D609-6B65-45A6-8027-3D1D37F6F144:4 | |
| 2021-10-23 03:16:52.72 spid334s The availability group database "MyDb4" is changing roles from "PRIMARY" to "RESOLVING" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required. | |
| 2021-10-23 03:16:52.72 spid335s Always On Availability Groups connection with secondary database terminated for primary database 'MyDb3itoring' on the availability replica 'db-node-secondary' with Replica ID: {e2714cda-b751-4baf-bd7d-e706ddca874f}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:16:52.93 spid333s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2714CDA-B751-4BAF-BD7D-E706DDCA874F:4 | |
| 2021-10-23 03:16:52.93 spid333s The availability group database "MyDb3itoring" is changing roles from "PRIMARY" to "RESOLVING" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required. | |
| 2021-10-23 03:16:53.74 spid59 Remote harden of transaction 'INSERT' (ID 0x000000000f362cfa 0000:24714057) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57776:115) failed. | |
| 2021-10-23 03:16:53.74 spid336s Always On Availability Groups connection with secondary database terminated for primary database 'MyDb1' on the availability replica 'db-node-secondary' with Replica ID: {604ebd17-9bc4-4480-90df-ca446489e6b5}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:16:53.94 spid337s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 604EBD17-9BC4-4480-90DF-CA446489E6B5:4 | |
| 2021-10-23 03:16:53.94 spid337s The availability group database "MyDb1" is changing roles from "PRIMARY" to "RESOLVING" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required. | |
| 2021-10-23 03:16:55.73 spid318 Remote harden of transaction 'UPDATE' (ID 0x000000000f362d16 0000:2471405b) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57820:6) failed. | |
| 2021-10-23 03:16:55.94 spid97 Remote harden of transaction 'user_transaction' (ID 0x000000000f362dab 0000:24714073) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57820:137) failed. | |
| 2021-10-23 03:16:58.34 spid270 Remote harden of transaction 'UPDATE' (ID 0x000000000f362d34 0000:2471405d) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57820:12) failed. | |
| 2021-10-23 03:16:58.95 spid233 Remote harden of transaction 'INSERT' (ID 0x000000000f362d41 0000:2471405f) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57820:19) failed. | |
| 2021-10-23 03:16:59.56 spid57 Remote harden of transaction 'user_transaction' (ID 0x000000000f362b0a 0000:24714034) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57820:16) failed. | |
| 2021-10-23 03:17:02.20 spid183 Remote harden of transaction 'user_transaction' (ID 0x000000000f362bcf 0000:2471405a) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57896:5) failed. | |
| 2021-10-23 03:17:02.61 spid294 Remote harden of transaction 'UPDATE' (ID 0x000000000f362d69 0000:24714065) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57820:46) failed. | |
| 2021-10-23 03:17:02.76 spid279 Remote harden of transaction 'UPDATE' (ID 0x000000000f362c1c 0000:2471403d) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57776:43) failed. | |
| 2021-10-23 03:17:02.77 spid315 Remote harden of transaction 'UPDATE' (ID 0x000000000f362d2f 0000:2471405c) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57820:9) failed. | |
| 2021-10-23 03:17:02.77 spid307 Remote harden of transaction 'UPDATE' (ID 0x000000000f362da6 0000:2471406c) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57820:85) failed. | |
| 2021-10-23 03:17:02.77 spid98 Remote harden of transaction 'UPDATE' (ID 0x000000000f362c41 0000:24714042) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57776:57) failed. | |
| 2021-10-23 03:17:02.77 spid129 Remote harden of transaction 'user_transaction' (ID 0x000000000f362bb5 0000:24714059) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57898:2) failed. | |
| 2021-10-23 03:17:02.84 spid293 Remote harden of transaction 'user_transaction' (ID 0x000000000f362c49 0000:2471405e) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57899:2) failed. | |
| 2021-10-23 03:17:02.85 spid133 Remote harden of transaction 'user_transaction' (ID 0x000000000f362b3f 0000:24714035) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57900:2) failed. | |
| 2021-10-23 03:17:02.85 spid256 Remote harden of transaction 'INSERT' (ID 0x000000000f362c85 0000:2471404a) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57776:81) failed. | |
| 2021-10-23 03:17:02.86 spid224 Remote harden of transaction 'UPDATE' (ID 0x000000000f362c7d 0000:24714049) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57776:78) failed. | |
| 2021-10-23 03:17:03.28 spid231 Remote harden of transaction 'user_transaction' (ID 0x000000000f362ac0 0000:24714045) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57820:15) failed. | |
| 2021-10-23 03:17:03.28 spid207 Remote harden of transaction 'user_transaction' (ID 0x000000000f362c3b 0000:2471406f) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57902:2) failed. | |
| 2021-10-23 03:17:04.17 spid144 Remote harden of transaction 'user_transaction' (ID 0x000000000f362b5b 0000:2471403f) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57901:2) failed. | |
| 2021-10-23 03:17:04.61 spid227 Remote harden of transaction 'user_transaction' (ID 0x000000000f362c8c 0000:24714066) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57904:2) failed. | |
| 2021-10-23 03:17:04.65 spid276 Remote harden of transaction 'user_transaction' (ID 0x000000000f362c69 0000:24714061) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57903:2) failed. | |
| 2021-10-23 03:17:04.66 spid119 Remote harden of transaction 'user_transaction' (ID 0x000000000f362b4a 0000:2471404f) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57820:54) failed. | |
| 2021-10-23 03:17:04.67 spid320 Remote harden of transaction 'user_transaction' (ID 0x000000000f362b66 0000:24714052) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57820:59) failed. | |
| 2021-10-23 03:17:04.70 spid72 Remote harden of transaction 'user_transaction' (ID 0x000000000f362c6b 0000:24714062) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57905:2) failed. | |
| 2021-10-23 03:17:04.70 spid322 Remote harden of transaction 'INSERT' (ID 0x000000000f362d79 0000:24714068) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57820:53) failed. | |
| 2021-10-23 03:17:04.72 spid319 Remote harden of transaction 'UPDATE' (ID 0x000000000f362cd1 0000:24714053) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57776:104) failed. | |
| 2021-10-23 03:17:05.35 spid83 Remote harden of transaction 'user_transaction' (ID 0x000000000f362c8b 0000:24714067) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57906:2) failed. | |
| 2021-10-23 03:17:05.35 spid196 Remote harden of transaction 'user_transaction' (ID 0x000000000f362b53 0000:24714050) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57820:90) failed. | |
| 2021-10-23 03:17:05.35 spid48s Always On Availability Groups connection with secondary database terminated for primary database 'MyDb2ging' on the availability replica 'db-node-secondary' with Replica ID: {68820bcc-ad5c-40e0-9b9a-75bf95a677b5}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:17:05.36 spid324 Remote harden of transaction 'UPDATE' (ID 0x000000000f362d93 0000:24714069) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57820:58) failed. | |
| 2021-10-23 03:17:05.36 spid103 Remote harden of transaction 'user_transaction' (ID 0x000000000f362b94 0000:2471404c) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57820:55) failed. | |
| 2021-10-23 03:17:05.43 spid313 Remote harden of transaction 'UPDATE' (ID 0x000000000f362ce9 0000:24714055) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57776:110) failed. | |
| 2021-10-23 03:17:06.37 spid106 Remote harden of transaction 'DELETE' (ID 0x000000000f362d9d 0000:2471406a) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57820:79) failed. | |
| 2021-10-23 03:17:06.77 spid241 Remote harden of transaction 'user_transaction' (ID 0x000000000f362ccf 0000:24714071) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57907:5) failed. | |
| 2021-10-23 03:17:07.46 spid87 Remote harden of transaction 'user_transaction' (ID 0x000000000f362dce 0000:24714072) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57820:108) failed. | |
| 2021-10-23 03:17:07.46 spid305 Remote harden of transaction 'UPDATE' (ID 0x000000000f362e22 0000:24714075) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57820:117) failed. | |
| 2021-10-23 03:17:07.55 spid280 Remote harden of transaction 'INSERT' (ID 0x000000000f362d4e 0000:24714060) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57820:22) failed. | |
| 2021-10-23 03:17:07.59 spid274 Remote harden of transaction 'INSERT' (ID 0x000000000f362d67 0000:24714063) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57820:43) failed. | |
| 2021-10-23 03:17:08.09 spid153 Remote harden of transaction 'UPDATE' (ID 0x000000000f362da2 0000:2471406b) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57820:82) failed. | |
| 2021-10-23 03:17:08.55 spid192 Remote harden of transaction 'user_transaction' (ID 0x000000000f362cd2 0000:24714076) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57910:2) failed. | |
| 2021-10-23 03:17:09.97 spid190 Remote harden of transaction 'user_transaction' (ID 0x000000000f362d94 0000:2471406e) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57820:95) failed. | |
| 2021-10-23 03:17:10.36 spid211 Remote harden of transaction 'user_transaction' (ID 0x000000000f362d90 0000:2471406d) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57911:2) failed. | |
| 2021-10-23 03:17:10.36 spid267 Remote harden of transaction 'UPDATE' (ID 0x000000000f362e34 0000:24714077) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57820:124) failed. | |
| 2021-10-23 03:17:10.77 spid281 Remote harden of transaction 'user_transaction' (ID 0x000000000f362dad 0000:24714070) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57820:107) failed. | |
| 2021-10-23 03:17:12.95 spid333s State information for database 'MyDb3itoring' - Hardened Lsn: '(37808:21885:1)' Commit LSN: '(37782:15663:3)' Commit Time: 'Oct 22 2021 4:53AM' | |
| 2021-10-23 03:17:12.98 spid337s State information for database 'MyDb1' - Hardened Lsn: '(50177:57820:1)' Commit LSN: '(50166:107296:3)' Commit Time: 'Oct 22 2021 4:53AM' | |
| 2021-10-23 03:17:15.13 Server Stopped listening on listener network name 'MyDb4' (VNN or DISTRIBUTED_NETWORK_NAME). No user action is required. | |
| 2021-10-23 03:17:15.16 spid124 Remote harden of transaction 'UPDATE' (ID 0x000000000f362e3f 0000:24714078) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57820:127) failed. | |
| 2021-10-23 03:17:15.19 spid271 Remote harden of transaction 'UPDATE' (ID 0x000000000f362e00 0000:24714074) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57912:14) failed. | |
| 2021-10-23 03:17:15.23 spid334s State information for database 'MyDb4' - Hardened Lsn: '(44334:303:1)' Commit LSN: '(44321:5809:3)' Commit Time: 'Oct 22 2021 4:53AM' | |
| 2021-10-23 03:17:20.38 spid48s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2714CDA-B751-4BAF-BD7D-E706DDCA874F:4 | |
| 2021-10-23 03:17:20.46 spid337s Process ID 271 was killed by an ABORT_AFTER_WAIT = BLOCKERS DDL statement on database_id = 7, object_id = 0. | |
| 2021-10-23 03:17:20.49 spid48s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 604EBD17-9BC4-4480-90DF-CA446489E6B5:4 | |
| 2021-10-23 03:17:20.77 Server Stopped listening on listener network name 'MyDb1' (VNN or DISTRIBUTED_NETWORK_NAME). No user action is required. | |
| 2021-10-23 03:17:20.85 spid333s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: E2C6D609-6B65-45A6-8027-3D1D37F6F144:4 | |
| 2021-10-23 03:17:21.67 spid204 Remote harden of transaction 'user_transaction' (ID 0x000000000f362bb3 0000:24714056) started at Oct 23 2021 3:16AM in database 'MyDb1' at LSN (50177:57915:2) failed. | |
| 2021-10-23 03:17:21.71 spid337s Process ID 204 was killed by an ABORT_AFTER_WAIT = BLOCKERS DDL statement on database_id = 7, object_id = 0. | |
| 2021-10-23 03:17:21.94 spid330s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [3B78D98A-354E-42E1-8FB1-539238E8BCEC]->[68820BCC-AD5C-40E0-9B9A-75BF95A677B5], database [MyDb2ging], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [49C715D9-C1FC-4E18-B06F-D76EFBAE8753]: Transitioning from [PENDING] to [CHECK_IF_SEEDING_NEEDED].' | |
| 2021-10-23 03:17:21.94 Server Stopped listening on listener network name 'MyDb3' (VNN or DISTRIBUTED_NETWORK_NAME). No user action is required. | |
| 2021-10-23 03:17:21.96 Server The Service Broker endpoint is in disabled or stopped state. | |
| 2021-10-23 03:17:22.10 spid21s Remote harden of transaction 'GhostCleanupTask' (ID 0x000000000f362ec1 0000:24714079) started at Oct 23 2021 3:17AM in database 'MyDb1' at LSN (50177:57916:24) failed. | |
| 2021-10-23 03:17:22.22 Server The Service Broker endpoint is in disabled or stopped state. | |
| 2021-10-23 03:17:22.40 spid65s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:17:22.40 spid65s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:17:22.40 spid65s DbMgrPartnerCommitPolicy::SetSyncState: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:17:22.51 Server The Service Broker endpoint is in disabled or stopped state. | |
| 2021-10-23 03:17:22.54 spid36s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:17:22.59 spid36s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:17:22.59 spid36s Always On Availability Groups connection with secondary database established for primary database 'MyDb2ging' on the availability replica 'db-node-secondary' with Replica ID: {68820bcc-ad5c-40e0-9b9a-75bf95a677b5}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:17:22.72 spid36s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:17:23.64 spid57 Always On: The local replica of availability group 'MyDb2' is preparing to transition to the resolving role. This is an informational message only. No user action is required. | |
| 2021-10-23 03:17:23.72 Server The availability group 'MyDb2' is being asked to stop the lease renewal because the availability group is going offline. This is an informational message only. No user action is required. | |
| 2021-10-23 03:17:23.72 spid57 The state of the local availability replica in availability group 'MyDb2' has changed from 'PRIMARY_NORMAL' to 'RESOLVING_NORMAL'. The state changed because the availability group is going offline. The replica is going offline because the associated availability group has been deleted, or the user has taken the associated availability group offline in Windows Server Failover Clustering (WSFC) management console, or the availability group is failing over to another SQL Server instance. For more information, see the SQL Server error log or cluster log. If this is a Windows Server Failover Clustering (WSFC) availability group, you can also see the WSFC management console. | |
| 2021-10-23 03:17:23.78 spid332s Always On Availability Groups connection with secondary database terminated for primary database 'MyDb2ging' on the availability replica 'db-node-secondary' with Replica ID: {68820bcc-ad5c-40e0-9b9a-75bf95a677b5}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:17:23.78 spid36s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:17:23.78 spid36s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:17:23.78 spid36s Always On Availability Groups connection with secondary database established for primary database 'MyDb2ging' on the availability replica 'db-node-secondary' with Replica ID: {68820bcc-ad5c-40e0-9b9a-75bf95a677b5}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:17:23.81 spid334s The availability group database "MyDb2ging" is changing roles from "PRIMARY" to "RESOLVING" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required. | |
| 2021-10-23 03:17:23.85 spid36s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:17:23.85 spid36s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:17:23.85 spid36s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:17:23.85 spid36s Always On Availability Groups connection with secondary database established for primary database 'MyDb2ging' on the availability replica 'db-node-secondary' with Replica ID: {68820bcc-ad5c-40e0-9b9a-75bf95a677b5}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:17:23.92 spid36s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:17:23.94 spid334s State information for database 'MyDb2ging' - Hardened Lsn: '(6426:15218:1)' Commit LSN: '(6426:14355:16)' Commit Time: 'Oct 22 2021 4:00AM' | |
| 2021-10-23 03:17:24.02 spid52s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [3B78D98A-354E-42E1-8FB1-539238E8BCEC]->[68820BCC-AD5C-40E0-9B9A-75BF95A677B5], database [MyDb2ging], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [49C715D9-C1FC-4E18-B06F-D76EFBAE8753]: Check if seeding needed failed with result 0x000005b4.' | |
| 2021-10-23 03:17:24.06 spid52s Automatic seeding of availability database 'MyDb2ging' in availability group 'MyDb2' failed with a transient error. The operation will be retried. | |
| 2021-10-23 03:17:24.14 spid52s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [3B78D98A-354E-42E1-8FB1-539238E8BCEC]->[68820BCC-AD5C-40E0-9B9A-75BF95A677B5], database [MyDb2ging], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [49C715D9-C1FC-4E18-B06F-D76EFBAE8753]: Seeding task failed with result 0x80000000.' | |
| 2021-10-23 03:17:24.14 spid52s Always On: DebugTraceVarArgs AR 'Seeding is canceled with cancelReason = 108' | |
| 2021-10-23 03:17:24.14 spid52s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [3B78D98A-354E-42E1-8FB1-539238E8BCEC]->[68820BCC-AD5C-40E0-9B9A-75BF95A677B5], database [MyDb2ging], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [49C715D9-C1FC-4E18-B06F-D76EFBAE8753]: Transitioning from [CHECK_IF_SEEDING_NEEDED] to [FAILED].' | |
| 2021-10-23 03:17:25.51 spid56 Always On: The local replica of availability group 'MyDb1' is preparing to transition to the resolving role. This is an informational message only. No user action is required. | |
| 2021-10-23 03:17:26.15 Server Stopped listening on listener network name 'MyDb2' (VNN or DISTRIBUTED_NETWORK_NAME). No user action is required. | |
| 2021-10-23 03:17:26.23 spid52s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [3B78D98A-354E-42E1-8FB1-539238E8BCEC]->[68820BCC-AD5C-40E0-9B9A-75BF95A677B5], database [MyDb2ging], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [49C715D9-C1FC-4E18-B06F-D76EFBAE8753]: Seeding encountered a transient failure, state '108', retrying...' | |
| 2021-10-23 03:17:26.23 spid52s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [3B78D98A-354E-42E1-8FB1-539238E8BCEC]->[68820BCC-AD5C-40E0-9B9A-75BF95A677B5], database [MyDb2ging], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [F620A77F-3592-4F7B-BAC6-B6427C29122D]: Transitioning from [PENDING] to [CHECK_IF_SEEDING_NEEDED].' | |
| 2021-10-23 03:17:26.25 spid16s Attempt to access non-existent or uninitialized availability group with ID '{E89FADFA-FF87-4C0F-8230-23A730E4DAC1}.'. This is usually an internal condition, such as the availability group is being dropped or the local WSFC node has lost quorum. In such cases, and no user action is required. | |
| 2021-10-23 03:17:26.25 spid16s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [3B78D98A-354E-42E1-8FB1-539238E8BCEC]->[68820BCC-AD5C-40E0-9B9A-75BF95A677B5], database [MyDb2ging], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [F620A77F-3592-4F7B-BAC6-B6427C29122D]: Seeding task failed with result 0x80000000.' | |
| 2021-10-23 03:17:26.25 spid16s Always On: DebugTraceVarArgs AR 'Seeding is canceled with cancelReason = 2' | |
| 2021-10-23 03:17:26.26 spid16s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [3B78D98A-354E-42E1-8FB1-539238E8BCEC]->[68820BCC-AD5C-40E0-9B9A-75BF95A677B5], database [MyDb2ging], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [F620A77F-3592-4F7B-BAC6-B6427C29122D]: Transitioning from [CHECK_IF_SEEDING_NEEDED] to [FAILED].' | |
| 2021-10-23 03:17:26.29 spid45s The state of the local availability replica in availability group 'MyDb3' has changed from 'RESOLVING_NORMAL' to 'SECONDARY_NORMAL'. The state changed because the availability group state has changed in Windows Server Failover Clustering (WSFC). For more information, see the SQL Server error log or cluster log. If this is a Windows Server Failover Clustering (WSFC) availability group, you can also see the WSFC management console. | |
| 2021-10-23 03:17:26.44 spid334s A connection for availability group 'MyDb3' from availability replica 'db-node-primary' with id [8210.9A-D04D-46E8-8BEC-B7FC49CDDA43] to 'db-node-secondary' with id [E2714CDA-B751-4BAF-BD7D-E706DDCA874F] has been successfully established. This is an informational message only. No user action is required. | |
| 2021-10-23 03:17:27.59 spid47s The state of the local availability replica in availability group 'MyDb4' has changed from 'RESOLVING_NORMAL' to 'SECONDARY_NORMAL'. The state changed because the availability group state has changed in Windows Server Failover Clustering (WSFC). For more information, see the SQL Server error log or cluster log. If this is a Windows Server Failover Clustering (WSFC) availability group, you can also see the WSFC management console. | |
| 2021-10-23 03:17:27.75 spid331s The availability group database "MyDb3itoring" is changing roles from "RESOLVING" to "SECONDARY" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required. | |
| 2021-10-23 03:17:27.75 spid331s State information for database 'MyDb3itoring' - Hardened Lsn: '(37808:21885:1)' Commit LSN: '(37782:15663:3)' Commit Time: 'Oct 22 2021 4:53AM' | |
| 2021-10-23 03:17:27.75 spid332s A connection for availability group 'MyDb4' from availability replica 'db-node-primary' with id [CAD7453A-CE3E-4251-8EDA-10038D9FB820] to 'db-node-secondary' with id [E2C6D609-6B65-45A6-8027-3D1D37F6F144] has been successfully established. This is an informational message only. No user action is required. | |
| 2021-10-23 03:17:27.76 spid50s Always On: DebugTraceVarArgs AR '[HADR] [Secondary] operation on replicas [E2714CDA-B751-4BAF-BD7D-E706DDCA874F]->[8210.9A-D04D-46E8-8BEC-B7FC49CDDA43], database [MyDb3itoring], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [F0F2C4D9-DD54-4A8D-A361-B717379E08E8]: Transitioning from [PENDING] to [CHECK_IF_SEEDING_NEEDED].' | |
| 2021-10-23 03:17:27.77 spid16s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [3B78D98A-354E-42E1-8FB1-539238E8BCEC]->[68820BCC-AD5C-40E0-9B9A-75BF95A677B5], database [MyDb2ging], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [F620A77F-3592-4F7B-BAC6-B6427C29122D]: Seeding failed with error code '41180', state '25'' | |
| 2021-10-23 03:17:29.51 spid16s Error: 41145, Severity: 16, State: 1. | |
| 2021-10-23 03:17:29.51 spid16s Cannot join database 'MyDb3itoring' to availability group 'MyDb3'. The database has already joined the availability group. This is an informational message. No user action is required. | |
| 2021-10-23 03:17:29.59 spid16s Always On: DebugTraceVarArgs AR '[HADR] [Secondary] operation on replicas [E2714CDA-B751-4BAF-BD7D-E706DDCA874F]->[8210.9A-D04D-46E8-8BEC-B7FC49CDDA43], database [MyDb3itoring], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [F0F2C4D9-DD54-4A8D-A361-B717379E08E8]: Transitioning from [CHECK_IF_SEEDING_NEEDED] to [CATCHUP].' | |
| 2021-10-23 03:17:29.61 spid16s Always On: DebugTraceVarArgs AR 'Processing BuildReplicaCatchup event with HADR Role: [SECONDARY]' | |
| 2021-10-23 03:17:29.61 spid16s Always On: DebugTraceVarArgs AR '[HADR] [Secondary] operation on replicas [E2714CDA-B751-4BAF-BD7D-E706DDCA874F]->[8210.9A-D04D-46E8-8BEC-B7FC49CDDA43], database [MyDb3itoring], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [F0F2C4D9-DD54-4A8D-A361-B717379E08E8]: Transitioning from [CATCHUP] to [COMPLETED].' | |
| 2021-10-23 03:17:30.08 spid297s Remote harden of transaction 'GhostCleanupTask' (ID 0x000000000f362f2a 0000:2471407b) started at Oct 23 2021 3:17AM in database 'MyDb1' at LSN (50177:57920:25) failed. | |
| 2021-10-23 03:17:30.78 spid36s The availability group database "MyDb4" is changing roles from "RESOLVING" to "SECONDARY" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required. | |
| 2021-10-23 03:17:30.81 spid36s State information for database 'MyDb4' - Hardened Lsn: '(44334:303:1)' Commit LSN: '(44321:5809:3)' Commit Time: 'Oct 22 2021 4:53AM' | |
| 2021-10-23 03:17:30.83 spid16s Always On: DebugTraceVarArgs AR '[HADR] [Secondary] operation on replicas [E2C6D609-6B65-45A6-8027-3D1D37F6F144]->[CAD7453A-CE3E-4251-8EDA-10038D9FB820], database [MyDb4], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [A0DC1275-CD8C-4D22-9141-7DA71CB5C413]: Transitioning from [PENDING] to [CHECK_IF_SEEDING_NEEDED].' | |
| 2021-10-23 03:17:38.69 spid21s Error: 41145, Severity: 16, State: 1. | |
| 2021-10-23 03:17:38.69 spid21s Cannot join database 'MyDb4' to availability group 'MyDb4'. The database has already joined the availability group. This is an informational message. No user action is required. | |
| 2021-10-23 03:17:38.69 spid21s Always On: DebugTraceVarArgs AR '[HADR] [Secondary] operation on replicas [E2C6D609-6B65-45A6-8027-3D1D37F6F144]->[CAD7453A-CE3E-4251-8EDA-10038D9FB820], database [MyDb4], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [A0DC1275-CD8C-4D22-9141-7DA71CB5C413]: Transitioning from [CHECK_IF_SEEDING_NEEDED] to [CATCHUP].' | |
| 2021-10-23 03:17:38.71 spid21s Always On: DebugTraceVarArgs AR 'Processing BuildReplicaCatchup event with HADR Role: [SECONDARY]' | |
| 2021-10-23 03:17:38.71 spid21s Always On: DebugTraceVarArgs AR '[HADR] [Secondary] operation on replicas [E2C6D609-6B65-45A6-8027-3D1D37F6F144]->[CAD7453A-CE3E-4251-8EDA-10038D9FB820], database [MyDb4], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [A0DC1275-CD8C-4D22-9141-7DA71CB5C413]: Transitioning from [CATCHUP] to [COMPLETED].' | |
| 2021-10-23 03:17:40.06 spid24s Remote harden of transaction 'GhostCleanupTask' (ID 0x000000000f3631cb 0000:2471407d) started at Oct 23 2021 3:17AM in database 'MyDb1' at LSN (50177:57925:25) failed. | |
| 2021-10-23 03:17:50.23 spid150s Remote harden of transaction 'GhostCleanupTask' (ID 0x000000000f363226 0000:2471407f) started at Oct 23 2021 3:17AM in database 'MyDb1' at LSN (50177:57929:25) failed. | |
| 2021-10-23 03:17:54.86 spid52 Always On: The local replica of availability group 'MyDb2' is preparing to transition to the primary role. This is an informational message only. No user action is required. | |
| 2021-10-23 03:17:58.04 spid332s State information for database 'MyDb4' - Hardened Lsn: '(44334:303:1)' Commit LSN: '(44321:5809:3)' Commit Time: 'Oct 22 2021 4:53AM' | |
| 2021-10-23 03:18:00.28 spid301s Remote harden of transaction 'GhostCleanupTask' (ID 0x000000000f36328a 0000:24714081) started at Oct 23 2021 3:18AM in database 'MyDb1' at LSN (50177:57934:25) failed. | |
| 2021-10-23 03:18:01.26 spid332s State information for database 'MyDb4' - Hardened Lsn: '(44334:303:1)' Commit LSN: '(44321:5809:3)' Commit Time: 'Oct 22 2021 4:53AM' | |
| 2021-10-23 03:18:01.59 spid52 The state of the local availability replica in availability group 'MyDb2' has changed from 'RESOLVING_NORMAL' to 'PRIMARY_PENDING'. The state changed because the availability group is coming online. For more information, see the SQL Server error log or cluster log. If this is a Windows Server Failover Clustering (WSFC) availability group, you can also see the WSFC management console. | |
| 2021-10-23 03:18:01.86 spid332s Starting up database 'MyDb4'. | |
| 2021-10-23 03:18:01.88 Server The lease worker of availability group 'MyDb2' is now sleeping the excess lease time (147391 ms) supplied during online. This is an informational message only. No user action is required. | |
| 2021-10-23 03:18:02.60 Server The Service Broker endpoint is in disabled or stopped state. | |
| 2021-10-23 03:18:02.60 Server Started listening on virtual network name 'MyDb2'. No user action is required. | |
| 2021-10-23 03:18:02.90 Server The state of the local availability replica in availability group 'MyDb2' has changed from 'PRIMARY_PENDING' to 'PRIMARY_NORMAL'. The state changed because the local replica has completed processing Online command from Windows Server Failover Clustering (WSFC). For more information, see the SQL Server error log or cluster log. If this is a Windows Server Failover Clustering (WSFC) availability group, you can also see the WSFC management console. | |
| 2021-10-23 03:18:03.06 spid332s Parallel redo is started for database 'MyDb4' with worker pool size [2]. | |
| 2021-10-23 03:18:03.88 spid331s The availability group database "MyDb2ging" is changing roles from "RESOLVING" to "PRIMARY" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required. | |
| 2021-10-23 03:18:03.89 spid331s State information for database 'MyDb2ging' - Hardened Lsn: '(6426:15218:1)' Commit LSN: '(6426:14355:16)' Commit Time: 'Oct 22 2021 4:00AM' | |
| 2021-10-23 03:18:04.80 Server The Service Broker endpoint is in disabled or stopped state. | |
| 2021-10-23 03:18:06.16 spid23s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [3B78D98A-354E-42E1-8FB1-539238E8BCEC]->[68820BCC-AD5C-40E0-9B9A-75BF95A677B5], database [MyDb2ging], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [68591461-C113-47FC-8B19-8416B1F40F6D]: Transitioning from [PENDING] to [CHECK_IF_SEEDING_NEEDED].' | |
| 2021-10-23 03:18:06.17 spid331s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:18:06.19 spid331s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:18:06.24 spid28s A connection for availability group 'MyDb2' from availability replica 'db-node-primary' with id [3B78D98A-354E-42E1-8FB1-539238E8BCEC] to 'db-node-secondary' with id [68820BCC-AD5C-40E0-9B9A-75BF95A677B5] has been successfully established. This is an informational message only. No user action is required. | |
| 2021-10-23 03:18:06.38 spid331s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:18:07.19 spid332s Recovery of database 'MyDb4' (8) is 4% complete (approximately 81 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required. | |
| 2021-10-23 03:18:07.78 spid22s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [3B78D98A-354E-42E1-8FB1-539238E8BCEC]->[68820BCC-AD5C-40E0-9B9A-75BF95A677B5], database [MyDb2ging], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [68591461-C113-47FC-8B19-8416B1F40F6D]: Transitioning from [CHECK_IF_SEEDING_NEEDED] to [CATCHUP].' | |
| 2021-10-23 03:18:09.06 spid332s Always On Availability Groups connection with primary database established for secondary database 'MyDb4' on the availability replica 'db-node-secondary' with Replica ID: {e2c6d609-6b65-45a6-8027-3d1d37f6f144}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:18:09.10 spid332s The recovery LSN (44334:303:1) was identified for the database with ID 8. This is an informational message only. No user action is required. | |
| 2021-10-23 03:18:09.51 spid332s Error: 35278, Severity: 17, State: 1. | |
| 2021-10-23 03:18:09.51 spid332s Availability database 'MyDb4', which is in the secondary role, is being restarted to resynchronize with the current primary database. This is an informational message only. No user action is required. | |
| 2021-10-23 03:18:09.54 spid332s Parallel redo is shutdown for database 'MyDb4' with worker pool size [2]. | |
| 2021-10-23 03:18:09.56 spid332s State information for database 'MyDb4' - Hardened Lsn: '(44334:305:1)' Commit LSN: '(44334:302:3)' Commit Time: 'Oct 23 2021 3:16AM' | |
| 2021-10-23 03:18:09.62 spid332s State information for database 'MyDb4' - Hardened Lsn: '(44334:305:1)' Commit LSN: '(44334:302:3)' Commit Time: 'Oct 23 2021 3:16AM' | |
| 2021-10-23 03:18:09.63 spid332s Starting up database 'MyDb4'. | |
| 2021-10-23 03:18:10.20 spid343s Remote harden of transaction 'GhostCleanupTask' (ID 0x000000000f3638d4 0000:24714083) started at Oct 23 2021 3:18AM in database 'MyDb1' at LSN (50177:57938:34) failed. | |
| 2021-10-23 03:18:10.37 spid331s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:18:10.37 spid331s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:18:10.48 spid332s Parallel redo is started for database 'MyDb4' with worker pool size [2]. | |
| 2021-10-23 03:18:10.54 spid331s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:18:10.54 spid331s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:18:10.54 spid331s Always On Availability Groups connection with secondary database established for primary database 'MyDb2ging' on the availability replica 'db-node-secondary' with Replica ID: {68820bcc-ad5c-40e0-9b9a-75bf95a677b5}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:18:10.54 spid331s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:18:10.65 spid22s Always On: DebugTraceVarArgs AR '[HADR] [Primary] operation on replicas [3B78D98A-354E-42E1-8FB1-539238E8BCEC]->[68820BCC-AD5C-40E0-9B9A-75BF95A677B5], database [MyDb2ging], remote endpoint [TCP://db-node-secondary.domain.local:5022], source operation [68591461-C113-47FC-8B19-8416B1F40F6D]: Transitioning from [CATCHUP] to [COMPLETED].' | |
| 2021-10-23 03:18:10.65 spid28s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:18:10.67 spid332s Always On Availability Groups connection with primary database established for secondary database 'MyDb4' on the availability replica 'db-node-secondary' with Replica ID: {e2c6d609-6b65-45a6-8027-3d1d37f6f144}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:18:10.71 spid332s The recovery LSN (44334:470:2) was identified for the database with ID 8. This is an informational message only. No user action is required. | |
| 2021-10-23 03:18:10.72 spid332s 75 transactions rolled forward in database 'MyDb4' (8:0). This is an informational message only. No user action is required. | |
| 2021-10-23 03:18:10.77 spid22s Always On Availability Groups connection with primary database established for secondary database 'MyDb4' on the availability replica 'db-node-secondary' with Replica ID: {e2c6d609-6b65-45a6-8027-3d1d37f6f144}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:18:10.78 spid28s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:4 | |
| 2021-10-23 03:18:10.78 spid28s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:4 | |
| 2021-10-23 03:18:10.78 spid28s DbMgrPartnerCommitPolicy::SetSyncState: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:4 | |
| 2021-10-23 03:18:10.79 spid331s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:4 | |
| 2021-10-23 03:18:10.79 spid331s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:4 | |
| 2021-10-23 03:18:10.79 spid331s Always On Availability Groups connection with secondary database established for primary database 'MyDb2ging' on the availability replica 'db-node-secondary' with Replica ID: {68820bcc-ad5c-40e0-9b9a-75bf95a677b5}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:18:10.79 spid28s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:4 | |
| 2021-10-23 03:18:10.81 spid22s The recovery LSN (44334:470:2) was identified for the database with ID 8. This is an informational message only. No user action is required. | |
| 2021-10-23 03:18:10.99 spid28s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:18:10.99 spid28s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:18:10.99 spid28s DbMgrPartnerCommitPolicy::SetSyncState: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:18:11.00 spid331s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:18:11.09 spid331s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:1 | |
| 2021-10-23 03:18:11.17 spid332s CHECKDB for database 'MyDb4' finished without errors on 2020-08-09 00:07:40.963 (local time). This is an informational message only; no user action is required. | |
| 2021-10-23 03:18:11.31 spid331s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:4 | |
| 2021-10-23 03:18:11.31 spid331s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:4 | |
| 2021-10-23 03:18:11.31 spid331s DbMgrPartnerCommitPolicy::SetSyncState: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:4 | |
| 2021-10-23 03:18:14.66 spid334s State information for database 'MyDb3itoring' - Hardened Lsn: '(37808:21885:1)' Commit LSN: '(37782:15663:3)' Commit Time: 'Oct 22 2021 4:53AM' | |
| 2021-10-23 03:18:14.97 spid334s State information for database 'MyDb3itoring' - Hardened Lsn: '(37808:21885:1)' Commit LSN: '(37782:15663:3)' Commit Time: 'Oct 22 2021 4:53AM' | |
| 2021-10-23 03:18:14.98 spid334s Starting up database 'MyDb3itoring'. | |
| 2021-10-23 03:18:15.08 spid334s Parallel redo is started for database 'MyDb3itoring' with worker pool size [2]. | |
| 2021-10-23 03:18:15.19 spid29s Remote harden of transaction 'GhostCleanupTask' (ID 0x000000000f364517 0000:24714085) started at Oct 23 2021 3:18AM in database 'MyDb1' at LSN (50177:57944:37) failed. | |
| 2021-10-23 03:18:15.33 spid334s Recovery of database 'MyDb3itoring' (6) is 0% complete (approximately 61 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required. | |
| 2021-10-23 03:18:16.08 spid334s Always On Availability Groups connection with primary database established for secondary database 'MyDb3itoring' on the availability replica 'db-node-secondary' with Replica ID: {e2714cda-b751-4baf-bd7d-e706ddca874f}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:18:16.12 spid334s The recovery LSN (37808:21885:1) was identified for the database with ID 6. This is an informational message only. No user action is required. | |
| 2021-10-23 03:18:20.21 spid348s Remote harden of transaction 'GhostCleanupTask' (ID 0x000000000f364521 0000:24714087) started at Oct 23 2021 3:18AM in database 'MyDb1' at LSN (50177:57950:29) failed. | |
| 2021-10-23 03:18:25.23 spid265s Remote harden of transaction 'GhostCleanupTask' (ID 0x000000000f364528 0000:24714089) started at Oct 23 2021 3:18AM in database 'MyDb1' at LSN (50177:57955:28) failed. | |
| 2021-10-23 03:18:30.24 spid43s Remote harden of transaction 'GhostCleanupTask' (ID 0x000000000f36454b 0000:2471408b) started at Oct 23 2021 3:18AM in database 'MyDb1' at LSN (50177:57960:30) failed. | |
| 2021-10-23 03:18:35.24 spid295s Remote harden of transaction 'GhostCleanupTask' (ID 0x000000000f36454f 0000:2471408d) started at Oct 23 2021 3:18AM in database 'MyDb1' at LSN (50177:57965:30) failed. | |
| 2021-10-23 03:18:40.26 spid299s Remote harden of transaction 'GhostCleanupTask' (ID 0x000000000f364552 0000:2471408f) started at Oct 23 2021 3:18AM in database 'MyDb1' at LSN (50177:57970:29) failed. | |
| 2021-10-23 03:18:45.27 spid349s Remote harden of transaction 'GhostCleanupTask' (ID 0x000000000f36455f 0000:24714091) started at Oct 23 2021 3:18AM in database 'MyDb1' at LSN (50177:57975:24) failed. | |
| 2021-10-23 03:18:50.27 spid342s Remote harden of transaction 'GhostCleanupTask' (ID 0x000000000f364563 0000:24714093) started at Oct 23 2021 3:18AM in database 'MyDb1' at LSN (50177:57979:21) failed. | |
| 2021-10-23 03:18:55.29 spid339s Remote harden of transaction 'GhostCleanupTask' (ID 0x000000000f364569 0000:24714095) started at Oct 23 2021 3:18AM in database 'MyDb1' at LSN (50177:57983:26) failed. | |
| 2021-10-23 03:19:00.30 spid344s Remote harden of transaction 'GhostCleanupTask' (ID 0x000000000f364573 0000:24714097) started at Oct 23 2021 3:19AM in database 'MyDb1' at LSN (50177:57988:2) failed. | |
| 2021-10-23 03:19:05.32 spid58s Remote harden of transaction 'GhostCleanupTask' (ID 0x000000000f364576 0000:24714098) started at Oct 23 2021 3:19AM in database 'MyDb1' at LSN (50177:57989:22) failed. | |
| 2021-10-23 03:19:15.32 spid219s Remote harden of transaction 'GhostCleanupTask' (ID 0x000000000f364585 0000:2471409a) started at Oct 23 2021 3:19AM in database 'MyDb1' at LSN (50177:57994:21) failed. | |
| 2021-10-23 03:19:20.34 spid36s Remote harden of transaction 'GhostCleanupTask' (ID 0x000000000f364594 0000:2471409c) started at Oct 23 2021 3:19AM in database 'MyDb1' at LSN (50177:57998:211) failed. | |
| 2021-10-23 03:19:26.91 spid46s Error: 41065, Severity: 16, State: 0. | |
| 2021-10-23 03:19:26.91 spid46s Cannot bring the Windows Server Failover Clustering (WSFC) resource (ID: '03747308-1442-4ac6-8400-2a736435caa1') online at this time. The WSFC resource is not in a state that can accept the request. Wait for the WSFC resource to enter a terminal state, and retry the operation. For information about this error, see error code 5023 in "System Error Codes" in the Windows Development documentation. | |
| 2021-10-23 03:19:26.92 spid46s Error: 41160, Severity: 16, State: 0. | |
| 2021-10-23 03:19:26.92 spid46s Failed to designate the local availability replica of availability group 'MyDb1' as the primary replica. The operation encountered SQL Server error 41065 and has been terminated. Check the preceding error and the SQL Server error log for more details about the error and corrective actions. | |
| 2021-10-23 03:19:30.34 spid277s Remote harden of transaction 'GhostCleanupTask' (ID 0x000000000f3645ae 0000:247140a5) started at Oct 23 2021 3:19AM in database 'MyDb1' at LSN (50177:58029:3) failed. | |
| 2021-10-23 03:19:59.10 Server The Service Broker endpoint is in disabled or stopped state. | |
| 2021-10-23 03:19:59.15 spid59 Always On: The local replica of availability group 'MyDb1' is preparing to transition to the primary role. This is an informational message only. No user action is required. | |
| 2021-10-23 03:19:59.19 Server The Service Broker endpoint is in disabled or stopped state. | |
| 2021-10-23 03:19:59.19 spid59 The availability replica for availability group 'MyDb1' on this instance of SQL Server cannot become the primary replica. One or more databases are not synchronized or have not joined the availability group. If the availability replica uses the asynchronous-commit mode, consider performing a forced manual failover (with possible data loss). Otherwise, once all local secondary databases are joined and synchronized, you can perform a planned manual failover to this secondary replica (without data loss). For more information, see SQL Server Books Online. | |
| 2021-10-23 03:19:59.24 spid59 Always On: The local replica of availability group 'MyDb1' is preparing to transition to the resolving role. This is an informational message only. No user action is required. | |
| 2021-10-23 03:19:59.50 Server The Service Broker endpoint is in disabled or stopped state. | |
| 2021-10-23 03:20:03.46 Server The Service Broker endpoint is in disabled or stopped state. | |
| 2021-10-23 03:20:04.01 Server The Service Broker endpoint is in disabled or stopped state. | |
| 2021-10-23 03:20:05.19 spid46s The state of the local availability replica in availability group 'MyDb1' has changed from 'RESOLVING_NORMAL' to 'SECONDARY_NORMAL'. The state changed because the availability group state has changed in Windows Server Failover Clustering (WSFC). For more information, see the SQL Server error log or cluster log. If this is a Windows Server Failover Clustering (WSFC) availability group, you can also see the WSFC management console. | |
| 2021-10-23 03:20:05.19 spid331s The availability group database "MyDb1" is changing roles from "RESOLVING" to "SECONDARY" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required. | |
| 2021-10-23 03:20:05.19 Server The Service Broker endpoint is in disabled or stopped state. | |
| 2021-10-23 03:20:05.19 spid331s State information for database 'MyDb1' - Hardened Lsn: '(50177:57820:1)' Commit LSN: '(50166:107296:3)' Commit Time: 'Oct 22 2021 4:53AM' | |
| 2021-10-23 03:20:05.23 spid22s A connection for availability group 'MyDb1' from availability replica 'db-node-primary' with id [43DE05A5-1C5E-4BA5-BD31-CD4D8E58AD62] to 'db-node-secondary' with id [604EBD17-9BC4-4480-90DF-CA446489E6B5] has been successfully established. This is an informational message only. No user action is required. | |
| 2021-10-23 03:20:06.42 spid69s State information for database 'MyDb1' - Hardened Lsn: '(50177:57820:1)' Commit LSN: '(50166:107296:3)' Commit Time: 'Oct 22 2021 4:53AM' | |
| 2021-10-23 03:20:06.51 spid69s State information for database 'MyDb1' - Hardened Lsn: '(50177:57820:1)' Commit LSN: '(50166:107296:3)' Commit Time: 'Oct 22 2021 4:53AM' | |
| 2021-10-23 03:20:06.52 spid69s Starting up database 'MyDb1'. | |
| 2021-10-23 03:20:07.34 spid69s Parallel redo is started for database 'MyDb1' with worker pool size [2]. | |
| 2021-10-23 03:20:08.55 spid69s Recovery of database 'MyDb1' (7) is 0% complete (approximately 141 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required. | |
| 2021-10-23 03:20:34.41 spid69s 27463 transactions rolled forward in database 'MyDb1' (7:0). This is an informational message only. No user action is required. | |
| 2021-10-23 03:20:34.42 spid69s Recovery completed for database MyDb1 (database ID 7) in 28 second(s) (analysis 1198 ms, redo 1738 ms, undo 0 ms [system undo 0 ms, regular undo 0 ms].) This is an informational message only. No user action is required. | |
| 2021-10-23 03:20:34.43 spid69s CHECKDB for database 'MyDb1' finished without errors on 2020-08-09 00:09:08.470 (local time). This is an informational message only; no user action is required. | |
| 2021-10-23 03:22:15.70 spid334s Error: 35278, Severity: 17, State: 1. | |
| 2021-10-23 03:22:15.70 spid334s Availability database 'MyDb3itoring', which is in the secondary role, is being restarted to resynchronize with the current primary database. This is an informational message only. No user action is required. | |
| 2021-10-23 03:22:15.70 spid334s Parallel redo is shutdown for database 'MyDb3itoring' with worker pool size [2]. | |
| 2021-10-23 03:22:15.71 spid334s State information for database 'MyDb3itoring' - Hardened Lsn: '(37808:21887:1)' Commit LSN: '(37808:21883:4)' Commit Time: 'Oct 23 2021 3:16AM' | |
| 2021-10-23 03:22:15.76 spid334s State information for database 'MyDb3itoring' - Hardened Lsn: '(37808:21887:1)' Commit LSN: '(37808:21883:4)' Commit Time: 'Oct 23 2021 3:16AM' | |
| 2021-10-23 03:22:15.77 spid334s Starting up database 'MyDb3itoring'. | |
| 2021-10-23 03:22:15.86 spid334s Parallel redo is started for database 'MyDb3itoring' with worker pool size [2]. | |
| 2021-10-23 03:22:16.20 spid334s Always On Availability Groups connection with primary database established for secondary database 'MyDb3itoring' on the availability replica 'db-node-secondary' with Replica ID: {e2714cda-b751-4baf-bd7d-e706ddca874f}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:22:16.24 spid334s The recovery LSN (37808:22950:2) was identified for the database with ID 6. This is an informational message only. No user action is required. | |
| 2021-10-23 03:22:16.25 spid334s 856 transactions rolled forward in database 'MyDb3itoring' (6:0). This is an informational message only. No user action is required. | |
| 2021-10-23 03:22:16.29 spid22s Always On Availability Groups connection with primary database established for secondary database 'MyDb3itoring' on the availability replica 'db-node-secondary' with Replica ID: {e2714cda-b751-4baf-bd7d-e706ddca874f}. This is an informational message only. No user action is required. | |
| 2021-10-23 03:22:16.34 spid22s The recovery LSN (37808:22950:2) was identified for the database with ID 6. This is an informational message only. No user action is required. | |
| 2021-10-23 03:22:17.52 spid334s CHECKDB for database 'MyDb3itoring' finished without errors on 2020-08-09 00:07:08.503 (local time). This is an informational message only; no user action is required. | |
| 2021-10-23 03:46:28.38 spid91s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:46:28.38 spid91s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:46:44.09 spid83s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:46:44.09 spid83s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:47:37.88 spid49s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:47:37.88 spid49s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:48:06.30 spid84s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:48:06.30 spid84s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:48:17.31 Logon Error: 17832, Severity: 20, State: 2. | |
| 2021-10-23 03:48:17.31 Logon The login packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor of the client library. [CLIENT: 10.16.1.75] | |
| 2021-10-23 03:48:35.96 spid86s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:48:35.96 spid86s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 03:48:58.15 spid23s Error: 9642, Severity: 16, State: 3. | |
| 2021-10-23 03:48:58.15 spid23s An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '') | |
| 2021-10-23 08:39:24.94 spid91 Always On: The local replica of availability group 'MyDb2' is preparing to transition to the resolving role. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:24.94 Server The availability group 'MyDb2' is being asked to stop the lease renewal because the availability group is going offline. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:24.94 spid91 The state of the local availability replica in availability group 'MyDb2' has changed from 'PRIMARY_NORMAL' to 'RESOLVING_NORMAL'. The state changed because the availability group is going offline. The replica is going offline because the associated availability group has been deleted, or the user has taken the associated availability group offline in Windows Server Failover Clustering (WSFC) management console, or the availability group is failing over to another SQL Server instance. For more information, see the SQL Server error log or cluster log. If this is a Windows Server Failover Clustering (WSFC) availability group, you can also see the WSFC management console. | |
| 2021-10-23 08:39:24.94 spid89s Always On Availability Groups connection with secondary database terminated for primary database 'MyDb2ging' on the availability replica 'db-node-secondary' with Replica ID: {68820bcc-ad5c-40e0-9b9a-75bf95a677b5}. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:24.94 Server Stopped listening on listener network name 'MyDb2' (VNN or DISTRIBUTED_NETWORK_NAME). No user action is required. | |
| 2021-10-23 08:39:24.94 spid70s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:4 | |
| 2021-10-23 08:39:24.94 spid90s The availability group database "MyDb2ging" is changing roles from "PRIMARY" to "RESOLVING" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:24.94 spid90s State information for database 'MyDb2ging' - Hardened Lsn: '(6426:15299:1)' Commit LSN: '(6426:15241:173)' Commit Time: 'Oct 23 2021 8:00AM' | |
| 2021-10-23 08:39:24.94 spid89s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 68820BCC-AD5C-40E0-9B9A-75BF95A677B5:4 | |
| 2021-10-23 08:39:25.18 spid44s Error: 41009, Severity: 16, State: 5. | |
| 2021-10-23 08:39:25.18 spid44s The Windows Server Failover Clustering (WSFC) resource control API returned error code 10.. If this is a WSFC availability group, the WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. Otherwise, contact your primary support provider. For information about this error code, see "System Error Codes" in the Windows Development documentation. | |
| 2021-10-23 08:39:25.71 Server Always On Availability Groups: Local Windows Server Failover Clustering node is no longer online. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:25.71 spid56s Always On: The availability replica manager is going offline because the local Windows Server Failover Clustering (WSFC) node has lost quorum. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:25.72 spid56s Always On: The local replica of availability group 'MyDb4' is stopping. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:25.72 spid56s The state of the local availability replica in availability group 'MyDb4' has changed from 'SECONDARY_NORMAL' to 'RESOLVING_NORMAL'. The state changed because the local instance of SQL Server is shutting down. For more information, see the SQL Server error log or cluster log. If this is a Windows Server Failover Clustering (WSFC) availability group, you can also see the WSFC management console. | |
| 2021-10-23 08:39:25.72 spid89s Always On Availability Groups connection with primary database terminated for secondary database 'MyDb4' on the availability replica 'db-node-secondary' with Replica ID: {e2c6d609-6b65-45a6-8027-3d1d37f6f144}. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:25.72 spid90s The availability group database "MyDb4" is changing roles from "SECONDARY" to "RESOLVING" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:25.72 spid90s State information for database 'MyDb4' - Hardened Lsn: '(44343:4098:1)' Commit LSN: '(44343:4093:3)' Commit Time: 'Oct 23 2021 8:39AM' | |
| 2021-10-23 08:39:25.72 spid56s Always On: The local replica of availability group 'MyDb1' is stopping. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:25.72 spid56s The state of the local availability replica in availability group 'MyDb1' has changed from 'SECONDARY_NORMAL' to 'RESOLVING_NORMAL'. The state changed because the local instance of SQL Server is shutting down. For more information, see the SQL Server error log or cluster log. If this is a Windows Server Failover Clustering (WSFC) availability group, you can also see the WSFC management console. | |
| 2021-10-23 08:39:25.72 spid89s Always On Availability Groups connection with primary database terminated for secondary database 'MyDb1' on the availability replica 'db-node-secondary' with Replica ID: {604ebd17-9bc4-4480-90df-ca446489e6b5}. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:25.72 spid70s The availability group database "MyDb1" is changing roles from "SECONDARY" to "RESOLVING" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:25.72 spid70s State information for database 'MyDb1' - Hardened Lsn: '(50177:58034:1)' Commit LSN: '(50177:58029:3)' Commit Time: 'Oct 23 2021 3:19AM' | |
| 2021-10-23 08:39:25.72 spid56s Always On: The local replica of availability group 'MyDb3' is stopping. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:25.72 spid56s The state of the local availability replica in availability group 'MyDb3' has changed from 'SECONDARY_NORMAL' to 'RESOLVING_NORMAL'. The state changed because the local instance of SQL Server is shutting down. For more information, see the SQL Server error log or cluster log. If this is a Windows Server Failover Clustering (WSFC) availability group, you can also see the WSFC management console. | |
| 2021-10-23 08:39:25.73 spid92s The availability group database "MyDb3itoring" is changing roles from "SECONDARY" to "RESOLVING" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:25.73 spid92s State information for database 'MyDb3itoring' - Hardened Lsn: '(37808:28594:1)' Commit LSN: '(37808:28592:2)' Commit Time: 'Oct 23 2021 8:26AM' | |
| 2021-10-23 08:39:25.73 spid89s Always On Availability Groups connection with primary database terminated for secondary database 'MyDb3itoring' on the availability replica 'db-node-secondary' with Replica ID: {e2714cda-b751-4baf-bd7d-e706ddca874f}. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:25.73 spid56s Always On: The local replica of availability group 'MyDb2' is stopping. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:25.74 spid56s Always On: The availability replica manager is starting. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:25.75 spid56s Always On Availability Groups: Waiting for local Windows Server Failover Clustering service to start. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:25.90 Server SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:26.18 Server The connection has been lost with Microsoft Distributed Transaction Coordinator (MS DTC). Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) will begin once the connection is re-established. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:30.76 spid56s Always On Availability Groups: Waiting for local Windows Server Failover Clustering node to start. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:30.76 spid56s Error: 17054, Severity: 16, State: 1. | |
| 2021-10-23 08:39:30.76 spid56s The current event was not reported to the operating system error log. Operating system error = (null). You may need to clear the operating system error log if it is full. | |
| 2021-10-23 08:39:30.76 spid56s Always On Availability Groups: Waiting for local Windows Server Failover Clustering node to come online. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:30.76 spid56s Always On Availability Groups startup has been cancelled, because SQL Server is shutting down. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:30.76 spid56s Error: 41089, Severity: 16, State: 0. | |
| 2021-10-23 08:39:30.76 spid56s Always On Availability Groups startup has been cancelled, because SQL Server is shutting down. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:30.76 spid10s Always On: The availability replica manager is going offline because SQL Server is shutting down. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:30.76 spid10s Always On: The local replica of availability group 'MyDb4' is stopping. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:30.76 spid10s Always On: The local replica of availability group 'MyDb1' is stopping. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:30.76 spid10s Always On: The local replica of availability group 'MyDb3' is stopping. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:30.76 spid10s Always On: The local replica of availability group 'MyDb2' is stopping. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:30.76 spid44s Always On: The availability replica manager is going offline because the local Windows Server Failover Clustering (WSFC) node has lost quorum. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:30.76 spid44s Always On: The local replica of availability group 'MyDb4' is stopping. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:30.76 spid44s Always On: The local replica of availability group 'MyDb1' is stopping. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:30.76 spid44s Always On: The local replica of availability group 'MyDb3' is stopping. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:30.76 spid44s Always On: The local replica of availability group 'MyDb2' is stopping. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:30.76 spid44s Always On: The availability replica manager is starting. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:30.76 spid44s Always On Availability Groups: Waiting for local Windows Server Failover Clustering service to start. This is an informational message only. No user action is required. | |
| 2021-10-23 08:39:30.93 spid37s The Database Mirroring endpoint has stopped listening for connections. | |
| 2021-10-23 08:39:30.93 spid37s Service Broker manager has shut down. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment