APPX Software Library

Chapter 8: Solve Connection and Import Problems

SQLDriverConnect Failed: Check the Microsoft Runtime

If ASQL or a 32-bit ODBC client reports:

SQLDriverConnect Failed

check the Microsoft Visual C++ v14 Redistributable (x86) as one possible cause. A Windows Server 2022 installation was reported to recover from this symptom after installing the 32-bit runtime. This is a reported troubleshooting remedy, not a guarantee that every connection failure has the same cause.

  1. Confirm that the ODBC client and driver are both 32-bit and that the intended AppxODBC DSN exists in the 32-bit ODBC Administrator.
  2. Install or repair the official Microsoft x86 Visual C++ runtime. Use x86 for these clients even when Windows is 64-bit. Microsoft's runtime download guidance identifies the supported package.
  3. Restart Windows if requested, reopen the client, and retry the connection.
  4. If the error remains, record the full ODBC message and SQLSTATE, then check the gateway listener, DSN Host (gateway computer), optional ODBC Service (gateway TCP-port alias), and APPX credentials. SQLDriverConnect Failed is a general connection-stage message; it does not by itself identify a missing runtime.

For other symptoms, see error 126 while opening the legacy DSN setup dialog, -20038 Cursor not closed, or a gateway service that cannot start. The runtime installation is a potential remedy for the connection symptom above; it did not resolve those separately tested gateway and cursor failures.