Moogsoft Docs

SCOM Connector Troubleshooting

Q. What will be the SCOM Connector behavior if it reaches its threshold limit?

A. SCOM Connector will send only one alert to Moogsoft AIOps providing information that SCOM Connector has reached the threshold limit and it will send only the names of alerts which are fetched. To overcome this, you have to make one of the following changes in the config file:

  • Increase the value of "AlertStormThreshold".

  • Change the value of "LastPollTimeAlert", make its value closer to the current time value.

Q. What will happen to alerts when the connection between SCOM server and SCOM Connector (Advanced) is broken, and SCOM is in running state?

A. After successful connection establishment between SCOM Connector (Advanced) and SCOM, the SCOM Connector (Advanced) will fetch only those alerts which are generated during last 10 * "AlertPollCycleTime"(As per SCOMConnectorConfig.json) seconds.

For Example: Let's suppose a successful connection is established at 10:00 AM and default value of AlertPollCycleTime is 45 seconds. In this case, the SCOM Connector will fetch only those alerts which are generated between 9:52:30 AM (450 seconds before current time) to 10:00 AM (current time).

Q. I have added multiple SCOM Servers to a SCOM Connector (Advanced), then in case of one SCOM Server failure, from where the alerts will be fetched?

A. In case of multiple SCOM Servers, when the SCOM Server with highest priority goes down, the alerts are fetched from the SCOM Server having the second highest priority. And one alarming alert will be sent to Moogsoft AIOps indicating that the SCOM Server with highest priority is down.

Q. I have added multiple Moogsoft Servers, then in case of one Moogsoft Server failure, where the alerts will go?

A. Alert will be sent to other active Moogsoft AIOps if one of the Moogsoft AIOps, in a Multi Moog setup, goes down. And one alarming alert will be sent to the other Moogsoft AIOps indicating that the first Moogsoft AIOps Server is down.

Q. What are the parameters to differentiate the different SCOM Connectors registered on SCOM Server?

A. SCOM Connector registers itself on SCOM Server by the parameter "ConnectorDescription", its default value is SCOM Connector. This parameter is available in the file SCOMConnectorConfig.json, and you can change the value accordingly.

Receiving an error, "A referral was returned from the server"
29961230.png

If the above error comes, then follow the steps given to get it resolved:

  1. Enter gpedit.msc in the Run menu. The Local Group Policy Editor opens.

  2. Navigate to Computer Configuration > Windows Settings > Security Settings> Local Policies> Security Options

  3. In the right pane, double click on User Account Control: Only elevate executable that are signed and validated and select Disabled

  4. Click on Apply and then OK

  5. Restart Computer.

Error 1053: "The service did not respond in a timely fashion" when attempting to start, stop or pause a service

While starting, stopping or pausing a service, if you are getting the above error message i.e. Error 1053, then follow the steps below:

  1. Go to Start > Run > and type regedit.

  2. Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control.

  3. With the control folder selected, right click on the pane and select new DWORD Value.

  4. Name the new DWORD: ServicesPipeTimeout

  5. Right-click ServicesPipeTimeout, and then click Modify.

  6. Click Decimal, type '180000', and then click OK

  7. Restart the computer.

Receiving an error, "Failed to Process Alerts"

In the Connector logs, if you are facing the above error messages, then you have to change the "PollCriteriaDateFormat" to "dd/MM/yyyy HH:mm:ss" (default format is "MM/dd/yyyy HH:mm:ss")in the SCOMConnectorConfig.jsonfile.

Connector not able to fetch alerts in SCOM 2016 using Load Balancer

If Load Balancer is not working with SCOM 2016, then you can validate the connectivity of Load Balancer by executing the below powershell commands. These commands should be executed on machine where connector is installed.

  • Get-SCOMManagementGroupConnection

Execute this command to create connection with the Management Group, if there is no connection already. Executing this command (no parameters required) will either connect to the Management Group or will give you the status as Active if already connected.

  • Get-SCOMAlert -ComputerName <HostName>

Here HostName can be the SCOM server hostname or Load Balancer Name configured in the connector. If the command runs successfully and bring alerts, then the connector should also get alerts, otherwise there is some issue with the connector. If command fails to get alerts, then the problem will be with configuration and not with the connector.

Below is the snapshot of successful execution of command Get-SCOMAlert -ComputerName <HostName>:

29961228.png

In case of connectivity issue with Load Balancer in SCOM 2016, the connector will not fetch alerts. In this case, connector will work with Computer Hostname and not with Load Balancer.