Could-not-Install-the-Certificate-Package-error-when-adding-RIM-nodes

While adding a Rim node you see the following error "Could not install the certificate package. Try again or check the log for details.":

Check the repository_system log file found in %ProgramData%\Qlik\Sense\Logs\Repository\Trace 
 
20190223T014326.849-0500    ERROR    US1SXWN00563    System.Repository.Repository.Core.Certificates.CertificatePasswordVerificationWebService    20    83bfea24-27b9-4291-8b1a-b831e4c15c83    WMSERVICE\gfa82744    An error occured when installing certificate package. System.ArgumentException: Certificate of type Service was not valid!↵↓   at Qlik.Sense.Common.Security.SecuritySetup.CheckCert(DotNetCert signingCert, DotNetCert cert, CertType type)↵↓   at Qlik.Sense.Common.Security.SecuritySetup.InstallSecurity(DotNetCert root, DotNetCert service, DotNetCert client)↵↓   at Repository.Core.Certificates.CertificatePasswordVerificationWebService.HandleRequest(IHttpListenerRequestWrapper httpRequest, IHttpListenerResponseWrapper httpResponse, IHttpRecording httpRecording)                83bfea24-27b9-4291-8b1a-b831e4c15c83

Troubleshooting/Resolution Steps:-

1. Make sure service account has local Admin Right.

2- Make sure the service account has the right to all Qlik folders. (Check the user is having rights on related folders)

3- Make sure that the service account has the right to C:\ProgramData\Microsoft\Crypto folders. (Provide full control to service account)

4- Reboot the server

5- Make sure that the main security policies are disabled:

• System Cryptography: Force strong key protection for user keys stored on the computer (It was enabled in the customer's environment ) 
• System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing.
• All "Public Key Policies" are disabled. ( Security Settings > Public Key Policies).

6- Check if some TLS disabled (1.2, 1.0, SSL 3.0)

7- Try manually add the certificates.

8. Uninstall the RIM node and reinstall, i fissue persists, proceed to next step

9. Test by adding another RIM nodes and see if that works or get the same issue just to mitigate that issue is not with the central server.

Note:- Follow all the steps in sequence mentioned above and then disable the Cryptography policies which should fix the issue.