4 Replies Latest reply on Jan 16, 2019 9:38 AM by jyi

    PI SDK connection failed and cannot find reason




      I've been encountered a case of PI sdk connection problem.

      The environment and symptom is like this


      1. environment

      PI Server: 2016 R2 / located in domain network

      PI Interface: located in workgroup network(that means the network is isolated)

      PI Trust is used for connection between workgroup and domain network.


      2. configuration

      I had configured OPC interface A1, A2, those are linked with fail-over.

      I have configured additional OPC interface B1,B2, and a client C on workgroup network.

      (Except the client C, other clients located on the same domain network as PI Server)

      The OPC interface version is all the same.


      3. symptoms

      The additional interface B1, B2 and client C cannot be connected to PI Server

      while existing interface A1,A2 and clients in domain networks are still running well and have no problem with connection.


      The server-side log

      Disconnected ID: 11560 ; Process name: PISDKUtility.exe(4116):remote(4116) ; User: piadmin ; OS User:  ; Hostname: ; IP: XXX.XXX.XXX.XXX ; AppID: XXX ; AppName: PISDKUtility
      ID: 11560; Duration: 0.1666667 min.; kbytes sent: 6.445313E-002; kbytes recv: 0.5585938; app: PISDKUtility; user: piadmin; osuser: ; trust: XXXXXX address: XXX.XXX.XXX.XXX; ip host:
      Deleting connection:  PISDKUtility.exe(4116):remote(4116), Shutdown request received from PISDKUtility.exe(4116):remote(4116), ID: 11560  XXX.XXX.XXX.XXX:64125
      New Connection ID: 11560 ; Process name: PISDKUtility.exe(4116):remote(4116) ; User: piadmin ; OS User:  ; Hostname: ; IP: XXX.XXX.XXX.XXX ; AppID: 732 ; AppName: PISDKUtility
      Successful login ID: 11560. Address: XXX.XXX.XXX.XXX. Host: . Name: PISDKUtility.exe(4116):remote. User: piadmin. OSUser: . Trust: XXXXXX
      Trust <XXXXXX> Granted to: \|XXXXXX|XXX.XXX.XXX.XXX|PISDKUtility.exe (15)


      The client-side log

      Disconnected ID: 12 ; Process name: PISDKUtility.exe(4116):remote ; User:  ; OS User: ; Hostname: ; IP: XXX.XXX.XXX.XXX ; AppID: ; AppName: 
      ID: 12; Duration: 0.1666667 min.; kbytes sent: 0.5585938; kbytes recv: 6.445313E-002; app: ; user: ; osuser: ; trust: ; ip address: XXX.XXX.XXX.XXX; ip host: 
      Deleting connection:  PISDKUtility.exe(4116):remote; Routing ID closed by session.; ID: 12 XXX.XXX.XXX.XXX:5450
      Failed to connect to server XXXX : 0x800404ac


      I set the connection to use PI default user protocol only, and could connect sdkutility & ICU to PI Server.

      Then I configured OPC interface, pibufss and run both services.

      The system looks fine now, however, it is still very weird.

      The pisdktuility and ICU.exe cannot be connected to PI Server, but OPC interface and pibufss is connected.

      I tryied a test that install PI AF builder on the machine and try to connect to PI server. It got failed.


      To summarize...

      API connection via PI trust OK

      All PI sdk connection via PI trust but pibufss not-OK

      sdk connection via PI default user protocol OK

      (+ sdk connection via Windows authentication not-OK)


      4. What I want to know is...

      I think I've checked general things based on KB articles and my experience.

      Which part should I check more to make connection via PI trust on this case?

      What problem would be with the Interface  B1,B2?

        • Re: PI SDK connection failed and cannot find reason

          Hi Jonghyun


          Looking at the logs and description of the problem, it looks there is some problem with client connection to server. As per the architecture defined you are connecting the client interface in work domain to PI server with different domain using trust. Hence would like you to verify the trust connection from Interface to PI Server.


          If you are using trust using network name, then would request you to create IP address and limit the access using application information as below


          Trust with Network Name: Application name (ICU)


          Trust with IP Address : Application (PI OPC inteface)



          Similary you can configure for SDK : PISDKUtility.exe,PIbufss.exe. 


          Once configured then would request you to connect to PI Data Archive and check network statistics in SMT  (Trust column) to understand the connection details.


          Also recommend you to check the logs on PI data archive server for every connection attempt.




          • Re: PI SDK connection failed and cannot find reason

            The 0x800404ac is a generic connection error. You can check the details of error codes in PI SDK Utility:

            0x800404ac (-2147220308) - Unable to open a session on a server.  Verify the local pinetmgr service and the remote PI system are running. 


            This could be caused due to the delay in client's hostname lookup in the PI Data server side and/or client's user accounts lookup in the PI Data server side.

            Please check the tuning parameter, ReverseNameLookupFlag in the 'Net Manager' tab from PI-SMT>Operation>Tuning Parameters. And try setting it to 0 and restart the PI Services.

            When PI Clients(interfaces, users) are in workgroup and PI Server is in domain, this scenario can happen. Other (not recommended) workaround is to add all non-Domain PI Clients' IP addresses and hostnames to hosts file in the server side or in DNS.

            KB01154 - Troubleshooting connectivity to the PI System - When using PI Trusts




            1 of 1 people found this helpful