On-premises_Data_Gateway error

Makama, ANTHEA (404) 0 Reputation points
2026-09-10T13:35:56.5533333+00:00

Unable to create connection for the following reason: There was an error in the data gateway.

Details: DTSA_On-premises_Data_Gateway: The parameter is incorrect. Session Id: 2efc6e07-e1c5-4b21-8a93-2ed4f6febd4b RequestId: b4c0408a-0671-4480-9642-0fccfb6e1f8e Cluster URI: https://api.powerbi.com Status code: 400 Time: Thu Sep 10 2026 15:30:06 GMT+0200 (South Africa Standard Time)

Azure Application Gateway
Azure Application Gateway

An Azure service that provides a platform-managed, scalable, and highly available application delivery controller as a service.

0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-09-10T13:36:14.39+00:00

    There was an error in the data gateway is a generic gateway-side failure. For this type of error, the supported troubleshooting path is:

    1. Confirm the gateway is on the latest version. Many connectivity and reliability issues are resolved in monthly gateway updates.
    2. Test the data source from the gateway machine itself. Open Power BI Desktop on the computer where the gateway is installed and try the same connection there. If it fails locally, the gateway refresh or connection creation is unlikely to succeed.
    3. Check the gateway event logs on the gateway server:
      • Open Event Viewer
      • Go to Applications and Services Logs
      • Select On-premises data gateway service
    4. Export gateway logs from the gateway app:
      • Open the on-premises data gateway app
      • Select Diagnostics
      • Select Export logs
    5. If the gateway was reachable but the source could not be accessed, validate the data source definition, server/database values, and credentials.
    6. If a proxy is used, verify the proxy configuration is consistent and that requests are not being blocked.
    7. If the gateway was recently configured or changed and shows as unreachable, restart the On-premises data gateway Windows service and retry.

    Relevant error patterns from gateway troubleshooting:

    • Unknown error in data gateway can occur for different reasons and should be investigated from the gateway machine and logs. The event logs are the primary place to get more detail.
    • Invalid connection credentials means the username/password or authentication method does not match the source.
    • Cannot connect to the database means the server was reached, but the specified database name or permissions are wrong.
    • The gateway can't access the on-premises data source means the service reached the gateway, but the gateway server could not reach the source.

    If the local test in Power BI Desktop succeeds but connection creation in the service still fails, narrow the issue to the gateway data source configuration in the Power BI service and review the exported logs for the exact failure around the reported session/request time.

    If the issue is not covered by the documented cases, the next step is to create a support ticket.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Jose Benjamin Solis Nolasco 12,036 Reputation points Volunteer Moderator
    2026-09-10T15:00:58.88+00:00

    Welcome to Microsoft Q&A,

    @Makama, ANTHEA (404) I hope you are doing well,

    The error:

    DTSA_On-premises_Data_Gateway: The parameter is incorrect.

    Status code: 400

    There was an error in the data gateway is a generic gateway-side failure. For this type of error, the supported troubleshooting path is:

    I recommend starting with these checks:

    1. Confirm the Gateway is in the latest version Microsoft supports only the latest six gateway releases. As of September 2026, the August 2026 release (3000.330) is the latest listed release.
    2. Restart the On-premises data gateway service after updating and retry creating the connection.
    3. Verify the data source configuration. Confirm that the server/database or other connection information entered when creating the connection exactly matches the source configuration expected by the gateway.
    4. Check the gateway logs. In the On-premises data gateway application, go to Diagnostics → Export logs and reproduce the connection-creation failure. Microsoft recommends starting with the gateway logs when troubleshooting gateway issues.

    You can also check:

    Event Viewer → Applications and Services Logs → On-premises data gateway service

    for events generated at approximately:

    Sep 10, 2026 15:30:06 UTC+02:00

    RequestId: b4c0408a-0671-4480-9642-0fccfb6e1f8e

    SessionId: 2efc6e07-e1c5-4b21-8a93-2ed4f6febd4b

    If the gateway is part of a cluster, make sure all gateway members are running the same supported version. Microsoft specifically recommends keeping cluster members synchronized to avoid unexpected failures.

    Microsoft documentation:

    If this answer helped clarify the platform capabilities and save you troubleshooting time, please consider marking it as Accepted. This helps others in the community find similar solutions.

     

    Was this answer helpful?

    0 comments

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.