RE: Mail log file corrupt, information store not mounting
- From: v-mzhuan@xxxxxxxxxxxxxxxxxxxx (Manfred Zhuang [MSFT])
- Date: Tue, 16 Oct 2007 10:30:50 GMT
Hello John,
Thank you for posting here.
From your post, I understand that information store cannot be mounted.Error 477 and 465 are found in event log.
It seems that your Exchange database has corrupted. Please refer to the
following steps:
1. Check the consistency of the databases. If a database is consistent, all
the log files have been committed to the store. If the database is not
consistent, the database may not be corrupted. Instead, the log files may
be missing, damaged, or not yet committed to the database. Run the
following commands to check the consistency of the public and private
databases (these lines have been wrapped for readability).
C:\Program Files\exchsrvr\BIN>eseutil /mh "C:\Program
Files\exchsrvr\MDBDATA\priv1.edb"
C:\Program Files\exchsrvr\BIN>eseutil /mh "C:\Program
Files\exchsrvr\MDBDATA\pub1.edb"
To verify that the .edb file is consistent, check the output line that is
labeled "State." 'Clean shutdown' means consistent, 'Dirty Shutdown' means
inconsistent. If you want to send the output of this command directly to a
text file, you can modify the command line as follows (the following lines
have been wrapped for readability).
C:\Program Files\exchsrvr\BIN>eseutil /mh C:\Program
Files\exchsrvr\MDBDATA\priv1.edb > mypriv.txt
C:\Program Files\exchsrvr\BIN>eseutil /mh C:\Program
Files\exchsrvr\MDBDATA\pub1.edb > mypub.txt
To display the text directly on the screen, add | more to the end of the
command.
If the Pub1.edb file and the Priv1.edb file are not located in the Program
Files\ExchSrvr\Mdbdata folder on the same drive as the ExchSrvr\Bin folder
that you are running the command from, replace the "C:\program
files\mdbdata\priv1.edb" portion of the command with the full path of the
Priv1.edb file. Make the same changes for Pub1.edb. If both the Pub1.edb
file and the Priv1.edb file are consistent, move all the log files out of
the folder where your database files are located, and then mount the
stores. The folder where your database files are located is typically the
Exchsrvr\Mdbdata folder. As with any situation where a log file has been
corrupted, some data loss will occur.
If one of the databases is inconsistent, try to perform a soft recovery of
the files to see if there are copies of the log files stored in the Mdbdata
folder.
Note: If you do not have the log files, the soft recovery process cannot be
completed. Go to step 2. Please also start the Information Store service.
When you perform a soft recovery, any uncommitted log files are committed
to the information store database.
To initiate a soft recovery, run the following command.
Open the folder where the database and log files reside, and then type the
following at a command prompt. The following line has been wrapped for
readability.
C:\Program Files\exchsrvr\MDBDATA>"C:\Program Files\exchsrvr\BIN\eseutil"
/r E00
Click Yes to run the repair. The utility displays the following message:
Microsoft (R) Exchange Server(TM) Database Utilities Version 6.0
Copyright (C) Microsoft Corporation 1991-2000. All rights reserved.
Initiating RECOVERY mode...
Logfile base name: E00
Log Files: (current directory)
System files: (current directory)
Performing soft recovery...
When the soft recovery is complete, the program displays the message:
Operation completed successfully in x.xxx seconds.
You can use this command to recover the databases if the databases are
fully recoverable. To confirm this behavior, repeat this step from the
beginning, and then run the eseutil /mh command again. If the state has
changed to "Consistent" for both the public information store and the
private information store, go to step 3.
2. If either of the databases is inconsistent, and the eseutil /r command
does not return them to a consistent state, use the procedure that is
described in this step.
Note When you use the following command, you may lose some Exchange 2000
Server or Exchange Server 2003 data, including the messages that were
contained in the log files that were not yet committed to the information
store database. The following command is a hard or forcible state recovery
command. Microsoft recommends that you use this command only if the public
information store or the private information store does not return to a
consistent state after you perform the steps described earlier in this
article.
At the command prompt, type the following commands (the following lines
have been wrapped for readability):
a. To bring the Priv1.edb file back into a consistent state: C:\Program
Files\exchsrvr\MDBDATA>"C:\Program Files\exchsrvr\BIN\eseutil" /p priv1.edb
b. To bring the Pub1.edb file back into a consistent state: C:\Program
Files\exchsrvr\MDBDATA>"C:\Program Files\exchsrvr\BIN\eseutil" /p pub1.edb
c. Click Yes to run the repair. The utility displays the following
message:
Microsoft (R) Exchange Server(TM) Database Utilities
Version 6.0
Copyright (C) Microsoft Corporation 1991-2000. All right reserved.
Initiating REPAIR mode...
Database: priv1.edb
Streaming File: priv1.stm
Temp. Database: TEMPREPAIR1820.EDB
Checking database integrity.
Scanning Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|----|----|----|----|-----|
....................................................
When the procedure is complete, the program displays the message:
Integrity check successful.
Note The .stm files are automatically included in the repair process.
3. Mount the databases and check if the issue persists, and then
immediately dismount them to so that users cannot access them during this
procedure.
Note You may stop the SMTP service before you mount the databases to
prevent new e-mail messages from coming in to the databases. When you run a
Hard Repair (eseutil /p), and the repair actually detects and removes
database corruption, you should run an offline defragmentation after the
repair and before you do anything else.
4. Stop the Information Store service and run a defragmentation of the
private and public store databases. Please run this step if you are low on
disk space.
Note Please ensure that you have free disk space equal to at least 110% of
the database size to run eseutil /d. If you do not designate a temporary
location for the database file by using the "t" command, the temporary
location is automatically set to the Exchsrvr/Bin folder.
At a command prompt, type the following commands (the following lines have
been wrapped for readability):
a. To defragment Priv1.edb:
C:\Program Files\exchsrvr\BIN>eseutil /d "C:\Program
Files\exchsrvr\MDBDATA\priv1.edb"
b. To defragment Pub1.edb:
C:\Program Files\exchsrvr\BIN>eseutil /d "C:\Program
Files\exchsrvr\MDBDATA\pub1.edb"
Note If both the private and the public information store databases are
large, this step may take some time. If you receive an error message that
indicates a lack of disk space when you try to perform this step, copy the
Program Files\ExchSrvr\Bin folder to a drive that has more disk space, and
then try to run the command from that location.
For more information about how to resolve this error message, click the
following article number to view the article in the Microsoft Knowledge
Base:
How to defragment with the Eseutil utility (Eseutil.exe )192185
http://support.microsoft.com/kb/192185/
Please try the above steps at your earliest convenience. If you have any
concern, please feel free to let me know.
Best regards,
Manfred Zhuang(MSFT)
Microsoft Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: John <livingusman@xxxxxxxxxxxxxx>
| Newsgroups: microsoft.public.windows.server.sbs
| Subject: Mail log file corrupt, information store not mounting
| Date: Mon, 15 Oct 2007 07:44:25 -0700
| Organization: http://groups.google.com
| Lines: 48
| Message-ID: <1192459465.162595.93120@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
| NNTP-Posting-Host: 84.12.141.15
| Mime-Version: 1.0
| Content-Type: text/plain; charset="iso-8859-1"
| X-Trace: posting.google.com 1192459465 13805 127.0.0.1 (15 Oct 2007
14:44:25 GMT)
| X-Complaints-To: groups-abuse@xxxxxxxxxx
| NNTP-Posting-Date: Mon, 15 Oct 2007 14:44:25 +0000 (UTC)
| User-Agent: G2/1.0
| X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; .NET
CLR 1.1.4322),gzip(gfe),gzip(gfe)
| X-HTTP-Via: 1.0 VS-SERVER
| Complaints-To: groups-abuse@xxxxxxxxxx
| Injection-Info: v29g2000prd.googlegroups.com; posting-host=84.12.141.15;
| posting-account=ps2QrAMAAAA6_jCuRt2JEIpn5Otqf_w0
| Path:
TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS02.phx.gbl!newsfeed0
0.sul.t-online.de!t-online.de!news.glorb.com!postnews.google.com!v29g2000prd
..googlegroups.com!not-for-mail
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:69357
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Hi
|
| I am getting the below error in event log. It seems log file e00 is
| corrupt and as a result the information store is unable to mount. Is
| there a way to fix this problem without resorting to backup?
|
| Thanks
|
| Regards
|
|
| Event Type: Error
| Event Source: ESE
| Event Category: Logging/Recovery
| Event ID: 477
| Date: 15/10/2007
| Time: 15:39:12
| User: N/A
| Computer: MYSERVER
| Description:
| Information Store (748) First Storage Group: The log range read from
| the file "C:\Program Files\Exchsrvr\mdbdata\E00.log" at offset 2953216
| (0x00000000002d1000) for 512 (0x00000200) bytes failed verification
| due to a range checksum mismatch. The read operation will fail with
| error -501 (0xfffffe0b). If this condition persists then please
| restore the logfile from a previous backup.
|
| For more information, click http://www.microsoft.com/contentredirect.asp.
|
|
|
| Event Type: Error
| Event Source: ESE
| Event Category: Logging/Recovery
| Event ID: 465
| Date: 15/10/2007
| Time: 15:39:12
| User: N/A
| Computer: MYSERVER
| Description:
| Information Store (748) First Storage Group: Corruption was detected
| during soft recovery in logfile C:\Program Files\Exchsrvr\mdbdata
| \E00.log. The failing checksum record is located at position 5768:153.
| Data not matching the log-file fill pattern first appeared in sector
| 5768. This logfile has been damaged and is unusable.
|
| For more information, click http://www.microsoft.com/contentredirect.asp.
|
|
.
- References:
- Prev by Date: RE: long time download email under the vista machine
- Next by Date: RE: Workstation Fax and Email Application
- Previous by thread: Mail log file corrupt, information store not mounting
- Next by thread: problem with RWW
- Index(es):
Relevant Pages
|
