Knight Online "DbAgent / Ebenezer SQL Connection Failed" Error Solution
When starting your Knight Online private server Ebenezer.exe, Ais_Server.exe or DbAgent.exe modules freezing on the splash screen or repeatedly "SQL Connection Failed" / "ODBC Error" error indicates that the game master files cannot communicate with the SQL Server database. It is impossible to open the server without resolving this error. For the exact solution, you can follow the steps below one by one.
Method 1: Checking ODBC Data Sources (DSN) Configuration
Knight Online exe files use ODBC hyperlinks in the Windows operating system to connect to the database. Missing or incorrect identification of these hyperlinks breaks the connection completely:
- to the Windows Start menu ODBC Data Sources (32-bit) Open the panel by typing . *(Important: Since the game files run on 32-bit architecture, you must choose the 32-bit panel).*
- System DSN Click the tab.
- here
KN_Online,Knight_DB,Account_DBCheck whether the ODBC names needed by your files infrastructure, such as files, are defined. - If defined, double-click on them and enter your SQL Server username (Usually `sa`) and SQL password. "Test Data Source" Press the button. If the test fails, your SQL password or server name is incorrect.
Method 2: Checking Password and Database Names in .ini Files
Even if your ODBC connections are correct, the information in the settings files in the server files may be written incorrectly:
- in your server folder
Ebenezer.ini,Ais_Server.iniandDbAgent.iniOpen the files. - contained within
[ODBC]or[DATABASE]under the headings DSN, UID (h) and PWD (Your SQL Password) Check the fields. - Make sure that the database names are exactly the same as the names in SQL Server (Ex: `KN_ONLINE`, `KO_MAIN`), down to uppercase and lowercase letters.
Method 3: Activating SQL Server "Named Pipes" and TCP/IP Protocols
By default, SQL Server installation can turn off TCP/IP connection requests from external or local services. To turn on these protocols:
- From the Windows Start menu SQL Server Configuration Manager Open the program.
- SQL Server Network Configuration -> Protocols for MSSQLSERVER Go to the tab.
- Located on the right Named Pipes and TCP/IP status of options "Enabled" Change it to (Active) and restart the SQL Server service (Restart).
This article is specially prepared for PvPServer.
