While calling LicensingFactory.GetLicensing() method gives SessionException which looks like below.
Tamper detected: IHRfX3VUNUZNOHVGaHRIdUFqNHQzUHcxd3FmY2xFOCAgZmFsc2UgeyBbInRfXzRFd3drclhVY2JHS1d1Rm9MQXN0MkZCSUY1USJdID0gdHJ1ZSxbInZpc3VhbF9zdHVkaW8iXSA9IHRydWUsWyJ0X19hbXpxOUJvdzIxTmxIRXNKUnZZTkpMVXk1SXMiXSA9IDFoOGUzRVVISXNnaE51dW StackTrace: FlxDotNetClient.SvcSessionException: MID=0, SID=0, EID=6: Tamper detected: IHRfX3VUNUZNOHVGaHRIdUFqNHQzUHcxd3FmY2xFOCAgZmFsc2UgeyBbInRfXzRFd3drclhVY2JHS1d1Rm9MQXN0MkZCSUY1USJdID0gdHJ1ZSxbInZpc3VhbF9zdHVkaW8iXSA9IHRydWUsWyJ0X19hbXpxOUJvdzIxTmxIRXNKUnZZTkpMVXk1SXMiXSA9IDFoOGUzRVVISXNnaE51dWZZaUY1aDJGdXM4LH0g ---> FlxClientCommon.SessionException: MID=0, SID=0, EID=6: Tamper detected: IHRfX3VUNUZNOHVGaHRIdUFqNHQzUHcxd3FmY2xFOCAgZmFsc2UgeyBbInRfXzRFd3drclhVY2JHS1d1Rm9MQXN0MkZCSUY1USJdID0gdHJ1ZSxbInZpc3VhbF9zdHVkaW8iXSA9IHRydWUsWyJ0X19hbXpxOUJvdzIxTmxIRXNKUnZZTkpMVXk1SXMiXSA9IDFoOGUzRVVISXNnaE51dWZZaUY1aDJGdXM4LH0g at Z.c42b7e595b624b067271ba80492e113a7.c78c4293b94c9379b23066a8444b66e56(UInt16& c1e7cda42c1344f35746723eda06c39c9, Byte[] c306c26e632118e6bc1a0485b6d29b40c) --- End of inner exception stack trace --- at Z.c42b7e595b624b067271ba80492e113a7.c78c4293b94c9379b23066a8444b66e56(UInt16& c1e7cda42c1344f35746723eda06c39c9, Byte[] c306c26e632118e6bc1a0485b6d29b40c) at FlxLicensingClient.Error.Initialize() at (cf5874f1fbfa57a7f6f6a3aad40bc9270 ) at FlxDotNetClient.LicensingFactory.GetLicensing(ILicensingOptions licensingOptions)
Diagnosis:
It has been found that this error occurs mostly in the cases where client machine is missing certificates or its trusted root certificate chain is broken and hence signature of FlxCore.dll/FlxCore64.dll doesn't gets verified.
This can be checked by running Microsoft's tool signtool with the "verify /pa" option from command prompt (For example: signtool verify /pa FlxCore64.dll). Running this should produce system error.
Solution:
1. Try running windows update or apply the pending windows patches and reboot the system. This should rebuild the certificate chain of system.
2. Verify again the certificate chain by running signtool verify /pa FlxCore64.dll and this should pass.
3. If still you are getting Tamper detected: FlxDotNetClient.SvcSessionException: MID=0, SID=0, EID=6 error, then it may need further debugging, so please reach out to support.
Additional Information:
In Certain machines it is found that, the FlxCore64.dll code signing certificate is not being trusted or added automatically to Machine trusted certificate store causing the error. In such cases, you can right click the dll go to properties Digital Signatures and export the certs in Base 64 encoded X.509 (CER) format and then install to the local machine store to resolve the issue.
