Forum Discussion
SAP BW connectivity issue with a port number
Hi all,
I am trying to integrate our SAP BW system with Power BI.
Fo test enviroment evrything is working fine, however when I am trying to make connection is fails.
The difference is that for Production enviroment I need to specify port in a server address like:
prodserver.net:3632
whereas in test it is just address like:
testserver.net
With port number I have error: Details: "The provided server name is invalid."
Whereas without port number Bi is directing to the worng port:
Details: "SAP Business Warehouse: RfcOpenConnection failed(RFC_COMMUNICATION_FAILURE):
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner 'prodserver.net:3350' not reached
Any idea how I can force Power BI to use proper port?
Thanks
7 Replies
- v-qiuyu-msft
Community Support
Hi lewand03,
From the description, the SAP BW service is configured to use specific port. You need to contact the SAP BW administrator to set the default port for prodserver.net.
Best Regards,
Qiuyun Yu- lewand03
Helper I
Thank you v-qiuyu-msft
Your soulution sound reaspnable, and I'll try to talk to my administrator, however I'd prefer any solution whic doesn't impact other 2500 users, portal settings etc.
Is there any way to force Power Bi to use proper port?
Thanks,
dariusz
- farsenea
Advocate I
Hi, I have the same problem and context (no way I can have the port number of our Prod BW landscape change to default...): any chance to have a way to specify / force a different port number ?
Thanks
- axipFrequent Visitor
I am having the same problem so can't get to step one with this tool. The port to initiate connection to the BW server is controlled by POWERBI. I don't see how the configuration of the SAP server would have anything to do with it. I find no way to change it in the tool, registry, or configuration files within POWERBI.
- axipFrequent Visitor
Although I changed nothing on my client, the BW connection began working a couple of days later when I tried again. Some windows updates had been applied to my machine, but I suspect that the reboot that was performed had something to do with it starting working. Our BW system must be using the default port used by the data source extract.