The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
Hello all,
I am able to connect to my office server in Power BI but when i try to connect it on Report builder to bring in Dataset, I am getting an error" Login successfull but an error occured during the login process. provider Named pipes provicer error:0, No process in on the other end of the pipe. ).
Any help appreciated how to resolve the issue. I am connected on Network while trying to connect. Thank you.
Solved! Go to Solution.
Hi @shavish ,
Hi @shavish , Thank you for reaching out to the Microsoft Community Forum.
Since Power BI Desktop connects fine, your network and credentials are likely not the issue. The problem is probably due to Report Builder defaulting to the wrong protocol or using a misconfigured connection. Depending on what you mean by “office server,” the fix will differ slightly, whether you're connecting to a Power BI dataset in the cloud or to an on-premises SQL Server or SSAS instance.
If you're connecting to a Power BI dataset hosted in the cloud, Named Pipes isn’t used at all, these datasets are accessed via XMLA over HTTPS. In Report Builder, create a new data source, choose Microsoft SQL Server Analysis Services as the connection type, and use XMLA endpoint format: powerbi://api.powerbi.com/v1.0/myorg/YourWorkspaceName
Sign in with your Power BI (Azure AD) account. Make sure the workspace is in a Premium or Premium Per User capacity, XMLA read/write is enabled, and you have Build permission on the dataset. This route avoids the Named Pipes protocol entirely and should connect without issue.
If instead you're connecting to an on-premises SQL Server or SSAS instance, Report Builder may be defaulting to Named Pipes, while Power BI Desktop connects using TCP/IP. To fix this, set your connection string in Report Builder like this: tcp:YourServerName,1433. Replace 1433 with the correct port if it’s different. On the server, open SQL Server Configuration Manager, go to SQL Server Network Configuration -> Protocols for [YourInstance] and ensure TCP/IP is enabled. You can also disable Named Pipes if you’re not using it. Restart the SQL Server or SSAS service, confirm the firewall allows traffic on the correct TCP port and update the SQL Native Client or MSOLAP drivers on your machine. To confirm your credentials are valid, test the same login in SQL Server Management Studio.
If this helped solve the issue, please consider marking it “Accept as Solution” and giving a ‘Kudos’ so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.
Hi @shavish , I hope you're doing well! Just checking in to see if you had a chance to review the details shared earlier. If any of the information addressed your needs, feel free to mark it as "Accept as Solution" or give it a 'Kudos' to help others in the community. Please let me know if you have any further questions!
Hi @shavish ,
I hope the information shared was helpful. If you have any additional questions or would like to explore the topic further, feel free to reach out. If any of the responses resolved your issue, please mark it "Accept as solution" and give it a 'Kudos' to support other members in the community.
Thank you!
Hi @shavish ,
I wanted to follow up and see if you’ve had a chance to review the information provided here.
If any of the responses helped solve your issue, please consider marking it "Accept as Solution" and giving it a 'Kudos' to help others easily find it.
Let me know if you have any further questions!
Hi @shavish , Thank you for reaching out to the Microsoft Community Forum.
Since Power BI Desktop connects fine, your network and credentials are likely not the issue. The problem is probably due to Report Builder defaulting to the wrong protocol or using a misconfigured connection. Depending on what you mean by “office server,” the fix will differ slightly, whether you're connecting to a Power BI dataset in the cloud or to an on-premises SQL Server or SSAS instance.
If you're connecting to a Power BI dataset hosted in the cloud, Named Pipes isn’t used at all, these datasets are accessed via XMLA over HTTPS. In Report Builder, create a new data source, choose Microsoft SQL Server Analysis Services as the connection type, and use XMLA endpoint format: powerbi://api.powerbi.com/v1.0/myorg/YourWorkspaceName
Sign in with your Power BI (Azure AD) account. Make sure the workspace is in a Premium or Premium Per User capacity, XMLA read/write is enabled, and you have Build permission on the dataset. This route avoids the Named Pipes protocol entirely and should connect without issue.
If instead you're connecting to an on-premises SQL Server or SSAS instance, Report Builder may be defaulting to Named Pipes, while Power BI Desktop connects using TCP/IP. To fix this, set your connection string in Report Builder like this: tcp:YourServerName,1433. Replace 1433 with the correct port if it’s different. On the server, open SQL Server Configuration Manager, go to SQL Server Network Configuration -> Protocols for [YourInstance] and ensure TCP/IP is enabled. You can also disable Named Pipes if you’re not using it. Restart the SQL Server or SSAS service, confirm the firewall allows traffic on the correct TCP port and update the SQL Native Client or MSOLAP drivers on your machine. To confirm your credentials are valid, test the same login in SQL Server Management Studio.
If this helped solve the issue, please consider marking it “Accept as Solution” and giving a ‘Kudos’ so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.
Hi @shavish ,
Hi @shavish I think it is because of a protocol issue. Ensure Named Pipes is enabled in SQL Server Configuration Manager, or switch to TCP/IP as the connection protocol. Check that the firewall allows traffic on the SQL Server port (default: 1433). Additionally, verify SQL Server authentication and update to the latest drivers.