Sometimes it works perfectly well but mostly I am getting error. I am getting the data from Historian through a virtual machine. error specifically occurs for getting live data which is changing continuously over the period of time.
Based on the tags you added to your question, I understand the data Historian is a Factory Talk Historian with an embedded PI System. If this is the case, what's the PI Data Archive version?
You also used tags like 'piwebapi', 'postman', 'pi-vision', 'pi web' and 'thingworx'. Can you please indicate what client application gives you the error?
yes the data Historian is Factory Talk Historian running on a virtual machine. I have installed PI system on the Virtual machine itself. I am getting the error in all the applications when I am trying to get the query from PI.
This is a screenshot of my PI running on VM.
Please allow me to clarify. The Factory Talk Historian has a PI Data Archive embedded and is a so called OEM System. End customers are supposed to contact Rockwell for 1st level support and Rockwell should have its channels into OSIsoft for 2nd level support.
Issues like the one you are experiencing may require log file analysis and having a remote session is often very useful. Hence you may want to use your OEM channel contacts to ask support for your connection issues.
I don't know for sure but believe the Factory Talk Historian embeds a PI Data Archive but not an AF Server. Certain products store configuration information in the "Configuration" database on the AF Server. One of these products is PI Web API. If you don't have an AF Server you will not be able to successfully install PI Web API. PI Vision depends on PI Web API. I also recall that the Factory Talk license file has some restrictions.
However, what should work is a remote connection to the PI Data Archive embedded into your Factory Talk through PI SDK. Can you please run PI SDK Utility on the client and attempt a connection to your server (PASS-C01). Does this occasionally or always fail? Is error [-10734] the only one or do you also see others?
can you let me know OEM channel contacts of Rockwell if you know any? I have installed AF server and PI is also running and I am able to access the data from a remote connection. The problem occurs when I am trying to fetch some live data.
I am able to fetch data using event frames but not with streamsets
I suggest you to contact Rockwell Support for 1st level support. I was looking around the Rockwell Support web page and believe the exact name of the Rockwell product with embedded PI is FACTORYTALK HISTORIAN SE. I also found the Factory Talk Historian SE INSTALLATION ASSISTENT and it appears Asset Framework is indeed included. I did not find any information stating PI Web API or PI Vision would be included. So to me this is the first question to raise with Rockwell Support.
I will reach out to the account manager at OSIsoft for Rockwell and make him aware of your question.
The account manager for Rockwell got back to me and confirmed contacting Rockwell Support for issues like yours is appropriate. Rockwell Support can escalate to OSIsoft following the procedures in place.
Please let us know if this approach is not working.
I'm updating this thread as I had a similar -10734 error and couldn't find the answer using Professor Google.
The issue was the server hosting the SDK requires port 5450 open.
It looks likes the SDK will reach out to the remote server on 5450, establish a connection then the remote server will build a new connect back to the SDK. This means that all of your firewall rules need to be bi-directional (firewalls, routers and Windows).
Inbound traffic to PI Server is over 5450 and network firewall should configured to enable traffic outbound for the inbound request over 5450. Please note there is no requirement for 5450 on the client side.
For a client (Datalink, Vision, ProcessBook, etc.), I completely agree.
For a PI-to-PI interface (FTV Historian to OSI PI DA), it is required. You need to configure the connection using the PISDKUTIL software on the Interface node first, establish the trusts on the FTV Historian then the FTV server will build a connection back.
Retrieving data ...