Solved

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

Posted on 2014-09-08
2
636 Views
Last Modified: 2014-09-09
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.
0
Comment
Question by:ruhkus
2 Comments
 
LVL 19

Accepted Solution

by:
Adam Farage earned 500 total points
Comment Utility
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
 

Author Closing Comment

by:ruhkus
Comment Utility
Thanks. I ran an eseutil /r and was able to get this back up and running.
0

Featured Post

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

Resolve DNS query failed errors for Exchange
Not sure what the best email signature size is? Are you worried about email signature image size? Follow this best practice guide.
In this video we show how to create a User Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Mailb…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now