4 Replies Latest reply on Mar 15, 2018 7:37 PM by gachen

    opcint.exe>PI-API> pinetwrite> piconnect failed [-1]: xxx-s-xxx:5450

    Bille

      Hello All,

      Is there a workaround to resolve opcint.exe>PI-API> pinetwrite> piconnect failed [-1]: xxx-s-xxx:5450

       

      Regards

       

      Bill

        • Re: opcint.exe>PI-API> pinetwrite> piconnect failed [-1]: xxx-s-xxx:5450
          LalBabuShaik

          As per KB : 20448OSI8, application must be restarted. If coding is possible, then then explicit disconnection (piut_disconnectnode()) and reconnection (piut_setservernode()) should be used to destroy that server context and reestablish it with a reinitialized/clean.

          • Re: opcint.exe>PI-API> pinetwrite> piconnect failed [-1]: xxx-s-xxx:5450
            gachen

            Hi Bill,

             

            Could you confirm the version of your PI OPC DA interface along with the version of PI API installed on that node? While seeing this error could indeed be a manifestation of known issue 20448OSI8, it should not be taken for granted that seeing this error is absolutely because of this known issue. API errors are very generic and typically very ambiguous, and the message you are seeing is as generic as they come:

             

            "opcint.exe>PI-API> pinetwrite> piconnect failed [-1]: xxx-s-xxx:5450"

             

            Broken down, "piconnect failed" means API was not able to successfully complete its call to the PI Data Archive server, specifically for a "pinetwrite" operation, which returned with error status "-1" (generic error). So all in all, the message does not tell us much, other than the API call to write data to the PI Data Archive failed for some reason.

             

            If you find that you are running a version unaffected by the known issue, then please check that the network connection is good between the interface node and the PI Data Archive server. In addition, if the connection is good and since this particular error is for "pinetwrite", it would also be a good idea to check the message logs on the PI Data Archive server. Specifically, see if there are messages indicating unhealthy behavior or errors with PI Snapshot Subsystem, such as '[-16212]/[-16214]' errors. If PI Snapshot Subsystem is in an unhealthy state, it could also cause API connections to fail to write and disconnect.

             

            Lastly, the fact that the PI OPC DA interface is trying to write directly to the server and get this error implies that your node is not using buffering. You may want to consider configuring PI Buffer Subsystem, which would prevent data loss in these scenarios.

            1 of 1 people found this helpful