Exchange 2016: OWA does not work, ASP.NET Event 1310

Frank Zöchling

9 years ago

I stumbled across an interesting problem with an Exchange 2016 server. This ASP.NET event 1310 kept appearing as a warning in the event display in the application log:

Here is the abbreviated error message:

Event code: 3008
Event message: A configuration error has occurred.
Event time: 20.01.2016 22:07:48
Event time (UTC): 20.01.2016 21:07:48
Event ID: 6c0bf342123d4f7b8e23253b5ae8030e
Event sequence: 1
Event occurrence: 1
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/2/ROOT/owa-16-130977976684578279
Trust level: Full
Application Virtual Path: /owa
Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\
Machine name: MAIL01

Process information:
Process ID: 9864
Process name: w3wp.exe
Account name: NT-AUTHORITY\SYSTEM

Exception information:
Exception type: ConfigurationErrorsException

Die Datei oder Assembly „Microsoft.CobaltCore“ oder eine Abhängigkeit davon wurde nicht gefunden. Falscher Parameter. (Ausnahme von HRESULT: 0x80070057 (E_INVALIDARG)

Request information:
Request URL: https://localhost:444/owa/proxylogon.owa
Request path: /owa/proxylogon.owa
User host address: 127.0.0.1
User:
Is authenticated: False
Authentication Type:
Thread account name: NT-AUTHORITY\SYSTEM

This warning appeared for every virtual IIS directory:

I had already checked the usual suspects such as website bindings and settings, everything was fine there. EAC worked smoothly, whereas OWA only brought up the following message after the login screen:

ActiveSync, EWS etc. did not work either. No other errors appeared in the event display either.

I then spent a long time looking for the problem, but discovered the solution more by chance when I started comparing the faulty installation with a working Exchange 2016 installation.

After a long search I stumbled across the following directory:

Auf dem funktionierenden Exchange Server enthält dieses Verzeichnis neben den ganzen Verzeichnissen auch eine Datei mit dem Namen „SharedWebConfig.config“

This file can also be found in another directory:

Ich habe also diese Datei „SharedWebConfig.config“ aus dem Verzeichnis „%ExchangeInstallPath%\FrontEnd\HttpProxy“ nach „%ExchangeInstallPath%\ClientAccess“ kopiert:

After the file was copied, I had to restart the IIS. To do this, the following command can be entered on the command line:

iisreset

Now OWA etc. is working again without any problems:

Übrigens: Der Inhalt der „SharedWebconfig.config“ scheint unabhängig vom Exchange Server zu sein. Es hätte wahrscheinlich auch funktioniert, die Datei vom funktionierenden Exchange Server auf den defekten Exchange Server zu kopieren. Auf den ersten Blick konnte ich nur unterschiedliche Pfade feststellen, was allerdings Umgebungsbedingt ist:

However, I never tried it again. I was happy when it worked :-)