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.
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.
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.
/gustav
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.
/gustav
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
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.
http://www.fmsinc.com/microsoftaccess/history/versions.htm
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.