Exchange 2013 Upgrade to CU7 from SP1 - installs successfully - Can no longer connect via ECP/OWA/Powershell/Outlook/Autodiscover

Question

Hi There,
I am having massive issues with my Exchange Server.
I have 2 Nodes, one has CAS and Mailbox Roles, the other just Mailbox.
I "upgraded" the CAS server to CU7 without any errors / issues.
Once I had restarted, nothing worked any more..  I couldn't access ECP, OWA, Powershell, Autodiscover or get outlook to connect.
I managed to get Powershell working, but changing the physical directory to "C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PowerShell" from "C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\PowerShell"
But for the life of me I cannot get ECP or OWA working (haven't even tried anything else)!
I am getting a load of Events with ID 1003.
The only error I am getting is:
Server Error in '/ecp' Application.
Method not found: 'Boolean Microsoft.Exchange.Net.Wopi.WopiRequestPathHandler.IsWopiRequest(System.Web.HttpRequest)'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.MissingMethodException: Method not found: 'Boolean Microsoft.Exchange.Net.Wopi.WopiRequestPathHandler.IsWopiRequest(System.Web.HttpRequest)'.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[MissingMethodException: Method not found: 'Boolean Microsoft.Exchange.Net.Wopi.WopiRequestPathHandler.IsWopiRequest(System.Web.HttpRequest)'.]
Microsoft.Exchange.HttpProxy.ProxyModule.AllowAnonymousRequest(HttpRequest httpRequest) +0
Microsoft.Exchange.HttpProxy.ProxyModule.OnAuthenticateInternal(HttpApplication httpApplication) +51
Microsoft.Exchange.HttpProxy.<>c__DisplayClass5.<OnAuthenticateRequest>b__4() +447
Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate) +40
Microsoft.Exchange.HttpProxy.Diagnostics.SendWatsonReportOnUnhandledException(MethodDelegate methodDelegate) +408
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +165
Which is almost meaningless...  but maybe someone out there has some idea?
Unfortunately this is very urgent for me a these are production servers and currently there is no email for my company.
So Please please please can someone help.
I have tried many many many things from various sites, and so far nothing has worked.
Thanks,
-Tim

Answer 1

Hi Tim,
We can do the following steps to have a try:
1. Check Application settings in IIS Application under Exchange Back End web site for BinSearchFolders value.
a. Open IIS Manager. Expand Sites > Exchange Back End.
b. Click ecp. Open Application Settings in /ecp Home.
c. Please check whether the value for “BinSearchFolders” is changed to an invalid value.
2. Verify Authentication settings for OWA and ECP.
a. In IIS manager > Default Web Site, make sure Anonymous Authentication is Enabled in Authentication.
b. Confirm that "Require SSL" is checked on the root of the default website.
c. Make sure the Basic and Forms authentications are enabled in Default Web Site and Ntlm, WindowsIntegrated authentication methods are enabled in Exchange Back End for both OWA and ECP.
Regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Winnie Liang
TechNet Community Support