vanroy 0 Posted December 23, 2016 Share Posted December 23, 2016 Hey Team any idea for, Failed to authorize update with ECP.4100 1, ESET file security 6.4 is no active with agent. 2. ESET file security 6.4 is active without agent 3. ESET file security 6.4 is active and later the agent installation is automatically disabled? Best Link to comment Share on other sites More sharing options...
vanroy 0 Posted January 3, 2017 Author Share Posted January 3, 2017 Any news for this? Link to comment Share on other sites More sharing options...
Administrators Marcos 4,694 Posted January 3, 2017 Administrators Share Posted January 3, 2017 Is a policy applied to EFSW from ERAS ? If so and the policy was created months ago, could you remove it and re-create it? It might have a seat-id included which would then cause issues with activation. Link to comment Share on other sites More sharing options...
ESET Staff MichalJ 430 Posted January 3, 2017 ESET Staff Share Posted January 3, 2017 According to the KB article http://support.eset.com/kb2434/ it indicates that it is Internal Error. It might indicate that there is some other security solution present on the system or malware. As this is obviously related to ERA Agent, just out of curiosity, are there any policies applied to the File Security (like the anti-ransomware policy, or any other policy created from exported configuration from another client)? I would recommend removing those policies, and then attempting reactivation again, using ERA agent (product activation task). There was a bug in the previous versions, that license was exported within the configuration and invalid license parameters were applied to the client together with the exported / converted policy, which resulted in "not activated" state, and failing to get updates of the protection modules. Link to comment Share on other sites More sharing options...
vanroy 0 Posted January 3, 2017 Author Share Posted January 3, 2017 Solved anti-ransomware policy is the problem. Best. Link to comment Share on other sites More sharing options...
Administrators Marcos 4,694 Posted January 3, 2017 Administrators Share Posted January 3, 2017 21 minutes ago, vanroy said: Solved anti-ransomware policy is the problem. The Dutch distributor fixed the policy several months ago and we've also released a new Configuration engine module to address this issue. If you use the same anti-ransomware policy, you should not experience the activation issue again. Link to comment Share on other sites More sharing options...
Recommended Posts