Event ID - 17302

Event Id17302
DescriptionThe maximum limit for connections has been reached.
Event InformationAccording to Microsoft

By default, SQL Server dynamically manages the memory needed for user connections. However, the maximum number of connections can be set to a fixed value by setting the user connections configuration option to a value other than 0. Setting the user connections option to a non-zero value is not recommended. If this option is set to a non-zero value and the specified number of connections is exceeded, any additional login attempts will fail with the above message. If the value is set to 1, the SQL Server instance may not start.
More information can be found in the Books Online topics "How to set user connections (Enterprise Manager)" and "user connections Option" as well as in the Microsoft Knowledge Base article 320728
If SQL Server is running and you have an existing system administrator connection to it, issue the following commands to reset the user connection option to the default value of 0 (dynamic):
sp_configure 'user connections', 0
reconfigure with override
The SQL Server instance will need to be restarted for the change to take affect.
If SQL Server will not start or if you are unable to use one of the existing connections, you will need to start the SQL Server instance in a minimal configuration and reset the user connection option to the default value of 0 (dynamic).
1.If the instance is clustered, make sure that SQL Server and SQL Server Agent are offline and that the node you are working from owns the SQL Server disk resources.
2.Stop or take offline MS DTC as well as any other application or service that can connect to this SQL Server instance.
3.Use the following syntax to start SQL Server from a command prompt (you must switch to the binn directory for this instance of SQL Server):
a.SQL Server 2000 default instance or SQL Server 7.0
sqlservr.exe -c -f
b.SQL Server 2000 named instance:
sqlservr.exe -c -f -s {instancename}
SQL Server will start as an application, and it will run in the command prompt window.
4.Use Query Analyzer to connect to SQL Server. Make sure to use a logon profile that has System Administrator permissions on SQL Server.
5.Issue the following commands:
sp_configure 'user connections', 0
reconfigure with override
6.In the command prompt window, press CTRL+C to quit SQL Server. Type Y to shut down SQL Server.
7.Start SQL Server normally.
Reference LinksEvent Id:17302 of Source Id:MSSQLServer

Catch threats immediately

We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.

See what we caught

Did this information help you to resolve the problem?

Yes: My problem was resolved.
No: The information was not helpful / Partially helpful.