Hi All,
Can anyone who know Alwayson help me .
Today morning, the AG wasn't available. But when the users came to me and checked the AG dashboard, it was green.
I am new to Alwayson availability groups. anyone knows what happened. I collected all the errorlog's and I see some messages but couldnt decipher it. I tried to change the db names n servernames n listerner name.Could anyone help me if there was any fail over happened. Systems team was blaming it was SQL issue and not the windows issue. but I could see messages that lost quorum and listener was not available.
Is this because everything manifest within sql and everyone starts blaming it is SQL Server issue? I don't know how to prove it is Windows DNS or cluster issue.
I am attaching the ERRORLOG.
RowID EntryTime source LogEntry
407 2019-09-27 02:44:59.370 spid52 Always On: The local replica of availability group 'BIPAG01' is preparing to transition to the resolving role in response to a request from the Windows Server Failover Clustering (WSFC) cluster. This is an informational message only. No user action is required.
408 2019-09-27 02:44:59.380 spid52 The state of the local availability replica in availability group 'BIPAG01' 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, Windows Server Failover Clustering (WSFC) management console, or WSFC log.
409 2019-09-27 02:44:59.380 Server The availability group 'BIPAG01' 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.
410 2019-09-27 02:44:59.380 spid85s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 074CE2AA-ED42-4AF3-8589-EBE6E0A5503E:4
411 2019-09-27 02:44:59.380 spid45s Always On Availability Groups connection with secondary database terminated for primary database 'test' on the availability replica 'vmp10' with Replica ID: {074ce2aa-ed42-4af3-8589-ebe6e0a5503e}. This is an informational message only. No user action is required.
412 2019-09-27 02:44:59.380 spid48s Always On Availability Groups connection with secondary database terminated for primary database 'db2' on the availability replica 'vmp10' with Replica ID: {074ce2aa-ed42-4af3-8589-ebe6e0a5503e}. This is an informational message only. No user action is required.
413 2019-09-27 02:44:59.380 spid37s Always On Availability Groups connection with secondary database terminated for primary database 'db1' on the availability replica 'vmp10' with Replica ID: {074ce2aa-ed42-4af3-8589-ebe6e0a5503e}. This is an informational message only. No user action is required.
414 2019-09-27 02:44:59.380 spid82s Always On Availability Groups connection with secondary database terminated for primary database 'db3' on the availability replica 'vmp10' with Replica ID: {074ce2aa-ed42-4af3-8589-ebe6e0a5503e}. This is an informational message only. No user action is required.
415 2019-09-27 02:44:59.380 spid90s Always On Availability Groups connection with secondary database terminated for primary database 'db4' on the availability replica 'vmp10' with Replica ID: {074ce2aa-ed42-4af3-8589-ebe6e0a5503e}. This is an informational message only. No user action is required.
416 2019-09-27 02:44:59.400 spid45s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 074CE2AA-ED42-4AF3-8589-EBE6E0A5503E:4
417 2019-09-27 02:44:59.400 spid39s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 074CE2AA-ED42-4AF3-8589-EBE6E0A5503E:4
418 2019-09-27 02:44:59.400 spid89s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 074CE2AA-ED42-4AF3-8589-EBE6E0A5503E:4
419 2019-09-27 02:44:59.400 spid37s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 074CE2AA-ED42-4AF3-8589-EBE6E0A5503E:4
420 2019-09-27 02:44:59.410 spid117s The availability group database "db1" 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.
421 2019-09-27 02:44:59.410 spid50s The availability group database "db2" 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.
422 2019-09-27 02:44:59.410 spid116s The availability group database "db3" 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.
423 2019-09-27 02:44:59.410 spid117s State information for database 'db1' - Hardened Lsn: '(4033:858628:1)' Commit LSN: '(4033:847445:7)' Commit Time: 'Sep 27 2019 2:40AM'
424 2019-09-27 02:44:59.410 spid50s State information for database 'db2' - Hardened Lsn: '(3618:24658:1)' Commit LSN: '(3618:22887:2)' Commit Time: 'Sep 27 2019 2:39AM'
425 2019-09-27 02:44:59.410 spid116s State information for database 'db3' - Hardened Lsn: '(8604:8049:1)' Commit LSN: '(8604:6871:6)' Commit Time: 'Sep 27 2019 2:40AM'
426 2019-09-27 02:44:59.410 spid92s The availability group database "db4" 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.
427 2019-09-27 02:44:59.410 spid92s State information for database 'db4' - Hardened Lsn: '(6836:77825:1)' Commit LSN: '(6836:70843:2)' Commit Time: 'Sep 27 2019 2:39AM'
428 2019-09-27 02:44:59.420 Server Stopped listening on virtual network name 'bilistener01'. No user action is required.
429 2019-09-27 02:44:59.420 spid114s The availability group database "test" 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.
430 2019-09-27 02:44:59.420 spid114s State information for database 'test' - Hardened Lsn: '(34:3905:1)' Commit LSN: '(34:3900:8)' Commit Time: 'Sep 27 2019 2:00AM'
431 2019-09-27 02:44:59.420 spid39s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 074CE2AA-ED42-4AF3-8589-EBE6E0A5503E:4
432 2019-09-27 02:44:59.420 spid39s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 074CE2AA-ED42-4AF3-8589-EBE6E0A5503E:4
433 2019-09-27 02:44:59.420 spid39s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 074CE2AA-ED42-4AF3-8589-EBE6E0A5503E:4
434 2019-09-27 02:44:59.420 spid39s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 074CE2AA-ED42-4AF3-8589-EBE6E0A5503E:4
435 2019-09-27 02:44:59.430 spid82s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: 074CE2AA-ED42-4AF3-8589-EBE6E0A5503E:4
436 2019-09-27 02:44:59.440 spid92s Nonqualified transactions are being rolled back in database db4 for an Always On Availability Groups state change. Estimated rollback completion: 100%. This is an informational message only. No user action is required.
437 2019-09-27 02:44:59.440 spid117s Nonqualified transactions are being rolled back in database db1 for an Always On Availability Groups state change. Estimated rollback completion: 100%. This is an informational message only. No user action is required.
438 2019-09-27 02:44:59.440 spid114s Nonqualified transactions are being rolled back in database test for an Always On Availability Groups state change. Estimated rollback completion: 100%. This is an informational message only. No user action is required.
439 2019-09-27 02:44:59.440 spid50s Nonqualified transactions are being rolled back in database db2 for an Always On Availability Groups state change. Estimated rollback completion: 100%. This is an informational message only. No user action is required.
440 2019-09-27 02:44:59.440 spid116s Nonqualified transactions are being rolled back in database db3 for an Always On Availability Groups state change. Estimated rollback completion: 100%. This is an informational message only. No user action is required.
441 2019-09-27 02:44:59.660 Logon Error: 983, Severity: 14, State: 1.
442 2019-09-27 02:44:59.660 Logon Unable to access availability database 'db3' 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.
443 2019-09-27 02:44:59.850 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.
444 2019-09-27 02:44:59.850 spid57s 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.
445 2019-09-27 02:44:59.850 spid57s Always On: The local replica of availability group 'BIPAG01' is stopping. This is an informational message only. No user action is required.
446 2019-09-27 02:44:59.860 spid57s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
447 2019-09-27 02:44:59.860 spid57s 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.
448 2019-09-27 02:44:59.860 spid57s Always On Availability Groups: Local Windows Server Failover Clustering service started. This is an informational message only. No user action is required.
449 2019-09-27 02:44:59.860 spid57s 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.
450 2019-09-27 02:44:59.860 spid57s Always On Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. No user action is required.
451 2019-09-27 02:44:59.860 spid57s 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.
452 2019-09-27 02:44:59.860 spid57s Always On Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is required.
453 2019-09-27 02:44:59.870 spid57s Error: 41022, Severity: 16, State: 0.
454 2019-09-27 02:44:59.870 spid57s Failed to create a Windows Server Failover Clustering (WSFC) notification port with notification filter 778567686 and notification key 3 (Error code 5073). The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
455 2019-09-27 02:44:59.870 spid25s 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.
456 2019-09-27 02:44:59.870 spid25s Always On: The local replica of availability group 'BIPAG01' is stopping. This is an informational message only. No user action is required.
457 2019-09-27 02:44:59.870 spid25s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
458 2019-09-27 02:44:59.870 spid25s 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.
459 2019-09-27 02:44:59.870 spid25s Always On Availability Groups: Local Windows Server Failover Clustering service started. This is an informational message only. No user action is required.
460 2019-09-27 02:44:59.870 spid25s 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.
461 2019-09-27 02:44:59.870 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. No user action is required.
462 2019-09-27 02:44:59.870 spid25s 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.
463 2019-09-27 02:44:59.870 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is required.
464 2019-09-27 02:44:59.870 spid25s Error: 41022, Severity: 16, State: 0.
465 2019-09-27 02:44:59.870 spid25s Failed to create a Windows Server Failover Clustering (WSFC) notification port with notification filter 778567686 and notification key 3 (Error code 5073). The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
466 2019-09-27 02:44:59.870 spid25s 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.
467 2019-09-27 02:44:59.870 spid25s Always On: The local replica of availability group 'BIPAG01' is stopping. This is an informational message only. No user action is required.
468 2019-09-27 02:44:59.880 spid25s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
469 2019-09-27 02:44:59.880 spid25s 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.
470 2019-09-27 02:44:59.880 spid25s Always On Availability Groups: Local Windows Server Failover Clustering service started. This is an informational message only. No user action is required.
471 2019-09-27 02:44:59.880 spid25s 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.
472 2019-09-27 02:44:59.880 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. No user action is required.
473 2019-09-27 02:44:59.880 spid25s 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.
474 2019-09-27 02:44:59.880 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is required.
475 2019-09-27 02:44:59.880 spid25s Error: 41022, Severity: 16, State: 0.
476 2019-09-27 02:44:59.880 spid25s Failed to create a Windows Server Failover Clustering (WSFC) notification port with notification filter 778567686 and notification key 3 (Error code 5073). The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
477 2019-09-27 02:44:59.880 spid25s 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.
478 2019-09-27 02:44:59.880 spid25s Always On: The local replica of availability group 'BIPAG01' is stopping. This is an informational message only. No user action is required.
479 2019-09-27 02:44:59.880 spid25s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
480 2019-09-27 02:44:59.880 spid25s 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.
481 2019-09-27 02:44:59.880 spid25s Always On Availability Groups: Local Windows Server Failover Clustering service started. This is an informational message only. No user action is required.
482 2019-09-27 02:44:59.880 spid25s 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.
483 2019-09-27 02:44:59.880 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. No user action is required.
484 2019-09-27 02:44:59.880 spid25s 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.
485 2019-09-27 02:44:59.880 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is required.
486 2019-09-27 02:44:59.880 spid25s Error: 41022, Severity: 16, State: 0.
487 2019-09-27 02:44:59.880 spid25s Failed to create a Windows Server Failover Clustering (WSFC) notification port with notification filter 778567686 and notification key 3 (Error code 5073). The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
488 2019-09-27 02:44:59.880 spid25s 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.
489 2019-09-27 02:44:59.880 spid25s Always On: The local replica of availability group 'BIPAG01' is stopping. This is an informational message only. No user action is required.
490 2019-09-27 02:44:59.880 spid25s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
491 2019-09-27 02:44:59.880 spid25s 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.
492 2019-09-27 02:44:59.880 spid25s Always On Availability Groups: Local Windows Server Failover Clustering service started. This is an informational message only. No user action is required.
493 2019-09-27 02:44:59.880 spid25s 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.
494 2019-09-27 02:44:59.880 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. No user action is required.
495 2019-09-27 02:44:59.880 spid25s 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.
496 2019-09-27 02:44:59.880 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is required.
497 2019-09-27 02:44:59.890 spid25s Error: 41022, Severity: 16, State: 0.
498 2019-09-27 02:44:59.890 spid25s Failed to create a Windows Server Failover Clustering (WSFC) notification port with notification filter 778567686 and notification key 3 (Error code 5073). The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
499 2019-09-27 02:44:59.890 spid25s 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.
500 2019-09-27 02:44:59.890 spid25s Always On: The local replica of availability group 'BIPAG01' is stopping. This is an informational message only. No user action is required.
501 2019-09-27 02:44:59.890 spid25s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
502 2019-09-27 02:44:59.890 spid25s 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.
503 2019-09-27 02:44:59.890 spid25s Always On Availability Groups: Local Windows Server Failover Clustering service started. This is an informational message only. No user action is required.
504 2019-09-27 02:44:59.890 spid25s 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.
505 2019-09-27 02:44:59.890 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. No user action is required.
506 2019-09-27 02:44:59.890 spid25s 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.
507 2019-09-27 02:44:59.890 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is required.
508 2019-09-27 02:44:59.890 spid25s Error: 41022, Severity: 16, State: 0.
509 2019-09-27 02:44:59.890 spid25s Failed to create a Windows Server Failover Clustering (WSFC) notification port with notification filter 778567686 and notification key 3 (Error code 5073). The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
510 2019-09-27 02:44:59.890 spid25s 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.
511 2019-09-27 02:44:59.890 spid25s Always On: The local replica of availability group 'BIPAG01' is stopping. This is an informational message only. No user action is required.
512 2019-09-27 02:44:59.890 spid25s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
513 2019-09-27 02:44:59.890 spid25s 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.
514 2019-09-27 02:44:59.890 spid25s Always On Availability Groups: Local Windows Server Failover Clustering service started. This is an informational message only. No user action is required.
515 2019-09-27 02:44:59.890 spid25s 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.
516 2019-09-27 02:44:59.890 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. No user action is required.
517 2019-09-27 02:44:59.890 spid25s 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.
518 2019-09-27 02:44:59.890 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is required.
519 2019-09-27 02:44:59.890 spid25s Error: 41022, Severity: 16, State: 0.
520 2019-09-27 02:44:59.890 spid25s Failed to create a Windows Server Failover Clustering (WSFC) notification port with notification filter 778567686 and notification key 3 (Error code 5073). The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
521 2019-09-27 02:44:59.890 spid25s 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.
522 2019-09-27 02:44:59.890 spid25s Always On: The local replica of availability group 'BIPAG01' is stopping. This is an informational message only. No user action is required.
523 2019-09-27 02:44:59.890 spid25s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
524 2019-09-27 02:44:59.890 spid25s 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.
525 2019-09-27 02:44:59.890 spid25s Always On Availability Groups: Local Windows Server Failover Clustering service started. This is an informational message only. No user action is required.
526 2019-09-27 02:44:59.900 spid25s 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.
527 2019-09-27 02:44:59.900 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. No user action is required.
528 2019-09-27 02:44:59.900 spid25s 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.
529 2019-09-27 02:44:59.900 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is required.
530 2019-09-27 02:44:59.900 spid25s Error: 41022, Severity: 16, State: 0.
531 2019-09-27 02:44:59.900 spid25s Failed to create a Windows Server Failover Clustering (WSFC) notification port with notification filter 778567686 and notification key 3 (Error code 5073). The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
532 2019-09-27 02:44:59.900 spid25s 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.
533 2019-09-27 02:44:59.900 spid25s Always On: The local replica of availability group 'BIPAG01' is stopping. This is an informational message only. No user action is required.
534 2019-09-27 02:44:59.900 spid25s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
535 2019-09-27 02:44:59.900 spid25s 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.
536 2019-09-27 02:44:59.900 spid25s Always On Availability Groups: Local Windows Server Failover Clustering service started. This is an informational message only. No user action is required.
537 2019-09-27 02:44:59.900 spid25s 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.
538 2019-09-27 02:44:59.900 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. No user action is required.
539 2019-09-27 02:44:59.900 spid25s 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.
540 2019-09-27 02:44:59.900 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is required.
541 2019-09-27 02:44:59.900 spid25s Error: 41022, Severity: 16, State: 0.
542 2019-09-27 02:44:59.900 spid25s Failed to create a Windows Server Failover Clustering (WSFC) notification port with notification filter 778567686 and notification key 3 (Error code 5073). The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
543 2019-09-27 02:44:59.900 spid25s 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.
544 2019-09-27 02:44:59.900 spid25s Always On: The local replica of availability group 'BIPAG01' is stopping. This is an informational message only. No user action is required.
545 2019-09-27 02:44:59.900 spid25s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
546 2019-09-27 02:44:59.900 spid25s 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.
547 2019-09-27 02:44:59.900 spid25s Always On Availability Groups: Local Windows Server Failover Clustering service started. This is an informational message only. No user action is required.
548 2019-09-27 02:44:59.900 spid25s 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.
549 2019-09-27 02:44:59.900 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. No user action is required.
550 2019-09-27 02:44:59.900 spid25s 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.
551 2019-09-27 02:44:59.900 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is required.
552 2019-09-27 02:44:59.900 spid25s Error: 41022, Severity: 16, State: 0.
553 2019-09-27 02:44:59.900 spid25s Failed to create a Windows Server Failover Clustering (WSFC) notification port with notification filter 778567686 and notification key 3 (Error code 5073). The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
554 2019-09-27 02:44:59.900 spid25s 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.
555 2019-09-27 02:44:59.900 spid25s Always On: The local replica of availability group 'BIPAG01' is stopping. This is an informational message only. No user action is required.
556 2019-09-27 02:44:59.900 spid25s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
557 2019-09-27 02:44:59.900 spid25s 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.
558 2019-09-27 02:44:59.910 spid25s Always On Availability Groups: Local Windows Server Failover Clustering service started. This is an informational message only. No user action is required.
559 2019-09-27 02:44:59.910 spid25s 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.
560 2019-09-27 02:44:59.910 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. No user action is required.
561 2019-09-27 02:44:59.910 spid25s 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.
562 2019-09-27 02:44:59.910 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is required.
563 2019-09-27 02:44:59.910 spid25s Error: 41022, Severity: 16, State: 0.
564 2019-09-27 02:44:59.910 spid25s Failed to create a Windows Server Failover Clustering (WSFC) notification port with notification filter 778567686 and notification key 3 (Error code 5073). The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
565 2019-09-27 02:44:59.910 spid25s 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.
566 2019-09-27 02:44:59.910 spid25s Always On: The local replica of availability group 'BIPAG01' is stopping. This is an informational message only. No user action is required.
567 2019-09-27 02:44:59.910 spid25s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
568 2019-09-27 02:44:59.910 spid25s 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.
569 2019-09-27 02:44:59.910 spid25s Always On Availability Groups: Local Windows Server Failover Clustering service started. This is an informational message only. No user action is required.
570 2019-09-27 02:44:59.910 spid25s 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.
571 2019-09-27 02:44:59.910 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. No user action is required.
572 2019-09-27 02:44:59.910 spid25s 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.
573 2019-09-27 02:44:59.910 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is required.
574 2019-09-27 02:44:59.910 spid25s Error: 41022, Severity: 16, State: 0.
575 2019-09-27 02:44:59.910 spid25s Failed to create a Windows Server Failover Clustering (WSFC) notification port with notification filter 778567686 and notification key 3 (Error code 5073). The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
576 2019-09-27 02:44:59.910 spid25s 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.
577 2019-09-27 02:44:59.910 spid25s Always On: The local replica of availability group 'BIPAG01' is stopping. This is an informational message only. No user action is required.
578 2019-09-27 02:44:59.910 spid25s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
579 2019-09-27 02:44:59.910 spid25s 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.
580 2019-09-27 02:44:59.910 spid25s Always On Availability Groups: Local Windows Server Failover Clustering service started. This is an informational message only. No user action is required.
581 2019-09-27 02:44:59.910 spid25s 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.
582 2019-09-27 02:44:59.910 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. No user action is required.
583 2019-09-27 02:44:59.910 spid25s 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.
584 2019-09-27 02:44:59.910 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is required.
585 2019-09-27 02:44:59.920 spid25s Error: 41022, Severity: 16, State: 0.
586 2019-09-27 02:44:59.920 spid25s Failed to create a Windows Server Failover Clustering (WSFC) notification port with notification filter 778567686 and notification key 3 (Error code 5073). The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
587 2019-09-27 02:44:59.920 spid25s 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.
588 2019-09-27 02:44:59.920 spid25s Always On: The local replica of availability group 'BIPAG01' is stopping. This is an informational message only. No user action is required.
589 2019-09-27 02:44:59.920 spid25s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
590 2019-09-27 02:44:59.920 spid25s 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.
591 2019-09-27 02:44:59.920 spid25s Always On Availability Groups: Local Windows Server Failover Clustering service started. This is an informational message only. No user action is required.
592 2019-09-27 02:44:59.920 spid25s 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.
593 2019-09-27 02:44:59.920 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. No user action is required.
594 2019-09-27 02:44:59.920 spid25s 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.
595 2019-09-27 02:44:59.920 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is required.
596 2019-09-27 02:44:59.920 spid25s Error: 41022, Severity: 16, State: 0.
597 2019-09-27 02:44:59.920 spid25s Failed to create a Windows Server Failover Clustering (WSFC) notification port with notification filter 778567686 and notification key 3 (Error code 5073). The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
598 2019-09-27 02:44:59.920 spid25s 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.
599 2019-09-27 02:44:59.920 spid25s Always On: The local replica of availability group 'BIPAG01' is stopping. This is an informational message only. No user action is required.
600 2019-09-27 02:44:59.920 spid25s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
601 2019-09-27 02:44:59.920 spid25s 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.
602 2019-09-27 02:44:59.920 spid25s Always On Availability Groups: Local Windows Server Failover Clustering service started. This is an informational message only. No user action is required.
603 2019-09-27 02:44:59.920 spid25s 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.
604 2019-09-27 02:44:59.920 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. No user action is required.
605 2019-09-27 02:44:59.920 spid25s 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.
606 2019-09-27 02:44:59.920 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is required.
607 2019-09-27 02:44:59.920 spid25s Error: 41022, Severity: 16, State: 0.
608 2019-09-27 02:44:59.920 spid25s Failed to create a Windows Server Failover Clustering (WSFC) notification port with notification filter 778567686 and notification key 3 (Error code 5073). The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
609 2019-09-27 02:44:59.920 spid25s 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.
610 2019-09-27 02:44:59.920 spid25s Always On: The local replica of availability group 'BIPAG01' is stopping. This is an informational message only. No user action is required.
611 2019-09-27 02:44:59.920 spid25s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
612 2019-09-27 02:44:59.920 spid25s 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.
613 2019-09-27 02:44:59.920 spid25s Always On Availability Groups: Local Windows Server Failover Clustering service started. This is an informational message only. No user action is required.
614 2019-09-27 02:44:59.920 spid25s 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.
615 2019-09-27 02:44:59.930 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. No user action is required.
616 2019-09-27 02:44:59.930 spid25s 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.
617 2019-09-27 02:44:59.930 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is required.
618 2019-09-27 02:44:59.930 spid25s Error: 41022, Severity: 16, State: 0.
619 2019-09-27 02:44:59.930 spid25s Failed to create a Windows Server Failover Clustering (WSFC) notification port with notification filter 778567686 and notification key 3 (Error code 5073). The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
620 2019-09-27 02:44:59.930 spid25s 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.
621 2019-09-27 02:44:59.930 spid25s Always On: The local replica of availability group 'BIPAG01' is stopping. This is an informational message only. No user action is required.
622 2019-09-27 02:44:59.930 spid25s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
623 2019-09-27 02:44:59.930 spid25s 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.
624 2019-09-27 02:44:59.930 spid25s Always On Availability Groups: Local Windows Server Failover Clustering service started. This is an informational message only. No user action is required.
625 2019-09-27 02:44:59.930 spid25s 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.
626 2019-09-27 02:44:59.930 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. No user action is required.
627 2019-09-27 02:44:59.930 spid25s 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.
628 2019-09-27 02:44:59.930 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is required.
629 2019-09-27 02:44:59.930 spid25s Error: 41022, Severity: 16, State: 0.
630 2019-09-27 02:44:59.930 spid25s Failed to create a Windows Server Failover Clustering (WSFC) notification port with notification filter 778567686 and notification key 3 (Error code 5073). The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
631 2019-09-27 02:44:59.930 spid25s 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.
632 2019-09-27 02:44:59.930 spid25s Always On: The local replica of availability group 'BIPAG01' is stopping. This is an informational message only. No user action is required.
633 2019-09-27 02:44:59.930 spid25s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
634 2019-09-27 02:44:59.930 spid25s 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.
635 2019-09-27 02:44:59.930 spid25s Always On Availability Groups: Local Windows Server Failover Clustering service started. This is an informational message only. No user action is required.
636 2019-09-27 02:44:59.930 spid25s 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.
637 2019-09-27 02:44:59.930 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. No user action is required.
638 2019-09-27 02:44:59.930 spid25s 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.
639 2019-09-27 02:44:59.930 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is required.
640 2019-09-27 02:44:59.930 spid25s Error: 41022, Severity: 16, State: 0.
641 2019-09-27 02:44:59.930 spid25s Failed to create a Windows Server Failover Clustering (WSFC) notification port with notification filter 778567686 and notification key 3 (Error code 5073). The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
642 2019-09-27 02:44:59.930 spid25s 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.
643 2019-09-27 02:44:59.930 spid25s Always On: The local replica of availability group 'BIPAG01' is stopping. This is an informational message only. No user action is required.
644 2019-09-27 02:44:59.930 spid25s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
645 2019-09-27 02:44:59.930 spid25s 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.
646 2019-09-27 02:44:59.940 spid25s Always On Availability Groups: Local Windows Server Failover Clustering service started. This is an informational message only. No user action is required.
647 2019-09-27 02:44:59.940 spid25s 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.
648 2019-09-27 02:44:59.940 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. No user action is required.
649 2019-09-27 02:44:59.940 spid25s 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.
650 2019-09-27 02:44:59.940 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is required.
651 2019-09-27 02:44:59.940 spid25s Error: 41022, Severity: 16, State: 0.
652 2019-09-27 02:44:59.940 spid25s Failed to create a Windows Server Failover Clustering (WSFC) notification port with notification filter 778567686 and notification key 3 (Error code 5073). The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
653 2019-09-27 02:44:59.940 spid25s 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.
654 2019-09-27 02:44:59.940 spid25s Always On: The local replica of availability group 'BIPAG01' is stopping. This is an informational message only. No user action is required.
655 2019-09-27 02:44:59.940 spid25s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
656 2019-09-27 02:44:59.940 spid25s 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.
657 2019-09-27 02:44:59.940 spid25s Always On Availability Groups: Local Windows Server Failover Clustering service started. This is an informational message only. No user action is required.
658 2019-09-27 02:44:59.940 spid25s 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.
659 2019-09-27 02:44:59.940 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. No user action is required.
660 2019-09-27 02:44:59.940 spid25s 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.
661 2019-09-27 02:44:59.940 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is required.
662 2019-09-27 02:44:59.940 spid25s Error: 41022, Severity: 16, State: 0.
663 2019-09-27 02:44:59.940 spid25s Failed to create a Windows Server Failover Clustering (WSFC) notification port with notification filter 778567686 and notification key 3 (Error code 5073). The WSFC service may not be running or may not be accessible in its current state, or the specified arguments are invalid. For information about this error code, see "System Error Codes" in the Windows Development documentation.
664 2019-09-27 02:44:59.940 spid25s 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.
665 2019-09-27 02:44:59.940 spid25s Always On: The local replica of availability group 'BIPAG01' is stopping. This is an informational message only. No user action is required.
666 2019-09-27 02:44:59.940 spid25s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
667 2019-09-27 02:44:59.940 spid25s 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.
668 2019-09-27 02:44:59.940 spid25s Always On Availability Groups: Local Windows Server Failover Clustering service started. This is an informational message only. No user action is required.
669 2019-09-27 02:44:59.940 spid25s 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.
670 2019-09-27 02:44:59.940 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. No user action is required.
671 2019-09-27 02:44:59.940 spid25s 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.
672 2019-09-27 02:44:59.940 spid25s Always On Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is required.Thanks,
Sam