System.TypeInitializationException

Ninendal

Hi,

Installing SQLMonitor 4.0 on Windows 2012R2 platform with SQL 2014 as backend results in an exception;

DEBUG - Done checking SQL Server Version...
DEBUG - Validation returned an error: The type initializer for 'Settings' threw an exception.
DEBUG - Checking credentials are windows credentials...
ERROR - Exception encountered during login check
System.TypeInitializationException: The type initializer for 'Settings' threw an exception. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
at System.Security.Cryptography.MD5CryptoServiceProvider..ctor()
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle._InvokeConstructor(Object[] args, SignatureStruct& signature, IntPtr declaringType)
at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Security.Cryptography.CryptoConfig.CreateFromName(String name, Object[] args)
at System.Security.Cryptography.MD5.Create()
at MvcMiniProfiler.MiniProfiler.Settings..cctor()
--- End of inner exception stack trace ---
at MvcMiniProfiler.MiniProfiler.Settings.EnsureProfilerProvider()
at MvcMiniProfiler.MiniProfiler.get_Current()
at #Qfdc.#agdc.#OZx(String )
at #Qfdc.#agdc.#N9f(String )
at #Mhw.#3iw.#Jfb.#Iq0()
at #Hgv.#Xgv.#BKg[#NrPb](Func`1 )
at #Mhw.#dmQ.#BKg[#NrPb](Func`1 )
at #Mhw.#3iw.#Hq0(#dmQ )

Any suggestions besides that MD5 is not secure and obsolete

Brian Donahue

The root cause of this is that Redgate licensing does not support FIPS (Federal Information Protection Standard). If you are allowed to disable FIPS, you should be able to do it in the computer's local security policy.