Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
9 years ago
Solved

named pipe connection support

Hi, Im experimenting with powerBI and WSUS internal database and wanted to check if someone did connect succesfully from powerBI Desktop to a local Windows Internal database as it seems for me that named pipe connection is a problem. I can connect to same internal db using SQL management studio but not via power BI Desktop. 

 

Im asking just to save a time a bit :) 

 

thanks for help

  • Hi Anonymous,

     

    Windows Internal Database is not available as a standalone product for use by end-user applications; Microsoft provides SQL Server Express and Microsoft SQL Server for this purpose. Additionally, it is designed to only be accessible to Windows Services running on the same machine.

     

    So I don't think it is currently available for Power BI Desktop.:smileyhappy:

     

    Regards

7 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    Anonymous If it's a SQL database it is most likely just a matter of having the appropriate ports or permissions open for access, I would imagine... Have you tried connecting via the IP?

    What is the error you are getting in Power BI?

    • Anonymous's avatar
      Anonymous
      Not applicable

      Anonymous Im running powerBI desktop on same server as the wsus internal dabatase is installed so I doubt ports. I have installed wsus using same credentials which Im using for connection. 

       

      My inspiration was this arcite https://blogs.technet.microsoft.com/gborger/2009/02/27/exploring-the-wsus-windows-internal-database/ about quering WSUS intranl dB and because its working OK with SQL management studio I cant undrstand why powerBI desktop strugles with same connection. 

       

      Error Im getting is this: 

       

      My aim is to pull data from WSUS internal database into powerBI to provide more fancy and modern reports than WSUS can do :) 

      • Anonymous's avatar
        Anonymous
        Not applicable

        AnonymousHere is a decent link to try various things related to that error. It is most likely one of them.

        A couple I run into a lot are needing to fully qualify the connection server\db, Allow Remote Connections and Browser Service.