Exchange 2007 transport service won't start - keeps replaying logs

As the title says, I had some issues with Exchange so I rebooted the server and finally all storage groups mounted. However, the transport service keeps getting stuck in a loop replaying log files, shutting down, creating a new instance and starting again, I read that possibly renaming the entire c:\Program Files\Microsoft\Exchange Server\TransportRoles\data folder may help, but I'm wondering if that is the best course of action, or perhaps I just need to move out the transaction log files from the Queue folder, but leave mail.que where it is. I assume I'd need to kill the msexchangetransport.exe process first as well.

Please advise next steps. Thanks.
ruhkusAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Adam FarageEnterprise ArchCommented:
Depends.. if the mail.que file is not starting it sounds like that file is corrupt. You do have the option to run ESEUTIL /MH against it to find the state of the shutdown, and then run ESEUTIL /R but if you know there are no emails in there (you might be able to run Get-TransportServer | Get-Queue) I would simply do the following:

- Shutdown the MS Exchange Transport service (which should be msexchangetransport.exe) in services.msc
- In the folder that contains the mail.que and the logs, create a new folder called "old" and move everything there. I would keep it within the %exchangeinstallpath%\TransportRoles\data folder.
- Start the MS Exchange Transport service

This will create a brand new transport database (mail.que) along with checkpoint file, and recreate the log sequence. You have a possibility that you will lose any emails that are stuck in the mail.que file, but if that is a concern that you would need to treat this as a dirty shutdown database and then start ESEUTIL /MH (to find the last log replayed, and the logs required) and then attempt to replay them into the database using ESEUTIL /R. I have seen this work, but if you do go down this route I would wait until the mail.que processes all messages and follow the steps above I provided. Starting clean is your best option right now.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ruhkusAuthor Commented:
Thanks. I ran an eseutil /r and was able to get this back up and running.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

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.