Hello, I have a question regarding an test that i did . I have an exchnage server with logs all commited into the database. The eseutil /mh shows clean shut down and the logs required are 0-0. Now i delete the e00.log and then try to mount the database which gives me error Event Type: Error Event Source: MSExchangeIS Event Category: General Event ID: 9518 Description: Error Current log file missing starting Storage Group /DC=COM/DC=COMPANY/CN=CONFIGURATION/CN=SERVICES/CN=MICROSOFT EXCHANGE/CN=MICROSOFT/CN=ADMINISTRATIVE GROUPS/CN=FIRST ADMINISTRATIVE GROUP/CN=SERVERS/CN=SERVER1/CN=INFORMATIONSTORE/CN=FIRST STORAGE GROUP on the Microsoft Exchange Information Store. I rename the last log (e000003b)to e00.log and then try to mount the store which gives me the same warning and event in the app log that says exchange is looking for the renamed log file. Now i delete the check point file and then try to mount the store which gives me the same error as before. Question: why is it that exchange database is not mounting. Once the exchange database is clean shut down it does not need the log files. Also when i rename the E000003B to e00.log i haev all transaction logs upto E000003A in a sequence and then the current log file. Any help is greatly appreciated. Thanks

Hello, I guess it's all related to a thing called log generation number ( lGeneration) . This is an unique value that is assigned to each log and that helps the store to keep track of logs, to identify them. If you do a esutil /ml on a log you will see that he has a value lGeneration that corresponds to his number ( e.g 657 or 0x291) On the other hand , if you do a eseutil /mh on the database you will see that there are a lot of fields where the lGeneration plays a role: last Consistent, last attach, last dettach . On a Clean Shutdown db these values all point to the lGeneration of log E00, which is the last one. If you delete it...it will not mount cause it needs that log to be able to attach itself to it a have a contigous sequeunce once again. The only way to get around it is to delete all the logs in the directory ( including chk) because that will just reinitialize the lGeneration process and the store will start counting form lGeneration zero again. Hope it helps, Mihai

Thanks. I read little more abt it.