Exchange 2003 issue
We have exchange 2003 running on server 2003. Recently e-mails have stopped being sent/received on a regular basis.
When I try and stop exchange Infostore it says it can't do it. I will then restart the server and all will be fine. Looking in the event log there is one message 'The memory settings for this server are not optimal for exchange'.
lack of space on the C drive? lack of space, possibly, writing the exchange transaction logs? that was the issue here.
Can't be space as we have over 130gb free!!
How about RAM, Exchange likes its RAM but it does make a bit of a mess of it in some situations fragmenting its data and running out of usable space. How much RAM does the server itself have and if it has more than 2GB do you have the /3GB switch on the windows boot command in boot.ini
The best bet would be to run http://www.microsoft.com/downloads/d...displaylang=en which will run through your setup with a fine tooth comb and find all sorts, possible driver and av core updates, config stuff etc.
The other thing to check would be your AV real time scanning exclusions which the above will also help with.
The server has 3gb memory so I've turned off the memory check in the registry.
I'll run the best practice analayzer aswell.
Does this make sense to anyone?
An error occurred on database "First Storage Group\Mailbox Store (SERVER3)".
Function name or description of problem: EcGenerateReadReport:
Once again, E-mails have stopped being sent/received.
I saw that, but didn't make any sense. I don't think that would stop e-mails being sent/received.
Another event log:
The data buffer created for the "EXOLEDB" service in the "C:\Program Files\Exchsrvr\bin\exodbpc.dll" library is not aligned on an 8-byte boundary. This may cause problems for applications that are trying to read the performance data buffer. Contact the manufacturer of this library or service to have this problem corrected or to get a newer version of this library.
Your exchange AD premissions could be off or you may need to rebuild the exchange database as it sounds to have gone a little screwy. I'd back it all up then use eseutil to do a rebuild Using the Exchange tools ISINTEG and ESEUTIL to Ensure the Health of your Information Store
This should sort out any DB issues and speed it up a tad.
The 8-bit boundry thing sounds like an issue that I had thought was mitigated years ago to do with the data partition used by exchange not being partitioned to exactly match disk boundries. This means that heavy write operations are spread across more than one sector of the hard drive doubling the retrive and write time and generally causing havoc. If it is this issue then it would require repartitioning the drive using a special command line tool then transfering the data across. How to Align Exchange I/O with Storage Track Boundaries