Joined: 08 Jun 2012
|Posted: Fri Jun 08, 2012 5:41 pm Post subject: FIX CRASH with System.Reflection.TargetInvocationException
|I had a few hours of head-scratching after installing the demo bundle. Whilst the Performance Profiler was fine, the Memory Profiler crashed on load with the following exception...
The exception message was (something like)...
"This implementation is not FIPS compliant ... blah, blah-de-blah"
The associated callstack began with a Reflected call to a SHA256 constructor and ended with the exception described above.
I couldn't find anyone else with similar symptoms but finally tracked the problem to my own Group Policy options in Vista.
TO FIX THIS PROBLEM (wait for Red Flag to release a FIPS compliant version, or...)
1. Open an instance of MMC and add the 'Security Options' snap-in
2 Navigate to...
Local Computer Policy|Computer Configuration|Windows Settings|Security Settings|Local Policies|Security Options
3. 'Disable' the setting
System cryptography: Use FIPS compliant algorithms for encryption, hashing & signing.
NOTE THAT: this is NOT a default setting and previously I had enabled it myself when attempting to tighten my security.
No restart required.