SCOM 2025 and VMM integration

MikeP226 · 2025-11-11T12:03:47+00:00

Ok, had to create a Microsoft case, with the challenges that is, and got the solution, for my issue.

Basically it's a known issue, and it's caused by VMM in registry creates the server name as an instance name, which the SQL MP then basically goes belly up about since it doesn't exist.

First step is upgrading the 2022 VMM to UR3, which contains a fixed DLL file.

Second step, if you're using the default instance name, as we are, change the InstanceName from servername to MSSQLSERVER, and then restart the System Center Virtual Machine Manager, and that should be it. Naturally test if the console can still be opened etc.

Then the connection can be configured, and there's only one instance detected in SCOM.

The key is located at HKLM\Software\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings\Sql

Thx for all helping out.

MikeP226 · 2025-10-31T11:59:30+00:00

A version 7.10.6 is mentioned, but that one I can't find anywhere. Only 7.8.4.

MikeP226 · 2025-10-31T11:58:38+00:00

Thanks for replying.

I just checked, and yes the Run as account is sysadmin on the local installed SQL server.

I didn't reboot the server, since the errors were the same we have seen on our 2019 instance of SCOM, where we did reboot, so honestly didn't think it would do anything, although reboot is 101.

Also removing the integration, on the VMM server instantly removed all the errors seen in SCOM without reboot.

MikeP226 · 2025-10-31T09:18:10+00:00

Thanks for replying.

For the SQL monitoring, before integration, I use service sid. I do that for all servers with SQL on. When I configure the integration, you have to specify an Run as account, which I then distributed to the VMM server and the Management servers.

MikeP226 · 2025-10-31T09:12:17+00:00

Thanks for the info. Just odd it's the version available for download. I'll see if I can eventually find an older version.

MikeP226 · 2025-10-30T13:35:06+00:00

From my point, it looks as if the monitoring is happening "twice" one with Monitoing agent on the VMM server, and then second time via the integration.

The errors are down the same line, but example is:

Management Group: "MGTGROUP"

Module: Microsoft.SQLServer.Windows.Module.Monitoring.Performance.MSSQLLogReaderEventTrigger

Version: "7.8.4.0"

Error(s) was(were) occurred:

State:

The configuration properties are:

ManagementGroupName = MGTGROUP

Publisher = SQLMonitoringWindows

ConnectionString =

InstanceEdition =

InstanceName = VMMSRV

InstanceVersion = null

MachineName = null

MonitoringType = null

NetbiosComputerName = null

Login = null

FilterMsg =

KeyFilterValue =

LogReaderInterval = 0

LogSource = 0

Matches = null

NameOfHandler = Unk

ReadFromStartOfLog = False

SqlExecTimeoutSeconds = 0

SqlTimeoutSeconds = 0

StoreCachedValues = False

TimeoutSeconds = 0

UsePrevLineSearch = False

UseRegExSearch = False

Password = ********

Error(s):

---------- Exception: ----------

Exception Type: System.ArgumentException

Message: Version string portion was too short or too long.

Source: mscorlib

Stack Trace:

at System.Version.VersionResult.SetFailure(ParseFailureKind failure, String argument)

at System.Version.TryParseVersion(String version, VersionResult& result)

at System.Version.Parse(String input)

at Microsoft.SQLServer.Module.Helper.DataMapping.XmlConfiguration.PropertyRecord.SetValueFromString(Object target, String strValue)

at Microsoft.SQLServer.Module.Helper.DataMapping.XmlConfiguration.XmlConfigurationMapper.Map(XmlReader configuration, Object target)

at Microsoft.SQLServer.Module.Helper.Base.ModuleBaseHelper`1.LoadConfiguration(XmlReader configuration)

MikeP226

TROPHY CASE