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

Create a technical support case if you need further support.

Event ID 705: Activation Failed appears when activating the Deep Security Agent (DSA)

    • Updated:
    • 18 May 2016
    • Product/Version:
    • Deep Security 8.0
    • Deep Security 9.0
    • Deep Security 9.5
    • Deep Security 9.6
    • Platform:
    • HPUX 11.x
    • IBM AIX
    • Linux - Red Hat RHEL 4 32-bit
    • Linux - Red Hat RHEL 4 64-bit
    • Linux - Red Hat RHEL 5 32-bit
    • Linux - Red Hat RHEL 5 64-bit
    • Linux - Red Hat RHEL 6 32-bit
    • Linux - Red Hat RHEL 6 64-bit
    • Linux - SuSE 10
    • Linux - SuSE 11
    • Unix - Solaris (Sun) version 10 (SunOS 5.10)
    • Unix - Solaris (Sun) version 9 (SunOS 5.9)
    • VMware ESX 4.0
    • VMware ESX 4.1
    • VMware ESX 5.0
    • VMware ESXi 4.0
    • VMware ESXi 4.1
    • VMware ESXi 5.0
    • VMware vCenter 5.0
    • Windows 2003 Enterprise
    • Windows 2003 Enterprise 64-bit
    • Windows 2003 Standard
    • Windows 2003 Standard 64-bit
    • Windows 2008 Enterprise
    • Windows 2008 Enterprise 64-bit
    • Windows 2008 Server R2
    • Windows 2008 Standard
    • Windows 2008 Standard 64-bit
    • Windows 7 32-bit
    • Windows 7 64-bit
    • Windows Vista 32-bit
    • Windows Vista 64-bit
    • Windows XP Professional
    • Windows XP Professional 64-bit
Summary

When trying to activate an agent, DSA always returns an "Activation Failed" error message.

Details
Public

Do the following to resolve this issue:

  1. Check the description of the error why the activation failed. Most of the time, the problem is self-explanatory.

    Unable to activate the Agent/Appliance because the Agent/Appliance has already been activated by another Deep Security Manager.

  2. Check if the Deep Security Manager (DSM) is able to resolve the hostname or FQDN of the agent.
     
    The name of the machine that appears in the computers section is the one used by DSM to communicate with the agent.

    C:\> nslookup Win7-32.seg.local
    Server: seg-dc.seg.local
    Address: 10.10.1.1
    Name: Win7-32.seg.local
    Address: 10.10.1.200

    check if DSM can resolve the hostname/FQDN of the agent

  3. Check if DSA is able to resolve the hostname or FQDN used by the server. You can find the DSM name used for communication by logging into the web console and going to System > System Information > System Activity > Deep Security Manager object.

    C:\> nslookup dsm.test.com
    Server: dc.test.com
    Address: 10.10.1.1
    Name: dsm.test.com
    Address: 10.10.1.50

  4. Check and make sure that the system time for DSA and DSM are synchronized.
  5. Check the DSA and make sure that it is not activated or registered to another Deep Security Manager.

    To check if DSA is activated or not:

    1. Go to the \Program Files\Trend Micro\Deep Security Agent install directory.
    2. Look for these three (3) files:
      • config.bin
      • ds_agent.config
      • ds_agent_dsm.crt

      If these files are available, it means that the agent is already activated.

    Alternatively, you may open the certificate file, ds_agent_dsm.crt, and go to the Details tab to verify the manager where the agent is activated from.

    open the certificate file

    If the DSM where it is registered is no longer available, deactivate the DSA:

    1. Open a command prompt.
    2. Go to the \Program Files\Trend Micro\Deep Security Agent install directory.
    3. Run this command to reset and deactivate the agent: dsa_control.exe /r

      The message "Agent reset successfully" appears after successfully completing the command.

      Deactivate DSA via command prompt

  6. You may activate the Deep Security Agent from the Deep Security Manager web console or via command line.
    1. Log on to the DSM web console.
    2. Do the following:
      • For Deep Security 8.0 and below, go to System > System Settings > Computers tab.
      • For Deep Security 9.0 and above, go to Administration > System Settings > Computers tab.
    3. Enable the Allow Agent Initiated Activation option and select For Any Computers.
    4. Go to the Deep Security Agent and open a command prompt.
    5. Go to the \Program Files\Trend Micro\Deep Security Agent installation directory.
    6. Run this command to activate the agent:

      dsa_control.exe /a dsm://<hostname-FQDN>:4120/

      The message "Command Session Completed" appears after successfully completing the command.

      Activate DSA via command line

