Troubleshoot common PI point errors

PI Point Not Found

Ensure the PI point exists on the configured Data Archive. Verify that the identity is mapped to the service account running the PI to CONNECT Agent and has read permission on the PI point and the PI point data.

PI Point Type Change Detected

Check the PI to CONNECT event logs in the Windows Event Viewer for the cause of the error. Filter the logs by "Type Change" or event ID "204" to locate the error message that contains the ID of the PI point that had its type changed. Change the type of this point to match its respective SDS Stream type. Then, restart the transfer to ensure all data is sent from the PI point in question. For more information, see PI to CONNECT change synchronization.

Cannot connect to the Data Archive. Windows authentication trial failed because insufficient privilege to access the Data Archive. Trust authentication trial failed because insufficient privilege to access the Data Archive.

Configure a PI mapping for the service account running the PI to CONNECT Agent that can connect to Data Archive. We recommend this approach as it is the most secure connection method. For information on creating PI mappings, see the section on how to create a PI mapping in the Run the PI to CONNECT Agent Configuration Utility topic.

[-10722] PINET: Timeout on PI RPC or System Call

Ensure the Data Archive is turned on, responsive, and able to receive connections over port 5450.