Event ID 1310 ASP .NET 4.0.30319.0

Question

Yesterday, I installed MS Exchange 2019 cu4 on my ML350G6 server with 144 GB ram and more than ample drive space

The installation proceeded without any errors or problems. During the installation, all of the default settings were accepted.

Problem, after the install, when I attempt to log into the EAC (Exchange Admin Center) via a web browser, I get the login page requesting "Domain\username:" and "Password:" I enter the domain administrator's credentials and receive the following:

This page isn't working right now<server name> can't currently handle this request
HTTP ERROR 500

All required MS Exchange services that are set to automatic, they are running. I have rebooted the server several times to restart the services. Everything appears to be running but I am unable to login to the EAC and continue configuring the Exchange Server:

The only error I receive in the event log is: Event ID 1310 ASP .NET 4.0.30319.0 and this error occurs each time I attempt to login into the EAC. The following is the entire event log information:

Event code: 3008
Event message: A configuration error has occurred.
Event time: 12/11/2020 8:44:37 AM
Event time (UTC): 12/11/2020 1:44:37 PM
Event ID: 624a64a529454065bfb0469a84be769d
Event sequence: 1
Event occurrence: 1
Event detail code: 0

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

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

Exception information:
Exception type: ConfigurationErrorsException
Exception message: Could not load file or assembly 'Microsoft.Search.Platform.Parallax, Version=2.21.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. (C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\web.config line 134)
at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective)
at System.Web.Configuration.CompilationSection.LoadAssembly(AssemblyInfo ai)
at System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig)
at System.Web.Compilation.BuildManager.GetPreStartInitMethodsFromReferencedAssemblies()
at System.Web.Compilation.BuildManager.CallPreStartInitMethods(String preStartInitListPath, Boolean& isRefAssemblyLoaded)
at System.Web.Compilation.BuildManager.ExecutePreAppStart()
at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException)

Could not load file or assembly 'Microsoft.Search.Platform.Parallax, Version=2.21.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)
at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.Load(String assemblyString)
at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective)

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

Thread information:
Thread ID: 85
Thread account name: NT AUTHORITY\SYSTEM
Is impersonating: False
Stack trace: at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective)
at System.Web.Configuration.CompilationSection.LoadAssembly(AssemblyInfo ai)
at System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig)
at System.Web.Compilation.BuildManager.GetPreStartInitMethodsFromReferencedAssemblies()
at System.Web.Compilation.BuildManager.CallPreStartInitMethods(String preStartInitListPath, Boolean& isRefAssemblyLoaded)
at System.Web.Compilation.BuildManager.ExecutePreAppStart()

at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException)

During the installation of the Exchange software, I was notified that .NET Framework 4.8 was required to continue, so I clicked on the download link and installed it.

If any suggested answer involves IIS, please note that I know very little about this management application

I did check the Bindings and each of them have the Microsoft Exchange certificate

I have run "iisreset /noforce" a few times with no change to my problem

The Domain Administrator has the required permissions for all Exchange services.

I have searched the forum to locate any similar posts, and have attempted to follow the suggested solutions, thus far, none have worked or I didn't understand the individual steps that were recommended.

If anyone request additional information that may be required to troubleshoot my problem, please be specific in the steps necessary to obtain the information.

Thank you and I look forward to any replies.

Answer 1

UPDATE. It is now working. I'm not certain what changed or what happened that it began to work.
Here is what I know:

• Security Update for Exchange Server 2019 CU4 (KB4540123) was installed through Windows Update.
• Since the Administrator account would not login, I elevated another AD account with full rights as administrator
• I ensured that all of the Bindings in IIS had the Microsoft Exchange certificate
• After the Exchange patch was installed, I rebooted the server
• I attempted to log in with the other elevated AD account
• Success, I was able to successfully log in

Once I was in to the EAC, I finished the configuration for the install, created a new Mailbox Database, Deleted the Administrator's mailbox and created a new mailbox in the new database.

Everything appears to be working just fine. I'm able to send and receive internal messages between different AD users.

My next steps are to open the firewall ports so that I can send and receive external message.

What changed, or what steps were performed that corrected the problem? I'm not certain.
Something I found was that after successfully login in to the EAC, an error popped up that a database could not be found. I did some further searching and discovered that from a previous install of Exchange back in 2016, a mailbox database still existed in ADSI edit. I deleted that database from ADSI edit and ensured that no old Exchange attributes still existed. I'm guessing that maybe the Administrator's account, when I installed the 2019 version of Exchange, the Admin mailbox was put in the old and non-existent database. This is all guessing as I'm not sure.

Anyway, everything is now working just fine.

Thank you, every one.

Answer 2

Hi,

Please find the below suggestions,

1.Try running UpdateCas.PS1 -> In EMS, got to BIN directory and run the script
2.Check if the Exchange backend website has the certificate - > go to IIS -> Expand Sites -> Exchange Backend -> Click on Bindings on right side -> https 444 -> Check if it has the certificate with name "Microsoft Exchange"
3.Check if the below files are located in appropriate location, if not copy it to the below location and run IISReset

Filename: SharedWebConfig.config

%ExchangeInstalledDrive%:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy
%ExchangeInstalledDrive%:\Program Files\Microsoft\Exchange Server\V15\ClientAccess

If the above suggestion helps, please click on "Accept Answer" and upvote it

Answer 3

I ran the UpdateCas.PS1 script. It ran successfully.

I checked the specified files and found them in the locations you mentioned.

I checked the certificate for the https 444 bindings and the Microsoft Exchange certificate was assigned to that binding.

When I attempted again to login to the EAC, it failed and I received the same error message.

On a side note, yesterday I noticed that a remnant of an old Exchange server from back in 2016 was found in ADSI edit. I removed that old server from ADSI Edit.

No joy in Mudville. Does anyone have another suggestion? Or are there additional checks to be made?

Let me know. Thanks.

Answer 4

Hi,

Please try the below steps,

1.Open IIS Manager. Expand Sites > Exchange Back End.
2.Click ecp. Open Application Settings in /ecp Home.
3.Please check whether the value for “BinSearchFolders” is changed to an invalid value. If so, please change it to:
C:\Program Files\Microsoft\Exchange Server\V15\bin;C:\Program Files\Microsoft\Exchange Server\V15\bin\CmdletExtensionAgents;C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\bin
4.Open Web.config file for OWA in the default path C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa. If there is any %ExchangeInstallDir% in the web.config content, replace all of them with C:\Program Files\Microsoft\Exchange Server\V15.
5.Please check the web.config file for ECP in Exchange back end and confim if there is any %ExchangeInstallDir% in the web.config content. If that is the case, please replace all of %ExchangeInstallPath% to c:\programfiles\Microsoft\Exchange Server\V15\Bin.
6.Run IISReset command to restart IIS services.
7.If issue still persists, run UpdateCas.PS1 and UpdateConfigFiles.ps1

If the above suggestion helps, please click on "Accept Answer" and upvote it

https://social.technet.microsoft.com/Forums/en-US/7e8e2c4e-f6fe-493f-9d29-44aeab398b74/exchange-2019-ecp-url-is-not-loading-and-gives-error?forum=Exch2019

Answer 5

Hi,

1. Is the path correct in IIS?
   
2. Check the web file in this path, can you find the line 134 it mentioned?
3. Check if this file exist in you server, here is its location:
   

---

If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.