Forum Discussion

a-vdarute's avatar
a-vdarute
Regular Visitor
7 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
    7 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

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

Hi,
 My machine is Azure AD Joined only (via Intune) – NOT domain joined. now i have NT SERVICE\PBIEgwService account, Gateway is running under NT SERVICE\PBIEgwService, when I tried to connect dataset with windows authentication(with my work account) it is throughing bellow error : 

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

Details: Partner_wise_dashboard: The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters.
kindly suggest a solution.
 

 

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