Error and informational messages for PI ICU

The required support DLL PIGenericNames.dll is not present or not registered

This error indicates that the PIPC\Library\PIGenericNames.dll file is not installed, missing or unregistered. To register the file, open a command window, change directories to the PIPC\Library directory, and type in the following command:

Regsvr32 PIGenericNames.dll

The required support DLL PISpt.dll is not present or not registered

This error indicates that the PIPC\Library\PISpt.dll file is not installed, missing or unregistered. To register the file, open a command window, change directories to the PIPC\Library directory, and type in the following command:

Regsvr32 PISpt.dll

The PI SDK version is older than the required version

PI ICU requires PI SDK 1.3.4 or later on the machine on which PI ICU is to run. If the PI SDK version is older, it must be upgraded.

Error 713 attempting to load the ICU Control

This error indicates that the PI ICU control has been registered on this machine, but the physical file has been moved or deleted. To fix this problem, re-install the PI ICU control for the interface type.

Error 450 attempting to load the ICU Control

This error indicates that the PI ICU control is registered and physically present on this machine, but it does not provide all the methods that PI ICU requires. Generally, this indicates that the PI ICU control version is inappropriate for the version of the PI ICU running on this machine. The PI ICU control user manual should indicate which version(s) of the PI ICU control are compatible with which versions of PI ICU.

Error -2147220478

This error indicates that either the local or remote PI Network Manager process is not running, and the PI SDK is not able to communicate to the local or remote PI servers.

Start the PI Network Manager service on the appropriate node and then restart PI ICU.

No interfaces showing up in Interface drop down list for a particular node

This indicates that the PI ICU program could not access the Module Database on the particular node in question. If the drop down Interface list is empty or missing interface instances for a particular node, make sure that a connection can be made to that Host's PI Server. If it can and you still are missing interface instances, make sure you have read/write access to the Module Database from the node where the PI ICU is being run. If not, correct the connection problems and rerun PI ICU to load the interface instances.

PI ICU control is on machine, but does not show up in PI ICU

This usually indicates that the PI ICU control has not been registered. The setup kit for a particular PI ICU control will attempt to register the control. To manually register a control, open a command window, change directories to the PIPC\ICU\<ICU Control Directory> directory, and type in the following command:

Regsvr32 <ICU Control dll or ocx Name>

Critical Error -11425 from PIBufss

This error indicates that a buffered server was selected that PIBufss cannot communicate with and therefore PIBufss cannot buffer data to it.

Make sure the server selected can be reached and that the PI mappings or PI trust definitions are correct.

Critical Error -11452 and -11402 from PIBufss

This error indicates that PIBufss cannot create the shared memory buffers or disk buffer file.

The most likely reason for this error is because some application was running and buffering, but it was not shut down before PIBufss was restarted. It is holding open the shared memory buffers.

To fix this problem, PIBufss and the application must be stopped and then PIBufss is restarted followed by this application.