Forum Discussion
OWA/ECP stop working after update ((
Hi KosmosKami,
Happy to hear that ECP is working now.
Regarding OWA, I'll need more info... Which error do you get?
Do you get any log in EV? Which ones?
Please check also that the certificate is still valid. You can check it running:
(Get-AuthConfig).CurrentCertificateThumbprint | Get-ExchangeCertificate | Format-List
FcoManigrasso On OWA page I am get an uninformative message after authorization
:-(
Something went wrong
Unfortunately, we cannot obtain this information right now. Please reply later. If you encounter problems, please contact supportAnd I still can't find the detailed log file that is responsible for OWA. I have seen posts online about what to look for in the IIS logs. Where is it on the right path?
Regarding the certificate, I can say that I checked the state of health with a script HealthChecker.ps1 and it warned that the validity of some certificates was coming to an end. So I used an another script MonitorExchangeAuthCertificate.ps1 to renew the certificates and then point them to IIS.
Hi KosmosKami,
You need to check the Event Viewer for the errors ID's when you try to access OWA.
Please provide also the output of the cmdlt posted in my previous reply, ( you can send me that in a private message ). It's possible that the certificate update failed and that could be the reason of your error. But without more details it's really hard to know. In EV you should be able to see more detailed error pointing to the right root cause.
It's quite interesting. I tried to find events using the error or warning filter. It turned out that the event I was interested in was with the information level. Event code 1309. The source is ASP.NET 4.0.30319.0
Event code: 3005 Event message: An unhandled exception occurred. Event time: 07.03.2023 21:20:45 Event time (UTC): 07.03.2023 18:20:45 Event ID: c51f5e3a06fc4aa8b569417c2d2cbc90 Event sequence: 2 Event occurrence: 1 Event detail code: 0 Application information: Application domain: /LM/W3SVC/2/ROOT/owa-4603-133226868366278403 Trust level: Full Application Virtual Path: /owa Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\ Machine name: EMAIL Process information: Process ID: 20032 Process name: w3wp.exe Account name: NT AUTHORITY\system Exception information: Exception type: ArgumentException Exception message: An element with the same key has already been added. in System.ThrowHelper.ThrowArgumentException(ExceptionResource resource) in System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add) at Microsoft.Exchange.Clients.Owa.Core.OwaSettingsLoaderBase.InitializeLocalVersionFolders() in Microsoft.Exchange.Clients.Owa.Core.OwaSettingsLoaderBase.Load() at Microsoft.Exchange.Clients.Owa.Core.OwaSettingsLoader.Load() in Microsoft.Exchange.Clients.Owa.Core.OwaApplicationBase.ExecuteApplicationStart(Object sender, EventArgs e) in Microsoft.Exchange.Clients.Owa.Core.OwaModule.Init(HttpApplication context) in System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr AppContext, HttpContext context, MethodInfo[] handlers) in System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr AppContext, HttpContext context) in System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr AppContext, HttpContext context) in System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) Request information: Request URL: https://email.contoso.com:444/owa Request path: /owa User host address: my-ip-address User: Is authenticated: False Authentication Type: Thread account name: NT AUTHORITY\system Thread information: Thread ID: 63 Thread account name: NT AUTHORITY\system Is impersonating: False Stack trace: in System.ThrowHelper.ThrowArgumentException(ExceptionResource resource) in System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add) at Microsoft.Exchange.Clients.Owa.Core.OwaSettingsLoaderBase.InitializeLocalVersionFolders() in Microsoft.Exchange.Clients.Owa.Core.OwaSettingsLoaderBase.Load() in Microsoft.Exchange.Clients.Owa.Core.OwaSettingsLoader.Load() in Microsoft.Exchange.Clients.Owa.Core.OwaApplicationBase.ExecuteApplicationStart(Object sender, EventArgs e) at Microsoft.Exchange.Clients.Owa.Core.OwaModule.Init(HttpApplication context) in System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr AppContext, HttpContext context, MethodInfo[] handlers) in System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr AppContext, HttpContext context) in System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr AppContext, HttpContext context) in System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) Custom event details:Hi KosmosKami,
From the EV log, it still seems that something is wrong with the SharedWebConfig.config file.
Maybe that copy paste wasn't the best way. Let me suggest the following steps:
- Navigate to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess and if your pasted SharedWebConfig.config file is still there, move it to another location as backup.
- Run cd %ExchangeInstallPath%\bin to change the current directory to the bin folder that's under the Exchange installation path.
- Use the DependentAssemblyGenerator.exe tool to generate the file:
DependentAssemblyGenerator.exe -exchangePath "%ExchangeInstallPath%\bin" -exchangePath "%ExchangeInstallPath%\ClientAccess" -configFile "%ExchangeInstallPath%\ClientAccess\SharedWebConfig.config"- Restart the Server.
Hope this helps.