Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
Currently facing an issue where we are unable to create new BW dataflows but at the same time, existing BW dataflows are editable & refresh normally.
Symptoms are:
Within the same workspace (P1 Premium, same gateway, same user), creating a new BW dataflow using the M codes from a working existing BW dataflow returns the error message of "Something went wrong while retrieving details for the on-premises data gateway"
Extremely confusing considering the message would suggest that there is an issue within the gateway but if that is the case, why does the BW dataflows previously built work as expected?
Current gateway screens shows the connection to be active with no error messages.
We have tried the following:
Solved! Go to Solution.
For us, a user can create a BW dataflow if they are set as an admin on the gateway, but they get this error if they are just a user of the BW datasource in the gateway.
It's working in the USA too.
I'm having this same problem. It just became an issue today 8/14/19. I can't create any new dataflows and I'm getting the "We encountered an error during evalulation. Details: Something when wrong while retrieving details for the on-premises data gateway. Please try again later".
Hi,
Whlist the issue remains, the suggested workaround does work.
The hidden culprit seems to be the fact that the blank query is unable to "test for connection" validating the datasource. So to "cheat" the process, you can use one of the alternate Datasource from GUI to establish the connection then copy paste the real M query into advance editor.
Long story short (and only works if you have access to a datasource that is supported i.e. you can establish a connection through the dataflow Web GUI)
The steps we perform as below:
YES - thanks for notifying. Works here (North Europe) as well now 🙂
What if I don't have access to a SQL server db?
I am able to add to my existing dataflow entities, the error happens when creating new dataflows.
Actually, I kinda find a solution.
I used "Blank Query" to try getting my data from a DB2 database... Gateway error message appeared.
Trying to make sure the Gateway is working properly I created a new query selecting "IBM DB2 Database" option from Get Data, I type the required connection settings and clicked Next. The query did connect to the database, but I got a error because there's no sql statement (So, the reason a "Blank query" is needed). Cancel this new query.
Hopelessly, I clicked "Refresh" in the original query... and Power Query actually connected the database and got the data!
Apparently, it is needed to first try to connect the database as you would do it in Power BI Desktop, so Power Query can connect to the server. Then, you can type the M code in a Blank query.
Thanks - I can't connect to the DB2, so I will try to find another way
Same issue here. Existing dataflows work propertly. "Something went wrong while retrieving details for the on-premises data gateway" error doesn't allow to create new ones.
hi, @S_loke
If this M code work well in power bi desktop.
and if you could refer to this post:
https://community.powerbi.com/t5/Service/SAP-BW-Dataflows/td-p/636441
Best Regards,
Lin
Hi,
Thanks but it wasn't the underlying issue. Previously, it was possible to create the dataflows to extract content from SAP BW in an identical process as the post you suggested.
However, it would seem that post gateway update, that the steps now are creating errors.
The confusing issue is that previously created dataflows continue to work suggesting that the mashupengine is still capable of connecting and communicate but is now unable to create new dataflows.
User | Count |
---|---|
64 | |
27 | |
25 | |
17 | |
11 |