Update on APM fix for agent crashing issue shipped in UR3

Overview of the .NET 2.0 fix that was shipped in UR3

We have been investigating this issue actively and this fix has not solved the issue completely. We are actively working to resolve the issue and release a hotfix soon.

Workarounds:

  • 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

 

Additional issues along with the workaround

SharePoint Central Administration site stops working when SCOM 2016 Agent is installed onto the server

  • Although SCOM 2016 Agent installs APM component in the disabled state by default, it adds a registry setting to load inactive APM into IIS Application pools
  • If APM is not yet configured for this server, those application pools will only have APM loaded in inactive state without any monitoring
  • The issue has been reported that inactive APM may crash SharePoint Central Administration v4 application pool and prevent this application from starting

Workarounds:

  • If APM feature is required on that server: downgrade SCOM Agent to 2012 R2 and continue monitoring;
  • If APM feature is not required on that server: keep SCOM 2016 Agent and re-install it with “NOAPM=1” in the setup command line

 

Web Site crashes during startup when SCOM 2016 Agent is installed onto the server

  • Although SCOM 2016 Agent installs APM component in the disabled state by default, it adds a registry setting to load inactive APM into IIS Application pools.
  • If APM is not yet configured for this server, those application pools will only have APM loaded in inactive state without any monitoring.
  • If application pool account has no access to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\System Center Operations Manager\12\APMAgent registry key, inactive APM won’t be able to read that key and this application pool process may crash.

Workaround:

  • Add “Read” access permission for the application pool account to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\System Center Operations Manager\12\APMAgent