Re: It happened all over again

From: Applebaum (mappleNOSPAM_at_inchNOSPAM.com)
Date: 04/13/04 

Date: Mon, 12 Apr 2004 22:43:13 -0400

Okay, I have an opportunity to start from scratch again! I left for two
hours and found things in the following state - event log posted below.
Here's what I'm planning, I'm very glad you're listening!

As suggested in the KB you linked to previously, I'm first backing up what I
have. The KB says to first remove the corrupted log file. Step 1 is to
Perform an offline backup of the Exchange databases in the storage group
that contains the corrupted log file.

They tell me to use Windows Backup. The backup job doesn't work - it stops
right away and reports that the files were corrupt and did not verify,
obviously taking too little time to back them up. So now I'm running a
backup with Backup Exec, backing up the information store (they're
dismounted) and also the MDBDATA directory (because I'm not sure what's
needed at this point).

Next I will follow this KB's direction: use eseutil to determine state of
databases, and proceed accordingly. At this point I don't want to mess with
any potentially corrupt log file and risk this happening again. I will let
the bosses decide tomorrow if saving that data is worth the $250. I just
hope that I can keep this from happening again.

Thank you again, you have been most helpful. Here are the events that I
found:

7:58PM
Source: ESE
Event ID: 486
Information Store (5748) An attempt to move the file
"G:\Exchsrvr\MDBDATA\E00.log" to "G:\Exchsrvr\MDBDATA\E0003B93.log" failed
with system error 183 (0x000000b7): "Cannot create a file when that file
already exists. ". The move file operation will fail with error -1022
(0xfffffc02).

<snip> I'm wondering why did it try to move that file? <snip>

Event ID: 413
Information Store (5748) Unable to create a new logfile because the database
cannot write to the log drive. The drive may be read-only, out of disk
space, misconfigured, or corrupted. Error -1022.

Event ID: 492
Information Store (5748) The logfile sequence in "G:\Exchsrvr\MDBDATA\" has
been halted due to a fatal error. No further updates are possible for the
databases that use this logfile sequence. Please correct the problem and
restart or restore from backup.

MSExchangeIS
EventID: 9558
An error occurred while writing to the database log file of storage group
"First Storage Group". Attempting to unmount all databases in this storage
group.

EventID 9539
The Microsoft Exchange Information Store database "First Storage
Group\Mailbox Store (SAI)" was stopped.

-- then the public store is stopped --

ESE
EventID 104
Information Store (5748) d42b9e67-60dd-4493-b9f4-1d89ceb31b94: The database
engine stopped the instance (0) with error (-510).

ESE Event 101
Information Store (5748) The database engine stopped.

--Matthew

"Kirill S. Palagin" <kpalagin@nomail.phxint.please.ru> wrote in message
news:OT3rQ1PIEHA.3248@TK2MSFTNGP12.phx.gbl...
> Applebaum wrote:
>
> > The very same thing has happened again!
>
> At what step?
>
> > About two hours later, virtually
> > the same error messages. Stores are not mounted. Am now attempting an
> > offline backup.
>
> You mean you are restoring from offline backup and planning to do what?
>
>
> <snip>

Relevant Pages

  • Re: cant mount information store
    ... Both database were dirty shutdown ... >>> Information Store First Storage Group: ... >>> Microsoft Exchange Information Store. ...
    (microsoft.public.windows.server.sbs)
  • failed drives, rebuilds, exchange corruptions, oh my!
    ... So I am looking for a little direction and possibly some ideas on how to handle a problem that has happened on an sbs2k server. ... My last good backup was Friday Night the 5th. ... ..Call Microsoft support and try to repair the existing database - will there be more problems/missing things down the road. ... Information Store 9e13042f-036a-4ed5-9acd-9dbb16f1c4a6: The database engine has successfully completed recovery steps. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Exchange is really messed up... (long)
    ... If you still have that PST with the data not merged into Exchange, ... Information Store First Storage Group: ... Information Store First Storage Group: The database engine has ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange 2003 cannot mount mailbox stores
    ... All of the Exchange services ... I have a good backup of the data, ... > Storage Group - Initialization of Jet failed. ... > Information Store First Storage Group: ...
    (microsoft.public.exchange.admin)
  • Re: It happened all over again
    ... They tell me to use Windows Backup. ... Information Store An attempt to move the file ... Information Store Unable to create a new logfile because the database ... An error occurred while writing to the database log file of storage group ...
    (microsoft.public.backoffice.smallbiz2000)
Loading