Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
8 years ago
Solved

Implementation 2.0 SAP Connector

Hi,   I have been testing the new Implementation 2.0 SAP Connector against our SAP BW system explained here: https://docs.microsoft.com/en-us/power-bi/desktop-sap-bw-connector   It works beautif...
Need Help
  • S_loke's avatar
    S_loke
    8 years ago

    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

  • S_loke's avatar
    S_loke
    8 years ago

    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/

Anonymous's avatar
Anonymous
Not applicable
8 years ago

Anonymous,

Can you successfully refresh data in Power BI Desktop? The above error message mentions Group Perfect Purchase Orders  table, please check if there are any issues in this table in Power BI Desktop.

In addition, please make sure that you are able to connect to SAP BW from clients which are installed in the same machine with gateway.

Regards,
Lydia

Anonymous's avatar
Anonymous
Not applicable
8 years ago

Thanks for the reply.

Yes, connecting and updating the data in Desktop works perfectly.

The VM running the gateway has a user with access to BW, and when setting up the connection in the PBI Gateway Manager it checks as working.

 

So I'm guessing that the problem is with the gateway software not having the BasXml.Gzip execution file.

Does that have to be installed separately? 

  • Anonymous's avatar
    Anonymous
    Not applicable
    8 years ago

    Hello,

     

    I guess you have to wait for June version of the gateway, which may include the new mashup engine able to use the installed 2.0 connector.

     

    Regards.

    • Anonymous's avatar
      Anonymous
      Not applicable
      8 years ago

      Year, it looks like it.

      Strange though that MS will release a new connector that doesn't work with their gateway...

      • S_loke's avatar
        S_loke
        Advocate I
        8 years ago

        having the exact same symptoms

         

        local client has desktop (june) and .NET installed with the PBIX refreshing as expected

         

        Gateway on VM is patched with June desktop and .NET

         

        However, once the PBIX is published and setup with the gateway, the error message is encountered.  Hopefully it is as simple as waiting for June gateway deployment.