On-premises_Data_Gateway error

Question

On-premises_Data_Gateway error

Makama, ANTHEA (404) 0

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)

0 comments

3 answers

Your answer

Answer 1

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

Confirm the gateway is on the latest version. Many connectivity and reliability issues are resolved in monthly gateway updates.
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.
Check the gateway event logs on the gateway server:
- Open Event Viewer
- Go to Applications and Services Logs
- Select On-premises data gateway service
Export gateway logs from the gateway app:
- Open the on-premises data gateway app
- Select Diagnostics
- Select Export logs
If the gateway was reachable but the source could not be accessed, validate the data source definition, server/database values, and credentials.
If a proxy is used, verify the proxy configuration is consistent and that requests are not being blocked.
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.

Answer 2

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:

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.
Restart the On-premises data gateway service after updating and retry creating the connection.
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.
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.

Answer 3

"The parameter is incorrect" at the moment you create the connection usually means the gateway or the data source details are not what the service expects, rather than a network fault, so the checks below are the order I would run them in.

The usual causes, in the order I check them. First, the gateway is installed in personal mode; Power Apps and Power Automate need standard mode (personal mode is Power BI only). Second, the gateway build is old: update it to the current release on the gateway machine and restart the service, because the connector and the gateway negotiate parameters and an old build fails exactly like this. Third, the machine the gateway runs on went to sleep or was restarted without the service coming back; put it on a machine that stays on and check the service after every Windows update. Fourth, the SQL login: the connection uses the credentials saved on the gateway data source, not the app user's, and if that login's password expired every user sees the failure at once. Fifth, the SQL Server Browser service is off and the connection string uses an instance name without a port; use server,port instead.

Licensing while you are there: SQL Server is a premium connector and the gateway needs a premium licence, so every user of the app needs Power Apps Premium (NZ$32.40 per user per month on the NZ list, September 2026). If only a few people use the app, pay-as-you-go at USD 10 per active user per app is cheaper for a single app.