Azure SQL Error - Resource ID : 2. The session limit for the database is xxx has been reached.

Question

I have an Microsoft Access application that uses an Azure SQL server. This has been running without any problems for many months.

Starting at the end of last week I'm getting the error - 'ODBC Driver for SQL Server Resource ID : 2. The session limit for the database is xxx has been reached.' This stops all users of the database from being able to do anything.

I can see by using the sp_who proceedure in SQL Server Management studio that only some of the machines that the application is running on are generating large numbers of sessions that remain in a 'sleeping' state and are not being cleared.

Nothing in the application has changed recently and I assume that this has been caused by a Windows and/or Access update that was applied last week.

Any information about how to solve this issue would be greatly appreciated.

Answer 1

This issue was fixed with the latest Office update (version 2408 - 17928.20156).

Thanks for the comments that were posted.

Answer 2

Hi,

This is most likely due to the current bug that has been filling this and other forums for 2 weeks.

A fix for this problem should be coming later today. We will then also update our documenting AFo article .

Servus
Karl
****************
Access Forever News DevCon
Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg

Answer 3

There's a new bug affecting Microsoft Access and this sounds like one of its symptoms.

Take a look at: https://www.devhut.net/another-msaccess-exe-process-not-closing-properly-bug/ perhaps the workarounds proposed there will help while we wait for an official fix from Microsoft in a future update.

Workaround #2, from the above article, seems to work for a lot of people while we wait for a proper fix from Microsoft!