Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Next up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now

Reply
V3GAS
Helper I
Helper I

"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 in the table
  • Query the table and see all data

PBI Query.PNG

 

When I try to load/apply the table into the report, I receive the following error:

PBI Error.PNG

To get the above table query, I have set the OData Feed permission to use Windows authentication. Does this have anything to do with the permissions? When trying to use the Organizational Account option, I get another error:

PBI Permission Error.PNG

1 ACCEPTED SOLUTION

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.

View solution in original post

6 REPLIES 6
keinshah
Helper I
Helper I

I face a similar problem. 

 

DataSource.NotFound: Dynamics365BusinessCentral: Request failed (404): The remote server returned an error: (404) Not Found. (The Sales Header does not exist. Identification fields and values: Document Type='Order',No.='STNLSO001653' CorrelationId: 9102fe11-c4ec-44df-8064-95097bd438f8.)
Details:
DataSourceKind=Dynamics365BusinessCentral
DataSourcePath=Dynamics365BusinessCentral
Url=https://api.businesscentral.dynamics.com/v2.0/PRODUCTION/OData/Sales_Order_Line?company=SMART

 

Any idea how to solve it?

Anonymous
Not applicable

Hi @V3GAS,

From your description, you are connecting to on-premises Project Server rather than Project Online from Power BI Desktop, right? If that is the case, I haven’t found any official articles or blogs stating that how to connect to on-premises Project Server and what authentication method in Power BI Desktop.

Could you please configure basic authentication type in Project Server and use basic authentication in Power BI Desktop? I also find an idea about adding add-on for on-premises Project Server, if you still get errors when exploring Project Server data in Power BI Desktop, please vote that idea.

However, if you connect to Project Online from Power BI Desktop, please follow the instructions in this article: https://powerbi.microsoft.com/en-us/documentation/powerbi-desktop-project-online-connect-to-data/ .

Thanks,
Lydia Zhang

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
Not applicable

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

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
Not applicable

Hi @V3GAS,

Glad to hear the issue is resolved.Smiley Happy



Thanks,
Lydia Zhang

Helpful resources

Announcements
New to Fabric survey Carousel

New to Fabric Survey

If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.

Power BI DataViz World Championships carousel

Power BI DataViz World Championships - June 2026

A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.

Join our Fabric User Panel

Join our Fabric User Panel

Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.

March Power BI Update Carousel

Power BI Community Update - March 2026

Check out the March 2026 Power BI update to learn about new features.