Hello! I need help - there was an Exchange 2013 server in my organization and it failed because of hard disk drive problems. So I have only domain controller and database backup (*.edb) at this moment. I decided to create the same server (using same configuration, same domain name):

setup /m:RecoverServer /Iacceptexchangeserverlicenseterms

Process has been started and it was OK but there is critical error while finalizing setup:

Welcome to Microsoft Exchange Server 2013 Cumulative Update 6 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for
installation.
Languages
Mailbox role: Transport service
Mailbox role: Client Access service
Mailbox role: Unified Messaging service
Mailbox role: Mailbox service
Management tools
Client Access role: Client Access Front End service
Client Access role: Front End Transport service

Performing Microsoft Exchange Server Prerequisite Check

    Configuring Prerequisites                                 COMPLETED
    Prerequisite Analysis                                     COMPLETED

Configuring Microsoft Exchange Server

    Preparing Setup                                           COMPLETED
    Stopping Services                                         COMPLETED
    Copying Exchange Files                                    COMPLETED
    Language Files                                            COMPLETED
    Restoring Services                                        COMPLETED
    Language Configuration                                    COMPLETED
    Mailbox role: Transport service                           COMPLETED
    Mailbox role: Client Access service                       COMPLETED
    Mailbox role: Unified Messaging service                   COMPLETED
    Mailbox role: Mailbox service                             COMPLETED
    Exchange Management Tools                                 COMPLETED
    Client Access role: Client Access Front End service       COMPLETED
    Client Access role: Front End Transport service           COMPLETED
    Finalizing Setup                                          FAILED
     The following error was generated when "$error.Clear();
        start-SetupService -ServiceName MSExchangeFrontendTransport

" was run: "Microsoft.Exchange.Configuration.Tasks.ServiceDidNotReachStatusExcep
tion: Service 'MSExchangeFrontendTransport' failed to reach status 'Running' on
this server.
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception
, ErrorCategory errorCategory, Object target, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception
, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Tasks.ManageSetupService.WaitForServiceStatu
s(ServiceController serviceController, ServiceControllerStatus status, Unlimited
`1 maximumWaitTime, Boolean ignoreFailures, Boolean sendWatsonReportForHungServi
ce)
   at Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(Servic
eController serviceController, Boolean ignoreServiceStartTimeout, Boolean failIf
ServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)
   at Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(String
 serviceName, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstall
ed, Unlimited`1 maximumWaitTime, String[] serviceParameters)
   at Microsoft.Exchange.Management.Tasks.StartSetupService.InternalProcessRecor
d()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String fun
cName, Action func, Boolean terminatePipelineIfFailed)".


The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.

What is wrong with my server? I already tried 3 times using different servers - and there is same error in the end of setup process. Help me, please - need to recover urgently this mail server...

Hi ,

Thank you for your question.

When the error occur, we could run Services.msc in RUN,

Then we could find Microsoft Exchange Frontend Transport, then make sure it is running, if not, we could run it by manually. Then re-setup to check if the issue persist.

https://technet.microsoft.com/en-us/library/dd876880(v=exchg.150).aspx

If the issue persist, please let us know which steps you have done before you run the command.

In addition, before we run it , we should reset the computer account for the failed server by the following link:

https://technet.microsoft.com/en-us/library/cc753596(v=ws.11).aspx

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

I can't start this service even manually. It starts and immediately stops. May be I should use this command?

Setup /m:RecoverServer /DoNotStartTransport

Hi ,

Thank you for your question.

We could check there are any errors in application log and send error to ibsexc@microsoft.com for our troubleshooting.

Or you could refer to the following link to fix it, then check if the issue persist:

https://support.microsoft.com/en-us/kb/2938053

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

So I should apply this "fixit" and run

Setup /m:RecoverServer /IAcceptExchangeServerLicenseTerms
once again, right? And what about database? Should I put it on the same disk (disk D in my case) before recovery starts?

Well, I will try CU7 instead CU6...

• Edited by Saturday, May 30, 2015 10:20 AM

Unfortunately still no result. This is log:

