SQL Server Blog Post

Troubleshooting

SQL Server Case of the Week: Log Shipping Fails on SQL Server 2025 When the Binaries Aren’t on C:\

Written by Sandra Delany

November 20, 2026

Quick Summary

The log shipping restore job will fail on SQL Server 2025 if the SQL Server binaries were installed on any drive other than the C:\ drive.

Context

A client had SQL Server 2025 installed for a migration. I set up log shipping, and the restore job failed. The backup and copy jobs on the source server were fine. Only the restore job failed.

The Problem

After setting up log shipping, the restore job failed with this error:

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly ‘Microsoft.SqlServer.ConnectionInfo, Version=17.100.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91’ or one of its dependencies. The system cannot find the file specified…at Microsoft.SqlServer.Management.LogShipping.LogShipping.Main(String[] args)

I’ve set up log shipping dozens (maybe hundreds) times, and I’ve never seen this error.

The Investigation

Like the error said, log shipping wanted assembly version 17.100.0.0, but the only version I could find registered was 17.0.0.0.

My first thought was that something was out of date, so I installed the latest cumulative update and the latest version of SSMS 22. That did not fix it.

I used PowerShell to look for Microsoft.SqlServer.ConnectionInfo.dll under C:\Program Files\Microsoft SQL Server\170. It was there, version 17.100.94.0, in the Setup Bootstrap\SQL2025\x64 folder. I also checked which versions of the SMO assemblies existed in the GAC. They were there too, but they were not being loaded.

The files existed, but log shipping could not find them. Why not?

I brought in coworkers, Buck Woody and Mike Lynn. Buck did some research. His findings point to sqllogship.exe.config. SQL Server 2025 appears to have bumped the SMO and ConnectionInfo assembly versions to 17.100.0.0, and the config file seems to resolve the DLL locations relative to the install path. That would explain why a non-default install drive causes problems.

Buck also found a possible alternative: edit sqllogship.exe.config, located in <SQL_Install_Dir>\170\Tools\Binn, and add an assembly binding redirect from version 17.100.0.0 to 17.0.0.0. I did not try this one, since changing that config file could introduce other issues.

The Fix

Mike found the fix. Copy the MDS5xSMO folder from the C: drive to the same path on the drive where the binaries are installed:

From: C:\Program Files\Microsoft SQL Server\170\Shared\MDS5xSMO
To: H:\Program Files\Microsoft SQL Server\170\Shared\MDS5xSMO

We had to create the Shared directory on the H:\ drive first, then copy just that folder. This worked because H:\ is where the SQL Server binaries were installed for that instance.

Lesson/Takeaway

  1. Check where the binaries are installed. If SQL Server 2025 binaries are not on the C:\ drive and log shipping restore fails with a missing Microsoft.SqlServer.ConnectionInfo 17.100.0.0 error, copying the MDS5xSMO folder to the matching path on the binaries drive fixed it for me.
  2. Patching did not fix this. Installing the latest CU and the latest SSMS did not resolve the error.
  3. I did not find any Microsoft documentation on this issue. Hopefully this saves you some time.

The Straight Path Team and Skills

This case shows one of many reasons why database migrations can experience unexpected issues. If you are considering upgrading your version of SQL Server, the Straight Path team can help make the migration as painless and cost-effective as possible.


Straight Path Solutions is a team of nearly 20 SQL Server experts trusted by 120+ clients. We treat our clients’ environments as if they were our own because our job depends on your success. Making your life pain-free in the land of SQL is the rewarding part of our work. If you’re planning a migration, dealing with backup concerns, or just want to sleep better knowing someone’s watching your environment, reach out to us.

This post is part of our Case of the Week series, real SQL Server issues and lessons from the field.


Sign Up for Updates

Sign up for our newsletter to receive updates about new blog posts, webinars, DBA tools, and more.

Privacy Policy

Leave a Comment

NOTICE: By posting a comment, you agree to this website's Terms of Service.