Closed mKenfenheuer closed 4 years ago
Sound similar to the issue https://github.com/dsccommunity/NetworkingDsc/issues/464
@mKenfenheuer are you installing the OS with a German Windows Server 2019 (1809) ISO or is it installed using en-US ISO and using language pack similar to the issue in the previous comment?I'm gonna try to repro this.
@mKenfenheuer I have repro the problem in issue https://github.com/dsccommunity/DscResource.Common/issues/50. Thanks for reporting!
@mKenfenheuer are you installing the OS with a German Windows Server 2019 (1809) ISO or is it installed using en-US ISO and using language pack similar to the issue in the previous comment?I'm gonna try to repro this.
Its a german iso, yes. Ive installed the language pack en-US and this works. I think its related to the current culture as only changing the current culture of the ps thread to en-us also works.
@mKenfenheuer I have repro the problem in issue dsccommunity/DscResource.Common#50. Thanks for reporting!
Great! Thx for looking into this!
Same problem with the italian version
This is being fixed in PR https://github.com/dsccommunity/DscResource.Common/pull/51
I will release a new version tomorrow that will fix this. That version will contain a new version of the common module DscResource.Common that have a fix for this issue.
Pushed a full release now, if the test passes it will be deployed within 3 hours. There have recently been some intermittent issues when running integration tests which makes me need to re-run them manually. :/
Closing this at this time. If you see any problems with the new release, please comment on this issue or reopen the issue.
Details of the scenario you tried and the problem that is occurring
Tried installing SQL 2017 with DSC, receiving error:
Verbose logs showing the problem
Suggested solution to the issue
I've tried to rename the file from DSC_SqlSetup.strings.psd1 to DSC_SqlSetup.psd1 and the setup gets at least past the installation but fails with Test-DscConfiguration.
The DSC configuration that is used to reproduce the issue (as detailed as possible)
SQL Server edition and version the target node is running
SQL Server 2017 Enterprise
SQL Server PowerShell modules present on the target node
The operating system the target node is running
Version and build of PowerShell the target node is running
Version of the DSC module that was used