Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
I have an AzueAS pulls data from on-prem SQL. I have 2 models already existing and migrated the gateway to new server.
I created a new model and deployed. The deployment succeeded, but processign fails with below error:
An error occurred during On-Premise Gateway related activity. Additional error details: DM_GWPipeline_Gateway_DataSourceAccessError
Received error payload from gateway service with ID 1296616: OLE DB connection failed to be established.
OLE DB connection failed to be established
Login failed for user '<domain>\<new gatewayserver name>$'.
What does this error mean and how to fix this issue?
Solved! Go to Solution.
@CSun,
Double click the data source in the Analysis Services project, click “Impersonation Information” tab, if you selected “Use the service account”, please make sure that the service account has access rights to the relational data source.
Or you can select “Use a specific Windows user name and password”, enter your account that has access permission on the relational data source, then re-process the project.
Regards,
Lydia
@CSun,
Double click the data source in the Analysis Services project, click “Impersonation Information” tab, if you selected “Use the service account”, please make sure that the service account has access rights to the relational data source.
Or you can select “Use a specific Windows user name and password”, enter your account that has access permission on the relational data source, then re-process the project.
Regards,
Lydia
I am still getting attached error while my database works fine.
Any suggestion what I am missing here ?
@v-yuezhe-msft thank you for that post. I was having a similar error when I was trying to connect an on-prem Excel-based data set into Analysis Services. When deploying the model up to Azure AS from SSDT I was getting errors until I picked the correct authentication method.
For those facing a similar situation, when impersonating the account use this as a guide to help
Thanks!
Eric
User | Count |
---|---|
11 | |
7 | |
5 | |
5 | |
4 |
User | Count |
---|---|
16 | |
14 | |
8 | |
6 | |
6 |