Troubleshooting

This section contains some typical problems encountered installing and using the PI SDK with some suggested troubleshooting techniques. Often, the factor that causes a problem may be difficult to discover. To assist in analyzing problems the PISDKUtility contains a "Support Data" menu that will export a set of XML files containing a summary of relevant configuration information for analysis. This utility may be start from the PISystem start menu shortcut. When contacting technical support, this information summary may may provide technical support with the reason for any difficulties.

Connection Failures

Unable to connect to servers

Make sure the target PI System is running properly.

A good way to check minimal functionality of the server and the network is to try connecting to the server using the snapshot tool available in the PISDKUtility application. The utility may be started from the PISystem start menu shortcut.

Test the PI SDK connectivity by running the PISDKUtility application and selecting the connections menu item, then click on a server check box. If the connection succeeds the dialog updates information about the connected server and authenticated user. If the connection fails the dialog information is blank. You can attempt to connect to other PI servers you may have configured in your Known Servers Table as well as review and modify the configuration information for those servers.

Make sure the local PI Network Manager subsystem is running. The PISDKUtility "About PISDK" menu item contains a PI Services Status information summary. This summary indicates if the Windows services configured for verification are running. Click the "..." button to verify that pinetmgr is included or to include additional services for monitoring.

PI API Connects but PI SDK does not

In some environments you may find that the PI API is able to connect to a server (tested using the apisnap utility from %PIHOME%\bin) but the PISDK fails to connect (tested using the connection manager in PISDKUtility ). This can occur because more rigorous security mechanisms are used in the PI SDK and on PI3 servers when accepting PI SDK connections.

The PI3 authentication mechanism uses additional communication with the domain controller and nameserver if they are available. Typically the problem lies in slow or absent response by network database software. The PI SDK and the server may both be affected by responses from the network databases. Some good diagnostic tools include the nslookup utility on both the client and the server, in each case passing the name of the machine on the opposite end of the expected connection and verifying that the name can be resolved quickly. If this fails or is slow the DNS configuration, or routing is likely the issue and needs to be resolved to allow the PI SDK to function properly. Also, the tracert utility may show dissimilar network routes to and from the PI Server. Finally, the route print command may indicate network interfaces that have confusing or blocked network destinations.

To use nslookup, pass it the name of the machine you wish to resolve, for example:

c:\winnt\system32> nslookup myserver.mydomain.com
Server:  nameserver.mydomain.com
Address:  192.168.1.1
Name:    myserver.mydomain.com
Address:  192.168.1.2

The response shows first the DNS server providing the information followed by the name and address requested.

Setup Failures

Registering the PISDK Library

If you receive a message along the lines of "Can't create ActiveX object" when trying to access a PI SDK object it could be that registration of one or more COM servers failed during setup. Check the setup log for messages to this effect and try repairing or reinstalling the PI SDK . The PI SDK COM DLLs are self-registering and can be reregistered by using regsvr32, which is distributed with the Windows operating system. The PI SDK COM DLL's that need to be registered are:

pisdk.dll
pi2srvr.dll
pisdkcommon.dll
pisdkparse.dll
pisdkregistry.dll
pitimeserver.dll
pisdkctl.ocx
pisdkdlg.dll

Also the several system DLL's are installed or upgraded if necessary during setup. Consult the release notes for a list of those files.

PI SDK Type Library not found under Project References in Visual Basic

Check the setup log file. Try running the installation again. You can click the browse button on the References dialog and browse for the pisdk.dll file that was installed. If you succeed in browsing for the library you will be able to write code using the VB IntelliSense features but you will probably need to reregister the PISDK library to successfully run the program.

Enabling Operational Intelligence