Symptoms
Assume that you use Always On availability groups (AG) in Microsoft SQL Server. When the AG goes offline, and if the SQL Server database is in the AG, the database Full-Text search auto crawl stops and never starts even when the AG is online again.
You may have to manually resume the auto crawl by running the following query:
"ALTER FULLTEXT INDEX ON Table_1 RESUME POPULATION"
DateTime Server The availability group 'AG' 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.
DateTime spid56 The state of the local availability replica in availability group 'AG' 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.
DateTime spid45s Always On Availability Groups connection with secondary database terminated for primary database 'ag2' on the availability replica 'SQLPROD2' with Replica ID: {ID}. This is an informational message only. No user action is required DateTime spid61s The availability group database "ag2" 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.
DateTime Server Stopped listening on virtual network name 'AGL'. No user action is required.
DateTime spid61s State information for database 'ag2' - Hardened Lsn: '(39:28080:1)' Commit LSN: '(39:28064:2)' Commit Time: DateTime
DateTime spid61s FT: Stopping all crawls for dbid: 9 stoptype: 1
DateTime spid61s CFTCrawlManager::CancelCrawls for dbid: 9, catalog id 0, table id: 0 StopAutoCrawls 1, crawl type 0, cancel type 1
DateTime spid61s CFTScheduler::DeleteAutoCrawl: Removing a CFTSCrawlInfo for dbid: 9, catalog id 0, table id: 0
DateTime spid42s DbMgrPartnerCommitPolicy::SetSyncAndRecoveryPoint: ID
DateTime spid61s Nonqualified transactions are being rolled back in database ag2 for an Always On Availability Groups state change. Estimated rollback completion: 100%. This is an informational message only. No user action is required.
DateTime spid56 Always On: The local replica of availability group 'AG' is preparing to transition to the primary 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.
DateTime spid56 The state of the local availability replica in availability group 'AG' has changed from 'RESOLVING_NORMAL' to 'PRIMARY_PENDING'. The state changed because the availability group is coming online. For more information, see the SQL Server error log, Windows Server Failover Clustering (WSFC) management console, or WSFC log.
DateTime Server The Service Broker endpoint is in disabled or stopped state.
DateTime Server Started listening on virtual network name 'AGL'. No user action is required.
DateTime Server The lease worker of availability group 'AG' is now sleeping the excess lease time (164828 ms) supplied during online. This is an informational message only. No user action is required.
DateTime Server The state of the local availability replica in availability group 'AG' has changed from 'PRIMARY_PENDING' to 'PRIMARY_NORMAL'. The state changed because the local replica has completed processing Online command from Windows Server Failover Clustering (WSFC). For more information, see the SQL Server error log, Windows Server Failover Clustering (WSFC) management console, or WSFC log.
DateTime Server The Service Broker endpoint is in disabled or stopped state.
DateTime spid61s The availability group database "ag2" is changing roles from "RESOLVING" to "PRIMARY" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Resolution
This issue is fixed in the following cumulative updates for SQL Server:
About cumulative updates for SQL Server:
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
References
Learn about the terminology that Microsoft uses to describe software updates.
