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
    2023-01-16T10:33:32+00:00

    Hi,

    In order to reach all those affected, I repeat my latest post from the other thread here, as otherwise you can only hope for a fix from Microsoft "by accident":

    We still lack a reproduction scenario to achieve anything at Microsoft. If someone can reliably generate the problem on their end, perhaps they could do the following:

    1. create a copy of the SQL Server db
    2. reduce the copy to the necessary tables/views to get the error
    3. anonymize data, if necessary
    4. script out the resulting db
    5. reduce the frontend to the necessary parts to get the error
    6. make a zip file with the resulting frontend+backend available and inform us

    I know this is a bit elaborate, but it's currently my only idea to get something going.

    George has also updated his doc article to say that we primarily need a repro scenario.

    Servus

    Karl

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-01-15T18:44:49+00:00

    I've confirmed that, after rolling back to 16.0.15726.20292, Build 2210, our quarterly reports again work just fine.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-01-14T05:41:17+00:00

    Hi Tom, I met with our IT and so far all of the users we have gone back to check were on monthly. Will let you know if/when I run into a Semi-annual.

    Scott

    That makes more sense now, since it appears as if none were on semi-annual. Two words to pass along to your IT support person: Group Policy

    In other words, s/he should be able to configure all employee computers from the comfort of their office (or cubicle), without having to walk around to each user’s computer.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-01-13T16:26:04+00:00

    Hi Tom, I met with our IT and so far all of the users we have gone back to check were on monthly. Will let you know if/when I run into a Semi-annual.

    Scott

    Was this answer helpful?

    0 comments
  5. Anonymous
    2023-01-12T21:15:34+00:00

    I 100% agree that everyone should be on Semi-Annual....especially after the snafu's over the last year or so. We went for years with no issues with Office Updates and I'd say there were at least 3 really bad bugs last year.

    Not sure how/why but we have been dealing with semi-annual users getting the bad version. Painfully working through each one until we have a fix.

    Scott

    Hi Scott,

    So you can confirm that even with the semi-annual channel set, some or all of your users are getting version 2211? Because my intentional update yesterday, in a virtual machine (VMWare Workstation guest machine) left me with a higher build number of version 2202.

    There should be a way for an administrator to create a group policy, for all computers on the same domain, that brings relief to having to update all computers one-by-one.

    Was this answer helpful?

    0 comments