Exchange published calendar HTTP 500 errors started appearing on on-premises servers after the August 2026 security update. Anonymous calendar subscriptions that had worked for years suddenly stopped refreshing: the iPhone, Google Calendar or Thunderbird subscription shows a server error, and opening the calendar.ics link returns HTTP 500. Nothing is wrong with the mailbox or the sharing policy. Microsoft has confirmed the bug, shipped a fix, and documented a temporary workaround, and this guide walks through both.
What Microsoft Confirmed About the Exchange Published Calendar HTTP 500
Microsoft documents the problem in KB5126672, “Published calendar (.ics) returns HTTP 500 for calendar applications.” According to the article, after you install the August 2026 security update (Exchange Server SE build 15.2.2562.46), subscriptions to an anonymously published Exchange calendar stop refreshing, the subscribing application reports a server error, and the URL returns HTTP 500. The KB lists Exchange Server SE, Exchange Server 2019 and Exchange Server 2016 as affected products.
The Exchange team carried it as a known issue in the September 2026 V2 security update post with the note “to be resolved in a future update.” That future update is the October 2026 Exchange Server security update, released on October 13, 2026, which lists the issue under “Issues resolved in this release.”
The failure is not limited to the classic /owa/calendar/{id}/{token}/calendar.ics path. KB5126672 says the same problem also hits reachcalendar.ics and published schedule feeds, so any external party consuming a published Exchange calendar can be affected.
Symptoms of the Exchange Published Calendar HTTP 500
A published calendar not refreshing is usually the first thing users notice. The full pattern is easy to recognize once you know what to look for:
- Users report that a subscribed Exchange calendar on a phone or in a third-party calendar app has stopped updating, while the calendar itself looks fine in Outlook and OWA.
- The subscribing application shows a generic server error instead of new events.
- Requesting the
calendar.icsURL returns a 302 Found that redirects to/owa/calendar/auth/errorFE.aspx?httpCode=500. - The 302 response also sets an
OwaLightcookie. - The problem began right after the August 2026 SU (or a later SU released before October) was installed.
If the published calendar not refreshing complaint matches these points and the mailbox owner has not changed any sharing settings, you are looking at the Exchange published calendar HTTP 500 bug, not a permissions or certificate problem.
Why the Exchange Published Calendar HTTP 500 Happens
Microsoft’s KB does not include a formal cause section. What it does say is that the workaround “selects the supported code path” by forcing the premium layout on the request. Combined with the OwaLight cookie in the failing response, the practical reading is that requests from calendar applications are being routed to the light layout, which is no longer a supported path in current builds, and that path fails with an internal error. That is an interpretation of Microsoft’s documented behavior, not an official root-cause statement, but it explains why adding layout=premium to the query string makes the feed work again.

Step 1: Confirm the Exchange Published Calendar HTTP 500
The quickest way to confirm the Exchange published calendar HTTP 500 is to request the feed yourself. First, get the published URL for an affected calendar. From the Exchange Management Shell:
Get-MailboxCalendarFolder -Identity "jdoe:\Calendar" |
Select-Object Identity, PublishEnabled, DetailLevel, PublishedCalendarUrl, PublishedICalUrlCode language: JavaScript (javascript)Then test the PublishedICalUrl the same way Microsoft does in KB5126672, using a calendar-client user agent and showing only the response headers:
curl.exe -s -o NUL -D - -A "iOS/26.6.1 (23G83) dataaccessd/1.0" "https://mail.contoso.com/owa/calendar/{id}/{token}/calendar.ics"Code language: JavaScript (javascript)A broken server answers with HTTP/1.1 302 Found, a Location header pointing to errorFE.aspx?httpCode=500, and a Set-Cookie: OwaLight= header. Note that curl.exe is used deliberately: in Windows PowerShell 5.1, plain curl is an alias for Invoke-WebRequest.
Finally, check which Exchange build each server is running so you know whether the fix is already installed:
Get-Command Exsetup.exe | ForEach-Object { $_.FileVersionInfo }Code language: PHP (php)Step 2: Fix the Exchange Published Calendar HTTP 500 With the October SU
The supported fix is the Exchange October 2026 security update. Microsoft lists these packages as resolving the published calendar issue:
- KB5128895 for Exchange Server Subscription Edition RTM (SU11)
- KB5128896 for Exchange Server 2019 CU15
- KB5128897 for Exchange Server 2019 CU14
- KB5128898 for Exchange Server 2016 CU23
Two caveats. First, the Exchange 2016 and 2019 packages are only available to organizations enrolled in the Period 2 Extended Security Update program, and the October blog states that October 2026 is the last month new security updates ship for those versions. From here on, only Exchange SE receives updates. Second, run the Exchange Health Checker before and after patching, and reboot the server once setup completes, as Microsoft recommends for every SU.
Also be aware of the separate October 2026 Windows Server update problem that can destabilize Exchange. It is unrelated to the Exchange SU, but if you are patching both at once, read our guide on Exchange OWA not working after the October 2026 updates first.

Step 3: Exchange Published Calendar HTTP 500 Workaround With URL Rewrite
If you cannot install the October SU immediately, KB5126672 documents a workaround: a single IIS URL Rewrite inbound rule that appends layout=premium to published calendar requests. Apply it on the Exchange Back End site only, not on Default Web Site and not at server level.
Check for the URL Rewrite module first
Exchange Setup does not install the IIS URL Rewrite module. Many Exchange servers already have it because the Exchange Emergency Mitigation Service depends on it, but confirm before you touch any configuration:
Test-Path "$env:windir\System32\inetsrv\rewrite.dll"Code language: JavaScript (javascript)If this returns False, install the module first. Microsoft warns that adding a rewrite section without the module causes HTTP 500.19 for the entire Exchange Back End site, which takes down far more than published calendars.
Option A: Create the rule in IIS Manager
- Open IIS Manager, expand Sites and select Exchange Back End.
- Open URL Rewrite and choose Add Rule(s) > Blank rule.
- Name it
OWA published calendar force premium layout. - Set the pattern to
^owa/calendar/.+\.ics$using regular expressions, with Ignore case enabled. - Add a condition: input
{QUERY_STRING}, type Does Not Match the Pattern, pattern(^|&)layout=. - Set the action to Rewrite, URL
{R:0}?layout=premium&{QUERY_STRING}, clear Append query string, and select Stop processing of subsequent rules. - Apply the rule. No application pool recycle is needed.
Depending on feature delegation, IIS Manager may write the rule either to applicationHost.config or to %ExchangeInstallPath%\ClientAccess\web.config. Remember that for rollback later.
Option B: Edit applicationHost.config directly
Back up the file first:
Copy-Item C:\Windows\System32\inetsrv\config\applicationHost.config "C:\Windows\System32\inetsrv\config\applicationHost.config.bak-$(Get-Date -f yyyyMMdd-HHmmss)"Code language: JavaScript (javascript)Then, inside <location path="Exchange Back End"> and its <system.webServer> element, add the rule exactly as Microsoft publishes it:
<rewrite>
<rules>
<rule name="OWA published calendar force premium layout" stopProcessing="true">
<match url="^owa/calendar/.+\.ics$" />
<conditions>
<add input="{QUERY_STRING}" pattern="(^|&)layout=" negate="true" />
</conditions>
<action type="Rewrite" url="{R:0}?layout=premium&{QUERY_STRING}" appendQueryString="false" />
</rule>
</rules>
</rewrite>Code language: HTML, XML (xml)Two details matter. Keep appendQueryString="false", because the action URL already carries the original query string. And write the ampersand as &: a literal & in the XML breaks the file and returns HTTP 500.19 for the whole site.
Apply the rule on every server that serves published calendars. If only some servers behind a load balancer have it, users will see intermittent HTTP 500 errors depending on which server answers.
Step 4: Verify the Exchange Published Calendar HTTP 500 Is Gone
Repeat the header test from Step 1:
curl.exe -s -o NUL -D - -A "iOS/26.6.1 (23G83) dataaccessd/1.0" "https://mail.contoso.com/owa/calendar/{id}/{token}/calendar.ics"Code language: JavaScript (javascript)A healthy server returns HTTP/1.1 200 OK with Content-Type: text/calendar; charset=utf-8, and there is no Set-Cookie: OwaLight= header. To check the body, drop the header switches; a working feed begins with BEGIN:VCALENDAR:
curl.exe -s -A "iOS/26.6.1 (23G83) dataaccessd/1.0" "https://mail.contoso.com/owa/calendar/{id}/{token}/calendar.ics"Code language: JavaScript (javascript)If you used the workaround, confirm where the rule lives:
& "$env:windir\System32\inetsrv\appcmd.exe" list config "Exchange Back End" -section:system.webServer/rewrite/rules
Select-String -Path "$env:windir\System32\inetsrv\config\applicationHost.config" -Pattern 'OWA published calendar'
Select-String -Path "$env:ExchangeInstallPath\ClientAccess\web.config" -Pattern 'OWA published calendar' -ErrorAction SilentlyContinueCode language: JavaScript (javascript)Subscribed clients refresh on their own schedule, so a phone may take a while to pull new events even after the URL returns 200.

