“SqlStoreConnection … method not found” when running Get‑DbaSsisEnvironmentVariable / New‑DbaSsisCatalog on dbatools 2.5.1

[SylvainDuran]

Hi team 👋

I’m bumping into a quirky error and could really use your collective wisdom.

What I’m doing

Import-Module dbatools -MinimumVersion 2.5.1
Get-DbaSsisEnvironmentVariable -SqlInstance <MyServer>
# or
New-DbaSsisCatalog -SqlInstance <MyServer> -SecurePassword $SecurePassword

What happens

WARNING: [10:30:37][Get-DbaSsisEnvironmentVariable] Can't load server |
Method not found:
'Void Microsoft.SqlServer.Management.Sdk.Sfc.SqlStoreConnection..ctor(System.Data.SqlClient.SqlConnection)'

What I’ve checked so far

The error seems to be triggered by the following line in the dbatools source (Get-DbaSsisEnvironmentVariable.ps1):

$ssis = New-Object Microsoft.SqlServer.Management.IntegrationServices.IntegrationServices $sqlconnection

• Loaded assemblies right after Import-Module dbatools:

  Microsoft.SqlServer.Dac                                17.100.0.0
  Microsoft.SqlServer.Smo                                17.100.0.0
  Microsoft.SqlServer.Management.Sdk.Sfc                 17.100.0.0
  …
  **Microsoft.SqlServer.Management.IntegrationServices   16.100.0.0**
  **Microsoft.SqlServer.Diagnostics.STrace               16.100.0.0**
  

  Only those two DLLs are v16 while the rest are v17.
  The error references SqlStoreConnection from Sfc.

• Quick Google research suggests version mismatches can break that ctor.

My question

Could the mixed v16/v17 assemblies be the culprit?
If yes, what’s the cleanest fix?

Any pointers or work‑arounds are super welcome!

---

Environment

Component	Version
dbatools module	2.5.1
PowerShell	5.1.26100.4652
OS & build	Windows Server 2025 Standard 24H2 26100.4652
Target SQL Server	2022 16.0.4205.1

Let me know if extra logs or traces would help—happy to share.

Thanks a ton for your time! 🙏

[potatoqualitee]

Thank you for the detailed report! I indeed did forget to update those two. The fix will be in the next release which I plan for Sunday or Monday.

[SylvainDuran]

Hi Chrissy,
Thank you so much for the quick turnaround and for taking care of this issue!
Looking forward to the next release – thanks again for all your hard work!
Best,
Sylvain

[SylvainDuran]

Hi @potatoqualitee,

Back from holidays, I’d like to re-open this topic because I’m still having issues after updating dbatools to the latest version, including the new dlls.

Now, when I try to use Get-DbaSsisEnvironmentVariable, I get the following error message:

WARNING: [Get-DbaSsisEnvironmentVariable] Can't load server | Could not load file or assembly 'Microsoft.SqlServer.Diagnostics.STrace, Version=17.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.

I checked the dbatools.library folder and noticed that the new dll for Microsoft.SqlServer.Diagnostics.STrace is version 17.100.0.0, but the code seems to expect version 17.0.0.0.

Here are the referenced assemblies for Microsoft.SqlServer.Management.IntegrationServices as loaded in my environment.
As you can see, it specifically expects Microsoft.SqlServer.Diagnostics.STrace version 17.0.0.0:

PS C:\temp> [System.Reflection.Assembly]::Load("Microsoft.SqlServer.Management.IntegrationServices")
PS C:\temp> $asm = [System.AppDomain]::CurrentDomain.GetAssemblies() | Where-Object { $_.GetName().Name -eq "Microsoft.SqlServer.Management.IntegrationServices" }
PS C:\temp> $asm.GetReferencedAssemblies() | Select-Object Name, Version

Name                                                       Version
----                                                       -------
mscorlib                                                   4.0.0.0
Microsoft.SqlServer.Management.Sdk.Sfc                     17.100.0.0
System                                                     4.0.0.0
Microsoft.SqlServer.ConnectionInfo                         17.100.0.0
Microsoft.SqlServer.Diagnostics.STrace                     17.0.0.0
Microsoft.Data.SqlClient                                   5.0.0.0
Microsoft.SqlServer.Smo                                    17.100.0.0
System.Drawing                                             4.0.0.0
System.Windows.Forms                                       4.0.0.0
System.Data                                                4.0.0.0
Microsoft.SqlServer.IntegrationServices.Common.ObjectModel 17.100.0.0
System.Web                                                 4.0.0.0

Is there a workaround for this issue, or is there a way to get the correct version of the dll?
Thank you for your help!