How can we help you today? How can we help you today?

Redgate Monitor – WMI error "Provider not found" when reading FipsAlgorithmPolicy

Hi,

We are seeing repeated System.Management.ManagementException: Provider not found errors logged on the VM hosting the Redgate Monitor Base Monitor. The errors occur when Redgate Monitor attempts to read local security-related registry values via WMI (e.g. SYSTEM\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy and SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Client). SQL Server monitoring otherwise appears to function normally.

Would like to know:
• which WMI provider Redgate Monitor uses for these local registry checks on the Base Monitor?
• whether failures for missing or restricted keys are expected and safe to ignore (particularly on hardened systems)?
• if there are any recommended configuration changes or exclusions for the Base Monitor VM?

MilChia
0

Comments

1 comment

Sort by
  • Tom Claringbold
    Official comment

    Hi MilChia,

    Redgate Monitor performs its Windows security‑related checks through WMI, using the standard registry provider (StdRegProv) in the root\cimv2 namespace. When certain registry locations such as LSA or SCHANNEL keys are missing or restricted (which is common on hardened systems) WMI can return “Provider not found” or related errors. These are external WMI issues rather than Redgate Monitor faults, and as long as normal SQL Server and machine monitoring continue to function, they are safe to ignore. If needed, you can verify WMI health (winmgmt /verifyrepository) and ensure the Base Monitor service account has sufficient WMI permissions, but it is not recommended to re‑enable deprecated or intentionally restricted security keys. These warnings typically indicate expected behavior on secured systems rather than a problem requiring remediation.

    Hope this answers your questions but please let me know if any further concerns on this.

    Some additional resource from Microsoft on this here: https://techcommunity.microsoft.com/blog/askperf/wmi-missing-or-failing-wmi-providers-or-invalid-wmi-class/375485

    Tom Claringbold

Add comment

Please sign in to leave a comment.