Exchange 2010 Installation error

Question

Hi All,
I'm at my over 10th installation of Exchange 2010 server and it is the first time I have to admit that I can't resolve the issue i'm faced off ;-)
Here is some info about my issue. The installation is on a Windows 2008 R2 (Virtual) sit on a Windows 2012 R2 server with Hyper-V and it is a fresh vanilla installation that I'm trying to install for the 3rd time. Each attempts returned me the same error
at the same steps.
The Exchange installation is a typical, common, CAS, Mailbox and HUB installation without any particular configuration in the setup.
Here is the error I get:
Client Access Role
Failed
Error:
The following error was generated when "$error.Clear(); 
$urlToUse = "https://" + $RoleFqdnOrName + "/ews/exchange.asmx";
new-WebServicesVirtualDirectory -windowsAuthentication:$true -WSSecurityAuthentication:$true -InternalNLBBypassUrl $urlToUse -DomainController $RoleDomainController -Force -GzipLevel High;
" was run: "An error occurred while creating the IIS virtual directory 'IIS://MTL1EX01.parasuco.com/W3SVC/1/ROOT/EWS' on 'MTL1EX01'.".
An error occurred while creating the IIS virtual directory 'IIS://MTL1EX01.parasuco.com/W3SVC/1/ROOT/EWS' on 'MTL1EX01'.
The type 'Microsoft.Exchange.Services.Wcf.MessageEncoderWithXmlDeclarationSoap11BindingElementExtension, Microsoft.Exchange.Services, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' registered for extension 'EWSMessageEncoderSoap11Element'
could not be loaded. (C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS\web.config line 2373)
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=ms.exch.err.Ex88D115&l=0&cl=cp
I Googled every single point of failure indication and I didn't get reliable fix or work around.
I used ADSI edit  to see if the IIS folders are there and yes they are except the EWS one which is mentioned in
the error message. Forest, Domain and AD have been prepared as it should, DCDIAG doesn't return any problem and the security has been set
properly for Legacy migration with an Exchange 2003 organisation.
Here is the par of the Exchange setup log where it stopped:
[03-06-2014 16:15:26.0488] [1] Processing component 'Client Access Services Configuration' (Configuring Client Access services.).
[03-06-2014 16:15:26.0488] [1] Executing: 
$urlToUse = "https://" + $RoleFqdnOrName + "/ews/exchange.asmx";
new-WebServicesVirtualDirectory -windowsAuthentication:$true -WSSecurityAuthentication:$true -InternalNLBBypassUrl $urlToUse -DomainController $RoleDomainController -Force -GzipLevel High;
[03-06-2014 16:15:26.0503] [2] Active Directory session settings for 'New-WebServicesVirtualDirectory' are: View Entire Forest: 'True', Configuration Domain Controller: 'powerhouse.parasuco.com', Preferred Global Catalog: 'powerhouse.parasuco.com', Preferred
Domain Controllers: '{ powerhouse.parasuco.com }'
[03-06-2014 16:15:26.0503] [2] Beginning processing new-WebServicesVirtualDirectory -WindowsAuthentication:'True' -WSSecurityAuthentication:'True' -InternalNLBBypassUrl:'https://mtl1ex01.parasuco.com/ews/exchange.asmx' -DomainController:'powerhouse.parasuco.com'
-Force:'True' -GzipLevel:'High'
[03-06-2014 16:15:26.0636] [2] Searching objects "MTL1EX01.parasuco.com" of type "Server" under the root "$null".
[03-06-2014 16:15:26.0649] [2] Previous operation run on domain controller 'powerhouse.parasuco.com'.
[03-06-2014 16:15:26.0650] [2] Processing object "MTL1EX01\EWS".
[03-06-2014 16:15:29.0130] [2] [ERROR] Unexpected Error
[03-06-2014 16:15:29.0130] [2] [ERROR] An error occurred while creating the IIS virtual directory 'IIS://MTL1EX01.parasuco.com/W3SVC/1/ROOT/EWS' on 'MTL1EX01'.
[03-06-2014 16:15:29.0131] [2] [ERROR] The type 'Microsoft.Exchange.Services.Wcf.MessageEncoderWithXmlDeclarationSoap11BindingElementExtension, Microsoft.Exchange.Services, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' registered for extension
'EWSMessageEncoderSoap11Element' could not be loaded. (C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS\web.config line 2373)
[03-06-2014 16:15:29.0138] [2] Ending processing new-WebServicesVirtualDirectory
[03-06-2014 16:15:29.0139] [1] The following 1 error(s) occurred during task execution:
[03-06-2014 16:15:29.0139] [1] 0.  ErrorRecord: An error occurred while creating the IIS virtual directory 'IIS://MTL1EX01.parasuco.com/W3SVC/1/ROOT/EWS' on 'MTL1EX01'.
[03-06-2014 16:15:29.0139] [1] 0.  ErrorRecord: System.InvalidOperationException: An error occurred while creating the IIS virtual directory 'IIS://MTL1EX01.parasuco.com/W3SVC/1/ROOT/EWS' on 'MTL1EX01'. ---> System.Configuration.ConfigurationErrorsException:
The type 'Microsoft.Exchange.Services.Wcf.MessageEncoderWithXmlDeclarationSoap11BindingElementExtension,
Microsoft.Exchange.Services, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' registered for extension 'EWSMessageEncoderSoap11Element' could not be loaded. (C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS\web.config
line 2373)
   at System.Configuration.BaseConfigurationRecord.EvaluateOne(String[] keys, SectionInput input, Boolean isTrusted, FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult)
   at System.Configuration.BaseConfigurationRecord.Evaluate(FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult, Boolean getLkg, Boolean getRuntimeObject, Object& result, Object& resultRuntimeObject)
   at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)
   at System.Configuration.Configuration.GetSection(String sectionName)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.ExtendedProtection.WebConfigReflectionHelper.CommitToWebConfig(ExchangeVirtualDirectory exchangeVirtualDirectory, Task task, String path, String site, String server, Boolean isTokenCheckingSpecified,
Boolean isSpnListSpecified)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.ExtendedProtection.CommitToMetabase(ExchangeVirtualDirectory exchangeVirtualDirectory, Task task)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalProcessMetabase()
   at Microsoft.Exchange.Management.SystemConfigurationTasks.NewWebServicesVirtualDirectory.InternalProcessMetabase()
   at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalProcessRecord()
   --- End of inner exception stack trace ---
