This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

[Greg]

As soon as a dropped a RadAsyncUpload control on the page, I started receiving the error above (the title).  If I view the application locally it runs just fine.  I run it on the server, it displays the error.  On the server (Windows Server 2008 R2 Standard, IIS 7.5) the registry key HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > LSA > FipsAlgorithmPolicy is enabled, locally it is not.  I read that rad controls are FIPS compatibile and am wondering why this is giving me issues.  I have tried adding the machineKey with 3DES and still get error. I have set debug="false" in web.config and still get error.  I am unable to remove the registry key.  Any guidance on what to do to get this to work?

Application Web.Config
...
<

system.web>       
  <customErrors mode="Off" />      
  <compilation debug="true" strict="false" explicit="true" targetFramework="4.5" />       
  <httpRuntime targetFramework="4.5" />     
</system.web>
...

Just updated my control set to the Q3 2012.

[Plamen]

Hi Greg,

 
The issue described looks like a known issue that is observed when one serialize generic types as described in this article. Please try the suggestions there and let us know if you still observe the error.

Hope this will be helpful.

Regards,
Plamen
the Telerik team

[Greg]

When attempting to install that hotfix I received this error:

The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch.

I'm running Windows Server 2008 R2 Standard SP1 x64.
My System.Runtime.Serialization for .Net 3.0 = 3.0.4506.5452

Any ideas on where to go from here?

[Plamen]

Hello Greg,

 
Please refer to this blog post where is provided extended explanation how we recommend to Updating RadControls for ASP.NET AJAX to another version or license.

Hope this will be helpful.

All the best,
Plamen
the Telerik team

[Greg]

I have followed the guide provided and it still  didn't work.  I am also having troubles exporting a radgrid to pdf.  Locally I have the registry setting = 0 and it works.  When I set it = 1 then I received the error. According to this link, "Starting from Q3 2011, RadControls for ASP.NET AJAX offically supports the FIPS standard."  but then the next line in the document is "Please note that PDF export is not FIPS compliant."

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 Telerik.Pdf.Security.SecurityManager.CreateOwnerEntry(SecurityOptions options) at Telerik.Pdf.Security.SecurityManager..ctor(SecurityOptions options, FileIdentifier fileId) at Telerik.Web.Apoc.Pdf.PdfCreator.SetOptions(PdfRendererOptions options) at Telerik.Web.Apoc.Render.Pdf.PdfRenderer.StartRenderer() at Telerik.Web.Apoc.Fo.FOTreeBuilder.Parse(XmlReader reader)

Does the export to pdf use MD5?   I'm at a loss on where to go from here.  I really do not want to drop these controls from our current and future projects.

[Daniel]

Hello Greg,

Our PDF export is based on 1.3 specification which does not allow FIPS-compliant algorithms to be used. We are currently researching other options, but I'm afraid I could not give you more specific information at this point. This is not something a "quick fix" could achieve but you can be sure that we will not ignore the problem.
Please excuse us for any inconvenience caused.

Best regards,
Daniel
the Telerik team