For those of you that upgraded to ConfigMgr 2403, you may have noticed that some console extensions, like the MDT extensions, will cause the ConfigMgr console to crash.
Credits: Thank you Ahmed Essam at Dell for sharing your findings with the community!
Symptom
When trying use any of the MDT console extensions, you get an an application crash, and the console closes. In the Application event log you will see errors with event IDs 1, 1026 and 1000.
Part of the Event ID 1 Error
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: There is an error in XML document (2, 2). ---> System.InvalidOperationException: <SmsFormData xmlns='http://schemas.microsoft.com/SystemsManagementServer/2005/03/ConsoleFramework'> was not expected.
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderSmsFormData.Read30_SmsFormData()Part of the Event ID 1026 Error
Application: Microsoft.ConfigurationManagement.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderSmsFormData.Read30_SmsFormData()The Event ID 1000 Error
Faulting application name: Microsoft.ConfigurationManagement.exe, version: 5.2403.1169.1000, time stamp: 0xf4582b78
Faulting module name: KERNELBASE.dll, version: 10.0.14393.5850, time stamp: 0x64253b64
Exception code: 0xe0434352
Fault offset: 0x000dcd42
Faulting process id: 0xaf0
Faulting application start time: 0x01daaab7a0b2f687
Faulting application path: C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin\Microsoft.ConfigurationManagement.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 87d29440-48eb-4ebd-898e-58af08d819b7
Faulting package full name:
Faulting package-relative application ID: Solution
Configure the MDT forms extensions (XML files) to use https instead of http per this great post by Ahmed:
MDT Task Sequence Integration with ConfigMgr 2403 caused the console to crash
https://www.linkedin.com/pulse/mdt-task-sequence-integration-configmgr-2403-caused-console-essam-td6lf/
Johan, I just finished building a version 2409 system. I then added MDT 8456 and went through the configuration for that, However when I went to the step called MDT Configure ConfigMgr Integration and Install the MDT extension to Configuration Manager and it runs and completes it and then start the console…it still fails by exiting the console if trying to build a MDT Boot Image or MDT Task Sequence. I discovered that the two .xml files are changed back to http. SO is it possible that you can do this change at 2403, but not at 2409?
I did not have to change the XML files after upgrading to 2409; the MDT extensions worked without https. Are you getting event IDs 1, 1026, and 1000 in the application event log?
Also, please note that Microsoft announced the deprecation of the MDT integration just before Christmas (2024), and it should no longer be used.
Thank you so much!!!
Ran into this issue today with the Dell software gallery after building a new sccm server and this saved my bacon. Thanks!
Excellent advice and tip as always Johan!
That seems really silly — changing the XML namespace will break every console extension. But at least it's not hard to fix.
But the TS with UDI still does not work
Failed to run the action: Use Toolkit Package. Error 1
C:_SMSTaskSequence\Packages\DIG00545\Scripts\ZTISCCM.wsf(2, 11) Windows Script Host: The value for the attribute is not valid : language
Let the parent group (Gather Logs and StateStore on Failure) decides whether to continue execution
I haven't tried UDI task sequences in 2403 (yet), but there are others reporting issues with UDI task sequences as well. What WinPE version are you using?