MS Access Multiuser - Access Freezes After Using Performance Analyzer

Author

Access Freezes After Using Performance Analyzer

Ed Ardzinski

2005-08-11, 1:29 pm

Not sure this is the best NG to post this in, but none of the others seemed
any more appropriate...

I just had 2 instances of a freeze up after using the performance analyzer
to suggest some indexes...it was an odd freeze up: Could still get to Access
via clicking on the task bar icon, but Alt-Tab did not recognized that Access
was there. And Access was absolutely unresponsive to anything.

The Task Manager said "running" but instantly returned the "not responding"
dialog as soon as I indicated to end task.

Anyone ever see this? TIA

btw, A2K3, Win XP (not on SP2)

SteveS

2005-08-26, 3:24 am

"Ed Ardzinski" wrote:

> Not sure this is the best NG to post this in, but none of the others seemed
> any more appropriate...
>
> I just had 2 instances of a freeze up after using the performance analyzer
> to suggest some indexes...it was an odd freeze up: Could still get to Access
> via clicking on the task bar icon, but Alt-Tab did not recognized that Access
> was there. And Access was absolutely unresponsive to anything.
>
> The Task Manager said "running" but instantly returned the "not responding"
> dialog as soon as I indicated to end task.
>
> Anyone ever see this? TIA
>
> btw, A2K3, Win XP (not on SP2)

I don't think that Access froze... the performance analyzer sometimes takes
what seems like a long time (sometimes 10 minutes seems forever!!!).

When you hit "End Process" and the "not responding" dialog box appears, it
indicates that Access didn't respond to the request to stop. This will/can
happen with *any* program.

Try arranging the desktop so you can see the Performance tab of the Task
Manager and Access, then start the performance analyzer. Watch the CPU usage
graph to see if the processor load goes to 100% and stays there. If so,
Access is working as hard as it can - go have a cuppa and a stretch.

Depending on the complexity of the database, CPU speed, amount of RAM, hard
drive space, time of day, what season, what direction your computer faces,
how you hold your tongue <g>, etc, it could take from one minute to over 30
minutes - sometimes hours even...... Remember: spend time now to save time
later.

HTH
--
Steve S
--------------------------------
"Veni, Vidi, Velcro"
(I came; I saw; I stuck around.)

Sponsored Links