2 responses to “Hosting company deleted database driver”

1. It sounds like you’re having a tough time with the transition after GoDaddy removed your database driver. Here are a few things you can check to troubleshoot your new connection string:

   1. Driver Name: Double-check the exact name of the driver as recognized by your server. Sometimes it’s slightly different than what it appears in documentation. You can find the exact names of installed drivers by running the following in your code:
      asp
Set odbc = Server.CreateObject("ADODB.Connection")
For Each driver In odbc.GetDrivers
Response.Write(driver & "<br>")
Next

   2. Architecture: Ensure that your application is running in the same architecture as the driver. If you’re using a 32-bit application (due to Classic ASP being 32-bit), make sure you use the 32-bit version of the MariaDB ODBC driver. You may need to adjust your application pool settings in IIS to enable 32-bit applications.

   3. Connection Properties: Sometimes, additional connection properties can help. Try updating your connection string like this:
      asp
connectstr = "Driver={MariaDB ODBC 3.1 Driver};SERVER=" & db_server & ";DATABASE=" & db_name & ";UID=" & db_username & ";PWD=" & db_userpassword & ";PORT=3306;"
      Make sure to adapt the driver name accordingly if you’re using a specific version.

   4. Firewall and Permissions: Ensure that your server’s firewall or security settings allow connections to the database, and verify that your database user has the necessary permissions.

   5. Error Messages: If you’re getting an error message in response to the connection attempt, that can provide important clues. Consider logging that error message to help diagnose the problem.

   6. Documentation and Examples: Sometimes it helps to refer to the documentation for the MariaDB ODBC driver or look for examples on how to configure the connection string properly.

   If you’ve tried these suggestions and are still stuck, please provide the specific error message you are receiving, as that can help in diagnosing the issue further.

   Reply

2. It sounds like you’re dealing with quite a frustrating situation. Transitioning to a new database driver can sometimes lead to unexpected issues. Here are a few things you might consider checking that could help troubleshoot the problem:

   1. **ODBC Driver Version**: Make sure that the version of the MariaDB Connector/ODBC you’re using is compatible with your specific version of MySQL. Sometimes, discrepancies between versions can cause connection problems.

   2. **Connection String Syntax**: Ensure that there are no typos or syntax errors in your updated connection string. Sometimes subtle differences can lead to failure in establishing a connection. For example, double-check that you’re using the correct driver name and that all semi-colons and quotes are properly placed.

   3. **Firewall settings**: Confirm that your GoDaddy hosting account allows outgoing connections to your MySQL server. Occasionally, firewall settings can restrict access, leading to connection errors.

   4. **Error Messages**: If you are receiving any specific error messages when trying to connect, these can provide valuable insight into what might be going wrong. Feel free to share those, as they can greatly assist in diagnosing the issue.

   5. **Alternative Drivers**: Depending on your hosting environment, there may be additional ODBC drivers available that might work more seamlessly with your database. Exploring alternative options could be worthwhile.

   6. **Testing Locally**: If possible, try to run a simple test connection locally, outside of the GoDaddy environment, to ensure that your connection string is

   Reply