Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Invalid Activation Code when installing Trend Micro Safe Lock Intelligent Manager (SLIM) due to FIPS Mode

    • Updated:
    • 4 Mar 2021
    • Product/Version:
    • Safe Lock 2.0
    • Platform:
Summary

Users may experience the following error when installing SLIM:

"The Activation Code is not valid. Type a valid Activation Code and try again."

image.png

Details
Public

From the following log entries, it can be seen that AC validation failed due to Windows Platform FIPS validating cryptographic algorithms.

02-01 16:25:05 [1] DEBUG [Debug.DebugUtil::_InvokeMethodFast] - root: C:\Users\opsadmin\AppData\Local\Temp\{65F111B1-CC32-411D-B1FB-C14F4C134CE7}\{B038D1BD-D5D7-4FE6-97AB-43268E1A95D7}\
02-01 16:25:05 [1] DEBUG [Debug.DebugUtil::_InvokeMethodFast] - input parameters:
02-01 16:25:05 [1] DEBUG [Debug.DebugUtil::_InvokeMethodFast] - arg[0] = -src
02-01 16:25:05 [1] DEBUG [Debug.DebugUtil::_InvokeMethodFast] - arg[1] = C:\Users\opsadmin\AppData\Local\Temp\{65F111B1-CC32-411D-B1FB-C14F4C134CE7}\{B038D1BD-D5D7-4FE6-97AB-43268E1A95D7}\
02-01 16:25:05 [1] DEBUG [Debug.DebugUtil::_InvokeMethodFast] - arg[2] = -check
02-01 16:25:05 [1] DEBUG [Debug.DebugUtil::_InvokeMethodFast] - arg[3] = -ac_valiation
02-01 16:25:05 [1] DEBUG [Debug.DebugUtil::_InvokeMethodFast] - arg[4] = TE-8GCW-LNMZD-KKRNH-73X7J-Q2W7G-YYFLQ
02-01 16:25:05 [1] DEBUG [Debug.DebugUtil::_InvokeMethodFast] - ===> AcValidation()
02-01 16:25:05 [1] WARN  [Core.TMSLCore::DoInitialize] - [TMSLCore] Initializing
02-01 16:25:05 [1] WARN  [Core.TMSLCore::DoInitialize] - [TMSLCore] self location: C:\Users\opsadmin\AppData\Local\Temp\{65F111B1-CC32-411D-B1FB-C14F4C134CE7}\{B038D1BD-D5D7-4FE6-97AB-43268E1A95D7}\TMSLCore.dll
02-01 16:25:05 [1] WARN  [Core.TMSLCore::DoInitialize] - [TMSLCore] config path: C:\Users\opsadmin\AppData\Local\Temp\{65F111B1-CC32-411D-B1FB-C14F4C134CE7}\{B038D1BD-D5D7-4FE6-97AB-43268E1A95D7}\config.xml
02-01 16:25:05 [1] FATAL [Core.TMSLCore::DoInitialize] - [TMSLCore] initialization failed, config error
System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
   at System.Security.Cryptography.RijndaelManaged..ctor()
   at Cryptography.AesProvider.AesDecryptTransfrom(String key, String iv)
   at Cryptography.AesProvider.DecryptAES256(String encrypted)
   at Core.TMSLCore.ReadConfig(String configFilePath)
   at Core.TMSLCore.DoInitialize()
02-01 16:25:07 [1] INFO  [Core.TMSLCore::ProcMessage] - got message: HANDLER_ID_LICENSE->(MsgId=PEEK_ACTIVATION_CODE)
02-01 16:25:07 [1] ERROR [Core.TMSLCore::ProcMessage] - 
System.NullReferenceException: Object reference not set to an instance of an object.
   at Core.TMSLCore.ProcMessage(eHandlerId HandlerId, Int32 MsgId, Object& MsgBody)
02-01 16:25:07 [1] ERROR [Debug.DebugUtil::_InvokeMethodFast] - save ac failed! - error: -1
02-01 16:25:07 [1] DEBUG [Debug.DebugUtil::_InvokeMethodFast] - result[0]= -1
02-01 16:25:07 [1] DEBUG [Debug.DebugUtil::_InvokeMethodFast] - ------- Done -------
02-01 16:27:54 [1] DEBUG [Debug.DebugUtil::_InvokeMethodFast] -

To resolve this problem, disable "System cryptography: Use FIPS complaint algorithms for encryption, hashing, and signing" in Local Policy and re-attempt to install.

image.png

Premium
Internal
Partner
Rating:
Category:
Troubleshoot
Solution Id:
000285851
Feedback
Did this article help you?

Thank you for your feedback!


*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.