Cannot establish ODBC 18 Connection via Interactive authentication

P Christel 20 Reputation points
2025-12-08T16:01:05.7033333+00:00

I have been unable to create an ODBC interactive connection to an Azure database. The credentials work fine in SSMS and using the SQLCMD. The browser window opens and allows me to authenticate. I have tried using the ODBC manager (32-bit) as well as a DSNless connection within my MS Access application. Either way yields the same result with an 0x534 error state 11. The browser window never opens to attempt authentication. Using a simple sql user/pw login works fine from the same machine, so it's not a firewall issue. From what I understand, the SQLCMD is using the 64-bit driver, so I'm wondering if there is an issue with the 32-bit driver.

Azure SQL Database
Answer recommended by moderator
P Christel 20 Reputation points
2025-12-09T16:21:52.5633333+00:00

Well, for kicks, I installed ODBC version 17 and it worked perfectly on the first try.

Was this answer helpful?

0 comments

3 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. P Christel 20 Reputation points
    2025-12-17T21:29:01.6333333+00:00

    I appreciate you looking into this, but it didn't really solve the problem. It seems as though I have to use v17 or MS needs to resolve the issue.

    Was this answer helpful?

  2. Adam Zachary 2,265 Reputation points
    2025-12-08T20:43:22.7366667+00:00

    I’ve run into this exact issue before, and in my case it was the 32-bit ODBC driver not handling interactive authentication properly. SQLCMD and SSMS use the 64-bit driver, which is why they work while the 32-bit ODBC prompt never launches the browser window. One of my customers saw the same 0x534 state 11 error a few weeks ago.

    Try installing and using the 64-bit ODBC 18 driver and make sure your Access app or DSN is actually pointing to it. If you must use 32-bit Access, interactive auth often fails, and the only workaround we had was switching to Azure AD Password authentication or using a 64-bit Access environment.

    In short, this is almost always a driver bitness mismatch rather than a firewall or credential issue.

    Was this answer helpful?

  3. Pilladi Padma Sai Manisha 11,715 Reputation points Microsoft External Staff Moderator
    2025-12-08T16:56:47.9866667+00:00

    Hi P Christel,

    It looks like you're having a tough time with establishing an ODBC interactive connection to your Azure database, especially since it works fine with SSMS and SQLCMD. The 0x534 error state you're encountering suggests a possible issue with how the authentication is being handled, particularly with the 32-bit ODBC driver.

    Here are a few steps you can try to troubleshoot this issue:

    1. Driver Version Check: Make sure you are using the latest version of the ODBC driver. ODBC driver versions 17.10 and higher have fixed various issues related to Microsoft Entra ID authentication. If you're currently using an older version, please consider upgrading.
    2. Connection String: Ensure that your connection string is correctly formatted for using Microsoft Entra ID for interactive authentication. You should specify the Authentication=ActiveDirectoryInteractive in your connection string. For example: 
      
   server=<your_server>.database.windows.net; database=<your_database>; UID=<your_user>; Authentication=ActiveDirectoryInteractive; Encrypt=yes;
    3. Firewall and Network Settings: Since you've ruled out firewall issues because simple SQL logins work fine, make sure that any network policies or settings specific to your ODBC connections are also configured properly.
    4. 64-bit vs 32-bit Drivers: If you're utilizing a 32-bit ODBC driver, ensure that the 32-bit version is compatible with your system's architecture. Sometimes, authentication methods can work differently based on the architecture used. Try switching to the 64-bit driver if you're currently using the 32-bit version and see if that resolves the issue.
    5. Browser Prompt Issue: If the browser window is not opening for authentication, try launching your ODBC application with administrative privileges, as this might help with the browser opening correctly.

    If the problem persists after trying the above steps, it may be beneficial to pinpoint the issue by isolating the environment further or checking for any known issues in Azure SQL Database that might be affecting connections at the moment.

    Follow-Up Questions:

    1. Which version of the ODBC driver are you currently using?
    2. Are there any specific error messages or behavior changes when trying with the 64-bit driver?
    3. Have you tested the connection string on another application (like a simple console application) to see if the issue is specific to MS Access?
    4. Is the operating system where you're running the ODBC manager updated to the latest version?
    5. Can you clarify if there's any other software installed that might interfere with ODBC connections, for example, security software or VPNs?

    Let me know if these steps help, or if you provide more details, I can assist you further!

    Relevant Documentation:

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.