[WARNING] Service checkpoint has not progressed. Previous checkpoint='0'- Current checkpoint='0'.
[05.30.2015 10:55:51.0312] [2] Previous service status query time is '30.05.2015 13:55:26'.
[05.30.2015 10:55:51.0312] [2] Current service status query time is '30.05.2015 13:55:51'.
[05.30.2015 10:55:51.0312] [2] Will wait '25000' milliseconds for the service 'MSExchangeFrontendTransport' to reach status 'Running'.
[05.30.2015 10:56:16.0512] [2] Service 'MSExchangeFrontendTransport' failed to reach status 'Running' on this server after waiting for '25000' milliseconds.
[05.30.2015 10:56:16.0512] [2] [WARNING] Service checkpoint has not progressed. Previous checkpoint='0'- Current checkpoint='0'.
[05.30.2015 10:56:16.0512] [2] Previous service status query time is '30.05.2015 13:55:51'.
[05.30.2015 10:56:16.0512] [2] Current service status query time is '30.05.2015 13:56:16'.
[05.30.2015 10:56:16.0512] [2] Will wait '25000' milliseconds for the service 'MSExchangeFrontendTransport' to reach status 'Running'.
[05.30.2015 10:56:41.0712] [2] Service 'MSExchangeFrontendTransport' failed to reach status 'Running' on this server after waiting for '25000' milliseconds.
[05.30.2015 10:56:41.0712] [2] [WARNING] Service checkpoint has not progressed. Previous checkpoint='0'- Current checkpoint='0'.
[05.30.2015 10:56:41.0712] [2] Previous service status query time is '30.05.2015 13:56:16'.
[05.30.2015 10:56:41.0712] [2] Current service status query time is '30.05.2015 13:56:41'.
[05.30.2015 10:56:41.0712] [2] Will wait '25000' milliseconds for the service 'MSExchangeFrontendTransport' to reach status 'Running'.

It waits some minutes and stop after that (. So I can't start setup again. What should I do?

This looks like:

So a couple of things

1. Yes your configuration in terms of IP address, Drive configuration etc should be the same
2. Did you have ALL roles on the same box prior? i.e. is it possible you already have the transport role installed elsewhere?
3. Am I correct to assume that your AD is intact and without issues?
   
4. Did you check the application event log when this error occurs to see if it sheds some light on the situation?   My practice when issues like this occur is to save off the system and application event log and clear them.  Then run the process and upon failure go look into the application and system event logs for all warning and critical errors to see if they give me an aha moment
   
5. Check out the article below, its for 2010 but could be a similar issue, i.e. check your DNS and also ensure you are using the same IP address
   

http://exchangeserverpro.com/exchange-2010-setup-fails-when-msexchangetransport-service-wont-start/

Its sounds to me like there is some conflict i.e. the Front End is already installed on another machine or perhaps you are using a different IP address which is then causing DNS to mess things up so ensure your using the exact same Machine name and IP address as before

If that doesn't work the other options would be to

• Open a support case with MS and have them remote in to help you resolve.  It will cost a few hundred to make it happen but probably worth it
• OR build a fresh new server and then either use database portability and re-home all mailboxes to new DB's and server OR use our DigiScope product http://www.lucid8.com/product/digiscope.asp to open the Offline EDB's and then import/migrate the information into the new server

Good luck and whatever the resolution is please be sure to post back

So I should apply this "fixit" and run

Setup /m:RecoverServer /IAcceptExchangeServerLicenseTerms
once again, right? And what about database? Should I put it on the same disk (disk D in my case) before recovery starts?

Well, I will try CU7 instead CU6...

Hi,

When we recover the Exchange server, we should configure computer which is the same as the former computer. Include IP address, disk drive .

Then we could check if you have disable Ipv6, if that, you could enable it.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Thank you but I already build a new domain and a new Exchange server. Tell me please - can I create domain (using different host) with old name and old-named Exchange - to mount old database and get all the messages?

ok wait  please clarify

1. You built a new domain and server for exchange, correct?
   
2. And are now trying to do a recovery of an exchange server from the old domain, correct?
3. If yes to all the above are the domain names the same
4. If yes to # 3 did you do a restore of the previous AD into the new domain?

If you need to end up using a 3rd party utility for recovery be very careful about the tool you select since there are only 3 trustworthy tools that handle the data in a complete & accurate manner, others not so much and end result could be creating a bigger mess with partial, incomplete or mangled data

Hi ,

No, you should recover the Exchange server in old domain, because Exchange configured information was stored in old domain, when we run the recover command, it will fetch information from old domain. We should not create a new domain.

We should recovery by the following link:

https://technet.microsoft.com/en-us/library/dd876880(v=exchg.150).aspx

Notice: new Exchange must have same configuration with old Exchange, include hard drive.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim