Forum Discussion
there was a data source access error. please contact the gateway administrator
Hi rayudu,
Firstly ensure that your SSAS server and gateway are installed in a same domain or trusted domains.
Secondly, in Power BI, the effective username is passed to the gateway and then onto your on-premises Analysis Services server each time a user interacts a report connected to Analysis Services. The email address that you use to sign in Power BI with is passed to Analysis Services as the effective user. This email address should match a defined UPN within the local Active Directory Domain, if a match cannot be found, you will get errors.
You can use the following command from your workstation to find out the UPN for your account, if the UPN doesn't match the email address you sign into Power BI with, you can use “Map user names” feature to solve this issue. Assume that you if you sign into Power BI with [email protected], but your local directory UPN is [email protected], you can configure a mapping rule to have [email protected] passed to Analysis Services. For more details, please review this article.
whoami /upn
Thanks,
Lydia Zhang
Hi rayudu,
Firstly ensure that your SSAS server and gateway are installed in a same domain or trusted domains.
Secondly, in Power BI, the effective username is passed to the gateway and then onto your on-premises Analysis Services server each time a user interacts a report connected to Analysis Services. The email address that you use to sign in Power BI with is passed to Analysis Services as the effective user. This email address should match a defined UPN within the local Active Directory Domain, if a match cannot be found, you will get errors.
You can use the following command from your workstation to find out the UPN for your account, if the UPN doesn't match the email address you sign into Power BI with, you can use “Map user names” feature to solve this issue. Assume that you if you sign into Power BI with [email protected], but your local directory UPN is [email protected], you can configure a mapping rule to have [email protected] passed to Analysis Services. For more details, please review this article.
whoami /upn
Thanks,
Lydia Zhang
Its not related with domain fisrt read carefully what I wrote. If you dont know the answer then dont give other answer which is not related with this.
If the data is huge in the cube then when you try to live connect to cube and click ok nothing will show in Field section I kept 24 hours like that but nothing came. Live connect works properly on samll amount of data in the cube.
After reviwed the gatewayXXX.log and found following error message
GatewayPipelineErrorCode=DM_GWPipeline_UnknownError
ProviderName=MSOLAP.5 --->
Inner exception chain: System.Runtime.InteropServices.COMException
<pi>System.Runtime.InteropServices.COMException (0x80040154): Retrieving the COM class factory
for component with CLSID {308FF259-8671-4DF4-B66C-9851BFACF446} failed due to the following error: 80040154
Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).I finally get the issue solved by unregister 32 bit msolap110.dll and 64 bit msolap130.dll using following command
regsvr32 -u "C:\Program Files (x86)\Microsoft Analysis Services\AS OLEDB\110\msolap110.dll"
regsvr32 -u "C:\Program Files\Microsoft Analysis Services\AS OLEDB\130\msolap130.dll"
and then reregister 64 bit msolap130.dll using command
Regsvr32 "C:\Program Files\Microsoft Analysis Services\AS OLEDB\130\msolap130.dll"
wish it is helpfule
Thanks Jennyy,
I had upgraded the gateway as well and few days after that, this error started.
Was able to fix it with your instructions.
Cheers
- I was also facing the same issue
Please export the error log by running enterpriseGatewayConfigurator.exe which locates under C:\Program Files\On-premises data gateway by default ,
Then check gateway log to find the details first.
