H
hoopster
We recently ran into a problem on two of our terminal servers where some of
our Outlook users would report extremely slow response from Outlook. It
would sometimes take 3-4 minutes for their Inboxes and other folders to
display. Additionally, they would experience significant delays even typing
messages. It didn't matter what mail server they were connecting to, nor did
it matter which server they used.
During troubleshooting I found quite a few users reporting issues with
Outlook hanging/slowness and I wanted to pass along our fix.
After much troubleshooting, the problem turned out to be a stale entry in
the registry. Specificially, the
"HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Journal" key
referenced a recently retired file server. We simply wrote a script to
delete that key for each user affected and the problem went away. I would
suggest that you review the entire
"HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook" tree to ensure
that there are no obviously invalid entries.
Hope this helps somebody.
Doug
our Outlook users would report extremely slow response from Outlook. It
would sometimes take 3-4 minutes for their Inboxes and other folders to
display. Additionally, they would experience significant delays even typing
messages. It didn't matter what mail server they were connecting to, nor did
it matter which server they used.
During troubleshooting I found quite a few users reporting issues with
Outlook hanging/slowness and I wanted to pass along our fix.
After much troubleshooting, the problem turned out to be a stale entry in
the registry. Specificially, the
"HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Journal" key
referenced a recently retired file server. We simply wrote a script to
delete that key for each user affected and the problem went away. I would
suggest that you review the entire
"HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook" tree to ensure
that there are no obviously invalid entries.
Hope this helps somebody.
Doug