Issue
- You are running ESET PROTECT On-Prem Server and MS SQL database on separate computers
- Resolve "SQL Server Error: 18" when connecting database during ESET PROTECT On-Prem
Solution
I. Prerequisites
- ESET PROTECT On-Prem Server and MS SQL Server installed on separate Windows computers.
II. Install ODBC Driver
-
Download and install Microsoft ODBC Driver for SQL Server version 17 and later.
-
Click Start → Services, right-click ESET PROTECT Server service and select Stop.
-
Navigate to the following directory:
-
C:\ProgramData\ESET\RemoteAdministrator\Server\EraServerApplicationData\Configuration\
-
Edit the
startupconfiguration.ini
file:- Replace
SQL Server
with the name of the MS ODBC Driver, listed in Start → ODBC Data Sources → Drivers tab.
- Add the following code to the end of the file:
Encrypt=yes;TrustServerCertificate=yes;
- Replace
Below is an example of startupconfiguration.ini
(replace the parts highlighted in yellow with your values):
DatabaseType=MSSQLOdbc
DatabaseConnectionString=Driver={ODBC Driver 17 for SQL Server};Server=10.20.30.40,1433;Uid=era_user;Pwd={SecretPassword};CharSet=utf8;Database=era_db;Encrypt=yes;TrustServerCertificate=yes;
-
Save the
startupconfiguration.ini
file. -
Click Start → Services, right-click ESET PROTECT Server service → select Start.
-
If you are able to log in to the ESET PROTECT Web Console, the encrypted connection to the database works properly. If you are not able to log in to the ESET PROTECT On-Prem Web Console, follow the troubleshooting steps below to revert the configuration changes.
III. Troubleshooting
-
Click Start → Services, right-click ESET PROTECT Server service and select Stop.
-
Navigate to the following directory:
C:\ProgramData\ESET\RemoteAdministrator\Server\EraServerApplicationData\Configuration\
-
Replace the
startupconfiguration.ini
file with the backup file (created in step 4 above). -
Click Start → Services, right-click ESET PROTECT Server service and select Start.