1 of 1 people found this helpful
Seeing that "pipt_findpoint for source tag returned [-5] Tag Not Found" message makes me think that perhaps the interface doesn't have sufficient permissions to view this tag on the source server. I would recommend checking the logs on the source server to see how the interface is connecting and what PI Identities it's being assigned as well as whether or not they have permissions to view this tag on the source server.
Thank you for you response.
I've already added the necessary trusts in the PI Server from the host and tried running the interface service as administrator, but still no luck.
What logs specifically are you mentioning, sir?
The logs in System Management Tools under Operations > Message Logs. I'd be interesting in confirming the security context there for the source PI Server. I'd like to know that we see the connection from the interface come in as an identity which has permissions on these tags.
If you are going to use the same name for source and destination point, I would suggest simply using /TN - Tag of the interface point is also source point tag name. See page 10 in the User Guide for more details.
To test the security access as Robert mentioned, you can simply attempt to read the tag using APISNAP then entering the tagname. Make sure to run the command-line utility running as the same account as the PI-to-PI service is running.
I have removed the problem of the pi point not being found because of the IP address that was set in the trust was incorrect. So I changed it to the right one.
But right now I still could not collect the data from the source. Is there any other way to fix this?
We've come into the conclusion that the source has stopped working and had to be restarted from their side. All configurations all along from our side are correct and work when tested to a random tag.
Thanks everyone for your help!