Re: It happened all over again

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Kirill S. Palagin (kpalagin_at_nomail.phxint.please.ru)
Date: 04/13/04


Date: Mon, 12 Apr 2004 22:55:04 -0400


 From the events it looks like you have got previous and newly created
log files intermixed. When you restore everything keep in mind that
logs can be on different volume from what you expect.

(I am going to conk-out for today).

Applebaum wrote:

> 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: Unable to attach the database
    ... BUT NEVER DELETE A LOG FILE! ... If you have a clean backup of the database, ... good understanding of SQL Server and how to work from this situation. ...
    (comp.databases.ms-sqlserver)
  • Re: M Drive
    ... and when trying to mount the database, ... Information Store Error -1811 occurred while opening logfile ... Error Current log file missing starting Storage Group ... on the Microsoft Exchange Information Store. ...
    (microsoft.public.exchange2000.setup.installation)
  • Re: M Drive
    ... and when trying to mount the database, ... Information Store Error -1811 occurred while opening logfile ... Error Current log file missing starting Storage Group ... on the Microsoft Exchange Information Store. ...
    (microsoft.public.exchange2000.admin)
  • Re: Stanby cannot be moved forward
    ... It very much looks like by opening the database you have switched the ... a log file. ... A backup is taken from production server to backup server. ...
    (comp.databases.oracle.server)
  • Re: event-id: 455, source: ESE98
    ... non-existent transaction logs to bring the database to the ... information store the database has been halted. ... The Microsoft Exchange server computer cannot be reached, ... Is that log file ...
    (microsoft.public.exchange2000.information.store)