Re: HELP!!! Priv corrupt - events 9297 and 467

Tech-Archive recommends: Fix windows errors by optimizing your registry

I'm exmerging out now - thankfully there's only 34 mailboxes, and only a few
are big. Should be finished soon. While I've been waiting for this I was
looking at the dial tone method - neat trick if you have a good backup.

When I move all the files out of mdbdata and restart the services, will the
mailboxes be available to exmerge in or will I have to touch each one? If
so, will sending a global email do the trick or will I have to use OWA or
somesuch? It's been so long since I was Exchange-based that I've forgotten
so much stuff.... very frustrating day.

Thanks again for all your suggestions,
SusanV

"Susan" <sconkey@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:esFqokLzIHA.1768@xxxxxxxxxxxxxxxxxxxxxxx
maybe...looks like you might be running out of options...

--
Susan Conkey [MVP]



"SusanV" <s@xxxxx> wrote in message
news:ecZcgbKzIHA.2292@xxxxxxxxxxxxxxxxxxxxxxx
Nope, the restore to the recovery group failed:
Unable to restore Exchange data to LSGSBS\Microsoft Information
Store\First Storage Group,
check the application event log for more information

Looks like maybe Exmerge is the way to go?

Applog:
Event Type: Error
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 619
Date: 6/12/2008
Time: 12:05:55 PM
User: N/A
Computer: LSGSBS
Description:
Information Store (1528) Recovery Storage Group: Attempted to attach
database 'C:\Program Files\Exchsrvr\Recovery Storage Group\Mailbox Store
(LSGSBS).edb' but it is a database restored from a backup set on which
hard recovery was not started or did not complete successfully.

For more information, click http://www.microsoft.com/contentredirect.asp.
=========================
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9519
Date: 6/12/2008
Time: 12:05:55 PM
User: N/A
Computer: LSGSBS
Description:
Error 0xfffffde0 starting database "Recovery Storage Group\Mailbox Store
(LSGSBS)" on the Microsoft Exchange Information Store.

For more information, click http://www.microsoft.com/contentredirect.asp.
Data:
0000: 46 61 69 6c 65 64 20 74 Failed t
0008: 6f 20 61 74 74 61 63 68 o attach
0010: 20 74 6f 20 4a 65 74 20 to Jet
0018: 44 42 00 DB.
============================
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9518
Date: 6/12/2008
Time: 12:05:55 PM
User: N/A
Computer: LSGSBS
Description:
Error 0xfffffde0 starting Storage Group
/DC=local/DC=lightshipgroup/CN=Configuration/CN=Services/CN=Microsoft
Exchange/CN=LIGHTSHIPGROUP/CN=Administrative Groups/CN=first
administrative group/CN=Servers/CN=LSGSBS/CN=InformationStore/CN=Recovery
Storage Group on the Microsoft Exchange Information Store.
MDB failed to start.

For more information, click http://www.microsoft.com/contentredirect.asp.
============================

"Susan" <sconkey@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:O4MJYQKzIHA.5472@xxxxxxxxxxxxxxxxxxxxxxx
yes, a restore is the best way to go on something like this...and if you
got a good backup, that's a good sign...

--
Susan Conkey [MVP]



"SusanV" <s@xxxxx> wrote in message
news:uA31BKKzIHA.4772@xxxxxxxxxxxxxxxxxxxxxxx
I just ran a backup of the first storage group, ran without errors.

Now I'm going to try restoring from Monday to a RSG, see how that goes.

Thanks again for your help.


"Susan" <sconkey@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:eYhRrGKzIHA.1772@xxxxxxxxxxxxxxxxxxxxxxx
that would be correct...how many mailboxes are we talking about, here?
what happens if you try to do a backup now? does it fail? if you try
to restore Monday's backup to an RSG, does it work?

--
Susan Conkey [MVP]



"SusanV" <s@xxxxx> wrote in message
news:OWh129JzIHA.4772@xxxxxxxxxxxxxxxxxxxxxxx
Hi Susan,
Backup failed last night, and I'm not sure when this issue started,
so Monday night's backup may be corrupt also. The only known good
backup I have is from Friday, and since Monday's was succesful the
logs from tjhe weekend are gone, correct?

SusanV

