Microsoft.Data.SqlClient is upgraded to 5.1.5

Prithivirajan Anbalagan 0

I have upgraded Microsoft.Data.SqlClient to version 5.1.5 and deployed it on the server. However, the application encountered an error stating "Could not load file or assembly 'Microsoft.Data.SqlClient, Version=1.0.19239.1'". I have checked for Microsoft.Data.SqlClient version on the server in the bin folder, GAC path, and Asp Net temp folder, and confirmed that the available version is 5.1.5. Despite this, the application is still trying to find the older version specified as 1.0.19239.1.

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
jehan 0 Reputation points

2024-08-13T15:02:31.45+00:00

It sounds like the application is referencing an older version of the library. Check your project files (like app.config or web.config) for binding redirects or specific version references that might still be pointing to the older version.
Prithivirajan Anbalagan 0 Reputation points

2024-08-14T07:29:46.58+00:00

I ran the command "Get-Project –All | Add-BindingRedirect" in the nuget console to resolve version conflicts in both the app.config and web.config files. However, the issue still persists and encounter from hosted server and not from my local machine. Please review the following error that I received from the application.

Message: Could not load file or assembly 'Microsoft.Data.SqlClient, Version=1.0.19239.1, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) FileName: Microsoft.Data.SqlClient, Version=1.0.19239.1, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5

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].

StackTrace Information *********************************************

at Microsoft.Extensions.Caching.SqlServer.DatabaseOperations.DeleteCacheItem(String key)

at Microsoft.Extensions.Caching.SqlServer.SqlServerCache.Remove(String key)

2 answers

Michael Taylor 54,806 Reputation points

2024-08-09T16:12:17.4566667+00:00

Sounds like you have a dependency that is looking for SqlClient v1.0. You didn't mention the type of app you're having. I assume it is a web app but not sure whether you're using NET Framework or NET 6/8. For NET Framework look in your web.config file and ensure you have a binding redirect for SqlClient that points to the 5.1.5 version. This will resolve the issue.

For NET 6/8 the binding redirect should not be an issue.

Ensure all your dependencies have been updated as well. Furthermore use the Consolidation tab in NuGet Package Manager UX for the solution to ensure you don't have any version conflicts.
Please sign in to rate this answer.
Prithivirajan Anbalagan 0 Reputation points

2024-08-12T13:03:25.6833333+00:00

I have ensured that all dependencies are updated from my side. I am using targetFramework="4.8" in my ASP.NET web forms application. I need an answer at the server level.

Michael Taylor 54,806 Reputation points

2024-08-12T14:21:45.47+00:00

This is not a server issue, it is an app issue. Your app, somewhere, has a dependency on an old version of SqlClient. Your app is trying to use the newer version but the runtime will fail the call because you cannot do that. The runtime requires that the exact version you said you needed when you built the code is available. No other (major/minor/patch) version will work as this could be an attempt to inject malicious code. The workaround is to use a binding redirect in your configuration.

Please refer to my earlier questions about the type of app and framework you're targeting. If you're using a .config file then you need to insert a binding redirect into it and then your problem will go away.

<runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="Microsoft.Data.SqlClient" publicKeyToken="23ec7fc2d6eaa4a5" culture="en-us" /> <bindingRedirect oldVersion="1.0.0.0-5.1.5.0" newVersion="5.1.5.0" /> </dependentAssembly> </assemblyBinding> </runtime>

The above, in your config, tells the runtime that if it finds any load requests for Microsoft.Data.SqlClient and versions between 1.0.0 and 5.1.5 then it should use 5.1.5 which is the version your app is shipping with.

Prithivirajan Anbalagan 0 Reputation points

2024-08-12T14:54:49.2333333+00:00

In my web.config file, I found the following binding redirects. Is this correct? If not, please provide the correct binding redirects tag.

<dependentAssembly> <assemblyIdentity name="Microsoft.Data.SqlClient" publicKeyToken="23ec7fc2d6eaa4a5" culture="neutral" /> <bindingRedirect oldVersion="0.0.0.0-5.0.0.0" newVersion="5.0.0.0" /> </dependentAssembly>

