question

kumaravelu-1265 avatar image
0 Votes"
kumaravelu-1265 asked Crystal-MSFT commented

SCOM 2012: APM .NET Server-Side monitoring Configuration Error or Conflict.

Hello All,



we have SCOM 2012 & SCOM 2019 running parallelly by using agent Multihomed (Side by side).

we use to receive these alerts"APM .NET Server-Side monitoring Configuration Error or Conflict" in SCOM 2019, we had disabled this for all object of a class for temporarily until we decommission SCOM 2012.

Now we are receiving huge number of warning alerts in SCOM 2012, kindly assist us on this issue.

Management Group
SCOM2012-MG01
SCOM2019-MG02

Alert Description is as below.
Multiple management groups have provided global configuration settings for this host server. The management group "SCOM2019-MG02" has sent new configuration settings that conflict with the existing configuration. The new settings were rejected.



Regards,

Kumar B

msc-operations-manager
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Crystal-MSFT avatar image
0 Votes"
Crystal-MSFT answered Crystal-MSFT edited

@kumaravelu-1265, For the error, it seems different settings are applied to the same agent. Here, could you help to confirm if the alert comes after we disable the rule or monitor with APM .NET Server-Side in SCOM 2019? If yes, we suggest to go to SCOM 2012 to see if the same rule or monitor is there. If yes, try to disable them on SCOM 2012 as well to see if the alerts will stop.

Please try the above suggestions and if there's any update, feel free to let us know.


If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

kumaravelu-1265 avatar image
0 Votes"
kumaravelu-1265 answered Crystal-MSFT commented

Hi Crystal,

we had disabled the Monitor itself "APM .NET Server-Side monitoring Configuration Error or Conflict" in SCOM 2019. The override screenshot is attached.

Yes the alert "APM .NET Server-Side monitoring Configuration Error or Conflict" triggers in SCOM 2012 after we had disabled the Monitor "APM .NET Server-Side monitoring Configuration Error or Conflict" in SCOM 2019.

100446-apm.jpg

Regards,
Kumar



apm.jpg (45.2 KiB)
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@kumaravelu-1265, Thanks for the response. I know "APM .NET Server-Side monitoring Configuration" has been disabled on the SCOM 2019 and the alert appears on SCOM 2012. Here we suggest to disable this monitor on SCOM 2012 with the similar steps on 2019 to avoid confliction. If there's any update, please let us know.

0 Votes 0 ·

@kumaravelu-1265, How's everything going? Did we try to disable the same monitor on SCOM 2012? If there's any update, feel free to let us know.

0 Votes 0 ·
RogerXue-3369 avatar image
0 Votes"
RogerXue-3369 answered

he APM alert usually appears if one or more of the agents received contradicting configuration settings for the same application under APM monitoring.

From your description , I know the agent is multi-homed. And it belongs to several management groups and receives the configuration from them, the difference in the settings for the same application can cause a conflict. We can compare the settings and make them match or exclude this agent from the target APM group for one of the management servers.

For details, pls. refer to
https://docs.microsoft.com/en-us/answers/questions/320511/scom-2019-apm-net-server-side-monitoring-configura.html

roger

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.