BUG: Many Failed Login Attempts Can Cause Error 17809

Article translations Article translations
Article ID: 189039 - View products that this article applies to.
This article was previously published under Q189039
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 17987 (SQLBUG_65)
Expand all | Collapse all


Open Data Services error 17809 can occur on all future connection attempts if SQL Server receives more than 200 failed login attempts in less than one minute. The number of failed logins to reach this condition varies based on the sp_configure memory value for the SQL Server. The error that you may receive in the errorlog is:
ods Unable to connect. The maximum number of '15' configured user
connections are already connected. System Administrator can configure
to a higher value with sp_configure.


To work around this problem, pause the SQL Server service to prevent client activity.


Microsoft has confirmed this to be a problem in SQL Server version 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

More information

This type of problem can occur under the following circumstances:
  • A client application is built with a password that all clients use to connect with.
  • The client application uses Make\Break connection logic or reconnects in the case of being disconnected.
  • The application password is changed to prevent client activity.


Article ID: 189039 - Last Review: October 26, 2013 - Revision: 4.0
Applies to
  • Microsoft SQL Server 6.5 Standard Edition
kbnosurvey kbarchive kbbug kbpending KB189039

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com