Michael Taylor 54,806 Reputation points

2024-08-12T15:02:52.8366667+00:00

Close. It hasn't been updated for 5.1.5. Change the oldVersion and newVersion strings to be 5.1.5.0 as I showed in my previous comment. Then the runtime will redirect any requests to the 5.1.5 version which is what you said you're using now. You can confirm that by looking in the properties for the DLL and looking at the product version (only major/minor/patch matter here).

Prithivirajan Anbalagan 0 Reputation points

2024-08-12T15:58:53.0833333+00:00

Full name of Microsoft.Data.SqlClient 5.1.5 is "Microsoft.Data.SqlClient, Version=5.0.0.0, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5"

Michael Taylor 54,806 Reputation points

2024-08-12T16:10:11.13+00:00

You are correct, the Nuget version 5.1.5 matches the 5.0.0 version of the assembly. So the binding redirect should reference 1.0.0.0-5.0.0.0 and new version should be 5.0.0.0.

Prithivirajan Anbalagan 0 Reputation points

2024-08-13T11:05:28.09+00:00

I updated the dependent assembly tag in my web.config file, but the issue persists in the hosted application. Please review the following error I received from the application.

Message: Could not load file or assembly 'Microsoft.Data.SqlClient, Version=1.0.19239.1, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) FileName: Microsoft.Data.SqlClient, Version=1.0.19239.1, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5

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].

StackTrace Information *********************************************

at Microsoft.Extensions.Caching.SqlServer.DatabaseOperations.DeleteCacheItem(String key)

at Microsoft.Extensions.Caching.SqlServer.SqlServerCache.Remove(String key)

Michael Taylor 54,806 Reputation points

2024-08-14T14:27:05.5133333+00:00

Please post the config file you're using with the appsettings/connectionstrings removed for privacy reasons.

Also PLEASE provide us the actual framework information that we've asked for before. You still haven't, I believe, clarified exactly what type of app(s) you're running here (MVC, web forms, winforms, etc) nor what actual framework version(s) you're targeting. Please provide us this information so we can stop guessing.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Prithivirajan Anbalagan 0 Reputation points

2024-08-23T08:38:00.97+00:00

I have attached the web.config file to resolve my issue.WebConfig.txt
Please sign in to rate this answer.
Michael Taylor 54,806 Reputation points

2024-08-23T13:58:52.0366667+00:00

Interesting. You have a probe path defined. I wonder if this is ultimately what is causing your issue. Do you really need that? In general the bin directory is your output directory and the runtime already searches there. However the custom\bin means you have a subfolder called custom\bin where it will also look. Ensure you don't have the file in there as well. Ideally you should modify your build process to copy any binaries you need into the output directory of your project at build time. Then you can eliminate the probe path.

The next thing I notice is that you seem to have a mix of assemblies going on it. This isn't causing your problem but is potentially getting in the way. I notice you have DevExpress controls in your assemblies list. If you are not using DevExpress then remove them. If you are then you can leave it but ensure that this version information is updated to match what you're using. I also notice you have Telerik in your assembly bindings. It would be odd to be using both Telerik and DevExpress in the same codebase. Ensure you need this as well. More importantly you have duplicate assemblies listed in your assemblies list. For example DevExpress.Web, DevExpress.Data and System.Design are listed twice. Clean up this list so you only have 1 entry per assembly.

I also see you have both Microsoft.ReportViewer.WinForms and Microsoft.ReportViewer.WebForms listed. You can't use Winforms in a web app so you can remove this altogether.

Jiale Xue - MSFT 46,376 Reputation points Microsoft Vendor

2024-08-28T09:56:50.3966667+00:00

Is there any update in this issue?

Prithivirajan Anbalagan 0 Reputation points

2024-08-28T12:06:04.2866667+00:00

Please provide a solution for Microsoft.Data.SqlClient-5.1.5

Jiale Xue - MSFT 46,376 Reputation points Microsoft Vendor

2024-09-02T02:53:40.79+00:00

Is your answer above the current solution? You don't seem to have answered Michael Taylor's question.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Microsoft.Data.SqlClient is upgraded to 5.1.5

2 answers

Your answer