• State Not Answered
  • Replies 9 replies
  • Subscribers 3 subscribers
  • Views 826 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,

 

Parents
  • 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

Reply Children
No Data