The ultimate Microsoft Fabric, Power BI, Azure AI, and SQL learning event: Join us in Stockholm, September 24-27, 2024.
Save €200 with code MSCUST on top of early bird pricing!
Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
Hi All,
We've got an error after doing update the gateway enterprise to the latest one.
Our gateway is on a VM Azure which contains our SSAS cube.
Before the mmigration everything worked fine (live connection from power bi to the cube, I mean).
After the migration:
-on the VM side, everything seem good (the gateway is ready to use).
-on the power bi manage gateway, all good (connected data sources, connection succesful)
-BUT when we try to use the report, we receive the message " The report could not access its data source. Please contact the <developper> , to have it fixed".
-AND THE WEIRD THING IS: When I try to install the gateway enterprise on my laptop, with exactly the same config (I use the same recovery key), the live connection works well.
--------------------
SO far, I refered to this article : https://powerbi.microsoft.com/de-de/blog/how-authentication-with-analysis-services-live-connections-... published by @GuyinaCube , I did all the check and everything is good.
Does anybody encounter this problem?
Thank you
Dung Anh
Solved! Go to Solution.
Hi All,
Thank you for your information.
We have already fixed this issue.
This is a very sneaky stuff, I think this post will be a good reference for anyone who have the same type of problem.
I resume:
1/ Before install latest version of PBI Gateway Enterprise: power bi worked fine with live connection on SSAS cube, everyone has accessed to their data. In general, everythings work fine since 3 years with the old data gateway.
2/ After installation lates version of PB Gateway Enterprise: power bi manage gateway is good, we can see every fields when we try to create report from SSAS cube (live connection) but we got a message when trying to visualize data : " The report could not access its data source. Please contact the <developper> , to have it fixed".
3/ How to resolved this issue:
Because the gateway old version is in 32 bit when we installed it, so in the REGISTRY it is configured with the 32 bits. And because the new one is 64, so It will not show the problem (everything is fine mean network, trusted domain, gateway connected, ready to use ...) .
So what my collegue did is he modified that 32 to 64 in registry, and then everything works like a charm!
Thnak you again for your faster response!
Dung Anh
Hi All,
Thank you for your information.
We have already fixed this issue.
This is a very sneaky stuff, I think this post will be a good reference for anyone who have the same type of problem.
I resume:
1/ Before install latest version of PBI Gateway Enterprise: power bi worked fine with live connection on SSAS cube, everyone has accessed to their data. In general, everythings work fine since 3 years with the old data gateway.
2/ After installation lates version of PB Gateway Enterprise: power bi manage gateway is good, we can see every fields when we try to create report from SSAS cube (live connection) but we got a message when trying to visualize data : " The report could not access its data source. Please contact the <developper> , to have it fixed".
3/ How to resolved this issue:
Because the gateway old version is in 32 bit when we installed it, so in the REGISTRY it is configured with the 32 bits. And because the new one is 64, so It will not show the problem (everything is fine mean network, trusted domain, gateway connected, ready to use ...) .
So what my collegue did is he modified that 32 to 64 in registry, and then everything works like a charm!
Thnak you again for your faster response!
Dung Anh
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Check out the August 2024 Power BI update to learn about new features.
User | Count |
---|---|
55 | |
24 | |
14 | |
14 | |
12 |
User | Count |
---|---|
106 | |
39 | |
28 | |
22 | |
22 |