Hi all,

I am trying to recover my lab Exchange 2013 server after removing a component of IIS messed all IIS functions, including all virtual directories.

The server is running on Hyper-V so I have removed and rebuilt the OS disk whilst the Exchange data resides on a separate disk. I've reset the computer account in AD and then run the command:

setup /m:recoverserver /targetdir:"d:\Program Files\Microsoft Exchange\v15" /DoNotStartTransport /IAcceptExchangeServerLicenseTerms

I have now done this a number of times and on each occasion it fails when attempting to start the Microsoft Exchange Transport Submission service. The error in the event log is as follows:

Log Name:      Application
Source:        Application Error
Date:          30/03/2013 20:18:53
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HV-E2K13
Description:
Faulting application name: MSExchangeSubmission.exe, version: 15.0.516.29, time stamp: 0x506956b8
Faulting module name: Microsoft.Exchange.Net.ni.dll, version: 15.0.516.27, time stamp: 0x5064072e
Exception code: 0xc00000fd
Fault offset: 0x0000000000639d07
Faulting process id: 0x1cc8
Faulting application start time: 0x01ce2d83cbb5568e
Faulting application path: D:\Program Files\Microsoft Exchange\v15\Bin\MSExchangeSubmission.exe
Faulting module path: C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.E91f4adf5#\6f9b1d97c1f0dcb9b1006260c405a5da\Microsoft.Exchange.Net.ni.dll
Report Id: 0a1e3a42-9977-11e2-93f1-00155d0a4b05
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-03-30T20:18:53.000000000Z" />
    <EventRecordID>112812</EventRecordID>
    <Channel>Application</Channel>
    <Computer>HV-E2K13</Computer>
    <Security />
  </System>
  <EventData>
    <Data>MSExchangeSubmission.exe</Data>
    <Data>15.0.516.29</Data>
    <Data>506956b8</Data>
    <Data>Microsoft.Exchange.Net.ni.dll</Data>
    <Data>15.0.516.27</Data>
    <Data>5064072e</Data>
    <Data>c00000fd</Data>
    <Data>0000000000639d07</Data>
    <Data>1cc8</Data>
    <Data>01ce2d83cbb5568e</Data>
    <Data>D:\Program Files\Microsoft Exchange\v15\Bin\MSExchangeSubmission.exe</Data>
    <Data>C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.E91f4adf5#\6f9b1d97c1f0dcb9b1006260c405a5da\Microsoft.Exchange.Net.ni.dll</Data>
    <Data>0a1e3a42-9977-11e2-93f1-00155d0a4b05</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Any thoughts?

Paul

Anyone, searching Google isn't coming up with anything.

Paul

Hello,

There is seldom information related to the error.

Please check if the server on which recovery is being performed have the same name as the lost server.

And you have installed the necessary prerequisites and operating system components.

Please refer to the following article to check if you have a correct operation when you recover an Exchange Server.

Recover an Exchange Server

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

If you have any feedback on our support, please click here

Cara,

I have checked what I have been doing to make sure I haven't missed anything silly. The computer has the same name as previous because I have reset the original computer account when joining the domain and no new computer account has appeared in AD.

• The OS is Windows 2012
• I've run Install-WindowsFeature RSAT-ADDS from PowerShell
• I've run the PowerShell command - "Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation"
• I've rebooted and then used Windows Update
• Finally I've run the command "setup /m:recoverserver /targetdir:"d:\Program Files\Microsoft Exchange\v15" /DoNotStartTransport /IAcceptExchangeServerLicenseTerms"
• All went well until recovery tried to bring back the Transport roles, the setup log then shows:

[03/30/2013 00:45:39.0186] [2] Active Directory session settings for 'start-SetupService' are: View Entire Forest: 'True', Configuration Domain Controller: 'Tardis.LEXFORD.local', Preferred Global Catalog: 'Tardis.LEXFORD.local', Preferred Domain Controllers: '{ Tardis.LEXFORD.local }'
[03/30/2013 00:45:39.0186] [2] Beginning processing start-SetupService -ServiceName:'MSExchangeSubmission'
[03/30/2013 00:45:39.0526] [2] [WARNING] Service checkpoint has not progressed. Previous checkpoint='0'- Current checkpoint='0'.
[03/30/2013 00:45:39.0526] [2] Previous service status query time is '30/03/2013 00:45:39'.
[03/30/2013 00:45:39.0526] [2] Current service status query time is '30/03/2013 00:45:39'.
[03/30/2013 00:45:39.0526] [2] Will wait '2000' milliseconds for the service 'MSExchangeSubmission' to reach status 'Running'.
[03/30/2013 00:45:41.0651] [2] Service 'MSExchangeSubmission' failed to reach status 'Running' on this server after waiting for '2000' milliseconds.
[03/30/2013 00:45:41.0651] [2] [WARNING] Service checkpoint has not progressed. Previous checkpoint='0'- Current checkpoint='0'.
[03/30/2013 00:45:41.0651] [2] Previous service status query time is '30/03/2013 00:45:39'.
[03/30/2013 00:45:41.0651] [2] Current service status query time is '30/03/2013 00:45:41'.

