SOLVED Microsoft.ConfigurationManagement has stopped working

[ShaneW07]

Hi all, this is my first time posting here, so hopefully this is the right place...

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

 

[Prajwal Desai]

When you upgraded to ConfigMgr 2107, did you not get Dot NET 4.8 Framework warning - https://www.prajwaldesai.com/fix-sccm-dot-net-4-8-prerequisite-warning/

Configuration Manager requires at least .NET version 4.6.2, but recommends the latest version 4.8. A later version of Configuration Manager will require .NET version 4.8. To minimize disruption, before you run Configuration Manager setup, update .NET and restart the system.

 

[ShaneW07]

When you upgraded to ConfigMgr 2107, did you not get Dot NET 4.8 Framework warning - https://www.prajwaldesai.com/fix-sccm-dot-net-4-8-prerequisite-warning/

Configuration Manager requires at least .NET version 4.6.2, but recommends the latest version 4.8. A later version of Configuration Manager will require .NET version 4.8. To minimize disruption, before you run Configuration Manager setup, update .NET and restart the system.

Thank you for your response. I did yes and before proceeding I would have made sure 4.8 was installed, when I said I tried installing the latest version, what I meant was 4.8 was already on the server so it won't let me know any higher, when I try an install 4.8 I get the following message ".NET Framework 4.8 or a later update is already installed on this computer.".

 

[Prajwal Desai]

If the console is reporting this error both on server and remote machine (with console installed), then I don't think the upgrade is completed. Can you confirm if the upgrade from 2103 -> 2107 was successful ?. I also want you to go to monitoring and verify if all the components are online and healthy.
Such issues require access to the ConfigMgr setup because we cannot exactly determine what's causing this. We will try to resolve it here otherwise you can always log a case with MS support.

 

[ShaneW07]

If the console is reporting this error both on server and remote machine (with console installed), then I don't think the upgrade is completed. Can you confirm if the upgrade from 2103 -> 2107 was successful ?. I also want you to go to monitoring and verify if all the components are online and healthy.
Such issues require access to the ConfigMgr setup because we cannot exactly determine what's causing this. We will try to resolve it here otherwise you can always log a case with MS support.

I can confirm the upgrade completed to my knowledge, I've been on this update for well over a couple of weeks now and it has been working perfectly, I've been coming in and out of the console on the remote machine this entire time. It literally only stopped working today right after I tried to install the Reporting Services Point Site Role.

Unless there is another way to check if all the components are healthy than sadly I'm out of luck there as I cannot get in the console at all it crashes and closes almost instantly.

 

[Prajwal Desai]

If all the components are healthy and online, I don't see a reason why the console shows no reports. Try finding what changes were done recently that triggered this issue. For example, did someone restore the VM, uninstall or repaired a ConfigMgr role etc.
I know how it feels when you launch the console, and it crashes with some stupid kernel error. I recommend logging a case with Microsoft support, and the support shall access your setup remotely to get more details about this issue.

 

[ShaneW07]

If all the components are healthy and online, I don't see a reason why the console shows no reports. Try finding what changes were done recently that triggered this issue. For example, did someone restore the VM, uninstall or repaired a ConfigMgr role etc.
I know how it feels when you launch the console, and it crashes with some stupid kernel error. I recommend logging a case with Microsoft support, and the support shall access your setup remotely to get more details about this issue.

I am unable to truly tell if it all the components are healthy.

No VM Changes were made as I'm the only one who makes the changes. The only change was the Reporting Services Point Site Role was installed from the console. Straight after this install finished successfully the console stopped working.

I sadly didn't know that the SQL Server Reporting Services needed to be installed until after I'd added the Reporting Services Point Site Role, would this causes any issues?

After I'd installed the new reporting role and realised something was wrong I took a snapshot and then tried troubleshooting, the first thing I tried other than reinstalling the console was installing and then Configuring the SQL Server Reporting Services. I got this all setup as it was supposed to be before adding the site role. And Upon this I've noticed one strange thing happening... When going to http://<servername>/reports/browse the folder that would normally be in here (ConfigMgr_<sitecode> keeps recreating itself but adding .old1, .old2 over and over again it's already up to .old124. This could be a red herring but it's certainly odd behaviour.

 

[Prajwal Desai]

I sadly didn't know that the SQL Server Reporting Services needed to be installed until after I'd added the Reporting Services Point Site Role, would this causes any issues?

You should have used online guides or hired a consultant for this.
From what I see, you are more concerned about the reports than ConfigMgr. First fix the console crash issue, and you can then reinstall the reporting services.

 

[ShaneW07]

You should have used online guides or hired a consultant for this.
From what I see, you are more concerned about the reports than ConfigMgr. First fix the console crash issue, and you can then reinstall the reporting services.

I know that know... I usually always use guides, your guides... But as it was just adding a Site Role I stupidly assumed it would tell me if it needed anything extra and that it would be okay, hence why I also took no snapshot. We all learn from our mistakes and I from now certainly won't be changing any roles without taking a snapshot and looking up some guides.

I'm defiantly more concerned about ConfigMgr, I was only stating odd behaviour that I've incurred since installing the new Reporting Services Point Site Role.

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...

 

[Prajwal Desai]

Glad to hear that. Finally, the issue is resolved. Once you determine the ConfigMgr is working fine, take a snapshot. Marking this thread as Solved.

 

[Garth]

I from now certainly won't be changing any roles without taking a snapshot and looking up some guides.

Just to be clear, Snapshots are NOT supported by CM and should NOT be "used" per se.

 

[ShaneW07]

Just to be clear, Snapshots are NOT supported by CM and should NOT be "used" per se.

Thank you for letting me know, hopefully they are only ever their as a last resort.

 

[Garth]

Thank you for letting me know, hopefully they are only ever their as a last resort.

Just remember that if you EVER use them it will affect everything and I mean everything. Clients, packages, dps, etc! Some of the issues are really HARD to fix. aka contact MS support only type of things.

 

[saleharaki]

Hi all, and thanks for your sharings.

I have exactly the same problem and I am stuck now for three days searching a solution.... with the Console is not working.
Please provide any advise that I can move forward.

 

[Prajwal Desai]

Hi all, and thanks for your sharings.

I have exactly the same problem and I am stuck now for three days searching a solution.... with the Console is not working.
Please provide any advise that I can move forward.

Please log another question with screenshots and logs.