I get the following error on our server:
Unhandled Exception: System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
at OfficeOpenXml.ExcelPackage.Save()
at OfficeOpenXml.ExcelPackage.SaveAs(Stream OutputStream)
We are required by security regulations to have the FIPS compliance check turned on in the OS. I'm not sure why spreadsheets are generated without error and others get this. You'll note in the error I'm not using an overload with a password parameter so there is no encryption being used to my knowledge. Any help would be appreciated. PLEASE do not suggest we disable FIPS testing in the OS... that is not an option unfortunately due to security regulations beyond my control. (Ironic how security regulations force us to use less secure encryption algorithms)
Comments: Is the other issue you speak of by any chance the issue with the Network Service account being listed as one with a profile in the registry but lacking the ability to create the required IsolatedStorage directory in it's profile? We had that issue as well and have worked around it by manually creating the IsolatedStorage directory in the Default User profile on the servers.
Unhandled Exception: System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
at OfficeOpenXml.ExcelPackage.Save()
at OfficeOpenXml.ExcelPackage.SaveAs(Stream OutputStream)
We are required by security regulations to have the FIPS compliance check turned on in the OS. I'm not sure why spreadsheets are generated without error and others get this. You'll note in the error I'm not using an overload with a password parameter so there is no encryption being used to my knowledge. Any help would be appreciated. PLEASE do not suggest we disable FIPS testing in the OS... that is not an option unfortunately due to security regulations beyond my control. (Ironic how security regulations force us to use less secure encryption algorithms)
Comments: Is the other issue you speak of by any chance the issue with the Network Service account being listed as one with a profile in the registry but lacking the ability to create the required IsolatedStorage directory in it's profile? We had that issue as well and have worked around it by manually creating the IsolatedStorage directory in the Default User profile on the servers.