Forum Discussion

SikuMatthias's avatar
SikuMatthias
New Member
7 months ago
Solved

PowerBI Gateway ODBC Connection

Hello everyone,

I'm trying to set up a gateway in the Power BI service that accesses our proAlpha database.

Unfortunately, I'm getting the following message:

The connection credentials cannot be updated.

Invalid request

Details:

If you would like to create a support ticket, please have the following information ready.

Session ID: 836602ab-8c75-4216-9507-418f9f27d30d
RequestId: 6606d437-23d7-40a7-92d6-4c11d41b5c89
Cluster URI: https://api.powerbi.com
Status Code: 400
Time: Wed Feb 04 2026 09:26:48 GMT+0100 (Central European Time)

However, the ODBC access credentials are correctly configured.

I'm afraid I don't know what to do next.

  • Hi SikuMatthias  -In Power BI Service rejects the ODBC configuration before authentication due to a mismatch between Desktop, Gateway, or driver setup.

    If Power BI Desktop connects using a DSN, the gateway must use the same DSN.If Desktop uses a connection string, the gateway must also use a connection string.

    check the, ODBC driver with 64-bit ODBC driver used in Power BI Desktop must be installed on the gateway machine.

    In Power BI Service → Dataset → Gateway connection, use Basic authentication for ODBC sources.
    Windows / OAuth often causes Invalid request (400) for ODBC drivers.

    Once done, restart the gateway and re-enter the credentials.

    check the above configrations and let us know. hope it helps.

  • Hi SikuMatthias ,

    Since the gateway and ODBC connections are functioning for other proAlpha databases, this likely isn’t just a credential problem.

    The error occurs when binding this particular shared report, which typically indicates that the dataset’s ODBC definition doesn’t exactly match the gateway data source. In these situations, republishing the report with the same DSN and settings already working on the gateway is usually the fastest solution.

     

    I hope this clarifies the situation. If I’ve misunderstood any part of your setup, please let us know.

4 Replies

  • Hi SikuMatthias  -In Power BI Service rejects the ODBC configuration before authentication due to a mismatch between Desktop, Gateway, or driver setup.

    If Power BI Desktop connects using a DSN, the gateway must use the same DSN.If Desktop uses a connection string, the gateway must also use a connection string.

    check the, ODBC driver with 64-bit ODBC driver used in Power BI Desktop must be installed on the gateway machine.

    In Power BI Service → Dataset → Gateway connection, use Basic authentication for ODBC sources.
    Windows / OAuth often causes Invalid request (400) for ODBC drivers.

    Once done, restart the gateway and re-enter the credentials.

    check the above configrations and let us know. hope it helps.

    • SikuMatthias's avatar
      SikuMatthias
      New Member

      Hi,

      PowerBI is running on a Server which has already configured the ODBC Connections for proAlpha database.

      I configured the Gateway, i also did it to set a functional Connection to those Databases (Germany, Poland and China).

      But when i try to configure my shared Report following things happen:

       

      Those following three Connections are marked as Online

       

       

      • V-yubandi-msft's avatar
        V-yubandi-msft
        Icon for Community Support rankCommunity Support

        Hi SikuMatthias ,

        Since the gateway and ODBC connections are functioning for other proAlpha databases, this likely isn’t just a credential problem.

        The error occurs when binding this particular shared report, which typically indicates that the dataset’s ODBC definition doesn’t exactly match the gateway data source. In these situations, republishing the report with the same DSN and settings already working on the gateway is usually the fastest solution.

         

        I hope this clarifies the situation. If I’ve misunderstood any part of your setup, please let us know.

  • Looks like an error of the connection credentials, maybe something went wrong

     

    delete that connection and create a new one with the credentials, is that solving?

     

    Best

     

    If this helped, please consider giving kudos and mark as a solution

    me in replies or I'll lose your thread

    Want to check your DAX skills? Answer my biweekly DAX challenges on the kubisco Linkedin page

    Consider voting this Power BI idea

    Francesco Bergamaschi

    MBA, M.Eng, M.Econ, Professor of BI