Exchange 2003 Log was deleted

Hello Experts,
I am trying to rescue a client who has deleted logs from an exchange 2003 server.  The log files where in the MBData folder.  The server is windows 2003 SP2.  The database will not mount with Event Log ID 455, ESE,


Event Type:      Error
Event Source:      ESE
Event Category:      Logging/Recovery
Event ID:      455
Date:            4/17/2015
Time:            10:07:09 AM
User:            N/A
Computer:      SERVER2
Description:
Information Store (344) First Storage Group: Error -1811 occurred while opening logfile C:\Program Files\Exchsrvr\mdbdata\E0007992.log.

and this error:
Event Type:      Error
Event Source:      MSExchangeIS
Event Category:      General
Event ID:      9518
Date:            4/17/2015
Time:            10:07:09 AM
User:            N/A
Computer:      SERVER2
Description:
Error Current log file missing starting Storage Group /DC=local/DC=mutual/CN=Configuration/CN=Services/CN=Microsoft Exchange/CN=CORP/CN=Administrative Groups/CN=MUTUAL/CN=Servers/CN=SERVER2/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.


I have looked at running the eseutil.  I do not need any information in the logs, just the databases intact.

Thanks
itwarlordSenior Engineer/OwnerAsked:
Who is Participating?
 
itwarlordSenior Engineer/OwnerAuthor Commented:
I know I am looking for a simple answer.  but doesn't eseutil or isinteg help in this regard?
0
 
Radhakrishnan RSenior Technical LeadCommented:
Hi,

I hope you have backup for exchange, if so, you need to restore it from backup and try mounting the datastore. Once that's completed, you can run a full backup for your exchange server and the logs files get deleted then.

You can follow the procedure outlined in this MS article https://support.microsoft.com/en-us/kb/896143, refer section "Method 2: If the Exchange log file was deleted" which details about to handle this scenario.

Hope this helps.
0
 
Thomas GrassiSystems AdministratorCommented:
Error code 1811 indicates hardware issue

Check this out

http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=6.5.7596.0&EvtID=455&EvtSrc=ESE&LCID=1033

try restoring the log files

hope they have a good backup
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
itwarlordSenior Engineer/OwnerAuthor Commented:
Rad,

my full backup was from Feb 25th.  after I do the full backup, can I then move the current priv1.edb and pub1.edb back?  

I need to get to the current database.

are you just trying to get the exchange to not look for the logs?

Thomas.  

I do have hard ware issues, but I think this is just a case of the file being deleted.

thanks
0
 
Thomas GrassiSystems AdministratorCommented:
As Rad shows

You can follow the procedure outlined in this MS article https://support.microsoft.com/en-us/kb/896143, refer section "Method 2: If the Exchange log file was deleted" which details about to handle this scenario.


Follow the steps in method 2

After you have a constant DB then you can move them
0
 
itwarlordSenior Engineer/OwnerAuthor Commented:
In method 2 it says you must play through the log files.  I don't have any.

So, I restore the exchange, then do a complete backup of exchange so that it thinks there are no log files, then stop the information store and move the restored EDB files out of the way and replace them with my current EDB files?
0
 
Thomas GrassiSystems AdministratorCommented:
You have a full backup dated Feb 25 correct?  No log files there?

No incremental backups newer with log files?

You need the log files to make the database consistence


Do you have any log files in the folder?

check this out

http://www.petri.com/mount_exchange_database_when_e00log_is_missing.htm
0
 
Thomas GrassiSystems AdministratorCommented:
try

 eseutil /p

 eseutil /r      this need more to run
0
 
Viral RathodConsultantCommented:
No first run eseutil /mh on exchange database and check the status . if it is dirty shutdown or clean shutdown

If it is "CleanShutdown" then there is no need to repaire exchnage database , if the database is clean shutdown then you can move all the log files and check point file to some other location and mount the database

"Clean Shutdown" means almost for sure there are no corruption on the database.

If database is "Dirty Shutdown" they you may need to run softrecovery if you don have the backup of logs files they you need to repire the exchnage database with Defrage and isinteg.

My article will help you for this :
https://viralr.wordpress.com/2011/05/06/exchnage-store-dismounted/

Letme know if you have any further query's.
0
 
itwarlordSenior Engineer/OwnerAuthor Commented:
I was the one who suggested the actual solution.  in fact, I had to go to Microsoft with this direction as everyone on here had hardware ideas.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.