OL2003 -- 100% processor usage during e-mail check

[Lanny Heidbreder]

Hey, all.

Windows XP
512 MB RAM
Pentium IV 2 GHz

I have about 30 e-mail accounts that I check through Outlook 2003.
Sometimes when doing a Send/Receive, Outlook will get stuck on an
account or two or five, and processor usage will spike to 100% and stay
there. Cancelling all in-progress transfers does NOT help; only killing
the outlook.exe process frees up my processor, and even then sometimes
it makes explorer.exe hang.

Any suggestions? (Other than use fewer e-mail accounts? )

Thanks,
Lanny Heidbreder

 

[Guest]

Use Outlook only for POP accounts and skip any web based mail accts. I doubt you have 30 pop accts. Outlook essentially converts itself to a browser for web mail--or 30 browsers. Use your browser instead. What you can do is arrange the accts into separate groups and check mail in smaller groups. Look up Account groups in Help.

 

[Lanny Heidbreder]

Use Outlook only for POP accounts and skip any web based mail accts. I doubt you have 30 pop accts. Outlook essentially converts itself to a browser for web mail--or 30 browsers. Use your browser instead. What you can do is arrange the accts into separate groups and check mail in smaller groups. Look up Account groups in Help.

Hmm, I'll try that. I actually DO have 30 POP accounts --- I own two
domains and create accounts liberally for different purposes.

I don't /think/ it's the two Hotmail accounts causing the trouble,
because I've seen the list be pared down to only POP accounts when the
trouble strikes. But maybe the culprits are already off the list when
they cause the problems. I'll give that a try.

Thanks,
LH

 

[Lanny Heidbreder]

Nope. I eliminated all non-POP accounts from the group that
auto-send/receives. Processor usage stuck at 100% again. When I killed
it, the processor usage stayed at 100%, but under AIM. It's done this
before, too --- the max processor usage hops around from application to
application. But it ALWAYS starts with Outlook.

 

[Thor Kottelin]

Processor usage stuck at 100% again. When I killed
it, the processor usage stayed at 100%, but under AIM. It's done this
before, too --- the max processor usage hops around from application to
application. But it ALWAYS starts with Outlook.

I wonder whether a virus scanner or similar software might be tying up your
applications when they try to access files. This is a shot in the dark, but
you might want to try temporarily shutting down those programs (under safe
conditions, of course).

Thor