Forum Discussion

a-vdarute's avatar
a-vdarute
Regular Visitor
6 months ago
Solved

Gateway connection error

Unable to update connection credentials. The on-premises data gateway's service account failed to impersonate the user.  Kindly help me resolve this error. 
Need Help
  • rohit1991's avatar
    rohit1991
    6 months ago

    Hii a-vdarute 

     

    If the error still persists after assigning permissions and restarting the gateway, the most likely cause is a Kerberos / impersonation mismatch between the gateway and the data source. As a next step, try switching the data source to use explicit credentials (for example, SQL authentication instead of Windows), or configure Kerberos delegation (double-hop) correctly if Windows authentication is required. Also verify that the same gateway is mapped to the dataset, the service account password hasn’t changed, and re-add the data source in the gateway cluster before updating credentials again.

  • v-achippa's avatar
    v-achippa
    6 months ago

    Hi a-vdarute,

     

    Thank you for the response and clarification. Since your machine is Azure AD joined only, windows authentication is not supported in this configuration. Because windows authentication requires a proper Active Directory domain join to enable user impersonation.

    • Switch the data source to use sql authentication instead of windows authentication. This does not require domain join and will work correctly with your current setup.

     

    Thanks and regards,

    Anjan Kumar Chippa

v-achippa's avatar
v-achippa
Community Support
6 months ago

Hi a-vdarute,

 

Thank you for the response and clarification. Since your machine is Azure AD joined only, windows authentication is not supported in this configuration. Because windows authentication requires a proper Active Directory domain join to enable user impersonation.

  • Switch the data source to use sql authentication instead of windows authentication. This does not require domain join and will work correctly with your current setup.

 

Thanks and regards,

Anjan Kumar Chippa

a-vdarute's avatar
a-vdarute
Regular Visitor
5 months ago

Hi,

After following your instructions, everything appears to be in order except for one issue: when I attempt to add the data source to the gateway, I am now encountering a new error,


A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

  • v-achippa's avatar
    v-achippa
    Community Support
    5 months ago

    Hi a-vdarute,

     

    This error is now a network connectivity issue between the gateway machine and sql server, not an authentication issue. Please verify the following:

    • Ensure the correct server and instance name is being used
    • Make sure sql server allows remote connections
    • TCP/IP is enabled in Sql Server Configuration Manager
    • Verify firewall rules allow traffic on port 1433 or the configured sql port
    • If using a named instance, ensure the sql server browser service is running

    The gateway machine must be able to connect to the sql server outside of the power bi first. Once the connectivity works, then adding the data source in the gateway will succeed.

     

    Thanks and regards,

    Anjan Kumar Chippa