"Susan" <sconkey@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23iDTNtJzIHA.2208@xxxxxxxxxxxxxxxxxxxxxxx
the recommendation in a case of serious corruption is to restore
from backup...that would probably be your best bet...

--
Susan Conkey [MVP]



"SusanV" <s@xxxxx> wrote in message
news:u3AkdnJzIHA.2220@xxxxxxxxxxxxxxxxxxxxxxx
SBS2003 R2, SP1, Exchange is SP2 (version 6.5.7638.1)

After a series of power failures where the UPS was unable to
recharge enough to bring the server down gracefully after powering
back up, I am getting EventID 9297 and 467 (full errors pasted
below) in the Application log every few minutes. The store mounts
OK but users keep getting Exchange is unavailable every few
minutes. Searching the web, I found very little on these errors,.

I dismounted the private store, backed it up, and ran eseutil:
C:\Program Files\Exchsrvr\bin> eseutil /d
c:\progra~1\exchsrvr\mdbdata\priv1.edb
results:
Operation terminated with error -338 (JET_errBadParentPageLink,
Database corrupted) after 1308.32 seconds.

Then ran isinteg:
C:\Program Files\Exchsrvr\bin>isinteg -s lsgsbs -fix -verbose -l
C:\isinteg.pri -test alltests
Results:
. . . . . SUMMARY . . . . .
Total number of tests : 21
Total number of warnings : 7
Total number of errors : 0
Total number of fixes : 1991
Total time : 0h:7m:33s

Reran isinteg, no errors warnings or fixes. Reran eseutil /g, says
database is still corrupt. The store will still mount, and mail is
still accessible, but I'm still getting the errors. Currently I
have the store dismounted to keep users out.

I thought to create a new store and move the mailboxes, but after
creating a new storage group, I cannot add a new mailbox store,
error says "This storage group already contains the maximum number
of stores allowed" - I assume this to be an SBS limitation?

So now what??? Any ideas before I pull out the plastic and call
MS???

ANY help would be appreciated!!!
SusanV

App log data:
===================================
Event Type: Error
Event Source: ESE
Event Category: Database Corruption
Event ID: 467
Date: 6/12/2008
Time: 9:45:58 AM
User: N/A
Computer: LSGSBS
Description:
Information Store (1528) First Storage Group: Database C:\Program
Files\Exchsrvr\mdbdata\priv1.edb: Index FidDeleteTimeIndex of table
IndexAge is corrupted (0).

For more information, click
http://www.microsoft.com/contentredirect.asp.
===================================
Event Type: Error
Event Source: MSExchangeIS Mailbox Store
Event Category: Background Cleanup
Event ID: 9792
Date: 6/12/2008
Time: 9:45:59 AM
User: N/A
Computer: LSGSBS
Description:
Cleanup of the DeliveredTo table for database 'First Storage
Group\Mailbox Store (LSGSBS)' failed with error -1017. 4 entries
were purged before the failure was encountered.

For more information, click
http://www.microsoft.com/contentredirect.asp.
===================================

















.

Relevant Pages

  • Re: Event 478
    ... Thanks a lot John. ... - The old database is still of the same size. ... demount its store and then delete it? ... If you move all the mailboxes to a new store, ...
    (microsoft.public.exchange.admin)
  • RE: isinteg Error message when trying to fix Exchange db on SBS 2003 R2
    ... I understand that you cannot mount the store ... 301438 You cannot mount a database because there is a corrupted transaction ... isinteg Error message when trying to fix Exchange db on ... | Storage Group Name: First Storage Group ...
    (microsoft.public.windows.server.sbs)
  • Re: priv1.edb and size maintanence
    ... The factors that contribute to store size are: ... Number of mailboxes on the store ... MTA database and Run Directories ... Be aware of the space message tracking logs consume, ...
    (microsoft.public.exchange.admin)
  • local delivery queue issues after DR
    ... EcLocallyDeliverMsg to the store failed. ... that mailboxes were corrupted. ... information store database, stop the Information Store service, delete the ...
    (microsoft.public.exchange.admin)
  • Re: Event 478
    ... I have finished moving the mailboxes and they all work fine. ... mounted the store. ... database is attachments. ... the item with the corrupt data won't move. ...
    (microsoft.public.exchange.admin)