..and that's as far as I get

Paul

Hello,

I suggest you disable IPV6 in the network connections properties and check the result.

And check if there is any error in application log.

If you have any feedback on our support, please click here

Tried disabling IPv6 but this had no impact on the outcome.

The only useful error in the Application Log is the one posted at the beginning of this thread which it does over and over, followed by Windows Error Reporting events.

Paul

Paul,

What if you do not specify the targetdir switch and use the default drive letter used for the earlier setup? 

1. Open ADSIEDIT.MSC or LDP.EXE.
2. Navigate to the following location: CN=ExServerName,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=ExOrg Name,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DomainName,CN=Com
3. Right-click the Exchange server object, and then click Properties.
4. Locate the msExchInstallPath attribute. This attribute stores the current installation path.

Also, setup logs are not showing anything significant than just a failure. I would suggest you clear the setup logs or rename the folder and start the recovery once again. You should be able to observe details of the failure. Paste them here. 

Milind,

The installation path in AD is "D:\Program Files\Microsoft Exchange\v15" so consistent with the value I've been supplying with /targetidr:

I have done what you have said with regard to setup logs but I can't see anything obvious until it tries to start the transport service and then just bombs with a timeout.

Paul

This is real strange that setup logs aren't showing anything. Can you try below?

1. Run the system file checker on the windows server that is being used for Exchange installation. I am sure if there is an issue with a system file like one of those native libraries mentioned in the event log that you pasted earlier it would get fixed. You can observe the CBS log for identifying what SFC did. http://blogs.technet.com/b/askcore/archive/2007/12/18/using-system-file-checker-sfc-to-fix-issues.aspx

2. Use a different Exchange 2013 installation media. Maybe download a fresh copy of installation media from MS download.

In the end I gave up and instead followed instructions for restoring using portability database principles. The new server built without a problem and Exchange 2013 had no errors.

Paul

• Proposed as answer by wayne c marshall Wednesday, May 22, 2013 4:01 PM

Hi,

Has anyone managed to succesfully correct this problem?

Thanks,Karl

If you are seeing the same error as Paul I would still recommend you run SFC / SCAANNOW on your box and re-run the setup. If it still fails, I would recommend removing .net framework, reinstall and then try setup.com /m:recoverserver.

If you still fail to get the setup running, try renaming the file Microsoft.Exchange.Net.ni.dll and Microsoft.Exchange.Net.ni.dll.aux located at  C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.E91f4adf5#\6f9b1d97c1f0dcb9b1006260c405a5da

Hi,
Im dealing with the same errors when trying to restore our productive mailbox from a disaster.
I've tried everything listed here but last Milind Naphade commentary.

I'm in that right now, i ll tell if it's working soon.
Ty!

• Edited by darthxen Wednesday, July 30, 2014 5:26 PM

Hi,
Im dealing with the same errors when i'm trying to restore our productive mailbox from a disaster.
I've tried everything listed here but last Milind Naphade commentary.

I'm in that right now, i ll tell if it's working soon.
Ty!

Hi Again. It Failed to start MSExchangeSubmission.exe
Here is the event on eventvwr (Some details on spanish wich is the language of my server)

Nombre de la aplicacin con errores: MSExchangeSubmission.exe, versin: 15.0.516.29, marca de tiempo: 0x506956b8
Nombre del mdulo con errores: Microsoft.Exchange.Net.ni.dll, versin: 15.0.516.27, marca de tiempo: 0x5064072e
Cdigo de excepcin: 0xc00000fd
Desplazamiento de errores: 0x000000000062f697
Identificador del proceso con errores: 0x7d0
Hora de inicio de la aplicacin con errores: 0x01cfac0a0bb16a68
Ruta de acceso de la aplicacin con errores: C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeSubmission.exe
Ruta de acceso del mdulo con errores: C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.E91f4adf5#\b028905d8fd3faa99c9801b69b1500da\Microsoft.Exchange.Net.ni.dll
Identificador del informe: 4a9638fc-17fd-11e4-9404-000c29f101d8
Nombre completo del paquete con errores: 
Identificador de aplicacin relativa del paquete con errores: 

