*Update : Rollup 10 for SCOM 2012 SP1 fixes this issue (https://support.microsoft.com/en-us/kb/3071088)

*Update : Rollup 7 for SCOM 2012 R2 fixes this issue (https://support.microsoft.com/en-us/kb/3064919)

Issue:

You are deploying the OpsLogix Oracle Management Pack to an environment using a Windows 2008 R2 (or earlier) server as an Oracle Monitoring Node (1). Using the “Oracle IMP Configuration Dashboard” to setup the Oracle Instances monitoring you get an error message (3) “Object reference not set to an instance of an object” when clicking the “Test Connection” button (2).

 

Analysis:

This problem is related to the Dot Net version loader. This loader is built into the SCOM agent and will decide with wicht Dot Net version to load at runtime. The OpsLogix Oracle Management pack uses a Dot net 4.0 module. The agent still tryies to load it as a Dot Net 2.0 module which will result in an error.

Solution:

Since this is an internal SCOM agent issue, and not directly OpsLogix related, we have the following workarounds:

  • Microsoft recognised this issue and indicated that the next RU for SCOM 2012/SP1/R2 will include this loading fix.
  • You can manual install a SCOM Gateway instead of a SCOM agent.
    Note:
    • You don’t have to generate any certificates.
    • Do NOT run the Gateway Approval tool.
    • Use the Pending Management for approving the agent add (be sure the SCOM security setting allow this)
    • A SCOM Gateway will work exactly like a normal SCOM agent except it is tuned for handling higher workloads.

If you have any questions please contact our support team at Support@opslogix.com