-
Notifications
You must be signed in to change notification settings - Fork 435
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
Compiling an exported configuration silently fails #3178
Comments
What PS Version are you using? Icould you share the detailed error message? |
The default version in the docker image: $PSVersionTable
Name Value
---- -----
PSVersion 5.1.17763.3770
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.17763.3770
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
I don't quite follow, from where? The issue is that there are no error messages. |
I was referring to this sentence above. Did you try to get the $Error variable? |
Gotcha, apologies. The first error I get with 'Stop' is detailed in #3179 (I didn't check the $Error variable). |
And the second/third error is detailed in #3181. |
Let's continue to work on the individual issues listed above. Will close this one for now. |
Details of the scenario you tried and the problem that is occurring
I tried to convert a configuration exported from a clean developer tenant (https://developer.microsoft.com/en-us/microsoft-365/dev-program).
The configuration was exported using certificate thumbprint and default mode, without any errors:
Then, when I try to compile it it silently fail w/o producing any
.mof
-file:Verbose logs showing the problem
The issue is that there are no verbose logs. Running with
-Verbose
doesn't make any change. EnablingEnable-DscDebug -BreakAll
didn't do any difference either.Suggested solution to the issue
Break on errors by default. Print logs when things fail.
What did finally work was to set
$ErrorActionPreference = 'Stop' ;
before running, then it breaks with a detailed message.The DSC configuration that is used to reproduce the issue (as detailed as possible)
The operating system the target node is running
I'm running inside a Windows Server Core container,
mcr.microsoft.com/windows/servercore:1809-amd64
.Version of the DSC module that was used ('dev' if using current dev branch)
The text was updated successfully, but these errors were encountered: