Resetting Exchange 2003 log sequence numbers manually?

wimpie_asg
wimpie_asg used Ask the Experts™
on
Hi all,

I have an Exchange 2003 server that has reached the end of its log circulation numbers. The databases does not mount any more, and there is an error Event ID:9518 failing to start JetDirect.

I have downloaded the tool Microsoft Troubleshooting assistant to reset the log number that Exchange 2003 uses - but it looks like it is freezing on me. Is there a way I can reset the log sequence numbers that Exchange uses manually?

Any help would be appreciated!

Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Manpreet SIngh KhatraSolutions Architect, Project Lead
Top Expert 2013

Commented:
You just have to move all Transaction log files,  the .res and .chk file to another locationa dn then mount.

This will give a warning stating a new set of log files would be created ...say yes and mount ..

Once done take a good FUll backup to be on the safer side :)
Manpreet SIngh KhatraSolutions Architect, Project Lead
Top Expert 2013
Commented:
Check this article might help you understand .... still have any queries make a post (DO NOT DELETE anything -- just move them to a different location)

http://support.microsoft.com/kb/240145
Manpreet SIngh KhatraSolutions Architect, Project Lead
Top Expert 2013

Commented:
How to Generate Services Revenue the Easiest Way

This Tuesday! Learn key insights about modern cyber protection services & gain practical strategies to skyrocket business:

- What it takes to build a cloud service portfolio
- How to determine which services will help your unique business grow
- Various use-cases and examples

Author

Commented:
Hi,

After only having the following files in my exchange folder:

pub1.edb
priv1.edb
priv1.stm
pub1.stm

I get the same error:

Event ID:      9518

Storage Group - Initialization of Jet failed.


Author

Commented:
I am willing to start a new Exchange database - but when I rename the MDBDATA folder to something else - and create a new MDBDATA folder - mount Exchange with no data what so ever - it is supose to ask me if I want to create a new database - but it does not! It comes up with the same error!!!

Commented:
First check the state of the database files using the "eseutil /mh" command.

example: eseutil /mh "D:\program files\exchsrvr\first storage group\priv1.edb"

make sure that the state of the database is in clean shutdown.

once we make sure that the database is in clean shut down, you can go ahead and move the log files associated to that database, to a different location.

if you have multiple database located under the same storage group, such databases will share the same set of exchange logs,

in such case we have to make sure that all the database are in clean shutdown before moving the log files.

after moving the log files, go ahead and mount the database(s) and you will find thet a new set of log files are generated.

Commented:
Adding to the previous comment.

pls make sure that you move the .chk file also with the .log files.

also go the properties of the database(s) in the ESM and theny go to the database tab and select the option "This database can be over written by  a restore", and then mount the database(s).

once the database(s) is mounted go ahead and uncheck the "This database can be over written by  a restore" option.

Author

Commented:
Hi,

My Exchange Databe is in a dirty shutdown state - how do I get it in a clean shutdown state?

Commented:
Hi,

In the report generated by eseutil /mh where it shows the status of the database as "Dirty Shutdown" the next row will state the log required:  look for the number mentioned in the brackets.

those hex. numbers will show the set of log files requried to bring the database in clean shutdown.
try locating those set of log files and use the eseutil /r command to replay the set of log files to the database.

if the replay of the log files fails then use a good backup to restore the database.

if you dont have a backup to restore from then, you might have to hard repair the database.

Note: Hard repair of the database should be the last option as hard reparing the database involves dataloss.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial