Forum Discussion
Implementation 2.0 SAP Connector
Just an update that with June deployment of the gateway, this is now working as expected with the reports being to be refreshed on PBI service
Hi,
The error message you have posted seems slightly different to the original thread although root cause may be the same.
The symptom that the original issue was related is:
- BW 2.0 connector refreshes sucessfully on Desktop
- Same PBIX BW 2.0 connector fails on Service
The fix was to update the gateway with June patch (released 29th June - version 14.16.6745.2)
https://powerbi.microsoft.com/en-us/blog/on-premises-data-gateway-june-update-is-now-available/
Hello,
I saw your question is resolved.
But please advise if your report is built on BW Application Server or BW Message Server connection please?
(Our BW Application server based reports works fine with gateway+scheduled refresh).
However not even able to add BW Message server as datasource yet. Gateway only has .Net Connector in our case.
It's working on our BW application server, but Kerberos SSO is still not working.
Regarding SSO I haven't yet come across anyone who has made it work.
Hopefully, MS will release a more comprehensive guide and troubleshooting soon!
Hi,
May not be the answer you are looking for but the solution was for application server.
Thank you Mholsen and S_loke.
I raised a support ticket and got a reply that SSO is not supported in Service for Import queries.
So far we have been successful to get SSO working in desktop version only - For import queries. (Both BW App server and message server)
There is documentation to get SSO Kerberos working for Direct queries..You were able to try that and still not successful?
Or you are also wanting to use import queries+SSO....? Thanks!
Yes, we are trying to follow the documentation for Kerberos SSO provided by MS, but no luck in making the connection work yet.
Should work with both Message Server and Application Server. But you have to install .NET connector (2.0) on both desktop and gateway. The report need to be build with that connector however you are not using it on the gateway when moving to automated refreshs.
Anonymous,
Yes. We have installed .NET connector (2.0) on both desktop and gateway. The report also built based on .NET connector.
The report is based out of BW Message Server and works fine in desktop.
However we are not even able to add BW Message server as datasource yet in the Gateway. Gives error as "Access to SAP Business Warehouse requires SAP client tools to be installed, including the latest version of SAP Netweaver RFC"
Gateway only has .Net Connector in our case.
Did you install RFC Connector(and SAP GUI) initially in the Gateway, and then you installed .NET connector in the gateway after it was rolled out?
In our case, we started afresh with .NET connector in Gateway and i reproduced the problem for MS Support.
However if i schedule the message server based report via personal gateway it refreshes fine. Personal Gateway(my PC) has both RFC and .NET connector and also SAP GUI.
On the other hand Application server based reports refreshes fine in gateway. (again .NET connector based reports).