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 No comments

69 answers

Sort by: Newest
  1. George Hepworth 23,120 Reputation points Volunteer Moderator
    2022-12-14T22:30:04+00:00

    I have been otherwise occupied all day without time to test further. The two times I did try, memory usage stayed at the same level after closing the query, and only dropped when the accdb was closed. I should be able to return to testing later today.

    It did occur to me to ask what version of SQL Server you and your users have and which SQL Server driver version you use.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-12-14T14:24:39+00:00

    Hello, if the user closes the program it does clear the memory out. The issue is if the continue to use it over the day or days. The memory keeps climbing until there is none available.

    In your scenario what happens if you run the same query multiple times without closing?

    Was this answer helpful?

    0 comments No comments
  3. George Hepworth 23,120 Reputation points Volunteer Moderator
    2022-12-14T14:22:02+00:00

    As a follow up, I just ran a query against a SQL Azure backend. I am also on MS 365, Build 16.0 .15831.20098 32-bit.

    I used a Cartesian query that generated over 8.5 million records. Memory usage did climb while the query ran, but not enough to cause an out of memory condition, not out of the ordinary in my experience, really. Memory Usage didn't drop, according to Task Manager, when I closed the query, but when I closed the accdb, it did.

    It might be helpful to describe a testing scenario in which you see this problem resulting in an Out of Memory situation.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-12-14T13:49:02+00:00

    Hi Tom, unfortunately some of my customers are set this way. We make recommendations but their IT dictate the update policy. I'll have changing to semi-annual in my back pocket as an option as it comes up.

    Thanks

    Was this answer helpful?

    0 comments No comments
  5. Tom van Stiphout 40,216 Reputation points MVP Volunteer Moderator
    2022-12-14T13:39:50+00:00

    It appears you are speaking of the Current Channel, which gets updates early. I find it too aggressive for Production systems. I would recommend backing off to a slower channel. Search online for "change office update channel" and you will find there are several ways depending on finer points.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments