Jump to content
  • 0

Failed to Connect After Switching from dblib to SQLSRV in P


Question

Posted

I’ve been using my ACP for a long time without any issues, but recently, it seems there was an update in cPanel that deprecated the use of the dblib driver for database connections.

 

The hosting provider informed me that dblib is no longer supported in PHP versions above 5.6, and they suggested switching to the sqlsrv driver.

 

Although my ACP is still running on PHP 5.6, I followed the advice and updated the database connection method in configs.php to use sqlsrv (by choosing the 4th option in the config), but I keep getting the following error: "Failed to connect! #SQLSRV #DB".

 

Has anyone come across this issue or know where I should start looking to resolve it?

 

Any insights would be really helpful!

2 answers to this question

Recommended Posts

  • 0
Posted
On 13/9/2024 at 12:42, mroovster said:

He estado usando mi ACP durante mucho tiempo sin ningún problema, pero recientemente, parece que hubo una actualización en cPanel que desaprobó el uso del controlador dblib para conexiones de base de datos.

 

El proveedor de alojamiento me informó que dblib ya no es compatible con versiones de PHP superiores a 5.6 y me sugirió cambiar al controlador sqlsrv.

 

Aunque mi ACP todavía se ejecuta en PHP 5.6, seguí el consejo y actualicé el método de conexión de la base de datos en configs.php para usar sqlsrv (eligiendo la cuarta opción en la configuración), pero sigo recibiendo el siguiente error: "Error al conectar! #SQLSRV #DB".

 

¿Alguien se ha encontrado con este problema o sabe dónde debería empezar a buscar para resolverlo?

 

¡Cualquier idea sería realmente útil!

 

Hello dear, if you are using a shared hosting, it is very likely that you do not have the sqlsrv connection module. you can check by adding a info.php

add an info.php file with the following code:

Quote

<?php
phpinfo();
?>



https://yourdomain.com/info.php

if your hosting provider allows php 5.6 and you have cloudlinux from php selector you can enable mssql.

If it does not allow that, you should ask the hosting provider if you can enable sqlsrv. (But many times they do not allow this method in shared hosting.)

 

  • 0
Posted

also i have shared a tester.php here in mxc if you find it use it so you know what your hosting can do or not, for l2off servers i would recommend you l2jcenter its a br hosting and i recommend them for my clients when they get my donate panels for l2off because its reliable that will work, otherwise you should have knowledge how to install it your self in a unix operating system level.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Posts

    • LIVE VERIFICATION? SUMSUB? “IMPOSSIBLE”? ▪ Spoiler: it is possible — if you know who to work with. A client came in with a task to pass **live verification** on **WantToPay**, a Telegram virtual card service. On the platform side — **Sumsub**: liveness check, SMS, manual review. “Fast” and “by eye” simply don’t work here. › What was done: → analyzed the verification scenario and Sumsub requirements → built the correct flow: phone number, email, timing → **completed live verification remotely, without account handover** → handled SMS and confirmation codes → brought the process to final approval ▪ Result: → verification passed → access granted → no flags or repeat requests ▪ Live verification is not luck. It’s scenario-based preparation — not hope. › TG: @mustang_service ( https:// t.me/ mustang_service ) › Channel: Mustang Service ( https:// t.me/ +6RAKokIn5ItmYjEx ) *All data is published with the client’s consent.* #verification #sumsub #livecheck #kyc #case
    • IMPORTANT INFO: In a few days, I will switch to completely new code, written from scratch with a new download system, patch building and management system. The Updater will become true 2026 code with "foolproof systems". I'm going to create a Discord server for customers to request new ideas and features. FIRST CUSTOMERS ARE ALREADY USING THE NEW UPDATER ON LIVE SERVERS! Watch this topic for upcoming info because the new updater is around the corner! Yes, you can still use self-update on the previous updater! No, the new updater won't be compatible with the old patch system! A new build is required, but players who already have game files won't have to download the entire patch again! New templates and updates to existing templates are coming soon! Sneak peek:  
    • i used guytis IL project and source. i found in his project there are 3 Client version source... 1,CliExt_H5   --->this one cant be compiled in VS2005,i did know why..is it for H5 client? 2,CliExtNew  --->this one is IL version ,but when i compiled it and use it.player cant login game,MD5Checksum wrong.i check the source code,but not found any hints. 3,L2Server    --->this one for HB client?im not sure...   so my question is what are the differences between these three versions of cliext.dll?how can i fix the issue of the MD5Checksum not matching problem?   01/29/2026 21:04:11.366, [CCliExt::HandleCheckSum] Invalid Checksum[1130415144] vs [-721420287] packet[dd] len[29] sum[2698] key[30] HWID[] Account[]! 01/29/2026 21:04:11.366, SocketLimiter::UserSocketBadunknownprotocol 11111111111 01/29/2026 21:04:11.366, [usersocket]unknown protocol from ip[113.137.149.115]!      
  • Topics

×
×
  • Create New...

Important Information

This community uses essential cookies to function properly. Non-essential cookies and third-party services are used only with your consent. Read our Privacy Policy and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..