You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Strangely, the culprit is having the DisplayName contain an en dash, such as "Group – name" - I expect other characters, such as em dash, would behave similarly. If I replace this character with a regular minus character, or remove it completely, the report is successfully created.
I can confirm that my dependencies are up to date, and that I am running this in an elevated terminal.
That sounds very strange, but somehow I expected something like that. The culprit here might be the fact that en dash is a Unicode character and not all Unicode characters might be available… I‘ll take a look at it if I have time.
Description of the issue
While attempting to create a report for a configuration, I received similar exceptions to those in the verbose logs.
I was able to reduce the configuration down to the one in the DSC configuration section, where the configuration reliably caused an exception.
My script is as follows:
Strangely, the culprit is having the
DisplayName
contain an en dash, such as"Group – name"
- I expect other characters, such as em dash, would behave similarly. If I replace this character with a regular minus character, or remove it completely, the report is successfully created.I can confirm that my dependencies are up to date, and that I am running this in an elevated terminal.
Is there anything that can be done here?
Microsoft 365 DSC Version
V1.24.1016.1
Which workloads are affected
Exchange Online
The DSC configuration
Verbose logs showing the problem
Environment Information + PowerShell Version
OsName : Microsoft Windows 11 Enterprise
OsOperatingSystemSKU : EnterpriseEdition
OsArchitecture : 64-bit
WindowsVersion : 2009
WindowsBuildLabEx : 22000.1.amd64fre.co_release.210604-1628
OsLanguage : en-GB
OsMuiLanguages : {en-GB, en-US}
The text was updated successfully, but these errors were encountered: