I've been encountered a case of PI sdk connection problem.
The environment and symptom is like this
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.
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.
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.
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?