Was able to connect for a while, until the server was migrated.

[Razmand1]

Hallo,

I was able to connect to the PI server and had lots of fun with it, until they migrated the server and now I cant get any data out of PI. I have tried a lot but the server administrators keep insisting that nothing has changed so i should be able to connect. I use the standard step by step guide to connect with the pi server and get time series data from data tags on the pi server. This is what I get as the OSI server version:

OSIsoft(r) AF SDK Version: 2.8.0.7444

And after I connect with the server using:

server = PIconnect.PIServer()

All is good, untill i want to get some data:

with PIconnect.PIServer() as server:
    points = server.search('*')
    for point in points[:10]:
        print(point)

Then I get this error:

PIAuthenticationException: Cannot connect to the PI Data Archive. Windows authentication trial failed because the authentication method was not tried. Trust authentication trial failed because insufficient privilege to access the PI Data Archive. 
   at OSIsoft.AF.PI.PIException.ConvertAndThrowException(PIServer piServer, Exception ex, String message)
   at OSIsoft.AF.PI.PIServer.RemoteConnect(AFConnectionPreference preference, NetworkCredential credential, PIAuthenticationMode authenticationMode)
   at OSIsoft.AF.PI.PIServer.InternalConnect(Int32 numRetries, IWin32Window owner, AFConnectionPreference preference, NetworkCredential credential, PIAuthenticationMode authenticationMode, Boolean checkConnectingAsSameUser)
   at OSIsoft.AF.PI.PIServer.AutoConnect(Boolean allowDirectConnect, Boolean force)

Can anyone help me with this please?

Kind regads,

Raz

[niltecedu]

This is a windows AD issue, see if your user has access to PI server

[Razmand1]

Hi Nilesh, Thank you so much for the reaction. Yes, my windows account is connected to pi, as per my excel I can get data from the tags I search using the pi data builder. Also the pi data link tab shows my connection to the server and the server name... Thanks again Op wo 1 feb. 2023 14:42 schreef Nilesh Zagade ***@***.***>:

…

This is a windows AD issue, see if your user has access to PI server — Reply to this email directly, view it on GitHub <#689 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATD3DR3A3JM6VUXICXRKD5LWVJR4PANCNFSM6AAAAAAUNUJZVA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[niltecedu]

hiya, so we have a similar issue come up quite often. try reinstalling pisdk since the windows account seems fine. seems like its trying to find it via older ip

…

On Wed, 1 Feb 2023 at 5:44 pm, Razmand1 ***@***.***> wrote: Hi Nilesh, Thank you so much for the reaction. Yes, my windows account is connected to pi, as per my excel I can get data from the tags I search using the pi data builder. Also the pi data link tab shows my connection to the server and the server name... Thanks again Op wo 1 feb. 2023 14:42 schreef Nilesh Zagade ***@***.***>: > This is a windows AD issue, see if your user has access to PI server > > — > Reply to this email directly, view it on GitHub > < #689 (comment) >, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/ATD3DR3A3JM6VUXICXRKD5LWVJR4PANCNFSM6AAAAAAUNUJZVA > > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> > — Reply to this email directly, view it on GitHub <#689 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJZ3KIG3DU7NIPGZF3MYTVLWVKOH5ANCNFSM6AAAAAAUNUJZVA> . You are receiving this because you commented.Message ID: ***@***.***>

[Razmand1]

Hi Nilesh,

Excuse me for reacting a bit late, I was on some training last couple of days.

Okay, so tomorrow will the system administrator be on site again, I will try and ask them to reinstall the PISDK. There is also another thing that can be noted:

I use Anaconda to navigate the different platforms, and when I pip install different versions of PIconnect, I get different error messages too... For example, when I reinstall PIconnect 0.8 version I get this error directly when I import PIconnect:

AuthenticationException: A call to SSPI failed, see inner exception.
at System.Net.Security.NegoState.StartSendAuthResetSignal(LazyAsyncResult lazyResult, Byte[] message, Exception exception)
at System.Net.Security.NegoState.StartSendBlob(Byte[] message, LazyAsyncResult lazyResult)
at System.Net.Security.NegoState.StartSendBlob(Byte[] message, LazyAsyncResult lazyResult)
at System.Net.Security.NegoState.StartSendBlob(Byte[] message, LazyAsyncResult lazyResult)
at System.Net.Security.NegoState.ProcessAuthentication(LazyAsyncResult lazyResult)
at System.Net.Security.NegotiateStream.AuthenticateAsClient(NetworkCredential credential, String targetName, ProtectionLevel requiredProtectionLevel, TokenImpersonationLevel allowedImpersonationLevel)
at System.ServiceModel.Channels.WindowsStreamSecurityUpgradeProvider.WindowsStreamSecurityUpgradeInitiator.OnInitiateUpgrade(Stream stream, SecurityMessageProperty& remoteSecurity)

