QlikView Management Service logs return Exception while decrypting: Bad Data error messages

[Chip_Matejowsky]

The QlikView Management Service logs contain the following error entry:

Error Exception while decrypting. EncryptedText length=8 chars Exception=System.Security.Cryptography.CryptographicException: Bad Data. || || at System.Security.Cryptography.CryptographicException.ThrowCryptographicException(Int32 hr) || at System.Security.Cryptography.Utils._DecryptData(SafeKeyHandle hKey, Byte[] data, Int32 ib, Int32 cb, Byte[]& outputBuffer, Int32 outputOffset, PaddingMode PaddingMode, Boolean fDone) || at System.Security.Cryptography.CryptoAPITransform.TransformFinalBlock(Byte[] inputBuffer, Int32 inputOffset, Int32 inputCount) || at System.Security.Cryptography.CryptoStream.FlushFinalBlock() || at System.Security.Cryptography.CryptoStream.Dispose(Boolean disposing) || at System.IO.Stream.Close() || at SolutionGlobal.Security.CryptoAlgorithm.Decrypt(EncryptedSecret encryptedSecret, Boolean isCurrentAlgorithm)

Resolution

• Exclude QlikView folders from Antivirus applications or other real-time system scanning utilities. See QlikView Folders and files to exclude from antivirus scanning.
• If using Certificate Trust for authentication between the QlikView Server services, verify that this certificate configuration is still valid.
• Restore the QVPR to a date prior to when the error in the QlikView Management Service log was first returned. See How To: Restore the QVPR From Backup or Recreate the QVPR.

Cause 

Antivirus software or other other real-time system scanning utilities may cause disruption if files needed by QlikView services are being locked for scanning / change monitoring. When using Certificate Trust for services authentication, the certificates may have expired or removed on the server running the QlikView Management Service (QMS). This will prevent the QMS from reading encrypted data in the QVPR, such as passwords (used in tasks and other areas of the QMC), resulting in the error message.

The log entry itself does not reference the "bad data", only a string length of the problematic string, which does not help in narrowing down the malformed data and correct it. Furthermore it is not advised to manually edit the QVPR and doing so will result in an unsupported environment.

Related Content 

Anti-virus, Endpoint detection and response and Advanced Threat Prevention exclusions for Qlik produ... 
Configuring servers with digital certificates 

Environment

QlikView