Upgrade to SQL Server 2019 Breaks Database Mail

Question

Upgrade to SQL Server 2019 Breaks Database Mail

SSC-Forever

Points: 42192

March 11, 2023 at 12:28 am

Long time since I've been on here. Anyway I have a test server that I recently upgraded from SQL Server 2014 to SQL Server 2019. Database Mail was working on 2014.

I have already been through the basics:

Database Mail XPs configuration setting is 1
Broker Enabled in MSDB is 1
sysmail_help_status_sp returns STARTED
no errors in sysmail_event_log
all e-mails since upgrade are stuck in sysmail_unsentitems, with no rows in sysmail_faileditems
have tried manually running sysmail_stop_sp then sysmail_start_sp
no errors in SQL Server log about this

The only clue I have been able to find is in the Windows event log I see the following:

1) Exception Information
===================
Exception Type: System.IO.FileNotFoundException
Message: Could not load file or assembly 'Microsoft.SqlServer.ConnectionInfo, Version=15.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
FileName: Microsoft.SqlServer.ConnectionInfo, Version=15.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91
FusionLog: WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

Data: System.Collections.ListDictionaryInternal
TargetSite: Void OpenConnection(System.String, System.String, System.String, System.String, System.String, Int32)
HelpLink: NULL
Source: DatabaseMailEngine
HResult: -2147024894

StackTrace Information
===================
   at Microsoft.SqlServer.Management.SqlIMail.Server.DataAccess.DataAccessAdapter.OpenConnection(String dbServerName, String dbName, String userName, String password, String appName, Int32 connectionTimeout)
   at Microsoft.SqlServer.Management.SqlIMail.IMailProcess.QueueItemProcesser.ProcessQueueItems(String dbName, String dbServerName, Int32

Unfortunately all references I can find for Microsoft.SqlServer.ConnectionInfo are for Visual Studio or PowerShell. Does anyone know what client library is missing here and where to get it?

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply

Site Owners SSC Guru Points: 80330 More actions · Answer 1

Thanks for posting your issue and hopefully someone will answer soon.

This is an automated bump to increase visibility of your question.

Chris Harshman SSC-Forever Points: 42192 More actions · Answer 2

So this weekend I ended up trying to do a repair on the shared components of 2019, but that didn't seem to do it. I ended up doing a repair on the 2019 instance itself and after that things seemed to start working again. I'm still not sure how the server got in this state, as there weren't any errors in logs from the upgrade itself. Oh well.