When I first installed and configured client side APM monitoring I couldn’t get any alerts or performance data. Here are some troubleshooting tips which helped me resolve the issue (with a little help from my friends - thanks Shawn and Vitaly!).

1) Check Server Side Monitoring has been implemented, configured and is working. If Server Side monitoring isn’t working then client side monitoring won’t work either. So start at the beginning.

2) Actually use the web application. If no-one is using the web application then there are no alerts or data to generate.

3) Check that client side monitoring code is being injected into the page (while browsing through your web application, right click the page and choose view source):

4) Check that the Client Side Collector is able to receive data

a) The CSMCollector is now always local to the web application – you can see this in IIS Management:

So one way to check the CSMCollector is working and contactable is to open a web browser and go to http://IISServerName/cscmcollector/csmcollector.asmx – you might well see this error.

The issue is precisely what the error message states – in APM in SCOM 2012 beta, ISAPI and CGI restrictions need to be set to enabled. If you look at the IIS Management Screenshot, one up from the error message, you’ll see in the bottom right an icon for “ISAPI and CGI Restrictions”. You’ll need to double click this and enable ISAPI.

Set each of the Not Allowed items to Allow and all should be fine.

Tags: APM (Avicode), CSM, Troubleshooting

This entry was posted on Tuesday, August 2nd, 2011 at 9:17 am and is filed under APM (Avicode), SCOM 2012. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.