Sysprogs forums › Forums › VisualGDB › System.TypeInitializationException on Windows Server 2016
- This topic has 2 replies, 2 voices, and was last updated 5 years, 4 months ago by
support.
-
AuthorPosts
-
December 6, 2018 at 16:03 #22989
curtis.hendrix
ParticipantI’m setting up a build agent on a Windows Server 2016 box. Visual Studio 2017 Professional and VisualGDB 5.4.10.2582 are installed.
Whenever I start Visual Studio, the following exception happens and VisualGDB does not get loaded into Visual Studio:
VisualGDB version: 5.4.10.2582 ------------------ System.TypeInitializationException ------------------ System.TypeInitializationException: The type initializer for 'o81' 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.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) 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 wf2..ctor(Byte[] b, Int32 a, Byte[] c) at o81..ctor() at o81..cctor() --- End of inner exception stack trace --- at VisualGDB.VSPackage.VisualGDBPackageCommon.DoInitialize(Boolean deferred) at VisualGDB.VSPackage.VisualGDBPackageCommon.OnShellPropertyChange(Int32 propid, Object var) ------------------ Inner exception ------------------ ------------------ System.Reflection.TargetInvocationException ------------------ 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.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) 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 wf2..ctor(Byte[] b, Int32 a, Byte[] c) at o81..ctor() at o81..cctor() ------------------ Inner exception ------------------ ------------------ System.InvalidOperationException ------------------ System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms. at System.Security.Cryptography.MD5CryptoServiceProvider..ctor()
December 6, 2018 at 16:49 #22990curtis.hendrix
ParticipantFigured out the issue. Using FIPS compliant algroithms needs to be disabled:
“Or else, go to Local Security Policy (Start -> Run -> secpol.msc) and then go to “Security Settings -> Local Policies -> Security Options” and on the right-side windows you should see the policies in that please look for the Policy “System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing” and checked the security thing and it should be Enabled.”
December 7, 2018 at 05:08 #22992support
KeymasterHi,
Good to know it works. Just in case anyone else runs into the same problem, here’s another workaround to this: https://blogs.msdn.microsoft.com/shawnfa/2008/03/14/disabling-the-fips-algorithm-check/
-
AuthorPosts
- You must be logged in to reply to this topic.