Symptoms
Consider the following scenario:
-
You are running Microsoft SQL Server 2014 or Microsoft SQL Server 2012 Service Pack 2 (SP2) on a server that hosts the secondary replica of an availability group as part of a rolling upgrade.
-
You have applied one of the following updates to the SQL Server installation:
-
SQL Server 2014 Cumulative Update 5
-
SQL Server 2012 Service Pack 2 Cumulative Update 4
-
SQL Server 2012 Service Pack 2 Cumulative Update 3
-
-
To finish installing the cumulative update, you restart this secondary replica.
-
You fail over the availability group that is transitioning the updated secondary replica to the primary role.
In this scenario, you may experience one or more of the following symptoms on the server that's running SQL Server and that's now hosting the primary replica of your availability group:
-
The secondary replicas are reported as "NOT SYNCHRONIZING."
-
Deadlocks that involve the session that recovered one of your availability databases are reported in the SQL Server error log.
-
If your availability database is enabled for SQL Server Service Broker, messages in your availability database may not be processed successfully.
For more information about these symptoms, this cause, and possible workarounds, see the following article in the Microsoft Knowledge Base:
3033492 AlwaysOn availability groups may be reported as NOT SYNCHRONIZING after you apply SQL Server 2014 CU5, SQL Server 2012 SP2 CU4, or SQL Server 2012 SP2 CU3
Resolution
Service pack information
To resolve this issue, obtain Service Pack 1 for SQL Server 2014.
For more information about SQL Server 2014 Service Pack 1 (SP1), see bugs that are fixed in SQL Server 2014 Service Pack 1.
Cumulative Update information
This issue was first fixed in the following cumulative update of 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:
To resolve this problem, apply the following hotfix. This hotfix is a critical on-demand (COD) hotfix. This COD hotfix should be applied instead of the following cumulative updates:
-
SQL Server 2014 Cumulative Update 5
-
SQL Server 2012 Service Pack 2 Cumulative Update 4
-
SQL Server 2012 Service Pack 2 Cumulative Update 3
Important If you have already applied these cumulative updates, you must use the workaround that's described in the following Knowledge Base article:
3033492 AlwaysOn availability groups may be reported as NOT SYNCHRONIZING after you apply SQL Server 2014 CU5, SQL Server 2012 SP2 CU4, or SQL Server 2012 SP2 CU3
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website:http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesTo apply this hotfix, you must have one of the following installed:
-
SQL Server 2014
-
SQL Server 2012 Service Pack 2
Restart informationYou may have to restart the computer after you apply this hotfix.
Replacement informationThis hotfix does not replace any previously released hotfix.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
Learn about the terminology that Microsoft uses to describe software updates.