Skip to content
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

Jump to bottom

PowerShell 7.4.6 along with dbatools 2.1.28 & dbatools.library 2024.4.12 - Microsoft.DataSqlClient.dll - Assembly with same name is already loaded #9566

Open
RareCrawdad opened this issue Dec 16, 2024 · 13 comments
Open

PowerShell 7.4.6 along with dbatools 2.1.28 & dbatools.library 2024.4.12 - Microsoft.DataSqlClient.dll - Assembly with same name is already loaded #9566

RareCrawdad opened this issue Dec 16, 2024 · 13 comments
Labels
bugs life triage required New issue that has not been reviewed by maintainers

Comments

@RareCrawdad
Copy link

Verified issue does not already exist?

I have searched and found no existing issue

What error did you receive?

Get-DbaAgentJob -SqlInstance $DestinationServer | Where-Object { …

The 'Get-DbaAgentJob' command was found in the module 'dbatools', but the module could not be loaded due to the
following error: [Couldn't import C:\Program
Files\PowerShell\7\Modules\dbatools.library\2024.4.12\core\lib\win-sqlclient\Microsoft.Data.SqlClient.dll |
Assembly with same name is already loaded] For more information, run 'Import-Module dbatools'.
     
     
     

### Steps to Reproduce

Running this using PowerShell 7.4.6, dbatools 2.1.28 & dbatools.library 2024.4.12. Calling a .ps1 file on a local drive.

# Define the source and destination SQL instances
$SourceServer= 'Server1,1433'
$DestinationServer = 'Server2,1433'

# Define the jobs to exclude
$excludeJobs = @()

# Delete all jobs on the destination server except the excluded ones
Get-DbaAgentJob -SqlInstance $DestinationServer | Where-Object { $_.Name -notin $excludeJobs } | Remove-DbaAgentJob -Confirm:$false

Start-Sleep -Seconds 5

# Copy jobs from the source server to the destination server, excluding the specified jobs
Copy-DbaAgentJob -Source $SourceServer -Destination $DestinationServer -ExcludeJob $excludeJobs -Force


### Please confirm that you are running the most recent version of dbatools

Script     2.1.28                dbatools                    
Script     2024.4.12             dbatools.library

### Other details or mentions

Windows Environmental Variables order:

PS C:\Users\xxxx> $env:PSModulePath -split ';'

C:\Program Files\PowerShell\7\Modules
C:\Program Files\WindowsPowerShell\Modules
C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules
C:\Program Files (x86)\Microsoft SQL Server\160\Tools\PowerShell\Modules\
C:\Program Files\PowerShell\Modules
C:\Users\xxxx\Documents\PowerShell\Modules

Troubleshooting Steps:

1. I have removed VSCode, PowerShell 7 & All cmdlets
2. Reinstalled only PowerShell 7 after reboot
3. Imported downloaded Modules for dbatools and dbatools.library
4. The .ps1 script ran
5. Rebooted Server
6. Received the Assembly with same name already loaded error. I have run out of options to test at this point.

### What PowerShell host was used when producing this error

PowerShell Core (pwsh.exe)

### PowerShell Host Version


Name                           Value
----                           -----
PSVersion                      7.4.6
PSEdition                      Core
GitCommitId                    7.4.6
OS                             Microsoft Windows 10.0.20348
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0



### SQL Server Edition and Build number

Microsoft SQL Server 2022 (RTM-CU16) (KB5048033) - 16.0.4165.4 (X64)   Nov  6 2024 19:24:49   Copyright (C) 2022 Microsoft Corporation  Standard Edition (64-bit) on Windows Server 2022 Standard 10.0 <X64> (Build 20348: ) (Hypervisor) 

### .NET Framework Version

[System.Runtime.InteropServices.RuntimeInformation]::get_FrameworkDescription() | Set-Clipboard

.NET 8.0.10

-- if that doesn't work, you can try Get-ChildItem 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP' -Recurse | Get-ItemProperty -Name version -EA 0 | Where PSChildName -Match '^(?!S)\p{L}' | Select PSChildName, version

PSChildName                      Version
-----------                      -------
v2.0.50727                       2.0.50727.4927
v3.0                             3.0.30729.4926
Windows Communication Foundation 3.0.4506.4926
Windows Presentation Foundation  3.0.6920.4902
v3.5                             3.5.30729.4926
Client                           4.8.04161
Full                             4.8.04161
Client                           4.0.0.0
@RareCrawdad RareCrawdad added bugs life triage required New issue that has not been reviewed by maintainers labels Dec 16, 2024
@RareCrawdad
Copy link
Author

I just tried this method from

https://learn.microsoft.com/en-us/powershell/scripting/dev-cross-plat/resolving-dependency-conflicts?view=powershell-7.4#why-do-dependency-conflicts-occur

, but getting same error:

WrapperScript.ps1

Path to the main script

$scriptPath = "C:\path\to\CopyJobs.ps1"

Use pwsh -c to run the main script in a new session

pwsh -c "& '$scriptPath'"

@RareCrawdad
Copy link
Author

I have also tried the following method:

https://stackoverflow.com/questions/77545580/upgrade-to-powershell-7-dbatools-2-causing-assembly-with-same-name-is-already

Same error message.

@RareCrawdad
Copy link
Author

I was able to get this to run several times, but still testing:

Unload the conflicting assembly if it's already loaded

$assembly = [System.AppDomain]::CurrentDomain.GetAssemblies() | Where-Object { $_.GetName().Name -eq "Microsoft.Data.SqlClient" }
if ($assembly) {
[System.AppDomain]::CurrentDomain.RemoveAssembly($assembly)
}

Load the required assembly

$dllPath = "C:\path\to\Microsoft.Data.SqlClient.dll"
Add-Type -Path $dllPath

I still have to run a clean PS session via the WrapperScript.ps1, but by adding the following on the main script, it seems to work thus far.

Still does not explain why the sudden change after updating Powershell and dbatools.

@mattcargile
Copy link
Contributor

Have you looked at your $PROFILE | select * files to see if any other modules are being loaded or the like? I am fairly perplexed by your issue.

Does Get-DbaAgentJob work if you launch pwsh from the Run Dialog box by hitting WIN + r keys then typing pwsh -noprofile?

@RareCrawdad
Copy link
Author

RareCrawdad commented Jan 9, 2025 via email

@mattcargile
Copy link
Contributor

I wouldn't say corrupt. If you run the below we can see what your $PROFILEs look like.

$PROFILE.psobject.Properties | ? name -Match host | % { cat $_.value -ea Ignore }

If you add a | Set-Clipboard to the end of the above it will automatically go into your clipboard to be pasted into Github. If it is too large, you can put it in a GitHub Gist.

@RareCrawdad
Copy link
Author

I had to run the following to get any output:

PS C:\Users\xxx> $PROFILE.psobject.Properties | Where-Object { $_.Name -Match 'host' } | ForEach-Object {

$profilePath = $_.Value
if (Test-Path $profilePath) {
    Write-Output "Reading profile: $profilePath"
    Get-Content $profilePath -ErrorAction Ignore
} else {
    Write-Output "Profile not found: $profilePath"
}

}
Profile not found: C:\Program Files\PowerShell\7\profile.ps1
Profile not found: C:\Program Files\PowerShell\7\Microsoft.PowerShell_profile.ps1
Profile not found: C:\Users\xxx\Documents\PowerShell\profile.ps1
Profile not found: C:\Users\xxx\Documents\PowerShell\Microsoft.PowerShell_profile.ps1

@mattcargile
Copy link
Contributor

Yeah you would only get output if you have a $PROFILE defined. Ok so it isn't a $PROFILE problem. There is something going on in your session I suppose. You would do a Get-Module and $error[0] | format-list * -force right after the error happens to retain the entire error. My assumption is there are other commands or modules you are loading that interfere with dbatools so a fresh session solves it.

@RareCrawdad
Copy link
Author

RareCrawdad commented Jan 13, 2025 via email

@niphlod
Copy link
Contributor

niphlod commented Jan 13, 2025

there's the SqlServer module loaded .... that's the one creating issues

@mattcargile
Copy link
Contributor

Yes, @RareCrawdad , you should not load SqlServer module in the same session as dbatools. Or you might be able to get away with always insuring dbatools is loaded first.

And in my personal opinion, I would drop SqlServer module altogether if it is at all possible and only use dbatools. I can't think of any feature SqlServer has that isn't in dbatools though I could very well be wrong.

@RareCrawdad
Copy link
Author

RareCrawdad commented Jan 13, 2025 via email

@potatoqualitee
Copy link
Member

@RareCrawdad -- once it's in memory, you cant remove it. you have to start a new session w/o sqlserver never having been loaded.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bugs life triage required New issue that has not been reviewed by maintainers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@niphlod @potatoqualitee @mattcargile @RareCrawdad