08-01-2012 03:42 PM
I just installed the 3.0.2 version of the 488-2. I went to run the sample C# project and received the following error: The type initializer for 'NationalInstruments.NI4882.Internal.GpibDll' threw an exception. Further inspection of the exception revealed: This implementation is not part of the windows FIPS validated cryptographic algorithms. I checked both my visual studio and windows 7 settings and it is disabled. Anyone have any ideas. This error occurs when I instantiate a device. Thanks in advance
08-02-2012 05:48 PM
Have you tried reinstalling the drivers? It sounds like it's not finding the dll correctly.
Also, what specific example are you using and are there other examples that you have tried?
08-03-2012 04:17 PM
I'll give that a shot come Monday and report back.
Thanks
08-06-2012 12:24 PM
I tried the following samples none of which worked: Notify, SimpleAsynchronousReadWrite, SimpleReadWrite. I tried doing a repair of the installation as well trying the samples and still I received the crypto error. I have checked the registry settings and the FIPS is disabled.
08-07-2012 05:18 AM
Here is the complete error:
The type initializer for 'NationalInstruments.NI4882.Internal.GpibDll' threw an exception.
System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
at System.Security.Cryptography.MD5CryptoServiceProvidor..ctor()
at NationalInstruments.NI4882.Internal.GpibDll..ctor()
at NationalInstruments.NI4882.Internal.GpibDll.ibdev(Int32 boardID, Int32 pad, Int32 sad, Int32 tmo, Int32 eot, Int32 eos)
at NationalInstruments.NI4882.Internal.DeviceImpl..ctor(Int32 boardNumber, Byte primaryAddress, Byte secondaryAddress, TimeoutValue timeoutValue, Boolean setEndOnWrite, Boolean endOfStringCharacterUsedOnRead, Object sender)
at NationalInstruments.NI4882.Internal.DeviceImpl..ctor(Int32 boardNumber, Byte primaryAddress, Byte secondaryAddress, TimeoutValue timeoutValue, Object sender)
at NationalInstruments.NI4882.Internal.DeviceImpl..ctor(Int32 boardNumber, Byte primaryAddress, Byte secondaryAddress, TimeoutValue timeoutValue, Object sender)
at NationalInstruments.NI4882.Internal.Device..ctor(Int32 boardNumber, Byte primaryAddress, Byte secondaryAddress)
08-07-2012 05:19 AM
Reinstalling did not work here is the complete error:
The type initializer for 'NationalInstruments.NI4882.Internal.GpibDll' threw an exception.
System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
at System.Security.Cryptography.MD5CryptoServiceProvidor..ctor()
at NationalInstruments.NI4882.Internal.GpibDll..ctor()
at NationalInstruments.NI4882.Internal.GpibDll.ibdev(Int32 boardID, Int32 pad, Int32 sad, Int32 tmo, Int32 eot, Int32 eos)
at NationalInstruments.NI4882.Internal.DeviceImpl..ctor(Int32 boardNumber, Byte primaryAddress, Byte secondaryAddress, TimeoutValue timeoutValue, Boolean setEndOnWrite, Boolean endOfStringCharacterUsedOnRead, Object sender)
at NationalInstruments.NI4882.Internal.DeviceImpl..ctor(Int32 boardNumber, Byte primaryAddress, Byte secondaryAddress, TimeoutValue timeoutValue, Object sender)
at NationalInstruments.NI4882.Internal.DeviceImpl..ctor(Int32 boardNumber, Byte primaryAddress, Byte secondaryAddress, TimeoutValue timeoutValue, Object sender)
at NationalInstruments.NI4882.Internal.Device..ctor(Int32 boardNumber, Byte primaryAddress, Byte secondaryAddress)
08-07-2012 07:27 PM
I have examples for multiple versions of the .NET runtime, which are you trying to run?
Also, what hardware are you trying to interface with?
05-06-2013 10:35 AM
Hello, I'm also getting this error. I'm using NI488.2 version 3.0 on a computer that requires FIPS compliant crypto algorithms.
Any ideas? Thanks, Tom
05-07-2013 02:47 PM
Hi Tom,
Quick check: are you using Visual Studio 2010? It looks like this is a known issue addressed in the following KB:
Why Does Visual Studio 2010 Fail to Build When FIPS Compliance Is Enabled in Windows?
http://digital.ni.com/public.nsf/allkb/990781D72A73D65586257968006B402B?OpenDocument
Let us know if this applies to you or not.
Cheers,
Andy C.
Applications Engineering
National Instruments
05-07-2013 09:26 PM
Hi Andy, thanks for the reply.
No, this is not the issue I'm having. The project I'm working on is VS 2008 and it compiles fine. I'm able to cause the exception by setting the FIPSALGORITHMPOLICY key in the registry on my dev computer (clearing it is not an option on our production computers).
I'd like to still use the NI488.2 drivers, but since I haven't seen the issue with NI's VISA drivers, I'm in the process of converting my code to use it.
-Tom