Hello All,

We are planning to configure Always on, we need your help to let us know the best license which we can use with Optimal Cost. I get to know that we can use it for Enterprise Edition only, can you please confirm same?

We have 4 cores(8 Logical Processors) machine and planning to install SQL Server 2012. Do we need to purchase extra license for the Secondary node though we just need to fetch the reports from it?

We need list of the SQL server and their Edition on which we can configure Always on. 

Regards,

Jiten Pansara

Hi All

• Could someone advice or help answer if my interpretation of the diagram below is correct?
• If I am correct then should this hold truth
  Can a SharePoint 2013 content database be added to a SQL AlwaysOn Availability Group (AOAG)  with both Synchronous and Asynchronous replicas? 

from the designed diagram below, is my interpretation as follow correct?

One AOAG group:  PROD-AG2

member Replicas:

SQL1 and SQL2  Synchronous mode (S)
SQL1 and SQL3  Asynchronous mode  (A)

Thanks in advance for all comments and advices.

Swanl

Hi  we have always on server 2016 R2 configured and read only routing also configured . Basically "user1" connect from client server and display as secondary  server. That ensured the read only routing is working 

sqlcmd.exe -S  LSNRname -d databasename -E -K ReadOnly

1>    Go

2>    Select @@servername

3>    Go

--------------------------

Question is on same client server(other 2016 R2 SQl server) I need to create a linked server to always on. and i created as follows. 

EXEC sp_addlinkedserver 
@server = N'Linkservername, 
@srvproduct=N'SqlServer',
@provider=N'SQLNCLI11', 
@datasrc=N'Listenenrname ', 
@provstr=N'ApplicationIntent=ReadOnly', 
@catalog=N'DBname';

.Linked server created. 

then I run following command to see which server is accessing from clinet server 

select * from OPENQUERY ( [Linkservername] ,'select @@servername' )

Its returned the correct servername.

Q1. I am not sure what user is use to connect which assess DB from the link. When select "Be made using the login's current security context"

Q2 . Secondly when I try to add user on  , then I am getting error. But please note I connect  using SSMS  same user specifying   listenername + ApplicationIntent=ReadOnly  and connected correctly.  Not sure why. Any one has any idea would be great . 

Hello,

i'm facing issues with my failover cluster.

I've installed a SQL Server Failover Cluster with Windows Server 2012 and SQL Server 2016 SP2 Enterprise.

16 of 18 instances have no issues when it comes to a failover event.

On the other two instances i have some (not all) databases which are going into the "recovery pending" state.

This happens every time when we're installing Windows Updates (automatically every first sunday a month) and the failover mechanism move the instances from one to the other node.

The SQL Server logs are clear - there are no entries, which could show an error.

Has someone experienced such an issue?

Thanks for your feedback.

We have 4 servers configured in always-on availability group, two in main site and two in DR site. 

The file share witness server is configured in main site. 

1. If main site goes down then what are the steps to bring the Windows Cluster Quorum online at DR site ?

2. After recovery of main site, what would be the steps to switch back to primary site?

Hi

We have a windows cluster with 3 nodes and no witness on windows 2016
Quorum type : NODE_MAJORITY
Number of Quorum Votes : 1 for each node

I am simulating a DR by shutting down Node 2 and Node 3, since every node has 1 vote and we are using node majority config, I am expecting that the cluster will fail and I have to start the cluster with "forcequorum" option to establish a service and bring Always ON and SQL online

This was not the case, the cluster is still up and Always ON running on Node 1 even if Node 2 and 3 are down and we lost node majority,  I am also able to reproduce the case using microsoft handsonlabs (Config Always ON availability group)
https://www.microsoft.com/handsonlabs/selfpacedlabs

Any explanation on this behavior?

Best regards

Greetings. We've got a 2012 Availability Group that has been well established for several years. We have 4 different jobs to backup Transaction Logs, each job backing up 4 databases. This will run fine > 99% of the time, then all of a sudden one of the backups will error out  with the following message:

Executed as user: mydomain\mylogin. The connection to the primary replica is not active.  The command cannot be processed. [SQLSTATE 42000] (Error 35250)  BACKUP LOG is terminating abnormally. [SQLSTATE 42000] (Error 3013).  NOTE: The step was retried the requested number of times (2) without succeeding.  The step failed.

Then all of a sudden it will start working again. It may be on the next attempt, or it may be an hour later. 

Here are several important fun facts:

1. This issue just started a couple weeks ago.
2. So far it's happened on 2 of the jobs, for a total of 5 DB's. 
3. There are no useful messages anywhere other than what I posted (Event Viewer, Cluster Manager, sql log, etc).
4. As mentioned, this will suddenly start working again on it's own.
5. While this job is failing, a different backup job can be running w/o issue (for another DB in the same AG).
6. While this job is failing, I can take the same backup for the same DB on the Primary node w/o issue.
7. The AG Dashboard show all green lights while this is happening. 

Any ideas?

Thanks in advance! ChrisRDBA

Hi all, 

I'm having a problem that I couldn't find any solution.  

we have jobs to back up logs on secondary replica and recently some of the databases keep failing with error:

The connection to the primary replica is not active.  The command cannot be processed.

our AG has been set up for years and the state is healthy when I checked dashboard.  we are using OLA script to do backups and in the same thread, most databases got backed up and only one of them failed and it's random. 

we've checked everywhere, sql error log, event viewer, we've restarted both sql servers but the problem is still there. 

please help. 

I have a couple of servers in always on high availability group with a disk quorum. The secondary is in non-readable mode. Searching for best practices or maintenance plans for this scenario didn't yield much through google.

Would be great to know how people are doing this? I can set up the maintenance on primary replica but was wondering how that would translate after a failover. Or, if we are supposed to create the same plan on the two servers (how would the maintenance job know which is primary server to perform the job on since the secondary would be non-readable?). 

