-
Notifications
You must be signed in to change notification settings - Fork 514
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
report from config: just dies trying to open the config. #5492
Comments
@mikeAtArch Did you run |
Nothing changed after winrm quickconfig and reboot. ran updates, no change. I started without ps7, no difference either direction. I have what appears to be 50k of clean data in the config file in a user export |
I sent a generic config through the report generator and it passed through, I'll review the data export and see what I can find |
You can try and narrow it down by selecting a subset of your configuration and try again until the error appears. Once you have it, we can take a look at it and see why it fails. |
I'm noticing I have dual credentials in my config files. After removing one I got a whole new set of errors. {
|
@mikeAtArch The format seems to be broken. You can paste multiline code with three consecutive backticks `, followed by a newline, and again three backticks on a new line. Then you can insert your code snippet there. Or you can upload a redacted version of your M365TenantConfig.ps1 file as .txt and we can take a look at it. |
Description of the issue
I haven't gotten anything out of the report generator.
This is a simple adduser and addgroup export.
New-M365DSCReportFromConfiguration -Type 'HTML' -ConfigurationPath 'C:\users\mike\DSC\temp\ConfigurationData.psd1' -OutputPath 'C:\users\mike\Dsc\temp\M365Report.html' -Verbose -Debug
VERBOSE: Loading file 'C:\users\mike\DSC\temp\ConfigurationData.psd1'
Microsoft 365 DSC Version
1.24.11
Which workloads are affected
Azure Active Directory (Entra ID)
The DSC configuration
Verbose logs showing the problem
VERBOSE: Loading file 'C:\users\mike\DSC\temp\ConfigurationData.psd1' just dies.
Environment Information + PowerShell Version
The text was updated successfully, but these errors were encountered: