Skip to content

Add a Database Mail known issue #1996

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dimitri-furman wants to merge 2 commits into from
Closed

Add a Database Mail known issue #1996

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
258fb7c
Add a Database Mail known issue
dimitri-furman Jan 20, 2026
28dd0d6
Add details of the problem and mitigation
dimitri-furman Jan 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 13 additions & 1 deletion support/sql/releases/sqlserver-2022/cumulativeupdate23.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: Cumulative Update 23 for SQL Server 2022 (KB5074819)
description: This article contains the summary, known issues, improvements, fixes, and other information for SQL Server 2022 Cumulative Update 23 (KB5074819).
ms.date: 01/15/2026
ms.date: 01/20/2026
ms.update-cycle: 1095-days
ms.custom: sap:Installation, Patching, Upgrade, Uninstall, evergreen, KB5074819
ms.reviewer: v-shaywood
Expand All @@ -24,6 +24,18 @@ This article describes Cumulative Update package 23 (CU23) for Microsoft SQL Ser

## Known issues in this update

### Database Mail stops working after installing this cumulative update

Microsoft is aware of an issue where Database Mail stops working after this cumulative update is installed. When this occurs, you might see the following message:

```output
Could not load file or assembly 'Microsoft.SqlServer.DatabaseMail.XEvents, Version=17.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
```

While we are working on a fix, we ask that customers who use Database Mail avoid installing this update.

If you already installed this cumulative update, [uninstall](/sql/sql-server/install/uninstall-a-cumulative-update-from-sql-server) it to revert Database Mail to a working state.

### Incorrect behavior of SESSION_CONTEXT in parallel plans

[!INCLUDE [av-session-context](../includes/av-sesssion-context.md)]
Expand Down
14 changes: 13 additions & 1 deletion support/sql/releases/sqlserver-2025/cumulativeupdate1.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: Cumulative update 1 for SQL Server 2025 (KB5074901)
description: This article contains the summary, known issues, improvements, fixes, and other information for SQL Server 2025 Cumulative Update 1 (KB5074901).
ms.date: 01/15/2026
ms.date: 01/20/2026
ms.update-cycle: 1095-days
ms.custom: sap:Installation, Patching, Upgrade, Uninstall, evergreen, KB5074901
ms.reviewer: v-shaywood
Expand All @@ -24,6 +24,18 @@ This article describes Cumulative Update package 1 (CU1) for Microsoft SQL Serve

## Known issues in this update

### Database Mail stops working after installing this cumulative update

Microsoft is aware of an issue where Database Mail stops working after this cumulative update is installed. When this occurs, you might see the following message:

```output
Could not load file or assembly 'Microsoft.SqlServer.DatabaseMail.XEvents, Version=17.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
```

While we are working on a fix, we ask that customers who use Database Mail avoid installing this update.

If you already installed this cumulative update, [uninstall](/sql/sql-server/install/uninstall-a-cumulative-update-from-sql-server) it to revert Database Mail to a working state.

### Incorrect behavior of SESSION_CONTEXT in parallel plans

[!INCLUDE [av-session-context](../includes/av-sesssion-context.md)]
Expand Down