MS Access 2013 - High CPU use

I have a 2012 R2 RDS server with Access 2013 installed.
The problem is that after a while (could be a day or two), the process MSACCESS.EXE consumes all CPU.
When this error occurs, the process in all RDS-sessions starts consuming CPU....even in new RDS-sessions.

The temporary solution is to restart the server....then it stops consuming CPU.....for a while.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
First thing I'd do is make sure Office/Access is fully updated on the RDS box. Note also you need to check the Hotfixes for Access/Office to determine if you need any of those:

Also a good idea to be sure the server software is fully up to date as well, of course. Don't depend on automated Windows updates - actually check the version number of the various executables to insure they're at the right version.

If you're still having issues, then we'd need to know more about the application. For example, unclosed objects and such can sometimes cause these things, but recent versions of Access generally do a good job of cleanup.
Gustav BrockCIOCommented:
It should mean nothing. Access has behaved this way since version 1.0, and what "consumes" the CPU is a low priority process that just tries to see what is available.
If you start some other process, say Internet Explorer, the CPU usage by Access should drop at once.

Jim Dettman can probably add something to this.

Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
gustav is correct.   MSAccess has always had coded a tight loop to check for keyboard input, so will show high CPU usage at times.

  However that's a temp thing and it should die off after 30 seconds or so and as he said, if another app needs CPU, it would let it have it.

  So I think we need a little more detail here; Access is a foreground app and as soon as a user logs off, you should have a clean slate.  Access will no longer be running, so I don't see how this can build up over a span of days.

 Fill in some details on exactly what the setup is please.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Dale FyeCommented:
I also don't understand why you would have Access running full time on your server.  That is the only way I would see this happening.

Are your users running all Access applications on their desktops, linked to data on the server?  If not, they should be.  Although I know I've violated this, I have a process that runs 24-7 which pulls data from a poorly designed RDBMS every 15 minutes and updates a SQL Server, but Access never takes up more than about 10% of the server CPU.  SQL Server, however does take up a huge chunk.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.