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

Create a technical support case if you need further support.

Unsuccessful Endpoint Sensor license deployment due to change in SQL Server Database

    • Updated:
    • 24 Jun 2020
    • Product/Version:
    • Apex Central 2019
    • Apex One 2019
    • Platform:

License deployment fails when activating Apex One Endpoint Sensor. The following error es encountered in Command Details:

"License deployment was unsuccessful
Endpoint Sensor Service: Unknown Error"

Root Cause Analysis

From ofcdebug.log, it shows that the user cannot login to the Endpoint Sensor database.

2020 03/04 11:28:17 [24d0 : 0021] (00) (F) [-iESServer-][TrendMicroEndpointSensorService.exe][PluginUtil.SqlConnectionClient][IsSQLConnReady] Check connection failed. exception: System.Data.SqlClient.SqlException (0x80131904): Cannot open database "HostName-ApexOne-iES" requested by the login. The login failed.
Login failed for user 'XXX\XXX'.

Below are possible causes for this issue:

  • User changed the password of the database account, or the password of the database account is expired.
  • User changed the Authentication Type of the Apex One SQL database from "Windows Account" to "SQL Server Account", or vice versa.
  • User changed the Apex One Endpoint Sensor database name.
  • User changed the permission of the database.

To resolve this:

  1. Check for any changes in the database settings.
  2. Check configuration files to know the information of Apex One & Apex One Endpoint Sensor database.
    1. Check ofcserver.ini, and get the Apex One database information:

      Server =
      Database = OSCE
      SQLAuthMode = 5020 (5020 means SQL authentication)

    2. Check the Apex One Endpoint Sensor configuration file, Event40\Config.xml:


  3. Utilize SQL Management Studio to make sure the database setting is consistent with the data above.
  4. Run SqlTxfr tool to update the database information to Apex One.

When using the Windows Account to log on to the server, Apex One applies the username of the currently logged on user.

The user account must belong to the local administrator group or Active Directory(AD) built-in administrator. The following User Rights Assignment policies must be configured as well using the Windows Local Security Policy or Group Policy Management console:

  • Log on as a service
  • Log on as a batch job
  • Log on locally

The user account must also have the following database roles:

  • dbcreator (only required if you are creating a new database instance using the Setup program)
  • bulkadmin
  • db_owner
Solution Id:
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.