Exchange 5.5 running Windows NT Server

I suspect that your server may have been infected with virus(es).

If you are directly connected to the Internet, then you are more exposed to virus attacks. If you have a ISP, then inquire from them if they have firewall and antivirus up and running.

It seems that Store.exe is grabbing all memory resources up to 426MB out of the 512Mb your server has.

As first line of defense, try installing antivirus program for Exchange.

Hope this helps.

The store.exe program is what Exchange 5.5 uses for the Microsoft Exchange Information Store service. It sounds like maybe you need to defragment and/or reindex your information store. A good place to start would be the eseutil or isinteg programssupplied with Exchange 5.5 located in the /exchsrvr/bin directory. Be sure to make a backup.

In the meantime, please provide me with more details of your Exchange setup: How many servers in this site? How many users are connecting? Small/meg/large company? Is the information store in a compressed folder? How large is your priv.ebd and your pub.edb? Have you run the MS Exchange Optimizer yet?

Store.exe will dynamically take up as much memory as it can and release it when other processes request it. That is by design. As far as troubleshooting can you move Exchange to another server (if available) and see if the box still has the same issues with just NT installed on it or does the problem follow which ever box you have exchange on?

It's normal for store.exe to take as much RAM as it can grab. That should not be a factor in your problem.

It sounds to me like a hardware problem. It's intermittent, so the diagnostics aren't catching it. I would challenge Dell to put it throughan extended torture test, not just the normal diagnostics.

I hope this helps.

Steve Diamond

Had very similar problem but got the BSOD after allowing the server to sit for about an hour. If possible let it sit and think about it awhile see if you get the BSOD.

This was effective for us After getting a full backup manually replace the offending store.exe

No gaurantees Good luck

We had a similar problem here. At the time we were running Backup Exec 7.3.

After spending hours looking into the problem with Exchange, we spoke with one of our vendor techs (who now works for us) about the problem. He pinpointed the problem right away. He had past experiences with the Backup Exec Server service and Backup Exec Name Server service causing the server to hang.

Stopping those services allowed the machine to respond. It appeared that for some reason (I have never looked intoit) these services were causing the lockup, but it appeared that Exchange was the culprit.

Try stopping the Backup Exec services and see if the machine becomes responsive. If so, do what we did and backup the machine from a remote backup server.

First off, it appears that it may be hardware related. I say this because you stated that you have re-installed. I have had similar problems when hardware has gone south.

I have BackupExec running on an NT box with Exchange Server, and have nothad a single system hang, but I wouldn't check it off my list this easily. :)

If I were you, I would tax the system for all it's worth, and see if you can get it to hang. If you can, start disabling services one or two at a time, and do this again. If you can narrow it down to a specific service, then you're on your way to many more happy monday mornings.

If we assume that it's hardware related, I would jump right to the ram. If you've got 2 or 3 DIMMS in there, yank all but one out and try to get the system to hang. Again, if you can determine that you've got a bad DIMM, well, happy monday. :)

This question was closed by the author