APM feature in SCOM 2016 Agent may cause a crash for the IIS Application Pool running under .NET 2.0 runtime.
Several callbacks within APM code of SCOM 2016 Agent utilize memory allocation that’s incompatible with .NET 2.0 runtime and may cause an issue if this memory is later accessed in a certain way. Those particular modifications were added in SCOM 2016 Agent and are not present in SCOM 2012 R2 Agent.
The fix for this issue is to be provided with SC 2016 OM Update Rollup 3. The aforementioned code paths will not be executed if the Application Pool is running under .NET 2.0 Runtime. We are also evaluating to release a hotfix for this issue.
There are several workarounds for this issue:
- Application pool can be migrated to .NET 4.0 Runtime;
- SCOM 2016 Agent can be replaced with SCOM 2012 R2 Agent, it’s forward-compatible with SCOM 2016 Server and APM feature will continue to work with the older bits;
- SCOM 2016 Agent can be reinstalled with NOAPM=1 switch in msiexec.exe setup command line, APM feature will be excluded from setup;