You notice that even though your Spectrum SCOM Connector service is running, you are not seeing any alerts in Spectrum from SCOM. Looking at the alerts in the SCOM Manager, you notice the alerts are not being forwarded to the registered Spectrum SCOM Connector.
Enable the SCOM Connector Debug by performing the steps below will reveal the following error in the SCOMConnector\CONNECTOR_DEBUG.OUT file:
2/23/2018 8:38:38 PM: SCOMSpectrumMgr::isConnected() - alarmDomain is available
2/23/2018 8:38:38 PM: SCOMSpectrumMgr::isConnected() - callbackRegistered = 1, ss_switch = False, isPrimary = 1
2/23/2018 8:38:38 PM: Getting new/updated alerts from SCOM...
2/23/2018 8:38:38 PM: Received 500 alerts from SCOM
2/23/2018 8:38:38 PM: SCOMWorker::run() - processing alert: https://scom.####.com:443/OperationsManager/default.aspx?DisplayMode=Pivot&AlertID=5e65d9c2-5351-4d2c-ae43-3dd8cffeb7fd, alarmID = , curResState = -1, alert->ResState = 255, alert->RepeatCount = 3
2/23/2018 8:38:38 PM: Using PrincipalName: null
2/23/2018 8:38:38 PM: Using CustomField1:
2/23/2018 8:38:38 PM: clearing alarm on model 0x629b5906
2/23/2018 8:38:38 PM: clearing alarm on model 0xaaa399a6
2/23/2018 8:38:38 PM: FAILURE: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at CsCModelDomain.CsCModelPropList_var.{dtor}(CsCModelPropList_var* )
at ___CxxCallUnwindDtor(IntPtr pDtor, Void* pThis)
at SCOMSpectrumMgr.clearAlarms(SCOMSpectrumMgr* , String modelName, String alertUrl)
at SCOMWorker.run()
2/23/2018 8:38:38 PM: Failed to process SCOM alert updates, waiting 30 seconds for services to become available...
The System.AccessViolationException is a .Net exception that gets thrown when there is an attempt to read from or write to protected memory. If several read or write operations have occurred through bad pointers, memory may be corrupted. Based on previous Sustaining Engineering review of the SCOM Connector code, this is likely the result of running an older SCOM Connector with a newer SpectroSERVER, and thus the conflict.
The SCOM Connector and SpectroSERVER must be the same release. Therefore, anytime you upgrade the SpectroSERVER, you must also upgrade the SCOM connector.
SpectrumSCOMConnector.exe –remove
”SpectrumSCOMConnector.exe –instal
l”. Reference the "Install the SCOM Connector" section of the documentation for more information.