Re: Exchange 2000 Server Very Slow

From: Matthew Byrd [MSFT] (matbyrd_at_online.microsoft.com)
Date: 03/24/05


Date: Thu, 24 Mar 2005 16:48:05 -0500

Hi Gscheffen,

Based on what your are describing I would say that either you have a memory
leak or you are having performance issues with your Disk drives.

Also I noticed in your post that you are running a nightly defrag of your
Exchange server. Microsoft does not recommend ever running defragmentation
utilities on drives that contain Exchange databases. These can do harm to
the databases and they will not gain you any performance as the databases
will still be random reads and writes based on usage and the internal
structure of the database.

You are going down the right path by using the Exchange performance white
paper. What I can recommend is that you try the following actions.

1) Apply the latest rollup fix from Microsoft:
http://www.microsoft.com/downloads/details.aspx?familyid=363A57A4-8BED-4BBB-BBE4-ABC11AB04611&displaylang=en

2) Download ExBpa from www.exbpa.com and run the tool against your
Environment. This tool should help to reveal if you are not ideally
configured for Exchange performance.

3) In your perfmon counter logs concentrate on the sec/read and sec/write
counter under physical or logical disk. The average values should not
exceed 0.020 seconds for optimal performance. Also you should not see any
spikes greater than 0.100 seconds.

4) Remove 3rd party software from the server one at a time. This will help
to eliminate what if any 3rd party software is causing this issue.

Hope this helps,

-- 
Matthew Byrd
Microsoft PSS
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
<gscheffen@gmail.com> wrote in message 
news:1111594708.770662.207220@f14g2000cwb.googlegroups.com...
> That symptom is the exact symptom to a badmail folder issue.  I went
> round and round and round with Microsoft finally they refunded me
> because I fixed it by simply directing the badmail to a different
> folder.  Try setting the badmail to go to a different folder.  If it
> fixes it I would look into how you are deleting the bad mail.  Also I
> have seen a similar issue to this on an SBS 2000 box that had a problem
> with a mirror that was not being properly reported in the event log,
> when I replaced the drive it performed well.  Both cases the task
> manager graphs looked like the system was not working hard at all.
>
>
>
> Curt Winter wrote:
>> Scott,
>>
>> I clear the BadMail FOlder every morning.
>>
>> We run diskkeeper, this defrags the server every night.
>>
>> The Pagefile has already be moved off the system Partition, and
> plenty of free space on the drive.
>>
>> I am capturing Performance Monitor Data currently, using the counter
> listed in the Exchange Performance Troubleshooting Guide.  Friday
> morning I will have the completed logs, the server was slow again
> today, so the slowdown should be in the Perf Logs.
>>
>> I have taken your advice and used shutdown.exe to schedule a reboot
> every morning until I can drill down to the root issue.
>>
>> Thanks for the suggestions.
>>
>> Curt
>>
>>      ----- Scott Harding - MS MVP wrote: -----
>>
>>      You could schedule a reboot with shutdown.exe from the resource
> kit as a
>>      temporary band aid. It sounds like some program has a memory
> leak and thus
>>      it takes a couple days to have the problem. This is going to be
>>      troubleshooting 101. Disable any unnecessary services, clear out
> any temp
>>      folders, run a full virus scan on the system, etc. If you
> shutdown exchange
>>      services during the slowness do things change? What about other
> services?
>>      How much RAM is available when this happens? Clear out the
> badmail folder?
>>      Check disk space? Defrag the drive? Move the pagefile off the
> system
>>      partition?
>>
>>      --
>>      Scott Harding
>>      MCSE, MCSA, A+, Network+
>>      Microsoft MVP - Windows NT Server
>>
>>      "Curt Winter" <curt.winter@rideone.com> wrote in message
>>      news:A2A61D70-8B83-44F6-B7A0-90E1EA0EA0C6@microsoft.com...
>>      > We are running Exchange 2000, SP3 on Windows 2000 SP4, on a
> Dell PowerEdge
>>      with two 1.0GHz Pentium IV CPU's with 1GB of RAM.
>>      >> After two days the server acts like it is running in quick
> sand,
>>      everything is slow.  Click on start menu wait 10-15 minutes for
> the menu to
>>      appear.  If you try and open a program, wait 10-15 minutes.  The
> CPU is
>>      80-95% free, the Memory shows normal usage.  OWA users can not
> open there
>>      inboxes, just hangs.  RPC clients get constant time out waiting
> for data.
>>      POP3 users get time out errors.
>>      >> The only thing I have found in the Event log the following
> entry:  (This
>>      is after the box slows way down)
>>      >> The categorizer is unable to categorize messages due to a
> retryable error.
>>      >> MSExchangeTransport
>>      > EVENT ID 6004
>>      >> We run iHateSPAM, Symantec Antivirus Client (which has
> exchange disabled,
>>      and set not to scan the exchange folders) and Disksweeper on the
> server
>>      also.
>>      >> All three of those software packages also run very slow when
> the Server
>>      goes into quick sand mode.
>>      >> I have upgraded the BIOS on the Server and the Firmware on
> the PERC RAID
>>      Controller.  Doubled checked the hard drive on the RAID
> controller all
>>      working fine.
>>      >> Once we re-boot the box works fine again for about two days,
> before it
>>      returns to Quick Sand Mode again, forcing us to re-boot.
>>      >> I would like to find a solution to the slowness issues, or
> for lack of a
>>      solution, how do I schedule the server to re-boot itself every
> morning ....
>>      >> Thanks for any assistance.
>>      >> Curt Winter
>>      > curt.winter@rideone.com
> 


Relevant Pages

  • Re: Exchange 2003 - Archiving and deleting emails
    ... The log file folder should only have a few megs or so of logs. ... Have you deleted old logs on server? ... Not old Exchange logs as those ... See what SBS support is working on ...
    (microsoft.public.windows.server.sbs)
  • RE: Windows server 2003 SP1
    ... I agree with Marina that you must keep the same server name to restore Exchange database. ... please also refer to the following KB articles for restore Exchange database. ... >Do the same for the public folder store ...
    (microsoft.public.windows.server.sbs)
  • Re: addressed before : exchange temp tables. server reboot, old mails sent.
    ... i have excluded exchange folders from file level anti virus ... server reboot, old ... At this time, I would suggest that we clear Temp Folder, ... |> TempTables according to the Exchange Server configuration. ...
    (microsoft.public.windows.server.sbs)
  • Re: After manually undoing a recent MS Update, my server is a mess
    ... information to login to my server remotely to look around--hoping he could ... External USB is no replacement for local drives. ... stored on) and chose to only restore the System files. ... The "Cases" drive was actually a shared folder on an external ...
    (microsoft.public.windows.server.sbs)
  • Re: Backing Up Exchange/Outlook
    ... First off I can confirm that Outlook is looking to Exchange for mail ... Therefore, when I go into NTbackup on the server, I need to back up ... and the First Storage Group consists of Mailbox Store and ... the Public Folder Store??? ...
    (microsoft.public.backoffice.smallbiz2000)