The PI SDK looks for registry keys under the HKLM\SOFTWARE\PISystem\PI-SDK key. I haven't heard of the Override key value. Could it be that the error message ended with "pathOverride" and not "override"? Could you please post here a screenshot of the error (maybe there are more details in the error that we are missing)?
What is the version of PI SDK?
Are there any relevant messages in the local PI SDK log? You can view the log in PISDKUtility -> Tools-> Message Log
Could you please also double-check the PI Data Archive connection settings in PISDKUtility -> PI SDK-> Connections?
If this is a single server: select the server and check the Network Node information.
If this server is a part of the collective: right-click on the collective and select Member Setup. Here, check the Path parameter.
The message indeed ends with "pathOverride."
the error that showed up in the message log is (with IP redacted): "5/26/2016 3:27:45.05301 PM, , Error, Failed to connect to server xxx.xxx.xxx.xxx : 0x80040402, PISQLCommander, , PISDK"
Here's the list of registered/installed components
PISDK.dll 22.214.171.1246 4/8/2015 1:33:58 PM C:\Program Files\PIPC\PISDK
PISDKCommon.dll 126.96.36.1996 4/8/2015 1:34:14 PM C:\Program Files\PIPC\PISDK
PISDKParse.dll 188.8.131.526 4/8/2015 1:34:18 PM C:\Program Files\PIPC\PISDK
PISDKRegistry.dll 184.108.40.2066 4/8/2015 1:34:22 PM C:\Program Files\PIPC\PISDK
PITimeServer.dll 220.127.116.116 4/8/2015 1:34:30 PM C:\Program Files\PIPC\PISDK
sdktrace.dll 18.104.22.1686 4/8/2015 1:34:58 PM C:\Program Files\PIPC\PISDK
I seem to be connected in the PI SDK Utility. The server name is bolded and checked. I also see the connection type and the connected user (PI Trust as pidadmin). I'm connected to a PI server version 3.4.395.80. It also says "connected as piadmin" near the bottom.
I'm not sure how to select the server and check the Network Node information. Where is that information?
Thank you so much for you help!
1 of 1 people found this helpful
Sounds like an authentication problem. The Data Archive server probably doesn't have a trust for PI SQL Commander's connection.
Creating the necessary trust would be a short-term solution. Here are a couple of videos to help with this:
As a long-term solution, I highly recommend that you configure Windows-based security. Here are a couple of videos on this:
Thank you Anna. I will watch the videos and report back on my issue.