SQL Error - Exception has been thrown by the target of invocation



Turns out the client had enabled FIPS Algorithm Policy on the GPO, disabling the FIPS policy temporarily allowed the scan to complete. Thanks to all who were involved!!!!


Get the Resultant Set of Policy from the machine to verify if FIPS is in GPO (cmd:  RSOP)



Computer Configuration -> Windows Settings -> Local Policies -> Security Options -> System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing





FIPS Enabled





FIPS Disabled



Have more questions?

Contact us

Was this article helpful?
0 out of 0 found this helpful

Provide feedback for the Documentation team!

Browse this section