Re: First Mailbox Storage Error, need help with recovery

From: Jerry Ndo (choicechen_at_hotmail.com)
Date: 10/14/04


Date: Thu, 14 Oct 2004 14:58:21 -0700

That's it, Ben! Thanks for the help! Got another issue with Exchange again.
I'll post a new topic.

"Ben Winzenz [Exchange MVP]" <ben_winzenz@NOSPAMdotmessageonedotcom> wrote
in message news:%23zRv4ojoEHA.324@TK2MSFTNGP11.phx.gbl...
> Make 100% sure that you do NOT have any File-level antivirus scanning ANY
> exchange directories. The most common cause of missing log files is
because
> a File-level antivirus application has quarantined or deleted a log file
> because it detected a virus in one of them. If you are running file-level
> AV, then you need to make sure you exclude all of the exchange
directories,
> especially the log file directory and database directory. Follow this KB
> article for details on which directories to exclude.
> http://support.microsoft.com/default.aspx?kbid=328841
>
> --
> Ben Winzenz
> Exchange MVP
>
>
> "Jerry Ndo" <choicechen@hotmail.com> wrote in message
> news:eQlXyXboEHA.2900@TK2MSFTNGP12.phx.gbl...
> > Ah, it just crashed again. I believe this would be the first error
before
> > the rest of them:
> > Source: ESE
> > Category: Logging/Recovery
> > Event ID: 455
> > Description:
> > Information Store (4976) First Storage Group: Error -1811 occured while
> > opening logfile C:\Program Files\Exchsrvr\mdbdata\E000005E.log.
> >
> > I looked at the MDBDATA folder, the latest file was E000005C.log. The D
> > and
> > E were missing.
> >
> > Thanks,
> > Jerry
> >
> >
> > "Jerry Ndo" <choicechen@hotmail.com> wrote in message
> > news:uqOKWnaoEHA.896@TK2MSFTNGP12.phx.gbl...
> >> Hello Ben, thanks for the quick reply.
> >>
> >> You are correct about -539. I had event 454 ESENT:
> >> Catalog Database (976) Catalog Database: Database recovery/restore
failed
> >> with unexpected error-539.
> >>
> >> The first time Exchange got corrupted, I tried to do isinteg and it
> >> didn't
> >> let me, so I deleted alll the log files and left only .edb and .stm in
> >> the
> >> mdbdata folder and ran the isinteg.
> >>
> >> What should I do?
> >>
> >> Thanks again,
> >> Jerry
> >>
> >> "Ben Winzenz [Exchange MVP]" <ben_winzenz@NOSPAMdotmessageonedotcom>
> >> wrote
> >> in message news:Ox1uQEXoEHA.3428@TK2MSFTNGP11.phx.gbl...
> >> > What events do you have in your event logs? Do you see any 1018,
1019,
> >> 1022
> >> > errors?
> >> >
> >> > The error that you posted correlates with:#define
> >> > JET_errDatabaseLogSetMismatch -539 /* Database does not belong with
the
> >> > current set of log files */
> >> >
> >> >
> >> > That message to me would indicate that there seems to be a problem
with
> >> the
> >> > log files as they relate to the database. Have you ever restored the
> >> > databases?
> >> >
> >> > You may also want to consider hardware problems. What is the
hardware
> >> specs
> >> > of the machine that Exchange is on? Hard drives, RAID controller,
> > procs,
> >> > memory, etc.?
> >> >
> >> > --
> >> > Ben Winzenz
> >> > Exchange MVP
> >> >
> >> >
> >> > "JerryNdo" <JerryNdo@discussions.microsoft.com> wrote in message
> >> > news:528CC00A-BF82-4079-BA51-633ED06A2AF8@microsoft.com...
> >> > > Hello, I have a server with only one domain and about 2GB of total
> >> > > mailboxes.
> >> > > The server went down every 7-10 days. I get ESENT: Catalog Database
> >> (976)
> >> > > Catalog Database: Database recovery/restore failed with unexpected
> >> > > error -539.
> >> > > I was able to fix it using eseutil /p, then /d, then isinteg.
> >> > > However,
> >> > > after
> >> > > 7-10 days it will crash again. It already happened 3 times and I
> >> > > don't
> >> > > know
> >> > > what to do.
> >> > > /p and /d seems to run fine, the isinteg return 3 errors on the
Test
> >> > > folder,
> >> > > and it stays that way.
> >> > > I have SBS 2003, I tried to create a new mailbox store and move all
> > the
> >> > > users there but it won't allow me to create a new store.
> >> > >
> >> > > Please help!!!
> >> > >
> >> > > Thanks,
> >> > > Jerry
> >> > >
> >> > > Below is the result of isinteg:
> >> > >
> >> > > Test Categorization Tables result: 0 error(s); 0 warning(s); 0
> > fix(es);
> >> 0
> >> > > row(s)
> >> > > ; time: 0h:0m:0s
> >> > > Test Restriction Tables result: 0 error(s); 0 warning(s); 0
fix(es);
> >> > > 0
> >> > > row(s); t
> >> > > ime: 0h:0m:0s
> >> > > Test Search Folder Links result: 0 error(s); 0 warning(s); 0
fix(es);
> > 0
> >> > > row(s);
> >> > > time: 0h:0m:0s
> >> > > Test Global result: 0 error(s); 0 warning(s); 0 fix(es); 1 row(s);
> > time:
> >> > > 0h:0m:0
> >> > > s
> >> > > Test Delivered To result: 0 error(s); 0 warning(s); 0 fix(es); 54
> >> row(s);
> >> > > time:
> >> > > 0h:0m:0s
> >> > > Test Repl Schedule result: 0 error(s); 0 warning(s); 0 fix(es); 0
> >> row(s);
> >> > > time:
> >> > > 0h:0m:0s
> >> > > Test Timed Events result: 0 error(s); 0 warning(s); 0 fix(es); 0
> > row(s);
> >> > > time: 0
> >> > > h:0m:0s
> >> > > Test reference table construction result: 0 error(s); 0 warning(s);
0
> >> > > fix(es); 0
> >> > > row(s); time: 0h:0m:8s
> >> > > Test Folder result: 3 error(s); 3 warning(s); 0 fix(es); 1240
row(s);
> >> > > time:
> >> > > 0h:1
> >> > > m:25s
> >> > > Test Deleted Messages result: 0 error(s); 0 warning(s); 0 fix(es);
0
> >> > > row(s);
> >> > > tim
> >> > > e: 0h:0m:0s
> >> > > Test Message result: 0 error(s); 0 warning(s); 0 fix(es); 73048
> > row(s);
> >> > > time: 0h
> >> > > :0m:27s
> >> > > Test Attachment result: 0 error(s); 0 warning(s); 0 fix(es); 41840
> >> row(s);
> >> > > time:
> >> > > 0h:0m:3s
> >> > > Test Mailbox result: 0 error(s); 0 warning(s); 0 fix(es); 26
row(s);
> >> time:
> >> > > 0h:0m
> >> > > :0s
> >> > > Test Sites result: 0 error(s); 0 warning(s); 0 fix(es); 102 row(s);
> >> time:
> >> > > 0h:0m:
> >> > > 0s
> >> > > Test Categories result: 0 error(s); 0 warning(s); 0 fix(es); 2069
> >> row(s);
> >> > > time:
> >> > > 0h:0m:0s
> >> > > Test Per-User Read result: 0 error(s); 0 warning(s); 0 fix(es); 49
> >> row(s);
> >> > > time:
> >> > > 0h:0m:0s
> >> > > Test special folders result: 0 error(s); 0 warning(s); 0 fix(es); 0
> >> > > row(s);
> >> > > time
> >> > > : 0h:0m:0s
> >> > > Test Message Tombstone result: 0 error(s); 0 warning(s); 0 fix(es);
> > 394
> >> > > row(s);
> >> > > time: 0h:0m:0s
> >> > > Test Folder Tombstone result: 0 error(s); 0 warning(s); 0 fix(es);
5
> >> > > row(s);
> >> > > tim
> >> > > e: 0h:0m:0s
> >> > > Now in test 20(reference count verification) of total 20 tests;
> >> > > 100%
> >> > > complete.
> >> >
> >> >
> >>
> >>
> >
> >
>
>



Relevant Pages

  • Re: Excessive amount of log files
    ... Based on that information I would say that your server is doing fine. ... 5mb attachment that will be 40Mb of transaction logs right there. ... an Exchange server will also cause transactions to be recorded. ... What we look for in high log file growth situation is large numbers of log ...
    (microsoft.public.exchange2000.general)
  • Cant figure out why Exchange keeps crashing
    ... My Exchange server crashes about every other month. ... with all the patches and Windows 2003 with all the patches. ... The database disk may be full. ... current log file such as E00.log to the latest log file in the Storage group ...
    (microsoft.public.exchange2000.information.store)
  • RE: DST CDO hotfix
    ... 0.921: Setup encountered an error: Setup cannot continue because one or ... more pre-requisites required to install Hotfix for Exchange 2000 Server ... For More details check the Log File KB928225.log ...
    (microsoft.public.exchange.setup)
  • 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)
  • Re: Account is not local
    ... >>> pages of the SMTP Virtal Server. ... >>The log file you asked me to look for does not exist ... is logging enabled on the SMTP Virtual Server? ... > _sending_ mail from the Exchange server. ...
    (microsoft.public.exchange.admin)