Cannot Activate NovaBACKUP due to FIPS Encryption .NET error
Last Updated: Nov 02, 2015 12:21PM PST
Cannot Activate NovaBACKUP due to FIPS Encryption .NET error:
The "FIPS compliancy mode" security policy setting will break the on-line and off-line activation in NovaBACKUP PC/Server/Business Essentials software. This can happen either during installation OR after being installed and changing keys/changing from trial mode to registered, etc..
If "FIPS compliancy mode" is ENABLED in the Local Security Policies area of “gpedit.msc” it will cause NovaBACKUP SMB activation to fail. The "FIPS compliancy mode" is DISABLED by default in all editions of Windows. "FIPS compliancy mode" is required by certain entities as so can be part of a system wide policy that is forced/enacted on machines and may not be easy to disable, you should at least be able to see if it is however enabled. When you Enable this "FIPS compliancy mode" setting it will A. force off-line activation every time even if you have internet connection and all firewalls disabled, and B. will produce a blank Hardware Key which produces in the end an error message “Activation failed because of unknown reason.” This probably affects all recent versions of NovaBACKUP that utilize .NET Framework 3.51. This policy edit breaks something in the way that .NET Framework is used by NovaBACKUP for activation.
Here are all of the screen shots that make this issue occur, all I did was enable that policy setting and simply attempt to activate NovaBACKUP v17.1.804 with a license key (this license key that you see in the screen shots is not valid so do not attempt to utilize that key):
The work-around for this is to disable "FIPS compliancy mode" in the policy settings of for the PC(s) with NovaBACKUP on them. It is possible that the mode can be re-enabled on the machine after installing and activating NovaBACKUP for which this article was written to work-around.