Share via

Office 365 - specifically Access

Anonymous
2019-01-02T15:40:21+00:00

I am constantly getting a system resources exceeded (database is under 1gb) system has 64 gb ram and over 3 tb in hard drive size. 

The only temporary solution I can find is to bring up task manager and go to the details tab and right click Access and click "set affinity" and select only 1 of my 12 cores (and has to be CPU 0 -- any others and Access repeats error) Once I set affinity to only one core, the database runs fine.

This issue repeats in all Access databases on my network. 

It seems odd that Access can only function correctly on one core of a twelve core system... The issue is that I have to do this with each and every database each and every time I open one. 

It is very apparent that my system resources are not be exceeded even though this is the message Access provides.

Microsoft 365 and Office | Access | For home | Windows

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

14 answers

Sort by: Most helpful
  1. Anonymous
    2019-01-31T01:51:58+00:00
    1. FIRST SUGGESTION:  There was a very similar thread where the problem was solved by increasing the MaxLocksPerFile registry entry which could be accomplished in VBA:

    DAO.DBEngine.SetOption dbMaxLocksPerFile, 1000000

    URL:  https://answers.microsoft.com

    1. SECOND SUGGESTION: If that doesn't work, unfortunately, there are specific database specifications for Access, and it has very little to do with the amount of ram, the number of cores in the processor or the HD size. Check out:

    There are a few "Project Specifications"/limitations too... check out the URL below:

    https://support.office.com

    I suspect you're going to have to simplify your project and slowly add back in the components to see which one is giving you the error. If the error comes up when you run a query or a macro, focus on that aspect of your work. You're going to have to play detective here...

    Good luck!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2019-01-03T22:31:18+00:00

    Hi Cherokee,

    Thanks for your update in private message. We understand the database has sensitive information and cannot be shared.

    Have you tried the suggestions mentioned in my initial reply?

    If the issue persists, could you also share with us other 2 required information? A screenshot of Product Information and the actions you perform before the error  "system resources exceeded" appears.

    Thanks,

    Tina

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2019-01-03T15:42:55+00:00

    Hi Cherokee,

    We'd like to suggest you try followings:

    1.The issue seems to occur on mostly 64-bit Access. If you are currently using 64-bit of Office and if you are willing, we suggest you try out 32-bit Access instead. You can install 32-bit of Office from Office 365 software page.

    2.Repair Office installation via this article.

    3.Update Office to the latest version from File>Account>Update Options>Update Now.

    If the issue persists after you try the suggestions, please share with us information below for troubleshooting:

    1.In Access, please click File>Account, then capture a screenshot of Product Information.

    2.When does the error "system resources exceeded" appear? What action are you performing before it appears? Running a query?

    3.Please share a sample database with us for test. We will send a private message to collect it.

    Thanks,

    Tina

    Was this answer helpful?

    0 comments No comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  5. Anonymous
    2019-01-02T16:05:35+00:00

    No solution for you, but i can confirm that with each newer version we have been seeing this error more and more frequently.

    Was this answer helpful?

    0 comments No comments