Re: Exchange 2003 Private Store Corruption
- From: "Ben Winzenz [Exchange MVP]" <ben_winzenz@nospamdotmessageonedotcom>
- Date: Wed, 12 Jul 2006 11:51:33 -0500
You were actually probably on the right track. After further review, my
guess is that the errors that are being seen will equate to actual database
corruption issues. While eseutil and isinteg still wouldn't be my first
choice, they certainly would be a solution to fix database corruption
issues.
--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)
"mitch Roberson" <mitch@xxxxxxxxxxxxxxxx> wrote in message
news:evj59AdpGHA.4812@xxxxxxxxxxxxxxxxxxxxxxx
My mistake thanks for the info.
"Ben Winzenz [Exchange MVP]" <ben_winzenz@nospamdotmessageonedotcom> wrote
in message news:upbyswcpGHA.4192@xxxxxxxxxxxxxxxxxxxxxxx
Eseutil won't fix corrupt mailboxes, only corrupt databases. Not to
mention, if you are referring to running eseutil in repair mode, it
doesn't "fix" problems. It deletes corrupt pages to fix the problem,
which most often results in lost data.
Isinteg *might* help, but it probably won't fix a corrupt mailbox either.
When I say corrupt mailbox, usually what you are deaing with is corrupt
"items" within the mailbox. This causes issues with Outlook.
When dealing with corrupt mailboxes, you can usually still move them, you
just have to bump up the failure count. Corrupt items within a mailbox
will usually be unreadable by anything, so they would already be gone.
Of course, if you knew which items those were, you could always do a
restore to a Recovery Storage Group and import the missing items from
there back into the mailbox.
--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)
"mitch Roberson" <mitch@xxxxxxxxxxxxxxxx> wrote in message
news:%23F6S2mcpGHA.1440@xxxxxxxxxxxxxxxxxxxxxxx
I would leave the page file size for now it should not be a problem while
you try to correct the other issues. I would remove the memory you
believe has a problem and be prepared to run ESE util and ISINTEG before
mounting the store
You should run ESE first the ISINTEG and run ese until you have no
errors then run ISINTEG till you have no errors.
"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?
2. Will the server perform OK with 1 GB of memory for a while? We have
about 75 mailboxes and a few public folders.
3. Since both Private Info stores are corrupted will they mount
properly when the server is rebooted?
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.
.
- References:
- Exchange 2003 Private Store Corruption
- From: Corbin O'Reilly
- Re: Exchange 2003 Private Store Corruption
- From: mitch Roberson
- Re: Exchange 2003 Private Store Corruption
- From: Ben Winzenz [Exchange MVP]
- Re: Exchange 2003 Private Store Corruption
- From: mitch Roberson
- Exchange 2003 Private Store Corruption
- Prev by Date: Re: Exchange 2003 Private Store Corruption
- Next by Date: Re: Outgoing Mail issue
- Previous by thread: Re: Exchange 2003 Private Store Corruption
- Next by thread: using PFMigrator
- Index(es):
Relevant Pages
|
Loading
