The PI interface cannot send data to the data archive and error 10054 appears. So, on the PI SMT, the tags receive the name "configure" instead of the value of the data source.
I hope you could help me with this.
Error 10054 is a Winsock error (Connection reset by peer), which indicates a network communications issue between the interface node and PI server. So a few things for you to check:
- Can you ping the PI server from the interface node?
- Can you make a PI-API connection to the PI server using the apisnap utility?
- Do you have an adequate PI Trust or PI Mapping configured for the interface connection?
- What information does the PI servers PI Message log show for the incoming connection?
The PI Interface and PI Server are installed on the same node. Every connection was established and working properly. After reboots, it was observed that the server was no longer receiving the values from the data source. Observing the error, the message log showed the following message:
Answering the questions:
The PI Interface and PI Server are on the same machine.
The following error is displayed while trying to connect:
Yes, because the connection was working properly.
The print is being shown above.
Thanks in advance for your help.
As John mentioned above, I would verify the complete set of SDK logs on your PI Data Archive. The print screen you show only contains the logs for your OPC interface. Here is what you could do:
In an admin command prompt navigate to the %piserver%\adm directory:
cd /d %piserver%\adm
Use pigetmsg.exe to output the logs to a .txt file:
pigetmsg -f >SDKLogs.txt
Stop/Start your interface and wait a few minutes. You can stop pigetmsg.exe in the command prompt by entering CTRL+C.
Have a look in your SDK logs to see if you have more information.
It's very interesting that you cannot run apisnap locally on your PI Data Archive. Are you sure the default server is the local server? Can you try running:
apisnap.exe <PI SERVER NAME>
Let us know what your findings are.
OK, what we really want to see however are the log entries from the PI server processes pinetmgr (PI Network Manager) and pibasess (PI Bases Subsystem) to see what they are doing with the incoming connection from the interface. You will need to pipe the output of pigetmsg to a text file for a longer period of time so we can see this information. It's also a bit strange that apisnap won't connect locally on the PI server. What is the default server listed in your %PIHOME%\dat\pilogin.ini file?
I have experienced this error  once. This behavior is generally observed when an interface / application which sends data to PI runs into insufficient disk space issue. This causes buffer functionality and remote host connection is terminated. Hence please check buffer statistics/ status and ensure sufficient disk space for buffer file. After rectifying disk space issue for buffer, buffering service and interface/application service can be restarted.
Retrieving data ...