Remove the Workaround After Patching
Once the Exchange October 2026 security update is installed, Microsoft says to remove the workaround. Delete the rule in IIS Manager, or remove the <rewrite> block from whichever file holds it. Check both applicationHost.config and %ExchangeInstallPath%\ClientAccess\web.config, because a leftover copy in either file keeps the rewrite active. No restart is required.
Even if you keep the rule for a while, recheck it after every CU and SU. Microsoft notes the configuration is not guaranteed to survive updates, so an Exchange published calendar HTTP 500 can return quietly after the next patch cycle if you rely on the rewrite instead of the fix.
Prevent the Next Exchange Published Calendar HTTP 500
- Keep a test subscription to a published calendar and run the curl check after every Exchange update, alongside the Health Checker.
- Track the “Known issues” section of each Exchange SU announcement before rolling out to all servers.
- Document which servers sit behind the load balancer for
/owa, so server-specific fixes are applied everywhere. - If you are still on Exchange 2016 or 2019, plan the move to Exchange SE now, since they no longer receive new security updates. Our guide to patching CVE-2026-96940 safely covers a safe patch order.
Read more: Best Fix Missing Teams Calendar Issue in Exchange On-Premises
Read more: How to Fix Outlook Search Not Updating in Shared Mailboxes
Why does my Exchange published calendar return HTTP 500?
The Exchange published calendar HTTP 500 is a confirmed bug. Microsoft documents in KB5126672 that after the August 2026 Exchange security update, anonymously published calendars can return HTTP 500 to calendar applications. The request is redirected to errorFE.aspx?httpCode=500 and the subscription stops refreshing.
Which update fixes the published calendar HTTP 500?
The Exchange October 2026 security update fixes it: KB5128895 for Exchange SE RTM, KB5128896 for Exchange 2019 CU15, KB5128897 for Exchange 2019 CU14 and KB5128898 for Exchange 2016 CU23.
What does the layout=premium workaround do?
It is an IIS URL Rewrite rule on the Exchange Back End site that appends layout=premium to .ics requests under /owa/calendar, which Microsoft says selects the supported code path. It requires the IIS URL Rewrite module.
Do I need to remove the URL Rewrite rule after patching?
Yes. Microsoft says to remove the workaround after installing the fix. Check both applicationHost.config and the ClientAccess web.config, because a leftover rule in either file keeps the rewrite active.
Why do I still see an Exchange published calendar HTTP 500 after the fix?
Usually because not every server behind the load balancer has the October SU or the rewrite rule. Apply the fix on every server that serves /owa, then retest with curl.exe against each server.
References
Microsoft Support: KB5126672: Published calendar (.ics) returns HTTP 500 for calendar applications
Microsoft Exchange Team: Released: October 2026 Exchange Server Security Updates
Microsoft Exchange Team: Released: September 2026 V2 Exchange Server Security Updates
Microsoft Support: Security update for Exchange Server SE RTM, October 13, 2026 (KB5128895)
Microsoft: Exchange Server Health Checker




