Forum Discussion

V3GAS's avatar
V3GAS
Icon for Helper I rankHelper I
9 years ago
Solved

"OLE DB or ODBC error: [DataSource.NotFound]" when loading table

Using Power BI Desktop to connect to a Project Server 2013 database using the OData Feed option, I am able to: Connect to the database Select a table from the database See a preview of the data i...
  • V3GAS's avatar
    V3GAS
    9 years ago

    Good News...

     

    I was able to connect using the OData Feed to our on-premises Project Server 2013 and apply the table in question to the report. I found that it was corrupt data in the table. 

     

    I slowly and methodically vetted the columns in the table by removing/replacing them and trying to apply to the report. As a matter of fact, it was a series of columns that was causing the issue. By keeping them out of the query, I am now able to utilize the data in the report.

     

    Thanks.

V3GAS's avatar
V3GAS
Icon for Helper I rankHelper I
9 years ago

Lydia,

 

Thanks for the information. You are correct as I am trying to connect to an on-premises Project Server (2013) to report from. I was able to bring in a few tables by using the URL for the Project Server PWA (OData Feed) query. The permissions I used was the Windows credentials with None as the Privacy Level.

 

Since I can already bring in a few tables, I think the reason I cannot bring in the rest of the tables, specifically the Projects table, is because there is "corrupt" data that is preventing me to apply it to the report. 

 

Thanks again.

Anonymous's avatar
Anonymous
Not applicable
9 years ago

Hi V3GAS,

There is no official articles or blogs stating how to connect to on-premises Project Server in Power BI Desktop and what tables are able to imported. What is the result if you configure Basic type authentication in project server?


And do you have sufficient permission on the Projects table? How about creating another PBIX file to connect to only Projects table?

Thanks,
Lydia Zhang

  • V3GAS's avatar
    V3GAS
    Icon for Helper I rankHelper I
    9 years ago

    Good News...

     

    I was able to connect using the OData Feed to our on-premises Project Server 2013 and apply the table in question to the report. I found that it was corrupt data in the table. 

     

    I slowly and methodically vetted the columns in the table by removing/replacing them and trying to apply to the report. As a matter of fact, it was a series of columns that was causing the issue. By keeping them out of the query, I am now able to utilize the data in the report.

     

    Thanks.

    • Anonymous's avatar
      Anonymous
      Not applicable
      9 years ago

      Hi V3GAS,

      Glad to hear the issue is resolved.:smileyhappy:



      Thanks,
      Lydia Zhang