Error Current Log File Missing Exchange 2007
Contents |
| My Forums | Address Book | Member List | Search | FAQ | Ticket List | Log Out Cannot mount mailbox store! e00.log missing? Users viewing at least one of this store's database files is missing exchange 2010 this topic: none Logged in as: Guest Tree Style Printable Version exchange 2013 database won't mount All Forums >> [Microsoft Exchange 2000] >> Information Stores >> Cannot mount mailbox store! e00.log missing? Page: [1] Login Message
At Least One Committed Transaction Log File Is Missing
<< Older Topic Newer Topic >> Cannot mount mailbox store! e00.log missing? - 3.Apr.2004 4:47:00 PM jasonlambert Posts: 1 Joined: 3.Apr.2004 From: London, UK Status: offline Hiya,I have a https://support.microsoft.com/en-us/kb/896143 problem with an Exchange 2000 server (SP3), running on a Windows 2000 Server patched to Service Pack 4.Basically i cannot mount the "Mailbox Store" or "Public Folder Store" from within the Exchange System Manager. - The error given when i try to mount the store is:code:An Internal Processing Error has occured. Try restarting the Exchange system manager or the Microsoft Information Store Service, or http://forums.msexchange.org/Cannot_mount_mailbox_store!_e00%25log_missing%3F/m_120048400/tm.htm Both.ID no: c1041724Exchange System MangerSeveral different entries appear in the Application log:code:Event Type: ErrorEvent Source: ESEEvent Category: Logging/Recovery Event ID: 455Date: 03/04/2004Time: 15:14:08User: N/AComputer: SERVERDescription:Information Store (4124) c0a65907-1259-44aa-8dfa-6c515ed40e5e: Error -1811 (0xfffff8ed) occurred while opening logfile C:\Program Files\Exchsrvr\mdbdata\E00.log. For more information, click http://www.microsoft.com/contentredirect.asp. and:code:Event Type: ErrorEvent Source: MSExchangeISEvent Category: General Event ID: 9518Date: 03/04/2004Time: 15:14:08User: N/AComputer: SERVERDescription:Error Current log file missing starting Storage Group /DC=LOCAL/DC=HARMONY/CN=CONFIGURATION/CN=SERVICES/CN=MICROSOFT EXCHANGE/CN=HARMONY/CN=ADMINISTRATIVE GROUPS/CN=FIRST ADMINISTRATIVE GROUP/CN=SERVERS/CN=SERVER/CN=INFORMATIONSTORE/CN=FIRST STORAGE GROUP on the Microsoft Exchange Information Store. Storage Group - Initialization of Jet failed. For more information, click http://www.microsoft.com/contentredirect.asp. Note that the contentredirect.asp links just generate a 404 from Microsoft.com.While some people may now be shouting "restore from backup", having just checked the MS Backup utility that runs every night, it looks like it hasnt actually been backing anything up since mid 2003. Our day-to-day files are backed up with a script that copies them to a linux box on the network, the exchange server it supposed to get backed up via tape. Well, restore from backup is out of the question.The next thing i go to look at is this e00.log, which i confirm does not exist. In C:\Program Files\Exchsrvr\
JET_errMissingLogFile -528 -548 – Exchange 2010 database recovery I have been dealing with recovering exchange databases for a long time now and recently had someone contact me with a typical no backup server crash http://msexchangeguru.com/2013/02/01/jet_errmissinglogfile-528-548/ scenario. The purpose of this article is to demonstrate a method by which "possibly" you can eliminate a repair or /p process or a restore of your Exchange database. Now, there is no guarantee that this would work – take it as a last resort. I am going to assume you have tried the normal process as outlined in the article: Exchange Database Recovery – Using eseutil commands: http://msexchangeguru.com/2009/07/12/exchange-database-recovery-using-eseutil-commands/ log file Here, we have some pre-requisites to go through before we proceed You have an Exchange 2010 database in a dirty shutdown state You have at least 300 log files in a healthy state First process is to make a note of which log files does the database require to make itself to a clean shutdown state To know this, run eseutil /mh which will show you the logs required: So current log file here we need the logs: E06000011B1 – Ox means the prefix of the log name Now, try to find if you have this log file intact. Mostly it maybe the E00.log file In my case, I had the E00.log and E00tmp.log Which means the server crashed when a new E00.log was in the process of being created. Now try to perform soft recovery and recover the database. Exchange gives you an option of lossy recovery which lets you ignore missing logs as outlined here: Exchange 2007: Operation terminated with error -939586631 The restore environment information isn't found or cannot be opened: http://msexchangeguru.com/2010/07/27/e2k7-restore-939586631/ So try the command: Eseutil /r E0n /l "Log file location" /d "Database Location" /a /i E0n – Name of the log file sequence like E00, E01, E02 etc /a – This is the key. This switch will allow a lossy recovery option /i – will override database mismatch If this doesn't work, simply try the following before you decide to repair the DB. NOTE: BACKUP ALL YOUR DATABASE and LOGS Rename the CHECKPoint file which is E06.chk in my case The checkpoint file remembers the last played log in our case won't help. Now create a newfolder – LOGS and copy all 300 logs