If you encountered an error when activating from the DSM web console, check the agent system events for any error message. If you encountered an error when activating the DSA locally, enable additional logging to determine the cause of the activation error.

  1. Go to the C:\\Windows directory.
  2. Create a file named ds_agent.ini.
  3. Add this parameter to the file to enable the debug:

    trace=*

  4. Activate the agent using the command line method.

Common Issues Related to Agent Activation

Deep Security Manager hostname is not reachable

When this issue occurs, make sure the hostname can be resolved correctly.

DSM certificate has already expired

To resolve this issue, make sure the date and time of both DSM and DSA are synchronized.

There is a duplicate name in the DSM database

To resolve the issue, check for possible duplicate hostname in the DSM web console and delete the duplicate name manually.

To resolve the issue:

  1. Reset the current DSA configuration by running this command under the ..\Program Files\Trend Micro\Deep Security Agent installation directory:

    dsa_control.exe /r

  2. Stop the Trend Micro Deep Security Agent Service.
  3. Manually delete the following files under the Deep Security Agent folder:
    • All files with *.db extension
    • All files with *.crt extension
  4. Start the Trend Micro Deep Security Agent Service.
  5. Perform another agent activation and check the result.

You are unable to activate your DSVA because of an error in communicating with the vShield manager. You cannot connect to the vShield manager because of any of the following:

  • The DSVA activation failed and shows "Error code: 3".

    Activation Failed:
    Registration of the Appliance with vShield Manager has failed.
    There was an error in communication between the Deep Security Virtual appliance and the vShield Manager. Please try running this wizard again. (Error code: 3)

    Activate Deep Security Virtual Appliance

  • There is a missing security certificate.

    Unable to connect to the vShield Manager due to missing or invalid certificate. Please try to Add/Update Certificate before connecting.

     
    If the alert only shows "Invalid credential for vShield Manager appears", just ensure that the username and password is correctly typed.

    dacvpcenter properties

  • There is a missing security VM on vShield Manager.

    vShield Endpoint Health and Alarms

    Below is a sample correct endpoint tab showing DSVA as a Security VM:

    Active Alarms

  • You are unable to ping DSVA from vShield manager or other computers.

To resolve the issue:

  1. Open your DSM console and highlight vCenter from the navigation pane.
  2. Right-click and select Properties.
  3. On the General tab, check if your settings are correct and click Test Connection. You will be notified if the connection is successful or not.

    dacvpcenter properties

  4. On the vShield Manager tab, click the Add/Update Certificate... button, accept the changes and click Close.
  5. On the vShield Manager tab, click Test Connection. You will be notified if the connection is successful or not.

    dacvpcenter properties

  6. On the DSM console select vCenter on the navigation pane and choose the affected DSVA. Reactivate the DSVA and verify if it is successful.

    DSM console

The error message "Activation Failed (Protocol Error)" appears when activating a virtual machine. Clicking on the error message will show the following details:

Level: Error
Event ID: 705
Event: Activation Failed
Event Origin: Appliance

Description:
An error occurred in the Deep Security Manager to Deep Security Agent/Appliance protocol: ProtocolException: Just created a virtual agent, queried for it, and it still thinks there is NO_SUCH_UUID, uuid: 4216367b-2ddb-78f1-f2fe-c7776ff0320c.

no such UUID

When a VM is created, the vCenter notifies the Deep Security Manager (DSM). This prompts the Master Agent in the Deep Security Virtual Appliance (DSVA) to instantiate a virtual agent for that VM.

The error occurs due to either of the following:

  • The vCenter was unable to notify the DSM when the VM was deployed to ESX.
  • The Master Agent failed to create a virtual agent for the VM.

To resolve the issue, reboot the DSVA before activating the VM:

  1. Log in to the vCenter using vSphere client.
  2. Look for the DSVA and press F2 to log in.
  3. Click Reboot System.
  4. Activate the VM.
Premium
Internal
Rating:
Category:
Troubleshoot
Solution Id:
1060686
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.


Need More Help?

Create a technical support case if you need further support.