Troubleshoot the AVEVA PI OPC UA Server
- Last UpdatedMar 30, 2026
- 1 minute read
- Developer
General Issues
|
Issue |
Fix |
|---|---|
|
Unable to connect from the client to the OPC UA port. |
The port 48032 (or custom, if configured) must be allowed through the Windows Firewall by creating an inbound TCP rule for the OPC UA port. |
|
When launching the Configurator separately (and not using directly during an installation), an additional section called Common Platform (with sub-sections System Management Server and Federated Identity Provider) may appear as unconfigured. |
Ignore this configuration as it does not affect the operation of the PI OPC UA Server. |
Certificate Issues
|
Issue |
Fix |
|---|---|
|
If the certificate from OPC UA client is rejected because it is not trusted, you will get a message stating that the rejected certificate in located in C:\ProgramData\AVEVA\PCS\OPC UA Rejected Client Certificates\certs folder. |
To fix this issue,
If the certificate from the OPC UA Server is rejected by the client because it is not trusted, consult the documentation for the OPC UA client on how to trust the server certificate. |
|
Certificate is rejected by the PI OPC UA Server because it is not trusted. |
Consult the documentation for the OPC UA client on how to trust the server certificate. |