Certificates are incorrect or missing

If some of your certificates are either missing or incorrect, this is indicated by the Connection status properties of collectives CommStatus, SyncStatus, and SyncFailReason shown in the Properties list of a selected member.

To troubleshoot a connection issue, you might require:

• Access to the message logs for the primary and secondary members.

• The ability to run PI Collective Manager on both the primary and secondary computers, so you can evaluate connection status fields.

Some of the more common problems that might occur with synchronizing certificates are described here.

If you are running PI Collective Manager on the primary member, and CommStatus and SyncStatus display -10733 No certificate is available on the server for TLS authentication, the primary member does not have a certificate for that member.

If you are running PI Collective Manager on a secondary member, and that computer is missing a certificate, CommStatus and SyncStatus will display -10733 No certificate is available on the server for TLS authentication for that secondary member.

If certificates are not synchronized, meaning that the primary and secondary members have certificates for each other, but they are incorrect, PI Collective Manager on the secondary member displays appropriate information in SyncFailStatus for that secondary member, but PI Collective Manager on the primary member will not show this. On the secondary member, SyncFailStatus will show a –10407 no access error that provides some information about the certificate that the secondary sent to the primary.

If certificates are missing or incorrect from the store on your computer, this indicates that issues occurred during installation. In this case, contact customer support.

For further troubleshooting information, see the knowledge base article Procedures to fix certificate related problems in PI Collectives 2017, and later.

Note: You must upgrade each member of a collective to Data Archive 2017. If a member is not upgraded, synchronization of that member with the collective is suspended. However, data collection continues and clients are serviced as usual until the Data Archive 2017 upgrade process generates and stores a self-signed certificate.