ExchangeSetup.log   ends with:

[07/30/2014 15:19:10.0220] [1] The following 1 error(s) occurred during task execution:
[07/30/2014 15:19:10.0220] [1] 0.  ErrorRecord: El servicio 'MSExchangeSubmission' no puede alcanzar el estado 'Running' en este servidor.
[07/30/2014 15:19:10.0220] [1] 0.  ErrorRecord: Microsoft.Exchange.Configuration.Tasks.ServiceDidNotReachStatusException: El servicio 'MSExchangeSubmission' no puede alcanzar el estado 'Running' en este servidor.
   en Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   en Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   en Microsoft.Exchange.Management.Tasks.ManageSetupService.WaitForServiceStatus(ServiceController serviceController, ServiceControllerStatus status, Unlimited`1 maximumWaitTime, Boolean ignoreFailures, Boolean sendWatsonReportForHungService)
   en Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(ServiceController serviceController, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)
   en Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(String serviceName, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)
   en Microsoft.Exchange.Management.Tasks.StartSetupService.InternalProcessRecord()
   en Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[07/30/2014 15:19:10.0236] [1] [ERROR] The following error was generated when "$error.Clear(); 
start-SetupService -ServiceName MSExchangeSubmission

" was run: "El servicio 'MSExchangeSubmission' no puede alcanzar el estado 'Running' en este servidor.".
[07/30/2014 15:19:10.0236] [1] [ERROR] Service 'MSExchangeSubmission' failed to reach status 'Running' on this server.
[07/30/2014 15:19:10.0236] [1] [ERROR-REFERENCE] Id=MailboxServiceControlLast___23a36fed7b6947e0906f388b5a90135c Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[07/30/2014 15:19:10.0251] [1] Setup is stopping now because of one or more critical errors.
[07/30/2014 15:19:10.0251] [1] Finished executing component tasks.
[07/30/2014 15:19:10.0267] [1] Ending processing DisasterRecovery-MailboxRole
[07/30/2014 15:19:10.0282] [0] No se complet la operacin de instalacin de Exchange Server. Puede encontrar ms detalles en ExchangeSetup.log ubicado en la <SystemDrive>: carpeta \ExchangeSetupLogs.
[07/30/2014 15:19:10.0282] [0] End of Setup
[07/30/2014 15:19:10.0282] [0] **********************************************

Any suggestion please??? idk what else can i do!

There is no C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.E91f4adf5#\6f9b1d97c1f0dcb9b1006260c405a5da

In my server. I've also looking for Microsoft.Exchange.Net.ni.dll and Microsoft.Exchange.Net.ni.dll.aux  on the entire disk with no luck.

Windows server 2012 Std.

Help me please!

EDIT: dumbme, this is BEFORE triying the restore, i've applied an snapshot so, probably that is the cause of the Miscrosoft.Exchange.Net.ni.dll doesnt exist?

• Edited by darthxen Wednesday, July 30, 2014 4:11 PM
• Proposed as answer by Howard.C.Brown 19 hours 29 minutes ago
• Unproposed as answer by Howard.C.Brown 19 hours 29 minutes ago

There is no C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.E91f4adf5#\6f9b1d97c1f0dcb9b1006260c405a5da

In my server. I've also looking for Microsoft.Exchange.Net.ni.dll and Microsoft.Exchange.Net.ni.dll.aux  on the entire disk with no luck.

Windows server 2012 Std.

Help me please!

EDIT: dumbme, this is BEFORE triying the restore, i've applied an snapshot so, probably that is the cause of the Miscrosoft.Exchange.Net.ni.dll doesnt exist?

• Edited by darthxen Wednesday, July 30, 2014 4:11 PM
• Proposed as answer by Howard.C.Brown Friday, July 24, 2015 12:00 PM
• Unproposed as answer by Howard.C.Brown Friday, July 24, 2015 12:00 PM

Guys, have you tried removing the mail queue from the transport\data folder, if this is stored on a different location than the default? as this may allow the transport service to start.