The CreatorCon Call for Content is officially open! Get started here.

SCOM integration problem. Service-Now to SCOM does not work

tpulls
Kilo Explorer

Hello,

I have the Service-Now SCOM Connector configured on both my SCOM server and MID server. Alerts from SCOM are being sent to Service-Now and even updated from Service-Now with the Incident Number. However, when I resolve the Incident in SN it is not closing the SCOM alert. If I understand correctly, SN will send a request to the MID server to trigger update_alert.exe. I can't tell if this is happening or not. The MID server is specified under Properties in Service-Now

I'm looking through agent0.log on the MID server and don't really see any errors. How does the MID server know what my SCOM server is in order to close the alerts with update_alert.exe? How else can i troubleshoot this? Is there a step-by-step guide out there to follow incase I missed something?

24 REPLIES 24

John,

That was exactly it. Thank you!


I am having the same trouble alert.exe for SCOM. I was wondering what you input for the management server name. What I need to do is communicate to the   SCOM admin exactly what I need for the SCOM name and where he would find it.


Can you explain what you changed in the script?   Mine had "LPSCOMFRMS" referenced (not sure where that came from), but I updated it to match the management group of the SCOM incidents but I'm still not getting updated tickets.



"ERROR: The requested name is valid, but no data of the requested type was found"


Never mind, figure it out.   It needed to be replaced with the name of the management server, not the name of the management group.


I am having the same trouble alert.exe for SCOM. I was wondering what you input for the management server name. What I need to do is communicate to the   SCOM admin exactly what I need for the SCOM name and where he would find it.