[03-06-2014 16:15:29.0139] [1] [ERROR] The following error was generated when "$error.Clear(); 
$urlToUse = "https://" + $RoleFqdnOrName + "/ews/exchange.asmx";
new-WebServicesVirtualDirectory -windowsAuthentication:$true -WSSecurityAuthentication:$true -InternalNLBBypassUrl $urlToUse -DomainController $RoleDomainController -Force -GzipLevel High;
" was run: "An error occurred while creating the IIS virtual directory 'IIS://MTL1EX01.parasuco.com/W3SVC/1/ROOT/EWS' on 'MTL1EX01'.".
[03-06-2014 16:15:29.0139] [1] [ERROR] An error occurred while creating the IIS virtual directory 'IIS://MTL1EX01.parasuco.com/W3SVC/1/ROOT/EWS' on 'MTL1EX01'.
[03-06-2014 16:15:29.0139] [1] [ERROR] The type 'Microsoft.Exchange.Services.Wcf.MessageEncoderWithXmlDeclarationSoap11BindingElementExtension, Microsoft.Exchange.Services, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' registered for extension
'EWSMessageEncoderSoap11Element' could not be loaded. (C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS\web.config line 2373)
[03-06-2014 16:15:29.0140] [1] [ERROR-REFERENCE] Id=ServicesComponent___ca981854eaa74c1ca684178d9ea52fff Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[03-06-2014 16:15:29.0140] [1] Setup is stopping now because of one or more critical errors.
I appreciate the time anybody would spend to help me with my issue

Answer 1

Well, here is a status of what I did.
After running the Cleanup tool, I ran the Exchange server setup again without re installing anything and I got the same error and I have found .NET issue in the application's event logs (Event ID 1111 .NET runtime optimization service with this error code:
- Error code 0x80029c4a =
Cannot Load Library); . Why that? because there still Windows Kernel Mode and User Mode .NET 1.11.
So I uninstalled them and ran the exchange setup again. It failed a the same point but nothing in the application log that time.
Going further to see if it is a .NET issue, I re installed from Windows Update the .NET
1.11 packages (Which are required prior to reinstall .NET 4.5) restart the server + re install version 4.5.1 and ran the setup again without the two available security patches for .NET 4.5.1. Guess what, same issue. No .NET error and no specific or related
log except the Exchange setup installation error.
From the MSExchange Management log, i have found that 2 errors are logged each time I run the setup:
Cmdlet failed. Cmdlet Install-ClientAccessRole, parameters {DomainController=powerhouse.parasuco.com, UpdatesDir=E:\Updates, ExternalCASServerDomain=webmail.parasuco.com}.
Cmdlet failed. Cmdlet New-WebServicesVirtualDirectory, parameters {WindowsAuthentication=True, WSSecurityAuthentication=True, InternalNLBBypassUrl=https://mtl1ex01.parasuco.com/ews/exchange.asmx, DomainController=powerhouse.parasuco.com, Force=True, GzipLevel=High}.
So it seems to me to be a IIS and security issue. Again, All other IIS virtual folders have been created without any problem. Why does the setup can't create the EWS one???