I do see people talking about creating backups through maintenance plans in the forum for situation like mine. However, I do not need that. For me it would be more about reorganizing index, update statistics, clean up history and check database integrity.

Hi All,

I have configured Distributed Always-On from DC1 to DC2 on SQL Server 2017 Ent edition as like below.

DC1 (Clust1)

DB1

DB2

Listener Name/VIP: DC1_List

DC2 (Clust2)

DB3

DB4

Listener Name/VIP: DC2_List

Distributor AO name: Dist_DC1_DC2

My Question:

1. Which SQL instance name or listener name I have to use in application connect string to connect DB? is it primary DB instance-DB1? 
2. Can we create VIP/listener for Distributor AO name (Dist_DC1_DC2)? If yes, can i use Distributor AO in application connection string to connect DB?

Hi!

Just wondering what happens in a 2 node always On AG when a manual failover occurs? 

Do the connections just move over to the replica node or are they terminated? Are the users even aware of the failover?

Thanks,

Zoe

Hi Experts,

From SQL 2016 Onwards on windows 2016 , is there any update wherein Windows Cluster is not required as a pre-requite for Always On.

If Yes , is there any document available for it

Thanks

Hi,

I don't have the servers to test this currently, so posting here. 

So future config plan is to have read only routing on readable secondaries with connection strings having application intent set to read_only. 

Above should suffice normally, but i am looking into a failsafe, so that the app can't login for reads by even a mistake to the primary.

I was under the impression that disabling those logins on primary would be a simple workaround? Please let me know, thanks.

D

Hi All,

ENV:SQL 2016 Standard. 
OS:Server 2016 

I have a two DB's (simple recovery model) and i have set up a maintenance plan to backup the DB's Mon - Thurs Differential and on Friday a Full. 

The issue I am facing is that the transaction logs are not shrinking automatically after a full backup, but i am not sure if you need to add something in the maintenance plan to achieve this? And if so could someone please point me in the right direction? I couldn't see any option to truncate the transaction log after the full backup completes. I checked the logs after a full backup had run and they are not shrinking.

Any assistance would be greatly appreciated.

Hi!

I have a clustered SQL instance on a 2 node cluster - ServerA & ServerB.

I also have ServerC which is standalone.

I want to create an AG group with the clustered instance as Primary and ServerC as a replica.

Do I need 3 IP addresses  for the listener? or just the normal 2?

Thanks,

Zoe

We are facing a problem in a java based application where the number of database connections to a SQL server database is always increasing. The database is configured in a HA group and the application connection to the database has been configured via a SQL Server always-on listener. Connection pooling has been implemented using dbcp2.

To troubleshoot the problem we tried running the application workload in two different database connectivity modes. The first mode using the always-on listener and the second by connecting directly to the primary database node of the HA group.

We found that the continuous increase in the number of database connections was found only when the connections were configured using the always-on listener. In this case the connections keep increasing leading to hundreds of connection to the database much beyond the limits set as part of the connection pool parameters.

When the same application workload was run with the database connection directly to the primary node, there was no dramatic increase in the number of connections. The number stayed well within the limits set for the connection pool.

The following connection pool parameters are being set.

jdbc.driverClassName=com.microsoft.sqlserver.    
jdbc.SQLServerDriver
jdbc.maxActive= 20
jdbc.maxTotal= 20
jdbc.maxIdle= 20
jdbc.minIdle=20
jdbc.maxWait= 30000
jdbc.autoReconnect=5
jdbc.initialSize=10
jdbc.defaultAutoCommit=false
jdbc.validationQuery=select 1
jdbc.testOnBorrow=false
jdbc.removeAbandoned=true
jdbc.removeAbandonedTimeout=150
jdbc.testWhileIdle=true
jdbc.timeBetweenEvictionRunsMillis=120000
jdbc.minEvictableIdleTimeMillis=180000
jdbc.numTestsPerEvictionRun=5
jdbc.setMaxWaitMillis=30000
jdbc.removeAbandonedOnBorrow=true
jdbc.removeAbandonedOnMaintenance=true

Irrespective of the configuration type, we were expecting the number of connections to stay within the configured limits.

Is there any specific parameters that needs to be configured for getting this to work as expected in the always-on configuration scenario?

Any pointers will help. Thank you.

Hi Folks

I am kind of stuck up with the below, 

1) Procedure to migrate 2008 SQL Cluster VM (connected to Dell Equallogic 4120E ISCSI 1TB LUN) to SQL 2017 Hyper-v Cluster.

2) Procedure to migrate 2008 VM cluster to  2019 Hyper-v Cluster will be use Microsoft migration tool to migrate to 2012 and then from there perform online migration to 2019? 

Appreciate if some one can help on this.

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

Hi 

I have a VLDB database (3.2 TBs) that is an Availability group that is going to run out of ids soon on a couple of tables. I need to check but I am guessing at least one of these tables is over TB.  I need to convert the int to bigint and the column is not a "clustered" index but it is the primary key.  I still need to check to see if there are foreign keys on the id as well but assume there are. 

The SQL Server is getting upgraded to 2016 in the next week or two. I've read most recommendations advocate for copying over the data into a new table with bigint as the primary key, etc. and re-applying the indexes and foreign key constraints. 

Some questions: 

Is there any scenario that would allow you to keep the database in the AG group? 

Could you use the "Alter Table" online that is available starting in SQL Server 2016 to change the primary NON-Clustered key from int to bigint?

If yes, would you need to drop the DB out of the availability group?  What are the ramifications to the db logging and how much would it cause the database mdf/ndfs and ldfs to grow? Can you keep the application online and users connected if you can use this method? Any other considerations? 

Thanks,

Sue

Sue