Exchange Connection Problems

Fix Cannot Access OWA or ECP on a Second Exchange Server

WPS Content Manager Sep 25, 2026 869 views

Question details

The user is unable to access Outlook on the web (OWA) or the Exchange Admin Center (ECP) via the private address of a second Exchange 2019 server, following a .NET Framework update.

How to Fix OWA and ECP Access Issues on a Second Exchange Server

Product: Exchange Server 2019
Device & OS: Windows Server 2019
Scenario: Attempting to access OWA, ECP, and active mailboxes after rolling back the August 2024 cumulative update for .NET Framework.
Observed behavior: The first server functions normally, but on the second server, OWA, ECP, and mailboxes remain completely inaccessible despite Exchange services and IIS appearing to run.

Before you start

Ensure you have administrative privileges to the Exchange Server, and verify that all Exchange-related services are actively running in the Windows Services console before modifying configurations.

Solution 1Recommended

Clear Browser Cache and Test via Incognito Mode

Corrupted browser data or cached credentials can simulate server-side connection failures, so it is important to rule out client-side issues first.

Before diving into complex server diagnostics, ensure the web interface failure is not simply a browser caching issue, which is common when server backend configurations change.

Open Clear Browsing Data Options

Launch your web browser and press Ctrl+Shift+Del to quickly open the cache clearing menu.

Wipe Cache and Cookies

Select 'All time' as the time range, ensure 'Cached images and files' and 'Cookies and other site data' are checked, and click 'Clear data'.

Test Using an InPrivate Window

Open a new Incognito (Chrome) or InPrivate (Edge) window and navigate to the OWA or ECP private address. Attempt to sign in to verify if access is restored.

Clear Browser Cache and Test via Incognito Mode

Client-Side Verification: If you can log in successfully via Incognito mode, the problem was localized to your browser cache, and the Exchange Server is functioning properly.

Solution 2

Review Exchange Event Logs for .NET Impact

Because the outage started after a .NET Framework cumulative update, checking the Event Viewer can identify silent service or application pool failures.

Solution 3

Consult Microsoft Exchange Server Communities

For complex on-premises issues where standard troubleshooting yields no event log errors, escalating to specialized Exchange communities is highly recommended.

Free Microsoft Office alternative

Need a Reliable and Lightweight Office Suite Alternative?

While resolving complex Exchange Server web access issues, you shouldn't let it slow down your daily document productivity. WPS Office is a highly compatible, fast, and free alternative to Microsoft Office that doesn't require heavy infrastructure maintenance.

1. Download the Installer: Visit the official WPS Office website and download the free installation package.
2. Run Setup: Execute the downloaded file and follow the quick on-screen instructions to install the suite.
3. Open Your Documents: Launch WPS Office and instantly open your existing Microsoft Office files without needing any conversions.

Fully compatible with Microsoft Word, Excel, and PowerPoint formats (.docx, .xlsx, .pptx)Lightweight desktop client with low system resource consumptionFree to use with a familiar, easy-to-navigate tabbed interfaceExcellent offline performance without relying on web-based Exchange servers

microsoft office alternative - wps office

Frequently Asked Questions

Why did a .NET Framework update break my OWA and ECP access?

Exchange Server relies heavily on IIS and the .NET Framework to run its web components. Certain .NET cumulative updates can alter security configurations, break application pools, or cause version mismatches that prevent OWA and ECP from loading correctly.

How can I verify if my OWA virtual directories are configured correctly?

You can open the Exchange Management Shell (EMS) on the affected server and run the command 'Get-OwaVirtualDirectory | Format-List'. This will display the InternalUrl and ExternalUrl to ensure they are pointing to the correct address.

What should I do if IIS is running but I still get an error on the OWA page?

Try manually recycling the specific application pools in IIS. Open IIS Manager, navigate to Application Pools, right-click on 'MSExchangeOWAAppPool' and 'MSExchangeECPAppPool', and select 'Recycle'. Alternatively, open an elevated command prompt and type 'iisreset' to restart all web services.

Outlook & Email Problems