Share via

SCOM 2019 SQL AlwaysOn Troubleshooting

Andy 1 Reputation point
2021-03-24T09:26:18.807+00:00

Hello,

We have a deployment of SCOM 2019 UR2 & have recently moved to a SQL 2017 AlwaysOn configuration, which I followed the the following documentation:

https://learn.microsoft.com/en-us/system-center/scom/manage-sqlserver-communication?view=sc-om-2019

When the SQL Server is on the primary, SCOM will start with no issues which would indicate that the configuration is correct, however when SQL fails over to the secondary SCOM will fail to start, the error message states that the connection was actively refused.

All Logins are present on the secondary SQL node, CLR has been enabled & the database has been made trustworthy, the port is open from the SCOM Management Server to the SQL Server. Any thoughts on what else to check?

System Center Operations Manager
System Center Operations Manager
A family of System Center products that provide infrastructure monitoring, help ensure the predictable performance and availability of vital applications, and offer comprehensive monitoring for datacenters and cloud, both private and public.
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. System Center guy 691 Reputation points
    2021-03-24T09:45:57.047+00:00

    I think that you should configure your SCOM database server to AlwaysOn availability Group. Please refer to Deploying SCOM into the AlwaysOn Availability Group.
    https://social.technet.microsoft.com/wiki/contents/articles/23021.deploying-scom-into-the-alwayson-availability-group.aspx

    roger

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.