-
2
- #1
innerspaces
IS-IT--Management
I had problems with retreiving email to display in my inbox, it was slow in Outlook XP / 2002 (and sometimes 2K) and Exchange Server 2K.
I have found a few reasons for it.
if you get the message on the outlook client
Outlook is retreiving data from the Microsoft Exchange Server "servername or FQDN". You can cancel the request or minimize this message to the windows taskbar until the Outlook closes the message automatically.
I found a few things that caused the problem.
When I looked at my application event log, I found many events informing me of the following problems (in other words these were the problems):
a. exchange virtual memory/cache fragmented
b. dns server or domain servers not responding
c. global catalogue not responding
d. many exchange errors
the reasons I found for this were
- on the exchange server - reboot it
- services - ensure that intersite messaging is started
- mail database needs offline defragging (priv1.mdb)
- are you getting to your 16gb limit for combined mailbox storage with MS Exchange 2K standard edition
- maybe the client machine needs the outlook profile resetting, delete old one and recreate it.
- start thinking about service packs for Exchange Server - if you put SP3 on, there are many rollup packs since then - THE MOST RECENT is May 2004, if you have or have not done rollup packs - just upgrade it now, (look! if this tip gets old, you are gonna have to look at the Microsoft site yourself and get the latest service pack or rollup pack) If you read up about the rollup pack, it fixes loads of problems which could be the cause of the slow email problem. I actually found that that the error showed only after I migrated to SP3.
the link to the May 2004 rollup is
ensure it has the v2 in the name of the patch, as there is another KB article and rollup patch for April 2004, which is v1, but doesn't mention v1 it in the name of it.
Now another problem I found was that when clicking about in the inbox, the emails took several seconds to respond and display - it was slow displaying the email. the reasons for this are as follows:
- MSN Messenger is running on the same computer
- ms messenger is running in services
- Instant messenger is running in outlook (XP and 2003 only)
personally I would not have any type of messenging running on my network - it is a security disaster and a waste of staff time. Anyway this is the fix
- in outlook, go to tools, options and other and remove the tick for instant messenger - close outlook and reopen it again (wow - fast now huh!)
- in the task tray, open the options for the ms messenger, and untick everything to prevent it from running at all.
- right click on my computer and select manage, expand the folders to find the services and disable messenger
now open outlook again and have a click about in the inbox, if the email shows instantly, this has fixed your problem, if not - maybe you got other problems.
I hope this helps everyone out there, I have exhausted my resources and found that these fixes above have resolved my issues - perhaps your issue is the same and it helped you. but if it isn't - it was worth a try anyway.
I can't respond the any further questions, I only know what I have typed here and it took me a couple of days to find it out in the first place
Julie-Ellen
I have found a few reasons for it.
if you get the message on the outlook client
Outlook is retreiving data from the Microsoft Exchange Server "servername or FQDN". You can cancel the request or minimize this message to the windows taskbar until the Outlook closes the message automatically.
I found a few things that caused the problem.
When I looked at my application event log, I found many events informing me of the following problems (in other words these were the problems):
a. exchange virtual memory/cache fragmented
b. dns server or domain servers not responding
c. global catalogue not responding
d. many exchange errors
the reasons I found for this were
- on the exchange server - reboot it
- services - ensure that intersite messaging is started
- mail database needs offline defragging (priv1.mdb)
- are you getting to your 16gb limit for combined mailbox storage with MS Exchange 2K standard edition
- maybe the client machine needs the outlook profile resetting, delete old one and recreate it.
- start thinking about service packs for Exchange Server - if you put SP3 on, there are many rollup packs since then - THE MOST RECENT is May 2004, if you have or have not done rollup packs - just upgrade it now, (look! if this tip gets old, you are gonna have to look at the Microsoft site yourself and get the latest service pack or rollup pack) If you read up about the rollup pack, it fixes loads of problems which could be the cause of the slow email problem. I actually found that that the error showed only after I migrated to SP3.
the link to the May 2004 rollup is
ensure it has the v2 in the name of the patch, as there is another KB article and rollup patch for April 2004, which is v1, but doesn't mention v1 it in the name of it.
Now another problem I found was that when clicking about in the inbox, the emails took several seconds to respond and display - it was slow displaying the email. the reasons for this are as follows:
- MSN Messenger is running on the same computer
- ms messenger is running in services
- Instant messenger is running in outlook (XP and 2003 only)
personally I would not have any type of messenging running on my network - it is a security disaster and a waste of staff time. Anyway this is the fix
- in outlook, go to tools, options and other and remove the tick for instant messenger - close outlook and reopen it again (wow - fast now huh!)
- in the task tray, open the options for the ms messenger, and untick everything to prevent it from running at all.
- right click on my computer and select manage, expand the folders to find the services and disable messenger
now open outlook again and have a click about in the inbox, if the email shows instantly, this has fixed your problem, if not - maybe you got other problems.
I hope this helps everyone out there, I have exhausted my resources and found that these fixes above have resolved my issues - perhaps your issue is the same and it helped you. but if it isn't - it was worth a try anyway.
I can't respond the any further questions, I only know what I have typed here and it took me a couple of days to find it out in the first place
Julie-Ellen
