Exchange sloowwwwww, should I defrag?

[goalie35]

Hi everyone,

Lately our Exchange has been running extremely slow. One day it's fine the next day it's lagging. Here is our scenario. Win2k Adv Server SP3, running Exchange 2000 SP3. We only have about 20 users running off an IBM Netfinity server 800Hmz 512mb RAM. Everyone is running either Win2k Pro or XP Pro with Outlook XP.

We seem to be getting alot of "requesting data..." boxes. But it's only happening to the same users. I noticed these handful of users have 5000+ items Sent & deleted. They have also been with the company since day 1. Could that be the issue? I have 3000 items sent & 3500 deleted & mine runs fine. I have only been here about 6 months. Could the lagging problem they are seeing be related to their items being way at the beginning of the database. The DB is only about 3GB's.

Should I run that eseutil to defrag? Would that help? Other than that we have no problems. Please help they are up my a$$.

 

[GaryRumson]

If i would you I would get some of these people to archive their old mail and get it off the server. As for defraging, your exchange should do that nightly to reclaim free space and with only 3 ggb your not in any trouble their. I also notice you only have 512 of memory. I would double that to 1GB, exchange takes a lot memory.

 

[goalie35]

Thanks man.

I actually just went around & set up auto-archiving on most machines. To get rid of old old mail off the server. I will def talk to them about upgrading the memory.

Is there a setting in Exchange for auto-defragging everynight? Am I missing it or is it built in already.

So you suggest don't run eseutil to defrag?

Thanks again!

 

[GaryRumson]

It should be set to defrag nightly. Go to your exchange server name and then mailbox store, right click on the store and go to Properties. You should see a tab called maintence. Here it should be set to run and defrag the database nightly. You can do a manual defrag if you want if this nightly cleaning doesn't help. Adding a little more memory never hurt. Also check the event viewer (application log)to see if anything looks wrong.

 

[goalie35]

GaryRumson,

Thanks so much for the help. I just checked the maintenance file & it seems to be set to run nightly from 3am to 7am. That should keep a nice defragged store correct?

I am definately trying to get them to push for more memory we only have 256mb. At least 512mb or 1gb would be nice.

I do keep getting an error in the Event log that I can't seem to get rid of.
MSExchangeFBPublish EventID:8213
System Attendant Service failed to create session for virtual machine "server". The error number is 0xc007052e

I found the Q article from Microsoft but that does not fix it. I have applied sp3 several times with no luck either.

 

[GaryRumson]

Well the Q article I guess your talking about is 296151. I'm not sure where else I could push you on that error. You say you only have 256mg of mem? I would have at least 512K in that machine. Other than that I'm out of ideas, hopefully the memory will work though.

 

[goalie35]

Yeah that was the article. I've tried the registry edit but no luck with that. There was also another article about resetting the Exchange Admin account. Tried that too but not luck. It's strange one day we might get like 10 of those errors, yet another day we can get like 200. Can't pinpoint any certain activity either. Thanks again!

 

[sroumald]

Hi guys , I'm having exactly the same problem u r having . I think the problem comes with the service pack 3 not but I'm not sure. I have a San Hp VA7400 all , all my exchange data is in their somehow it is supposed to be a rocket but it is behaving like a sick tortoise.I have two Servers one lh6000r with 512 mb and lp1000r with 512 mb of ram .All of them used a Emulex hba card connected to a brocade switch .It must be a rocket that is not the case.Can Anyone help me

Thanks Netadmin

Saleem

 

[goalie35]

Saleem,

Yeah I agree. Ever since I loaded SP3 things went downhill & also I keep getting this ERROR:

MSExchangeFBPublish EventID:8213
System Attendant Service failed to create session for virtual machine "server". The error number is 0xc007052e

Never got that until after SP3 install.
I wish I could revert back to SP2!

 

[member 141630]

SERVICE PACK 3 -
I have found that after applying service pack3 my IMAP and POP3 have ceased to work reliably - both services very intrmittent. Built a new test server and the moment I applied SP3 for Exchange, my POP3 and IMAP access became flaky again - (FYI the server drops the client connection request as soon as a username has been submitted).. about 90% of the time. So I will NOT be using SP3 for Exch2K.
Incidentally, SP3 for Windows seems OK... havent any issues with that..... UNLESS YOU KNOW DIFFERENT!!! If you do let me know of your findings...

In the meantime I would say SP2 for Exchange is the only stable release..