Sorry ,one correction : PI Analysis Framewrok is present on the PI server
Based on the error message it looks like you're using a PI Data Archive (PI Server) version that doesn't support windows authentication. Fist of all I would recommend that you upgrade your PI Data Archive to the newest version available. PI Data Archive 2012 have a lot of performance and security improvements.
DataLink 2013 and newer does not support using PI Users, the only workaround when you don't have the option of windows authentication is to create a PI trust. What you may do is to create a trust for Excel (excel.exe), that way your users can still use DataLink 2013 and newer.
Recommended: Upgrade PI Data Archive and create windows mappings for your users (AD security).
PI server version I'm using is 3.4.375.99
3 of 3 people found this helpful
PI Server 3.4.380.36 is the first server with support for Windows Integrated Security. (Ref: PI Data Archive - Roadmap Details )
Meaning you're basically left with two options to get DataLink 2014 (2013 and newer) working in your environment:
1: (Recommended) Upgrade your PI server to a newer version with support for Windows Security.
2. (Least effort) Create a PI trust that allows Excel (and/or IP range) access to your PI server.
Thanks Andre for your response.
First obtion is better but will take time as PI server is production server.
Hence, second obtion is much feasible as of now.But, I have a doubt in it:
It seems, I need to create trust for each user seeeking use of Datalink 2013 and above. Is it possible to create only one trust for application and users using datalink 2013 and above can connect to PI server easily with same trust?
2 of 2 people found this helpful
One trust pr user would be the most secure way to do this but this can become a nightmare for you (administrators) really fast. I don't think you can create a trust that only allows DataLink 2014/2013 since the connecting application would be Excel. To allow all Excel users (and only Excel) you could create a trust with a IP range and specify application Excel.exe: