Discussion Locked

Exchange 2003 -- Slow Sending/Receiving

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have Windows 2003 Server that is our DNS, DC, and Exchange Server(I know this is not recommended but you use what you have). We have been experiencing signifcant slow downs in email delivery internally. It only happens once maybe twice a day. Also, our "Outlook 2003 users recieve an error that says Outlook is trying to contact EXchangeServer.domain.local."

Any ideas on where I can start troubleshooting and what I could look at first would be greatly appreciated.
Thanks

11 replies

by haileyan

During these periods of slowness open up task manager on the server. Go to the processes tab and sort by CPU time. See which processes are using up most of the processor time.

I have seen virus scanning software that begins to take up too much CPU time. TrendScanmail for Exchange had this problem and they have a patch out to fix it.

Also check your file system virus scanner and make sure (A) that it is not scanning the M: drive and (B) it is not scanning the exchange database (edb & stm files.)

There is another thing you should check. Unless you have the Enterprise version of Exchange you have a 16GB limit on the database file size. Browse to the Exchange database folder (usually C:\Program Files\Exchsrvr\MDBdata.) Yoru main email database file will be named Priv1.edb. Also check the Priv1.stm. The combined total of the 2 of these is your database size. If you are close to 16GB you are likely experienceing slowness due to extreme fragmentation in the database.

Here is a technote for doing an offline defragmentation of the exchange database. This is the only way to reduce the file size of the Exchange databases.

http://support.microsoft.com/default.aspx?scid=kb;en-us;192185&Product=exch2k

by haileyan

An offline defrag of exchange databases only reduces the file size if there is free space within the database that can be removed.

by james schroer

Check your queues. I had this problem with E2K and I noticed that I had over 500 queues. The time out was set to something like 2 days and to try every 10 mins. I dropped that down to 1 day and bumped up the retry time to every 15 mins and the number of queues fell and it elimiated this problem.

by cgriffith318

The queue does not seem to be the problem. We are only averaging around 15-20 messages at one time in the queue.

by cgriffith318

I am using Symantec Virus for MS Exchange 4.5
The database is no where near 16Gb.
The virus scanner is not scanning the database files.

I will double check to verify that Symantec is not taking up to much of the CPU time and I will try to run an offline defragmentation.

Anymore ideas?

by haileyan

Is the slow down on a regular interval? Same time each day?

It may be due to the rugular only maintenance proceses.

Don't forget to make sure that your antivirus is not scanning Exchange systems that it should not be. M: Drive, edb and stm files.

Answer number two may be right on as well. If you check your SMTP queues there may be a ton of them. If you do not have any files size limits for individual email messages globaly or in the SMTP settings it could be that periodic large attachments are causing the problem.

by cgriffith318

When I recieved the error in Outlook 2003 about trying to contact Exchange Server. I brought up Task manager and looked at the process that was taking up most of the memory.

The process was store.exe It was ranging from 271,764k - 296,852k.

Any ideas on how to fix it?

by cgriffith318

It slows down at different times of the day. There is no pattern to it. I double checked again the scanning of the antivirus and that is not it.

by cgriffith318

Our information store crashed due to a fauling appication store.exe. This was due to an Inbox rule on one of the mailboxes in the store. I called MS and got the Hotfix for this issue. so maybe it had something to do with the slow downs. (hopes!)

Thanks for the comments!

This discussion is closed to new replies.