Solved

Exchange going really slow - outlook exclamation mark!

Posted on 2008-10-17
4
974 Views
Last Modified: 2011-10-19
We have exchange 2003 running on server 2003 R2 across two sites, one domain. Was running fine until last week when people started getting "outlook is trying to contact exchange server" exlamation error. CPU was fine as was memory. We defraged just in case overnight but still no difference.
Then, by coincidence, we had to reboot our DC for the site. (which is also the GC). Immediately exchange recovered and was lighting fast. Since then we still get slowdowns, but these are immediatly resolved by rebooting the DC. Error logs don't seem to show anything untoward and now at a loss to explain/fix it..................
0
Comment
Question by:davelongman
  • 2
  • 2
4 Comments
 
LVL 8

Assisted Solution

by:greesh_hem
greesh_hem earned 200 total points
ID: 22740685
Try to run a DCDiag on the exchange server with the switch

DCdiag /s:Servername

where Servername would be the NETBios name of your domain controller and try to look at the diagnostics to see if you find any failures.

Also try to take a network trace since there is a good possibility that the network packets may be getting dropped.
0
 
LVL 1

Author Comment

by:davelongman
ID: 22740831
Dcdiag passed all tests - file attached.

What's the best way to take a network trace please?

Thanks,
dcdiag.txt
0
 
LVL 8

Assisted Solution

by:greesh_hem
greesh_hem earned 200 total points
ID: 22765128
Install Netmon on one of the Outlook client machine and then run it from there.

http://blogs.technet.com/netmon/
0
 
LVL 1

Accepted Solution

by:
davelongman earned 0 total points
ID: 22851170
Thanks greesh hem, we didn't see packet loss so ran exchange tech assistant. This has shown RPC delays and also a disk bottleneck occuring (we believe due to MAPI clients increasing over time). I am going to install a new scsi drive and move the transaction logs over so hopefully this will resolve the situation. I am confused as to why booting the GC improved matters, but I think it may be because exchange then temporarily stops the processing that was hammering the disk access and then once it found the backup GC it started to slow down again.

Thanks for your help in at least proving it local to the exchange server itself, even though initial diags looked like a DC/AD problem.
0

Join & Write a Comment

Local Continuous Replication is a cost effective and quick way of backing up Exchange server data. The following article describes the steps required to configure Local Continuous Replication. Also, the article tells you how to restore from a backup…
Marketers need statistics and metrics like everybody else needs oxygen. In this article we explain how to enable marketing campaign statistics for Microsoft Exchange mail.
In this video we show how to create an Address List in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Organization >> Ad…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

747 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now