2016 SCOM

The 2016 of Microsoft’s SCOM has the ability to crash application pools. it is specifically related to the APM feature and as a result the issue can be resolved by removing that specific feature, updating to SCOM 2019, or removing SCOM entirely.

Verify and Resolve

After FiM app pool has been created and server installed, and if hitting the ASMX page results in app pool crashing…

1. Open Microsoft Event Viewer and check for the following error message

2. Faulting application name: w3wp.exe, version: 8.5.9600.16384, time stamp: 0x52157ba0

   Faulting module name: PerfMon.dll, version: 8.0.10918.0, time stamp: 0x577fd1ba

   Exception code: 0xc0000409

   Fault offset: 0x000f897b

   Faulting process id: 0x280c

   Faulting application start time: 0x01d5eb2cb188ec68

   Faulting application path: C:\WINDOWS\SysWOW64\inetsrv\w3wp.exe

   Faulting module path: C:\Program Files\Microsoft Monitoring Agent\Agent\APMDOTNETAgent\V8.0.10918.0\PerfMon.dll

   Report Id: f18ff1e7-571f-11ea-80e5-00155d070b0c

   Faulting package full name:

   Faulting package-relative application ID:

3. If the exception code and faulting application path match then your app pool crashes are at least in part due to SCOM.

4. To resolve either upgrade to 2019, update 2016 SCOM install to not include APM, reinstall 2016 SCOM to not include APM, or remove SCOM entirely.

5. Detailed information on updating/reinstalling without APM can be found here.

Related articles