Client connection log messages

PI Network Manager (pinetmgr) writes messages to the PI message log that track communications between PI clients and the Data Archive server.

The following message from pinetmgr indicates that a client is attempting to connect to the Data Archive server. Note that a connection ID (cnxn ID) is assigned.

Note: The following example is applicable to a PI system that is running PI API version 1.6.8 or earlier. The example does not apply to PI API 2016 for Windows Integrated Security, since it shows the system connecting to a trust.

D 22-Sep-09 21:41:33 pinetmgr (7004)
>> PInet accepted TCP/IP connection, cnxn ID 31 Hostname: , 195.10.22.187: 1269

A PI SDK-based client will first publish its name. In this example the client name is AboutPI-SDK.exe.

I 22-Sep-09 21:41:33 pinetmgr (7039)
>> Connection accepted: Process name: AboutPI-SDK.exe(4372):remote(4372) ID: 31

The Data Archive server will then attempt to authenticate the client. That is, the client will pass in certain credentials and the Data Archive server will accept or reject these credentials. In this example the client successfully connects via Windows authentication:

I 22-Sep-09 21:41:33 pinetmgr (7082)
>> Successful login ID: 31. Address: 195.10.22.187. Name: AboutPI-SDK.exe(4372):remote. Identity List: piadmins | PIWorld. Environment Username : FABRIKAM\testuser. Method: Windows Login (SSPI,Kerberos)

If the client is unable to connect via one method, it may try another. Here it fails to connect via Windows authentication but is able to connect via trust.

I 22-Sep-09 22:38:27 pinetmgr (7138)
>> Unsuccessful login ID: 35. Address: 195.10.22.187. Name: AboutPI-SDK.exe(43
72):remote. Credentials used: FABRIKAM\testuser. Method: Windows Login (SSPI,Kerbero
s). Error: [-10433] No identity mapping for this request
I 22-Sep-09 22:38:27 pinetmgr (7076)
>> Successful login ID: 35. Address: 195.10.22.187. Host: . Name: AboutPI-SDK.e
xe(4372):remote. User: piadmin. OSUser: . Trust: addertrust

The server administrator has the option to disable certain authentication methods. In this example, explicit logins have been disabled. The message will look like the following example:

I 23-Sep-09 12:52:35 pinetmgr (7138)
>> Unsuccessful login ID: 44. Address: 195.10.22.187. Name: AboutPI-SDK.exe(50
48):remote. Credentials used: piadmin. Method: Explicit Login. Error: [-10431] Greg Holt 2010-08-03: Weird the way it broke Authentication across two lines Authentication method is disabled by current server policy
If the server is unable to authenticate a PI SDK-based client, it will be forceably disconnected.
I 22-Sep-09 22:25:03 pinetmgr (7096)
>> Deleting connection: AboutPI-SDK.exe(4372):remote(4372), Shutdown request
received from AboutPI-SDK.exe(4372):remote(4372), ID: 31 195.10.22.187:1269

PI API-based applications have a different set of connection establishment messages. All PI API-based client connection messages begin with "New Pinet 1 connection". First the Pinet 1 protocol is printed:

D 22-Sep-09 21:04:01 pinetmgr (7051)
>> New Pinet 1 connection: RandE Protocol: 00010008

The Data Archive server then attempts to use the credentials of the incoming connection to locate a record in the PI trust database. If a match is found, the following message is written (For PI API-based clients the published application name is truncated. The name is a five-character name: four characters plus a capital "E". In this example, the client name is RandE):

I 22-Sep-09 21:04:01 pinetmgr (7053)
>> New Pinet 1 connection: RandE Successful Trust-Relation login: adder2k3_32_1.osisoft.int|127.0.0.1|RandE piadmin.
If a match is not found, the messages are:
I 22-Sep-09 21:53:40 pinetmgr (7054)
>> New Pinet 1 connection: RandE No Trust established for: adder.osisoft.int|19
2.168.5.137|RandE. Explicit login is required for access.
I 22-Sep-09 21:53:42 pinetmgr (7077)
>> Access Denied: [-10413] No trust relation for this request ID: 32. Address
: 195.10.22.187. Host: . Name: RandE. User: . OSUser: . Trust: