Bumped into this issue at a customers location. The MG came to a standstill which started with these two errors:
- Database error. MPInfra_p_ManagementPackInstall failed with exception:
Database error. MPInfra_p_ManagementPackInstall failed with exception:
There is insufficient system memory in resource pool 'default' to run this query.
- AppDomain OperationsManager.dbo[runtime].78 was unloaded by escalation policy to ensure the consistency of your application. Out of memory happened while accessing a critical resource.
The application domain in which the thread was running has been unloaded.
- .NET Framework execution was aborted by escalation policy because out of memory. Thread was being aborted.
First errors 1 and 2 were thrown. Afterwards the Console (UI) wouldn’t start anymore. Only the error as stated in Item 3 was thrown, happening on every computer where the Console (UI) was started.
After some thorough investigation it turned out the SQL server hosting the OpsMgr database was running out of memory. Because it of it, it couldn’t serve any requests any more, resulting in an unresponsive SCOM Console.
This SQL server only ran 8 GB of RAM. After doubling it to 16 GB, and allocating a maximum of 12 GB of RAM to the related SQL instance, everything was just fine again.
The SQL server hosting the OpsMgr database is crucial to the overall health, performance and availability of the related Management Group. Therefore this server needs to be a beefed one for CPU, RAM and disk IO.