Re: Exchange 2003 Private Store Corruption
- From: "Corbin O'Reilly" <corbinoreilly@xxxxxxxxxxxxx>
- Date: Wed, 12 Jul 2006 12:21:02 -0400
Thanks for the info Ben. Yes they are mounted now so hopefully you are right
and they will mount properly after the reboot. The HP Insight Online
Diagnostic Utility says "Correctable Memory Threshold Exceeded" for DIMM 4
so it does look like the memory is faulty. Have you seen 474 errors before?
In your experience what leads to a 474 error? The description points to
hardware. I am exporting mailboxes to PST files right now. Did you see
Mitch's previous response. I am just trying to get the server back up and
running without the faulty memory installed. My plan is to create a new
store, move as many uncorrupted mailboxes as I can to it, and then try to
repair the old stores.
"Ben Winzenz [Exchange MVP]" <ben_winzenz@nospamdotmessageonedotcom> wrote
in message news:%23iIUsWcpGHA.3600@xxxxxxxxxxxxxxxxxxxxxxx
Inline.
--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)
"Corbin O'Reilly" <corbinoreilly@xxxxxxxxxxxxx> wrote in message
news:OX7tg.8250$IF2.4659@xxxxxxxxxxxxxxxxxxxxxxxxx
Hello everyone. I need some help. We have an Exchange 2003 Enterprise
Edition Server running Windows 2003 Enterprise Edition R2 server. The
machine is a HP DL380 G4 server with 2 GB of memory and has been online
for about two months. The only thing running on this server is Exchange
2003 and Trend-Micro AntiVirus for Exchange. The server came standard
with 2 - 512 MB HP-brand DIMMs. We purchased additional memory from CDW.
They are 2 -512 MB EDGE-brand DIMMs and are supposed to be compatible. On
the first day that we powered up the server the server said there was an
issue with DIMM 4, the EDGE-brand chip. After a reboot the error went
away. About three weeks ago I noticed that the server had not completed
its online backup properly and two of our employees were having Calendar
issues. I checked the Event Viewer and it had tons of 474 errors which
says that there is probably a hardware problem. I created a new store on
the server and moved all mailboxes to the new store. The two mailboxes
with the corrupted Calendars would not move so I left them in the
corrupted store until I got back from vacation. While on vacation for two
weeks I checked the NTBACKUP logs daily and the online backups were
completing properly. Everything was fine for almost the entire time I was
gone. The day before I got back from vacation I got calls from 5
employees saying they were having strange Exchange problems. Some were
not getting new e-mails (we use cached mode), others had Inboxes that
were empty, etc. I checked the NTBACKUP log and sure enough the new store
I created is now corrupted too with a 474 error. My theory is that the
EDGE-brand memory chip is acting up and corrupting the store. What I
would like to do is shutdown the server and remove the 2 - 512 MB
EDGE-brand memory DIMMs from server, and boot it back up. I have a couple
of questions:
1. The server is partitioned into a RAID 1 OS C-Drive and a RAID 6
Exchange Data E-Drive. The server currently has 2 GB of memory and the
page file is located on the C-Drive and is set to Initial
: 3072 and Maximum: 6144. Since I will be removing the 2 - 512 MB
EDGE-brand DIMMs the new total memory size will be 1024 MB (1GB). Should
I adjust the page file to Initial: 1536 and Maximum 3072 in Windows 2003
BEFORE or AFTER I remove the memory?
I don't think it much matters whether you do it before or after, though,
except that if you do it afterwards, you will have to reboot a second
time.
2. Will the server perform OK with 1 GB of memory for a while? We have
about 75 mailboxes and a few public folders.
More than likely, it will be just fine. It doesn't sound like your server
is heavily loaded
3. Since both Private Info stores are corrupted will they mount properly
when the server is rebooted?
Are they mounted right now? If so, then once you reboot, they should be
able to mount. Dealing with corrupt mailboxes is somewhat different than
dealing with an actual corrupt database. Corrupt databases are not
mountable. Databases with corrupt mailboxes usually are mountable, but
the mailbox itself may or not be able to be fixed. I'd consider using
Exmerge to export whatever you can from the corrupt mailboxes. If they
can be moved, great. If not, then the mailboxes should be deleted and
re-create on the new store.
I am trying desperately to avoid being dead in the water tonight. My
concern is that the stores will not come up and we will be totally down.
I am getting more complaints from different employees so the problem
seems to be spreading and getting worse. I would appreciate your
expertise on this problem. Thanks.
As an additional note, have you run any server diagnostics to test the new
memory? What is your plan if removing the memory doesn't curtail the
problem? It's really better to have a true diagnosis that the memory is
faulty before you pull it out. HP should have some diagnostics that you
can run to test the memory. I'd do that first before you pull it out.
.
- Follow-Ups:
- Re: Exchange 2003 Private Store Corruption
- From: Ben Winzenz [Exchange MVP]
- Re: Exchange 2003 Private Store Corruption
- References:
- Exchange 2003 Private Store Corruption
- From: Corbin O'Reilly
- Re: Exchange 2003 Private Store Corruption
- From: Ben Winzenz [Exchange MVP]
- Exchange 2003 Private Store Corruption
- Prev by Date: Re: change POP3 recipient
- Next by Date: upgrading current install to new hardware
- Previous by thread: Re: Exchange 2003 Private Store Corruption
- Next by thread: Re: Exchange 2003 Private Store Corruption
- Index(es):
Relevant Pages
|
|
