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

Create a technical support case if you need further support.

"Error processing PKCS7 data" appears in host events of Deep Security

    • Updated:
    • 8 Jan 2020
    • Product/Version:
    • Deep Security 10.0
    • Deep Security 11.0
    • Deep Security 12.0
    • Deep Security 9.6
    • Platform:
    • N/A
Summary

You may encounter the following error message in host events:

Unable to complete the operation due to the following error on the Agent/Appliance: Error processing PKCS7 data: error:06065064:

Additionally, one or more of the following symptoms may occur:

  • It shows "Send Policy Failed" events.
  • Deep Security Agent (DSA) may turn into offline status after its successful activation.
  • Only one computer appears on the Computer page even when multiple computers are activated.
Details
Public
 
This article about PKCS7 is only for the error code "error:06065064". For scenarios with other error codes, this article is not applicable.

The Deep Security Manager (DSM) identifies Deep Security Agents based on the UUIDs. When computers have duplicated UUIDs, the issues mentioned above may occur because DSM could not handle requests from DSA due to duplicated UUIDs.

Some possible reasons of UUID duplication are as follows:

  • Virtual machines are cloned using an unsupported method.
  • A computer was not deactivated before restoring, and then it was restored after the computer was already activated by DSM.

To fix the issue:

  1. Find out the cause of UUID duplication and correct it.
  2. Remove the duplicate computers from the Computers page.
  3. Reset and reactivate the Deep Security Agent.

In case you are not able to identify the UUID duplication issue, do the following as a workaround:

  1. Go to Administration > System Settings > Agents.
  2. Change the value of If a computer with the same name already exists: to Activate a new Computer with the same name.

​​Note that it is still recommended to identify and correct the duplicated UUID issue in your deployment. Communication between DSM and DSA may have unexpected behaviors due to duplicated UUIDs.
Premium
Internal
Rating:
Category:
Troubleshoot
Solution Id:
1116586
Feedback
Did this article help you?

Thank you for your feedback!

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.

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.