When I Install PIconnect 0.9.1 I get this error only after I imported PI connect and connected to the server and request some data:

Cannot connect to the PI Data Archive. Windows authentication trial failed because the authentication method was not tried. Trust authentication trial failed because insufficient privilege to access the PI Data Archive.
at OSIsoft.AF.PI.PIException.ConvertAndThrowException(PIServer piServer, Exception ex, String message)
at OSIsoft.AF.PI.PIServer.RemoteConnect(AFConnectionPreference preference, NetworkCredential credential, PIAuthenticationMode authenticationMode)
at OSIsoft.AF.PI.PIServer.InternalConnect(Int32 numRetries, IWin32Window owner, AFConnectionPreference preference, NetworkCredential credential, PIAuthenticationMode authenticationMode, Boolean checkConnectingAsSameUser)
at OSIsoft.AF.PI.PIServer.AutoConnect(Boolean allowDirectConnect, Boolean force)

And with the latest PIconnect version (0.10.6):

ModuleNotFoundError: No module named 'pythonnet'

Also, when I use python 3.8 with PIconnect version (0.10.6): I get a different error:
C:\Users*myname*\Anaconda3\envs\py38\lib\site-packages\PIconnect\PIAF.py:41: InitialisationWarning: Failed loading server data for servername with error AuthenticationException
warnings.warn(

And again with 3.8 and now PIconnect 0.8: Directly error with importing PIconnect

AuthenticationException: A call to SSPI failed, see inner exception. ---> System.ComponentModel.Win32Exception: The target principal name is incorrect
--- End of inner exception stack trace ---
at System.Net.Security.NegoState.StartSendAuthResetSignal(LazyAsyncResult lazyResult, Byte[] message, Exception exception)
at System.Net.Security.NegoState.StartSendBlob(Byte[] message, LazyAsyncResult lazyResult)
at System.Net.Security.NegoState.StartSendBlob(Byte[] message, LazyAsyncResult lazyResult)
at System.Net.Security.NegoState.StartSendBlob(Byte[] message, LazyAsyncResult lazyResult)
at System.Net.Security.NegoState.ProcessAuthentication(LazyAsyncResult lazyResult)
at System.Net.Security.NegotiateStream.AuthenticateAsClient(NetworkCredential credential, String targetName, ProtectionLevel requiredProtectionLevel, TokenImpersonationLevel allowedImpersonationLevel)
at System.ServiceModel.Channels.WindowsStreamSecurityUpgradeProvider.WindowsStreamSecurityUpgradeInitiator.OnInitiateUpgrade(Stream stream, SecurityMessageProperty& remoteSecurity)

And with PIconnect 0.9.1: I added part of the error and highlighted it to show that self.connection.Connect(force_connection) was highlighted in jupyter notebook...

File ~\Anaconda3\envs\py38\lib\site-packages\PIconnect\PI.py:147, in PIServer.enter(self)
144 else:
145 # Don't force to retry connecting if previous attempt failed
146 force_connection = False
--> 147 self.connection.Connect(force_connection)
148 return self

PIAuthenticationException: Cannot connect to the PI Data Archive. Windows authentication trial failed because the authentication method was not tried. Trust authentication trial failed because insufficient privilege to access the PI Data Archive.
at OSIsoft.AF.PI.PIException.ConvertAndThrowException(PIServer piServer, Exception ex, String message)
at OSIsoft.AF.PI.PIServer.RemoteConnect(AFConnectionPreference preference, NetworkCredential credential, PIAuthenticationMode authenticationMode)
at OSIsoft.AF.PI.PIServer.InternalConnect(Int32 numRetries, IWin32Window owner, AFConnectionPreference preference, NetworkCredential credential, PIAuthenticationMode authenticationMode, Boolean checkConnectingAsSameUser)
at OSIsoft.AF.PI.PIServer.AutoConnect(Boolean allowDirectConnect, Boolean force)

Sorry for the long post, i wanted to make sure you got everything to look at. So I am not really sure what the problem really is... I appreciate all the help. Also real time would be appreciated. I love this module, so I am open to go the lengths to get this working again...

Kind regards,

Raz

PS: I use pip install to install this module in Jupyter notebook:

!python -m pip install piconnect

[Hugovdberg]

The error in 0.10.6 that pythonnet is not found is quite strange, it appears the installation did not succeed, but I'm not sure why you can still import PIconnect. pythonnet is listed as a required dependency both for pip and conda, so are you sure you did really install 0.10 completely?

The order in which the errors occur has indeed changed a bit since some of the initialization code has moved around. In 0.8 connection errors would lead to the package not loading at all, even if only one server was not reachable. In 0.9 the connection was only tried once you actually wanted to connect, but that meant some overhead on each call. In 0.10 the initialization was done at the start, but connection errors are only printed as a warning.

Also, the errors might be a bit different because different versions of PIconnect depend on different versions of pythonnet to make the actual calls using the Microsoft .NET Framework, but SSPI is the mechanism to negotiate the authentication method and using the current logged in user for authentication.

I really suspect there is something wrong in the installation of either PIconnect, pythonnet (maybe try in a clean conda environment?), .NET Framework or the PI AF SDK.

[Razmand1]

Hi Hugo,

Thanks for the reply,

So I got in touch with my system administrator and he removed all of PI OSI from my laptop and reinstalled it. Also, deleted Anaconda and reinstalled it. I use the following command in Jupyter notebook:

!python -m pip show PIconnect

response:

Name: PIconnect
Version: 0.10.6
Summary: Python connector to OSIsoft PI SDK
Home-page: https://github.com/Hugovdberg/PIconnect
Author: Hugo Lapré
Author-email: [email protected]
License: MIT license
Location: c:\users\razmand.hamarasheed\anaconda3\lib\site-packages
Requires: wrapt, pandas, pytz, pythonnet
Required-by:

and to install:
!python -m pip install piconnect

Collecting piconnect
Using cached PIconnect-0.10.6-py2.py3-none-any.whl (31 kB)
Requirement already satisfied: pandas in c:\users\username\anaconda3\lib\site-packages (from piconnect) (1.1.3)
Collecting pythonnet
Using cached pythonnet-3.0.1-py3-none-any.whl (284 kB)
Requirement already satisfied: wrapt in c:\users\username\anaconda3\lib\site-packages (from piconnect) (1.11.2)
Requirement already satisfied: pytz in c:\users\username\anaconda3\lib\site-packages (from piconnect) (2020.1)
Requirement already satisfied: numpy>=1.15.4 in c:\users\username\anaconda3\lib\site-packages (from pandas->piconnect) (1.19.2)
Requirement already satisfied: python-dateutil>=2.7.3 in c:\users\username\anaconda3\lib\site-packages (from pandas->piconnect) (2.8.1)
Collecting clr-loader<0.3.0,>=0.2.2
Using cached clr_loader-0.2.5-py3-none-any.whl (51 kB)
Requirement already satisfied: six>=1.5 in c:\users\username\anaconda3\lib\site-packages (from python-dateutil>=2.7.3->pandas->piconnect) (1.15.0)
Requirement already satisfied: cffi>=1.13 in c:\users\username\anaconda3\lib\site-packages (from clr-loader<0.3.0,>=0.2.2->pythonnet->piconnect) (1.14.3)
Requirement already satisfied: pycparser in c:\users\username\anaconda3\lib\site-packages (from cffi>=1.13->clr-loader<0.3.0,>=0.2.2->pythonnet->piconnect) (2.20)
Installing collected packages: clr-loader, pythonnet, piconnect
Successfully installed clr-loader-0.2.5 piconnect-0.10.6 pythonnet-3.0.1

Is there a different way to install?

Note that from the start it used to work, but not anymore after 1 year (when the migration happend). This could be due to something else than the migration, but just a note.

[Hugovdberg]

To me this sounds like there is some configuration issue on your computer. It is strange you can use PI Datalink, but not PIconnect, as they use the same DLL's and configuration to connect to the server as far as I'm aware. There is no configuration in PIconnect that keeps a reference to servers once the python process ends, everything is requested from the local configuration.

As I don't think this is an issue with this package, but a useful discussion, if only for documentation, I will convert this to a discussion instead of an issue.

[Razmand1]

Hi Hugo,

Thank you for the reply. What would be the configuration problem? Would i better reinstall Python/Anaconda? or do you mean anything else?

BTW: Love this module very thankful for it! great job!

Raz

[Hugovdberg]

I replied in the other thread, but I think it is the PI config on your machine or some installation error

[Razmand1]

Problem solved:

PI OSI soft was moved to a different server. We deleted PI OSI from the laptop and installed it but changed the standard server settings to the new server and all the problems stated above were solved.

I did not really understand how I was able to use PI processbook while still using the old server, but could not use PIconnect. But the problem is solved and I am happy once more :).