Access
A family of Microsoft relational database management systems designed for ease of use.
332 questions
It appears the OP fixed this on their own, or lost interest in fixing it.
Microsoft Access Error After April 2024 Microsoft Update: Too many client tasks
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 33%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EG%3C/text%3E%3C/svg%3E)
Green
0
Reputation points
I am getting the error "Too many client tasks" when querying an Access database using ODBC after an April 2024 Microsoft update was applied, which was the update for Office 2016 KB5002340.
When I uninstalled that update, it's working well again. Is Microsoft aware of this, and will the fix be available soon?
I saw the below thread and where it should be fixed with a Microsoft update. But my problem seems to be the opposite, i.e. it was working and the April 2024 Microsoft update caused it to stop working.
{count} votes
-
AllenLiu-MSFT 42,351 Reputation points Microsoft Vendor2024-05-06T05:58:14.6933333+00:00 It seems the problem is NOT a MCM related problem, it's more related to Access, we add the tag Access so that the experts who are familiar with that topic may help.
-
Green 0 Reputation points
2024-05-06T21:21:31.79+00:00 Thanks, I did update it to remove MCM from the tags.
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 41%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETV%3C/text%3E%3C/svg%3E)
Tom van Stiphout 1,701 Reputation points MVP2024-05-06T21:36:16.96+00:00 First time I hear about it.
As always, at a minimum we need the exact version number and bitness of Access, odbc driver name and version number. What is your back-end database? What version is it at? -
Green 0 Reputation points
2024-05-13T19:18:13.4133333+00:00 It's version 2302. But the database is saved and then placed on a different system where ODBC is used. That system is the one that was updated using KB5002340 from last month, then I started getting those messages. Once Microsoft Update KB5002340 was uninstalled, everything worked well again.
-
Green 0 Reputation points
2024-05-23T20:44:36.33+00:00 Updating the ODBC driver to Microsoft Access 365 is a better solution. The original version I was having a problem with after the Microsoft KB5002340 update was the Access 2016 ODBC driver, as stated originally, with the database being created in Microsoft Access version 2302.
Thanks for your replies everyone.
Sign in to comment
2 answers
Sort by: Most helpful
-
Tom van Stiphout 1,701 Reputation points MVP
2024-05-08T13:54:17.4866667+00:00 -
Green 0 Reputation points
2024-05-13T19:20:51.67+00:00 The issue still exists and I think that avoiding Microsoft Update KB5002340 is not really a good solution. Perhaps for now, yes, but a new update should be released that resolves this problem.
Sign in to comment -
-
Green 0 Reputation points
2024-05-23T20:41:51.8266667+00:00 Updating the ODBC driver to Microsoft Access 365 is a better solution. The original version I was having a problem with after the Microsoft KB5002340 update was the Access 2016 ODBC driver, as stated originally, with the database being created in Microsoft Access version 2302.
Thanks for your replies everyone.