FIX: Error 35262 with Severity 17 occurs when database is part of an Availability Group in SQL Server 2017

Applies to: SQL Server 2017 Developer on WindowsSQL Server 2017 Enterprise Core on WindowsSQL Server 2017 Enterprise on Windows

Symptoms


When a database is part of an AlwaysOn Availability Group (AG), then you may receive an error message in SQL server error log with Severity 17. 
Date/Time spid20s Always On: The availability replica manager is starting. This is aninformational message only. No user action is required.
Date/Time spid7s Error: 35262, Severity: 17, State: 1.
Date/Time spid7s Skipping the default startup of database'DatabaseName' because the database belongs to an availability group(Group ID:  GroupID). The database will be started by the availabilitygroup. This is an informational message only. No user action is required.
Note In general, error with severity 17 indicates that the statement causedSQL Server to run out of resources (such as memory, locks or disk space forthe database) or indicates software errors that cannot be corrected by theuser.

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 update 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.