SCCM Issue - When I open the management console I get the following message "Microsoft.ConfigurationManagement has stopped working."

Question

Hi,

I'm running System Center Configuration Manager Version 2107 (5.00.9058.1000) and currently when I open the management console on the server itself or a remote machine it opens with the following error "Microsoft.ConfigurationManagement has stopped working" and then gives me the following options "Debug" or "Close Program". Clicking Debug gives the following dialog box "Visual Studio Just-In-Time Debugger", which states 'An unhandled Microsoft .NET Framework exception occurred in Microsoft.ConfigurationManagement.exe [6352]. Just-In-Time debugging this exception failed with the following error: No installed debugger has Just-in-Time debugging enabled. In Visual Studio, Just-In-Time debugging can be enabled from Tools/Options/Debugging/Just-In-Time." The console does briefly load and the only thing that shows in the console is Administration.

I did the below and after the below the error above started to occur, as it was only a Site Role being added I did not take a VM Snapshot, very silly of me, I regret this now!

I was installing the Site Role "Reporting services point" according to the following logs installing the role was successful on the server, "srsrpsetup.log" and "srsrpMSI.log", after adding the Site Role I tried to head to Reports and it was still blank and when creating a report it would say the role needed to be installed, so I assumed the console needed to be closed and reopened to take effect, however, upon doing this I then received the error above.

When opening the console the following three logs are created in Event Viewer:

Application Error
"
Faulting application name: Microsoft.ConfigurationManagement.exe, version: 5.2107.1063.1000, time stamp: 0x904f05b2
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1202, time stamp: 0x448a4f5d
Exception code: 0xe0434352

More of this log can be provided if required.
"
.NET Framwork
"
Application: Microsoft.ConfigurationManagement.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentException

More of this log can be provided if required.
"
Critical
"
System.ArgumentException: Version string portion was too short or too long.
at System.Version.VersionResult.SetFailure(ParseFailureKind failure, String argument)
at System.Version.TryParseVersion(String version, VersionResult& result)
at System.Version.Parse(String input)
at System.Version..ctor(String version)

More of this log can be provided if required.
"

I have already tried reinstalling the console on both the server and the remote machine, I have also tried installing the latest version of .NET Framework and I have tried running the .NET repair tool. Sadly none of these were successful.

I will try my best to provide any logs requested and would be extremely grateful for any help or advice.

Thanks

Answer 1

Thankfully I have been some what lucky in fixing the issue... The other IT Administrator on site who also uses the console still had it open on their workstation. Using their console I was able to go into the Site Roles and remove the Reporting Services Point role, once removed I waited 20 minutes checked the "srsrpsetup.log" and "srsrpMSI.log" and both said the uninstall was successful. After that I tried to open the console on the server and on the original remote machine and it was working fine.

Without access to the console I am not sure how I would've been able to resolve the issue, I am not aware of any way to remove a Site Role without access to the Console. I'd assume there is a way and I probably just don't know it.

I've since taken a snapshot of the working server and then reinstalled the Reporting Services Point role and with this install the console stayed working.

Thank you for your responses they have been greatly appreciated. Sadly I am not sure in the end what the actual cause of the problem was...

Answer 2

Hello @ShaneWilliams,

As initial troubleshooting I would recommend the next:

1. Update .NET framework for Windows Server via MS update
2. Update latest CU for server
3. Ensure your hardware performance at that server is fine
4. index your sql database

Hope this helps with your query,

---

--If the reply is helpful, please Upvote and Accept as answer--

Answer 3

Hi,

Thanks for your update, and I am glad to hear that your problem is solved. We could check if the problem will recur by SmsAdminUI.log, which records Configuration Manager console activity.

Besides, I change your comment to Answer, please accept answer, so that it will make someone who has the similar issue easily find the answer.

If you have any other issues, please don't hesitate to let us know.

Thanks and have a nice day.

Best regards,
Amanda