Exchange 2013 CU7 - not running after aborted upgrade
Hi Folks

Hoping you can help here....

I was installing Exchange Server 2013 CU7 and about half-way through it aborted as it didn't like a particular receive connector.

Now the majority of Exchange Services are not starting and if I try to run SP1 setup in recovery mode I receive the following in the ExchangeSetupLog

***************************************************************************************

[02/15/2015 11:10:45.0958] [0] Starting Microsoft Exchange Server 2013 Service Pack 1 Setup
[02/15/2015 11:10:45.0958] [0] **********************************************
[02/15/2015 11:10:45.0974] [0] Local time zone: (UTC+10:00) Canberra, Melbourne, Sydney.
[02/15/2015 11:10:45.0974] [0] Operating system version: Microsoft Windows NT 6.2.9200.0.
[02/15/2015 11:10:45.0974] [0] Setup version: 15.0.847.32.
[02/15/2015 11:10:45.0974] [0] Logged on user: LJHPMQ\administrator.
[02/15/2015 11:10:46.0411] [0] Command Line Parameter Name='mode', Value='RecoverServer'.
[02/15/2015 11:10:46.0411] [0] Command Line Parameter Name='targetdir', Value='X:\Exchange Server\V15'.
[02/15/2015 11:10:46.0411] [0] Command Line Parameter Name='iacceptexchangeserverlicenseterms', Value=''.
[02/15/2015 11:10:46.0411] [0] Command Line Parameter Name='sourcedir', Value='d:\'.
[02/15/2015 11:10:46.0552] [0] RuntimeAssembly was started with the following command: '/Mode:RecoverServer /TargetDir:X:\Exchange Server\V15 /IAcceptExchangeServerLicenseTerms /sourcedir:d:"'.
[02/15/2015 11:10:46.0552] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0, wasn't found.
[02/15/2015 11:10:46.0552] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14, wasn't found.
[02/15/2015 11:10:46.0568] [0] Copying Files...
[02/15/2015 11:10:46.0568] [0] Starting copy from d:\Setup\ServerRoles\Common to C:\Windows\Temp\ExchangeSetup.
[02/15/2015 11:10:58.0695] [0] Finished copy from d:\Setup\ServerRoles\Common to C:\Windows\Temp\ExchangeSetup.
[02/15/2015 11:10:58.0695] [0] File copy complete. Setup will now collect additional information needed for installation.
[02/15/2015 11:10:58.0711] [0] Assembly dll file location is C:\Windows\Temp\ExchangeSetup\Microsoft.Exchange.Setup.Console.dll
[02/15/2015 11:11:04.0802] [0] Setup is choosing the domain controller to use
[02/15/2015 11:11:06.0942] [0] Setup is choosing a local domain controller...
[02/15/2015 11:11:07.0363] [0] [ERROR] Exception has been thrown by the target of an invocation.
[02/15/2015 11:11:07.0394] [0] [ERROR] Method not found: 'Boolean Microsoft.Exchange.Data.Mime.MimeAddressParser.IsValidDomain(System.String, Int32, Boolean)'.
[02/15/2015 11:11:07.0394] [0] CurrentResult SetupLauncherHelper.loadassembly:444: 1
[02/15/2015 11:11:07.0394] [0] The Exchange Server setup operation didn't complete.  More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[02/15/2015 11:11:07.0394] [0] CurrentResult main.run:235: 1
[02/15/2015 11:11:07.0394] [0] CurrentResult setupbase.maincore:396: 1
[02/15/2015 11:11:07.0394] [0] End of Setup
[02/15/2015 11:11:07.0394] [0] **********************************************



********************************************************************************************

Also the most of the Exchange errors in the Application Event log refer to the IsValidDomain String in one way or another

Example below.....

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchange Front End HTTP Proxy" />
    <EventID Qualifiers="49152">1003</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-02-16T00:05:51.000000000Z" />
    <EventRecordID>4486186</EventRecordID>
    <Channel>Application</Channel>
    <Computer>LJH-FPSvr.ljhpmq.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Autodiscover</Data>
    <Data>System.MissingMethodException:Method not found: 'Boolean Microsoft.Exchange.Data.Mime.MimeAddressParser.IsValidDomain(System.String, Int32, Boolean)'.
   at Microsoft.Exchange.Data.Mime.Internal.MimeInternalHelpers.IsValidDomain(String address, Int32 offset, Boolean checkLength)
   at Microsoft.Exchange.Data.SmtpAddress.IsValidDomain(Stringdomain)
   at Microsoft.Exchange.Data.Directory.PartitionId.ValidatePartitionFqdn(String fqdn)
   at Microsoft.Exchange.Data.Directory.ADSessionSettings.SessionSettingsFactory.FromRootOrgScopeSet()
   at Microsoft.Exchange.HttpProxy.DirectoryHelper.GetConfigurationSession()
   at Microsoft.Exchange.HttpProxy.DownLevelServerManager.InternalRefresh()
   at Microsoft.Exchange.HttpProxy.DownLevelServerManager.RefreshServerMap(BooleanisTimer)
   at Microsoft.Exchange.HttpProxy.DownLevelServerManager.Initialize()
   at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate)</Data>
  </EventData>
</Event>

I am also unable to connect to the Exchange Administration Shell it fails with the following error....

Connecting to remote server xxxxx.xxxx.local failed with the following error message: The WinRM client cannot process the request.
 It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid.


Any thoughts or pointers would be appreciated.

Thanks in advance

RazorJ
February 18th, 2015 7:39pm

seems like an issue with Software bundle. did you try to resume installation with a different installation image ? can you get the information which is logged in the latest .ps1 file which is located in C:\ExchangeSetuplogs ?

Free Windows Admin Tool Kit Click here and download it now
February 19th, 2015 6:42am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics