Event ID 1309 and you can't access OWA and ECP after you install Exchange Server 2016 or Exchange Server 2013
Article
Applies to:
Exchange Server 2016 Enterprise Edition, Exchange Server 2016 Standard Edition, Exchange Server 2013 Enterprise, Exchange Server 2013 Standard Edition
Original KB number: 3099532
Symptoms
You successfully installed Microsoft Exchange Server 2016 or Exchange Server 2013. The installation process may have failed or been interrupted at some stage and then resumed and finally completed successfully. However, when you try to access Exchange Control Panel (ECP) or Outlook Web App (OWA), you receive the following error message:
something went wrong
Sorry, we can't get that information right now. Please try again later. If the problem continues, contact your helpdesk.
Additionally, the following event may be logged in the Application log:
Log Name: Application
Source: ASP.NET 4.0.30319.0
Event ID: 1309
Task Category: Web Event
Level: Warning
Keywords: Classic
User: N/A
Computer: Exch2.contoso.com
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event ID: f23d9d455f3145068c57286262ac517f
Event sequence: 1
Event occurrence: 1
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/2/ROOT/owa-5-130879214460462920
Trust level: Full
Application Virtual Path: /owa
Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\
Machine name: EXCH2
Process information:
Process ID: 4348
Process name: w3wp.exe
Account name: NT AUTHORITY\SYSTEM
Exception information:
Exception type: TargetInvocationException
Exception message: Exception has been thrown by the target of an invocation.
at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck,
Boolean&canBeCached, RuntimeMethodHandleInternal&ctor, Boolean&bNeedSecurityCheck)
* SharedWebConfig.config is missing from either of these locations:
C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy
C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess
Cause
This issue occurs if SharedWebConfig.config is missing from either of the following locations:
The SharedWebConfig.config file generates during the post-installation phase of Setup. If Setup resumes after an interruption, it doesn't do the post-installation steps for the roles that were successfully installed before the interruption.
Learn how to troubleshoot meeting creation, attendee access, meeting recording issues, and content sharing. Learn how to optimize live events, and how to troubleshoot messaging issues.