-
-
Notifications
You must be signed in to change notification settings - Fork 821
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.
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
Invoke-DbaQuery segfaults on Linux with PowerShell 7.2 when using Kerberos auth #8179
Comments
I get the same error from docker |
This was supposedly fixed in Microsoft.Data.SqlClient v4.0.1 (and System.Data.SqlClient v4.8.4). |
That is what I'm working on now, actually -- trying to get it to System.Data.SqlClient 5.0 but I'm in DLL hell. I imagine I'll figure it out by the weekend. For reference (tho I have new problems): microsoft/sqlmanagementobjects#114 |
Have there been any updates to this? I too am experiencing seg faults when running a simple Invoke-DbaQuery call in PS 7.3.0 on Centos 7. |
@garyhampson yes, this will be resolved when dbatools 2.0 is released in the upcoming weeks. I have tested invoke-dbaquery with success. |
gonna mark this as done but you'll have to wait for dbatools 2.0 in the gallery before it'll work |
Thanks @potatoqualitee - Do we know when 2.0 will be made available? Just curious if I should try to work around this issue for now or wait for it to be released. |
it'll probably be about 2 weeks, @garyhampson |
Verified issue does not already exist?
Yes
What error did you receive?
Segmentation fault (core dumped)
EXIT STATUS 139
Steps to Reproduce
Are you running the latest release?
Yes
Other details or mentions
This is a known issue: dotnet/SqlClient#1390.
It was fixed in Microsoft.Data.SqlClient v4.0.1, can we upgrade the bundled package to the latest version?
What PowerShell host was used when producing this error
PowerShell Core (pwsh.exe)
PowerShell Host Version
SQL Server Edition and Build number
.NET Framework Version
.NET 6.0.0-rtm.21522.10
The text was updated successfully, but these errors were encountered: