Replies: 1 comment
-
|
That is some weird behaviour. I'm not sure why it would work from one connection but not the other. As I only use the Windows authentication, I can not test this. Do you have a complete snippet to reproduce the error so I can at least trace which parts of the code you use? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
So I imagine this has something to do with how our PI is configured and our remote connections are also configured, but thought I would reach out here.
When I am remote and not in the office, and connected via my VPN connection, PIConnect works flawlessly connecting to the default server and I can access data.
However, now that I am going back into the office more, I am getting access/connection issues that I cannot resolve:
Here is the error I am getting
So I have tried multiple lines of code to try and connect. PIConnect detects the default server, 'sccpi3' but just can't connect.
Here is what I tried and runs, with no errors, but then I can't get data:
PI.PIServer(server='sccpi3', username='username', password='password', domain=None, authentication_mode=AuthenticationMode.PI_USER_AUTHENTICATION, timeout=None)And it appears to tell me I am connected:
PIServer(\\sccpi3)Internally when accessing Datalink or Processbook, we use PI User Authentication.
Any help is appreciated.
Beta Was this translation helpful? Give feedback.
All reactions