Note: We have learned that customers using Exchange Server 2013 and Exchange Server 2007 co-existence can experience an issue causing Exchange Server 2013 CU6 databases to failover. Please refer to...
Updated Jul 01, 2019
Version 2.0
Blog Post
I've had the following problem on a number of fresh build 2012R2 servers with greenfield installs of 2013 CU6 in freshly built domains with 2012R2 DCs:
After install you get the event 1310 from source "asp.net 4.0.30319.0" logged many times, each complaining that DLLs could not be loaded for each of the virtual directories as "the file specified could not be found". OWA and ECP wouldn't load and just returned
the "something went wrong :-(" page.
After a couple of days of investigation it seems that the sharedwebconfig.config file hadn't been created. All the web.config files in each of the virtual directories were trying to load modules, like antixss, but the server didn't know where to find them as
the paths to these files are now stored in the sharedwebconfig.config file, which for some reasons wasn't created on each of my servers experiencing the problem.
Looking at CU5 an earlier servers, each of the web.config files have full paths to the DLLs. It therefore seems that CU6 has transitioned to a "shared config" approach rather than repeating all the paths in every web.config. Once I found a working CU6 server
I just copied the sharedwebconfig.config file from c:program filesMicrosoftexchange serverv15clientaccess, did an IISRESET and everything started working.