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?
Hi,
We are seeing repeated
System.Management.ManagementException: Provider not founderrors 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\FipsAlgorithmPolicyandSYSTEM\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?