Exchange 2019 Admin Center Not Opening

Bernard Grieshaber 1 Reputation point
2023-01-06T12:40:25.727+00:00

One of our clients Exchange 2019 server is not opening exchange admin center after logging in; it just spins. It is running on Windows Server 2019 Standard and is an on-premise server. Server is up to date on all Windows and exchange (CU12 15.2.1118.20) updates. I am seeing errors Event ID 5139 WAS source in system log and Event ID 2280 IIS-W2SVC source in application log (details of these are listed below). I have removed and recreated the OWA & ECP virtual directories, Checked the bindings on default website and backend which both are correct, and ran SFC repair. I did find another article that suggested removing DynamicCompressionModule from applicationhost.config file which did stop the above errors from occurring but also stopped all email from being received or sent. I have compared this with another client's Exchange server and cannot find anything out of place. I appreciate any and all help.
Log Name: System
Source: Microsoft-Windows-WAS
Date: 1/6/2023 6:03:09 AM
Event ID: 5139
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: BN-MAIL-2019.cityofbn.com
Description:
A listener channel for protocol 'http' in worker process '28652' serving application pool 'DefaultAppPool' reported a listener channel failure. The data field contains the error number.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WAS" Guid="{524B5D04-133C-4A62-8362-64E8EDB9CE40}" EventSourceName="WAS" />
<EventID Qualifiers="32768">5139</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2023-01-06T12:03:09.517096100Z" />
<EventRecordID>624506</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>BN-MAIL-2019.cityofbn.com</Computer>
<Security />
</System>
<EventData>
<Data Name="AppPoolID">DefaultAppPool</Data>
<Data Name="ProcessID">28652</Data>
<Data Name="param3">0</Data>
<Data Name="ProtocolID">http</Data>
<Binary>05000780</Binary>
</EventData>
</Event>
Log Name: Application
Source: Microsoft-Windows-IIS-W3SVC-WP
Date: 1/6/2023 6:31:17 AM
Event ID: 2280
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: BN-MAIL-2019.cityofbn.com
Description:
The Module DLL E:\MSExchange2019\ClientAccess\Owa\auth\exppw.dll failed to load. The data is the error.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-IIS-W3SVC-WP" Guid="{670080D9-742A-4187-8D16-41143D1290BD}" EventSourceName="W3SVC-WP" />
<EventID Qualifiers="49152">2280</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2023-01-06T12:31:17.412174600Z" />
<EventRecordID>5620139</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>BN-MAIL-2019.cityofbn.com</Computer>
<Security />
</System>
<EventData>
<Data Name="ModuleDll">E:\MSExchange2019\ClientAccess\Owa\auth\exppw.dll</Data>
<Binary>05000000</Binary>
</EventData>
</Event>

Exchange Server
Exchange Server
A family of Microsoft client/server messaging and collaboration software.
1,173 questions
Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,467 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Aholic Liang-MSFT 13,826 Reputation points Microsoft Vendor
    2023-01-09T06:26:35.2+00:00

    Hi @Bernard Grieshaber ，

    I did find another article that suggested removing DynamicCompressionModule from applicationhost.config file which did stop the above errors from occurring but also stopped all email from being received or sent.

    Was the module backed up before it was removed? If possible ,please recover the module you deleted first.
    Then please refer to the following steps to try to resolve the error ID 2880：

    1. Remove the exppw.dll entry from applicationhost.cofig (c:\windows\system32\inetsrv\config)
      Note: Remember take a backup before you remove the line.
    2. Then registered the exppw.dll by following the below steps:
    3. IIS Manager -> Select the Server Name in the left Pane -> Open Modules in the middle pane.
    4. Click on ‘Configure Native Modules’ in the right pane -> Click the button ‘Register’ -> Type the name as ‘exppw’
    5. Browse and select the path of above file as:E:\MSExchange2019\ClientAccess\Owa\auth\exppw.dll
    6. Made sure that the 'exppw.dll' is only present at OWA level and not at any of the top heirarchy.
    7. Then ensured for this module in OWA (VDir), ‘Module Type’ is set to ‘Native’ and ‘Entry Type’ is ‘Local’
    8. Run IISreset /noforce

    Here is a similar thread for you reference : The Module DLL C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Owa\auth\exppw.dll failed to load

    Hope this helps!

    (Note: Microsoft provides third-party contact information to help you find additional information about this topic. This contact information may change without notice. Microsoft does not guarantee the accuracy of third-party contact information.)

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    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.

  2. Amit Singh 4,866 Reputation points
    2023-01-09T09:33:58.737+00:00

    Try to Stop and restart the application pool. Application pools occasionally need to be restarted in order to return to normal operation. Because application pools depend on the Windows Process Activation Service (WAS), you may have to restart WAS. If you restart WAS, you may also have to restart the World Wide Web Publishing Service (W3SVC), which depends on WAS.

    0 comments