Question Access consuming 100% CPU and unable to exit gracefully on Windows Server 2008 (MS Ac

vaibhav1985 · Feb 23, 2015

Hello Guys
I am facing issue on windows server 2008 server machine having MS Access 2007 installed. Database is not able to quit and freezes. Grey windows remains.
I am executing a set pf macros.. which is called from a batch file in a sequence.

The command which is executed to quit the database is 'DoCmd.Quit acQuitSaveAll'. On close "Compact & Repair" option is already selected).

Please Help !!!!!

gemma-the-husky · Feb 23, 2015

it's probably the C&R. Trying to C&R over a network will be very slow and unreliable

100% take that off.

Do it manually from time to time.

AcQuitSaveAll saves design changes that haven't already been saved. nothing to do with data. I would change that too.

Once you do this, I expect it will close normally.

vaibhav1985 · Feb 23, 2015

I need to perform the compact and repair on database closing automatically.. as it is being executed from task scheduler.

This problem has started coming after Access 2003. It was working fine in Access 2003. Is it related to comaptibility between Access 2007 and Windows Server 2008?:banghead:

gemma-the-husky · Feb 23, 2015

The best way to C&R on a network is to copy to a local PC, do the C&R and copy back.

Most of us would never try and do a C&R on close.

A2007 has a larger footprint than A2003, so it probably is related to memory resources. As I say, I would just not ever do a C&R on close. I would prefer to take a copy of the dbs before doing this.

Are there size issues? ie is the dbs near 2GB?

vaibhav1985 · Feb 23, 2015

No, this is not a problem related to DB size .
However it seems that when there is a design change, it hangs at 'DoCmd.Quit acQuitSaveAll'

Database .exe can be seen in the task manager running at 100% CPU load.
and if we try to close manually by clicking the 'X' button at the top right, it is not getting closed. It freezes. It needs to be ultimately killed from the task manager.

Please suggest.. if you have any other inputs.

spikepl · Feb 23, 2015

it is being executed from task scheduler.

and

when there is a design change, it hangs at 'DoCmd.Quit acQuitSaveAll'

Please explain how there can be a design change in a job run from the task scheduler.

jdraw · Feb 23, 2015

How well are the design changes -- designed, thoroughly tested --individually and collectively - user tested in context ? This 100% utilization is often the result of infinite loop in processing logic - may not be in your situation. I suspect your testing procedures, but you haven't told us much about that. And corruption could also be a factor, but I'd also like to hear the response to spike's question.

Question Access consuming 100% CPU and unable to exit gracefully on Windows Server 2008 (MS Ac

vaibhav1985

New member

gemma-the-husky

Super Moderator

vaibhav1985

New member

gemma-the-husky

Super Moderator

vaibhav1985

New member

spikepl

Eledittingent Beliped

jdraw

Super Moderator

Similar threads

Users who are viewing this thread