Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, May 6, 2019 8:34 AM
Event Viewer Error log
Faulting application name: w3wp.exe, version: 10.0.14393.0, time stamp: 0x57899135
Faulting module name: PerfMon.dll, version: 8.0.10977.0, time stamp: 0x59cfb424
Exception code: 0xc0000409
Fault offset: 0x000f8c7b
Faulting process id: 0x14c0
Faulting application start time: 0x01d4ff81f2dabeec
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: 2a9ee8ec-58e9-4b66-b6b8-e8e511b0b005
Faulting package full name:
Faulting package-relative application ID:
Website Info
.net framework 4.7
we build website with msbuild command and csproj file.
msbuild params
/p:DeployOnBuild=true /p:WebPublishMethod=Package /p:PackageAsSingleFile=true /p:SkipInvalidConfigurations=true /p:OutPutPath="bin\(BuildConfiguration)" /p:PackageLocation="$(build.artifactstagingdirectory)\"
All replies (10)
Monday, May 6, 2019 9:22 AM ✅Answered
Okay, then your issue is not related to System Center Operations Manager, I suggest you ask in the Log Analytics forums over here:
Microsoft Azure > Azure Log Analytics
https://social.msdn.microsoft.com/Forums/azure/en-US/home?forum=opinsights
Blog: https://thesystemcenterblog.com LinkedIn:
Monday, May 6, 2019 8:47 AM
Hello,
There was an issue with .NET Framework 2.0, although you're using a newer one it might still be somehow related, HERE is a similar forum thread about this issue.
APM feature in SCOM 2016 Agent may cause a crash for the IIS Application Pool running under .NET 2.0 runtime
https://support.microsoft.com/en-us/help/4464228/apm-feature-in-scom-2016-agent-may-cause-a-crash-for-the-iis-applicati
Here's also a blog post about this issue:
APM feature in SCOM 2016 Agent may cause a crash for the IIS Application Pool running under .NET 2.0 runtime
This issue was fixed in Update Rollup 3 for System Center 2016 Operations Manager
"The Application Performance Monitoring (APM) feature in System Center 2016 Operations Manager Agent causes a crash for the IIS Application Pool that's running under the .NET Framework 2.0 runtime. Microsoft Monitoring Agent should be updated on all servers that use the .NET Framework 2.0 application pools for APM binaries update to take effect. Restart of the server might be required if APM libraries were being used at the time of the update."
I suggest you update your SCOM 2016 to Update Rollup 3 or the later, the latest is Update Rollup 7.
Best regards,
Leon
Blog: https://thesystemcenterblog.com LinkedIn:
Monday, May 6, 2019 8:50 AM
It was actually entirely fixed only with UR6 :
Application pool crashes and SharePoint application crashes because of APM agent and the profiler are now fixed. These occurred because the profiler was always on. This issue is fixed by disabling the profiler by default and enabling it only when APM is configured.
So don't bother updating to UR3, go straight to UR7 :)
Monday, May 6, 2019 8:55 AM
True, preferably update to the latest Update Rollup straight away, this way you'll most likely get more things "fixed" :-)
Update Rollup 7 for System Center 2016 Operations Manager
https://support.microsoft.com/en-us/help/4492182/update-rollup-7-for-system-center-2016-operations-manager
Blog: https://thesystemcenterblog.com LinkedIn:
Monday, May 6, 2019 9:12 AM
Hi Leon,
- our server just install the Microsoft Monitoring Agent services. no install System Center.
- not all the website is crashed by the Monitoring Agent. the same website build with sln file works well, but build with csproj file crashed by Monitoring Agent
- when uninstall the Monitoring agent under "Programs and Features", both build csproj and sln work well.
Monday, May 6, 2019 9:17 AM
So you have installed the Microsoft Monitoring Agent for Log Analytics in Azure?
Blog: https://thesystemcenterblog.com LinkedIn:
Monday, May 6, 2019 9:19 AM
yes, we have installed the Microsoft Monitoring Agent
Monday, May 6, 2019 9:37 AM
ok, thanks
Monday, May 6, 2019 9:45 AM
Hi，
Agree with the above explanation.
".csproj" is a Visual Studio .NET C# Project file extension. This file will have information about the files included in that project, assemblies used in that project, project GUID and project version etc. This file is related to your project. It will be automatically generated when we create 。
APM is typically enabled through the SCOM console on a server-by-server basis and delivers some really nice DevOps scenarios for monitoring .NET workloads at a code level。 In previous version, it will cause application pool crash which will lead to IIS website crash. You can upgrade your Operations Manager server to RU6 or later to see if it is working.
Application pool crashes and SharePoint application crashes because of APM agent and the profiler are now fixed. These occurred because the profiler was always on. This issue is fixed by disabling the profiler by default and enabling it only when APM is configured.
Meanwhile, based on my research, I find ".sln" is not .Net related. Maybe you can change to use this one.
Hope the information can help.
Best regards.
Crystal
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Monday, May 6, 2019 9:53 AM
I suggest you reinstall the MMA with the NOAPM switch, which will entirely remove the faulty APM feature. That should fix the issue!
These instructions are for SCOM agent but it's basically the same thing : https://kevinholman.com/2017/08/05/reinstalling-your-scom-agents-with-the-noapm-switch/