• State Not Answered
  • Replies 9 replies
  • Subscribers 3 subscribers
  • Views 825 views
  • Users 0 members are here
Options
Related

PI VISION DOES NOT CONNECT TO A COLECTIVE DATA ARCHIVE

catharinasilveira

I had 2 DA i created kerberos delegation to both , and in the pi vision admin pag i was able to connect with both. After i create a collection of thoses 2 DA the vision in the page shows the X , but somehow i am able to search for the tags,

 

  • 0
    1. Have you verified that the SDK (or more likely PSE) connections have updated? ie, has the KST been updated on your Vision server?
    2. Did you restart Vision after ensuring the KST was updated to reflect the Collective instead of the individual servers?
    3. Did you verify the collective shows up in the Admin page for DA servers (which also verifies the KST) and that it is selected?

    Also, I do recommend using AF to reference data over directly referencing PI Points.

  • 0 in reply to MainelyInnovations

    Hello ​ , thank you for the help.

    1 - I was able to connect on both SDK and PSE and show the the collection connect

    2- Yes i run the iisreset. Has another way to restart PI VISION?

    3- The colective shows, but as a said with the red X.

    Do you think could be something related to the fact i am using the certificated from the osisoft and it is connect using http and not https ?

  • 0
    1. Make sure you are giving the Collective group a name that is different from the primary and secondary names.
    2. Connect to one of the collective members from PSE (Inside PI Vision Server). This should connect you automatically to the collective group.
    3. Refresh PI Vision Admin Page to see the collective name under Data Servers tab.
  • 0 in reply to Community User

    Hello (Missing Content)​ 

    Thank you for your comments.

    I had tried thoses steps and shows the same error .

    One thing when i try to connect to the DA shows this message in the message log

    -Deleting connection: Accepting TCP/IP Connection, waiting for protocol version, Asynch read failed. [2] The system cannot find the file specified., ID: 749  

    -Deleting connection: Accepting TCP/IP Connection, waiting for protocol version, client attempted TLS connection but PInetmgr does not have a certificate loaded. ID: 748 

    All thoses messages are related to the PI Vision server machine.

    Do you have a ideia what can be ? the Kerberos was setp for both DA , when i run :

    setspn -q PIServer/<hostname>

    it says Existing SPN found for both Da, soo i am not sure if is related to kerberos.

     

     

  • 0 in reply to catharinasilveira

    First, where is the red X that you're bringing up? Secondly, the Kerberos configuration you've mentioned here is the DA portion which is configured automatically when the DA is installed (although it does break at times). Configuring a collective out of individual PI Servers would not break existing Kerberos Delegation for PI Vision. I would recommend going through this KB to validate that delegation is setup correctly (depending on what you're actually seeing) - Knowledge (osisoft.com)

  • 0 in reply to catharinasilveira

    Thank you ​ 

    I am seeing the red X in PI Vision admin pag.

    I am checking the kerberos delegation, but i am also verify the message logs in DA. like i said show messages like that:

    -Deleting connection: Accepting TCP/IP Connection, waiting for protocol version, Asynch read failed. [2] The system cannot find the file specified., ID: 749  

    -Deleting connection: Accepting TCP/IP Connection, waiting for protocol version, client attempted TLS connection but PInetmgr does not have a certificate loaded. ID: 748 

    Now i am looking for for something related to TLS because when i run the command shows me this information:

    F:\Program Files\PI\adm>pidiag -tls --verify

    Failed Reasons(3) are listed below

        TLS Certificate Registration is incomplete

        Run pidiag -tls -r <thumbprint> to re-register

        Verification Failed

    Do you think it could be related to this problem?

    ​

  • 0 in reply to catharinasilveira

    ​  and as i said, before the collection , both DA were connected to PI Vision . Once the collection was created on the PI admin page shows the red X in the collective name, but at the same time i am able to pull data from the colletive in a display on pi vision for example

  • 0 in reply to catharinasilveira

    @catharinasilveira (Customer)​ 

    It seems to be certificates issue. You should install the first server certificate in the second server and vice versa without copying private keys

  • 0

    Hi ​ 

    I’m encountering the same issue when connecting via HTTPS. Additionally, sometimes the Data Archive collective appears, while other times it does not. I'm using a certificate to access PI Vision, and after experimenting with changing the certificate in the IIS bindings, I noticed that when I connect via HTTP through port 80, the Data Archive collective displays perfectly in the admin page.

    Could you please try this on your end? Based on my observations, it seems most likely to be a certificate-related issue.