Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


When the number of sessions that are used by both user connections and system or background tasks reaches the maximum limit (32,767 or fewer, depending on the User connections Server Configuration Option) in Microsoft SQL Server 2016 or 2019, a required system or background task does not run. Additionally, error 17300 may be logged in the error log. If this task is required for SQL Server to continue running as expected (for example, the XE Dispatcher Task), this may cause SQL Server to shut down.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


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:

More Information

In SQL Server, any user connection or system task must be running within a session by having a unique identifier between 1 and 32,767. The first 50 sessions are reserved for system tasks, and the rest of the sessions may be shared between the user connections and system tasks. Notice that the actual number of system tasks will vary depending on the server or database configuration, such as using Availability Groups, running Full-Text search, and so on. If enough user connections are created so as to leave no space for more system tasks, trying to create an additional system task may fail. Even if the administrator reduces the number of maximum user connections through the server configuration, space for only 50 system tasks is guaranteed.

This fix increases the number of guaranteed system tasks to at least 500. This means that if the configured number of user connections is set to a default or more than 32,267, the actual number of user connections will be limited to 32,267 to guarantee that 500 system tasks can run. If the user sets the number of user connections to less than 32,267, all remaining space up until 32,767 will be available for the system tasks (as opposed to 50 system tasks before you apply this fix).


Learn about the terminology that Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!