Microsoft Access Memory Issue after December 6 2022 Build15831 Office Update

Anonymous
2022-12-13T20:25:43+00:00

I've found that Access programs are running out of memory or getting system resources exceeded errors after the recent office update. If I open task manager and watch the memory resources the continue to go up and are never released like they normally do. This was not an issue until the update last week. Working in O365 32 bit access.

Anyone else experiencing this?

Microsoft 365 and Office | Access | For business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

69 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2022-12-16T19:39:33+00:00

    I have the same problem, or perhaps only a similar problem. The Access program reports "out of memory" but there seems to be plenty of memory available. Windows reports 5% memory use - this is a machine with tons of memory. Access.mdb is linking via ODBC to both local and remote SQL Server instances. Popup message reports "Out of Memory".

    Control/break at the error message brings up the "continue/debug" option. When I choose debug, I get another popup message that says "Unexpected error; quitting" with an OK button and a Help button. The Okay button makes the message go away but the program does not quit. It's not doing anything productive, either, I think it's frozen. Task Manager reports 340 MB memory in use by this instance of Access.

    This is happening on a Windows Server 2016 VM with 368 GB RAM, using Microsoft 365 Apps for business, version 2211, build 15831.20190 Current Channel. Problem just started this week after an update. Program launched at 7:30 this morning and around 1:15 the error popped up. Kill the job, restart it and it's okay for at least several hours. Has happened 2 days in a row.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-12-15T15:07:23+00:00

    On Premises. Here is a connection string example.

    ODBC;DRIVER=SQL Server;SERVER=sqlpc2\sql2019;DATABASE=PT;UID=PTUser;PWD=abc;

    Was this answer helpful?

    0 comments
  3. George Hepworth 23,120 Reputation points Volunteer Moderator
    2022-12-15T14:58:48+00:00

    Remotely hosted or on-premises?

    The SQL Server Driver is in the connection string.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-12-15T14:15:42+00:00

    Correct the Sql Server is on a server that we connect to via odbc.

    Having the issue with both SQL Server 2017 and 2019 at my office.

    Was this answer helpful?

    0 comments
  5. George Hepworth 23,120 Reputation points Volunteer Moderator
    2022-12-15T13:58:51+00:00

    Further testing on my part (limited time so far, so not thorough) indicates this problem does seem to appear with a remotely hosted SQL Server, but not a local installation on the same computer.

    Please let us know SQL Server Driver versions in use, and also are your users linking to a remotely hosted SQL Server or an on-premises SQL Server.

    Was this answer helpful?

    0 comments