-
Notifications
You must be signed in to change notification settings - Fork 542
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
Error Occurs When Running New-M365DSCDeltaReport #5863
Comments
It would be really useful if someone could assist with this - we also have this issue. Getting a capture is one thing but not being able to convert it to readable output is another The member 'neutralQuaternaryAlt' is not valid. Valid members are I tried editing the file and you end up with an invalid configuration file. Can anyone assist? Thanks |
This looks like an invalid export, the output doesn't match the defined schema. I'll take a look once I have time. |
I have the same issue since about two weeks, parser issues during any report generation. |
@Morph2310 With the same resource or another one? If it's for another resource, please open a separate issue so that we don't mix them up. |
The same resource, but additionally resources in exports from ExO, Intune and Teams, so I will open separate issues according to the resources. One common denominator - parsing. |
@Morph2310 Thanks a lot, one per resource would be great. We enforced a check that the configuration has to be valid before a drift or a report can be generated so that we don't mistakenly compare "wrong" stuff. Information for the others: A PR is open that fixes the export (which will in term also fix the issue with the delta report). |
Running an Export/Capture of a Workload, for example Intune with the validate switch set to
The validation error from the terminal is also:
Could you provide any pointers in where to look to resolve this or would you know how to resolve? Without any assistance, I can only think of using the components parameter i.e. ( Thanks in advance |
@Royhutton The first error message appears if you are using PowerShell 7.5 because there is an issue there with object cloning. This is already reported in the PowerShell repository, but no fix yet. Please stick to Windows PowerShell 5.1 for now. The second one is because the export is done in a wrong format. Can you tell me which resource is affected by that and maybe a sample of the resource that's failing? This would be great. |
@FabienTschanz Thanks for this info - With an Export running (using 5.1) for an Intune Workload capture now i get the validation error:
That in the partial capture file is:
|
Got it, so it's the IntuneDeviceConfigurationPolicyAndroidDeviceOwner policy. I'll take a look at it tomorrow. |
Thanks for the bug fix there guys. Getting further.
Is this a known issue? |
@Royhutton yes, this should be fixed by #5924. Please re-export the configuration and try again. If it still doesn't work, open a separate issue for it. The latest version is 1.25.326.1, which includes the fix (better said, already .319.1 contains it). |
Description of the issue
The following command results in an error:
Error Message:
Conditions of Occurrence:
$newFile and $oldFile are files output by the following command:
Export-M365DSCConfiguration -Workloads @("OD", "SPO") -Path $rootPath -ApplicationId $applicationId -TenantId $tenantId -CertificateThumbprint $certificateThumbprint -FileName $initialConfigurationFileName
A custom theme exists in the SPO tenant:
Microsoft 365 DSC Version
1.25.219.2
Which workloads are affected
SharePoint Online
The DSC configuration
Verbose logs showing the problem
Environment Information + PowerShell Version
The text was updated successfully, but these errors were encountered: