Forum Discussion
Wonderware Historian as oData
I am new to PBI and have found something that is unmentioned elsewhere.
I am attempting to pull in Wonderware historian Data from a tier two server that has Wonderware 2017 on it. When trying to use an oData connection per Wonderware’s documentation I use, http://'serverhostname':32569/Historian/v1 to pull in the data. I am able to see that there are tables but receive this as an error for all of them:
“DataSource.NotFound: OData: Request failed (404): The remote server returned an error: (404) Not Found. (Not Found)
Details:
DataSourceKind=OData
DataSourcePath=http://'serverhostname':32569/historian/EventProperties
Url=http://'serverhostname':32569/historian/EventProperties?$top=1000”
When looking into it, a suggestion to fix this error is to shorten the number of columns, I do not know how to do this without the data being pulled into PBI. So, I tried only pulling in one of the tables alone and got this:
“Details: "Microsoft.Mashup.Engine1.Library.Resources.HttpResource: Request failed:
OData Version: 3 and 4, Error: The remote server returned an error: (404) Not Found. (Not Found)
OData Version: 4, Error: The remote server returned an error: (404) Not Found. (Not Found)
OData Version: 3, Error: The remote server returned an error: (404) Not Found. (Not Found)"”
When I looked into this error it appears it occurs whenever one tries to pull in too specific of data. Looking into the error message more, it appears this has been worked out for SharePoint more than the application I use.
Does anyone have a suggestion of what to try? I was able to see some data when I performed a Direct Query but this is not how I want to connect as this connection does not appear to let me show the data as historized inputs.
Thanks in advance!
Nick
5 Replies
I’m just wondering if anyone has connected Wonderware Historian data to power BI before? When using the oData connection with Wonderware’s documentation I use, http://'serverhostname':32569/Historian/v1 to pull in the data. I am able to see that there are tables, 13 in total, but receive this as an error for all sets:
“DataSource.NotFound: OData: Request failed (404): The remote server returned an error: (404) Not Found. (Not Found) Details: DataSourceKind=OData DataSourcePath=http://'serverhostname':32569/historian/EventProperties Url=http://'serverhostname':32569/historian/EventProperties?$top=1000”
When looking into it, a suggestion to fix this error is to shorten the number of columns to pull in. So, I tried only pulling in one dataset and got this,
“Details: "Microsoft.Mashup.Engine1.Library.Resources.HttpResource: Request failed: OData Version: 3 and 4, Error: The remote server returned an error: (404) Not Found. (Not Found) OData Version: 4, Error: The remote server returned an error: (404) Not"
This occurs, from my research if one tries to pull in data with too specific of a URL.
Bit of background, I am working with a 2016 SQL Server with Historian 2017 being used as a tier 2 server
Are there any suggestions for me to proceed with from someone that has successfully made this connection before?
Thank you in advance!
Nick
Xiaoxin,
I want to pull in the data via oData as this allows a historized view of it. When I try to connect it gives the first error message I mentioned. Becasue of this I wanted to make sure PBI could connect so I created a connection with as a SQL Database with a direct Query which showed most of the data, but not all that I want. Also, it was not a historized version of the data. So, the true connection needed would be an oData connection.
The Historian is set up as oData version 3 supported. I have confirmed that this is the correct url. I am able to use the url as an oData feed through Wonderware Trends, a simple graphing tool, on another server that we have to see the data I want to pull into PBI.
I guess my big stick up is how to work around the original error, either how to shorten the number of columns being pulled into the server if that is the ture reason I received it or some other work around that I do not know about.
Nick
This is a late reply but there is a quicker and more user-friendly to connect to Wonderware historians (and many, many more). Check this blog post in Power BI Community Blog.
Thanks
