The SQL Auto Close feature automatically closes inactive database connections after a specified period of inactivity. By default, auto close is enabled but Trellix does not like this behaviour. In this article, we will discuss the fix to “Disable SQL Auto Close: Auto Close is enabled for both ePO and ePO Events Databases”. Please see Trellix ePolicy Orchestrator Installation on Windows Server, and how to upgrade Trellix ePolicy Orchestrator.

Note: According to Microsoft, the best practice is to disable this option if the database is accessed frequently. Therefore set the AUTO_CLOSE option to False for the database.

Also, see how to Disable or Enable Auto log on in Windows, Fixes to Trellix ePolicy Orchestrator Installation Errors, and how to fix “Auto Logon Error “The username and password specified is not valid“.

Auto Close Option

Auto Close ensures efficient database management and resource utilisation. System performance is optimised by automatically closing idle connections after a specified period of inactivity.

This prevents unnecessary resource consumption and potential performance degradation. This practice helps maintain database integrity and stability while enhancing overall system responsiveness.

Why was this error prompted “Auto Close is enabled for both ePO and ePO events databases”

Error message “Auto Close is enabled for both ePO and ePO events databases. Please disable them before proceeding with the installation”.

By now, you should be aware of what the SQL Server Auto Close option is. And why Trellix wants it disabled.

When AUTO_CLOSE is set to True, this option can cause performance degradation on frequently accessed databases because of the increased overhead of opening and closing the database after each connection. AUTO_CLOSE also flushes the procedure cache after each connection.

Note: Make sure you disable Auto Close for both the Core database and Events database.

Disable Auto Close on Microsoft SQL Server

Launch the SQL Server Management Studio and Connect to your database Engine.

Right-click on the ePO database, and select properties. The step should also be performed for the event database. Else the ePO Update Tool process will not upgrade.

In the database properties, we can see the Auto Close option is set to True. We shall set this to false.

Use the drop-down associated to set this option to False. When done, click on OK.

Disable Auto Close for the Event database

Starting from this version “ePO 5.10”. ePolicy Orchestrator (ePO) adds a new, entirely separate database called the ePO Events database to handle threat event information.

After you upgrade to or install ePO 5.10, a new SQL database is created in addition to the existing ePO database with the format ePO_<ePOServerName>_Events.

As mentioned earlier, this step needs to be repeated also for the Event Database

I hope you found this guide useful on “Disable SQL Auto Close: Auto Close is enabled for both ePO and ePO Events Databases”. Please feel free to leave a comment below.