-
Notifications
You must be signed in to change notification settings - Fork 224
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
SqlServiceAccount: Throws exception when used with SQL Server 2022 #1800
Labels
bug
The issue is a bug.
Comments
johlju
added
bug
The issue is a bug.
help wanted
The issue is up for grabs for anyone in the community.
labels
Nov 25, 2022
johlju
added a commit
to johlju/SqlServerDsc
that referenced
this issue
Nov 25, 2022
johlju
changed the title
SqlServiceAccount: Throw exception when used with SQL Server 2022
SqlServiceAccount: Throws exception when used with SQL Server 2022
Nov 25, 2022
johlju
added a commit
to johlju/SqlServerDsc
that referenced
this issue
Nov 26, 2022
This was resolved with PR #1808. To use this resource on SQL Server 2022 the SqlServer module 22.0.49-preview is needed, and also the latest preview of SqlServerDsc (building and deploying as I write this). |
johlju
removed
the
help wanted
The issue is up for grabs for anyone in the community.
label
Jan 22, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem description
When running the integration tests for SqlServiceAccount, on the build worker that have installed the SQL Server 2022 of the Database Engine, it fails with an exception. It seems it fails when getting the current state.
To reproduce, enable the Pester tag
'Integration_SQL2022'
on line 48 in the integration tests of SqlServiceAccount and then run the pipeline (or the integration test).This has probably something to do with the type
Microsoft.SqlServer.Management.Smo.Wmi.ManagedComputer
, and might be because feature like CONN and SDK are no longer available in SQL Server 2022. Or, maybe we need to install a newer version of the SqlServer PowerShell module. But it is all a guess since I have not debugged the resource. 🤔Verbose logs
DSC configuration
Suggested solution
Unknown. But seems this need to be handled differently for SQL Server 2022.
SQL Server edition and version
SQL Server PowerShell modules
Operating system
PowerShell version
SqlServerDsc version
The text was updated successfully, but these errors were encountered: