locked
Unable to synchronize the OpsMgr Alert Connector in scsm2012 RRS feed

  • Question

  • Experts,

    We have created the OpsMgr Alert Connector and successfully synchronized at first time. But, later if we run synchronize, connector is not running and stucks.

    Why this issue is happening.

    Thanks,

    Kumaresan

    Friday, July 13, 2012 12:13 PM

Answers

  • A common fix is to uninstall and re install the connector from SCSM.  Worked for me last time I was having issues.

    Is your OpsMan action account a SCSM administrator?  It should be and if it isn't you would see this issue.


    - Get on the floor, do that dinosaur

    Wednesday, July 18, 2012 2:53 PM

All replies

  • Hi Kumaresan,

    What does the Operations Manager log display?

    Br,


    Kenneth Bess - http://www.systemcenterblog.net

    Friday, July 13, 2012 2:38 PM
  • Did you set it up in OpsMan as well?

    - Get on the floor, do that dinosaur

    Tuesday, July 17, 2012 2:46 PM
  • Hi

    There is no logs regarding the connector in Operations Manager logs.

    Yes, we had set it up in OpsMgr as well.

    Thanks

    Kumaresan

    Wednesday, July 18, 2012 3:49 AM
  • Hi

    Could you clarify what you mean by "Not running" - in the Service Manager console, administration, connectors - what is the value for "Status" and "Finish Time" for the SCOM Alert connector?

    How have you configured SCOM to forward all alerts? If so, if you open a SCOM alert in SCOM and look at the History tab, do you see that the Alert has been forwarded to Service Manager?

    Do you have any other connectors deployed? E.g. Derdack enterprise Alert. If the other system "catches" the SCOM alert first then I have found that the alert doesn't get forwarded to Service Manager.

    Cheers

    Graham


    Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk
    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

    Wednesday, July 18, 2012 7:40 AM
  • A common fix is to uninstall and re install the connector from SCSM.  Worked for me last time I was having issues.

    Is your OpsMan action account a SCSM administrator?  It should be and if it isn't you would see this issue.


    - Get on the floor, do that dinosaur

    Wednesday, July 18, 2012 2:53 PM