Resolve specific PI SDK buffering issues  

Messages not listed here might be described on the OSIsoft Technical Support website.

Some of the messages below are written to the PI message log, while others are returned by PI SDK or displayed by a specific application. The same message can appear in more than one context, for example, a message returned by PI SDK might also be written to the PI message log, appear in an application, or both. The Program column shows the source of each message, but does not necessarily identify every possible context in which the message appears.
Note: In system messages, the term RPC data refers to both PI SDK and AF SDK data.
Message Program Description and steps to resolve
Buffering is turned off for PI Buffer Subsystem. Will not buffer either API or RPC data PI Buffer Subsystem Settings in PICLIENT.INI indicate that PI Buffer Subsystem is disabled on this computer. In this case, PI Buffer Subsystem will not buffer any data.

Steps to resolve:

Review the information in KB00042 to determine whether you can use PI Buffer Subsystem instead of API Buffer Server. If not, resume buffering with API Buffer Server.

Otherwise, to use PI Buffer Subsystem for both PI API and PI SDK buffering:
  1. Use PI ICU (Tools > Buffering) to change the buffering service from API Buffer Server to PI Buffer Subsystem.
    • If PI Buffer Subsystem 4.3 or later is installed, this starts Buffering Manager, which guides you through the upgrade to PI Buffer Subsystem.
    • If an earlier version of PI Buffer Subsystem is installed, this opens the Buffering dialog box, where you can select PI Buffer Subsystem.
  2. Then, in PI SDK (Utility > PI SDK Buffering > PI SDK Buffering Configuration), press F5 for updated status.

    The system displays a message indicating that PI Buffer Subsystem is buffering data to the PI Server that you specified using PI ICU.

Failed to write buffer configuration [-10733] PINET: RPC Resolver is Off-Line. {80043017} PI SDK You attempted to configure buffering using PI Buffer Subsystem, but PI Buffer Subsystem is not running. This may occur if you use SetEnvironmentOptions to set the buffered server. Not applicable when using PI Buffer Subsystem versions 4.3 or later.
0x80040725 Failed to update events on the server. PI SDK This message number, text, or both are returned when PI SDK attempts to send data directly to a server, but fails because PI Buffer Subsystem has already written to (and therefore taken ownership of) the point. This problem can happen if the buffering service becomes unavailable after a period of successful buffering.

This is a known issue. After PI Buffer Subsystem registers with the server and starts sending data for a point, only PI Buffer Subsystem can write snapshot values (either new values or edits) for that point. Point ownership is used to maintain consistent compression.

To resolve this problem, you need to identify and fix any problems that are preventing PI Buffer Subsystem from receiving or sending data. This allows PI SDK and AF SDK to send data using PI Buffer Subsystem instead of sending it directly to the server.

Write failed. Unbuffered write would desynchronize data. server_name PI SDK A PI SDK call that does not support buffering was made to a collective. Such calls cannot be completed because they can update only the primary collective member, which would result in desynchronized collective archives.
Pibufss service is not running. Unable to buffer. PI buffer subsystem should be running but isn't. PI SDK (related to next message below)This message might be returned to the calling application when using PIData.UpdateValue(..., dmReplaceDuplicates, ...) even though buffering appears to be disabled. In this case, data should be sent to PI Server and not buffered.
Pibufss service is not running. Unable to buffer. Configuration unavailable PI SDK (related to previous message above) This message might be returned to the message log when using PIData.UpdateValue(..., dmReplaceDuplicates, ...) even though buffering appears to be disabled. In this case, data should be sent to PI Server and not buffered.
Failed to retrieve the list of capabilities from pibufss. [-10727] PINET: RPC is Non-Existent. PI SDK (related to PI SDK Utility message PI Buffer Subsystem is not running. Please enable by going to the "Tools|Buffering Manager..." menu described below) If PI SDK Buffering is enabled, but the PI Buffer Subsystem service is not running, PI SDK Utility will log this error in the message log when PI SDK Utility starts and when you click Buffering > PI SDK Buffering Configuration.
Steps to resolve:
  • If you have not yet configured PI Buffer Subsystem 4.3, then in PI SDK Utility, click Buffering > PI SDK Buffering Configuration. In the PI SDK Buffering Configuration window, click Tools > Buffering Manager and follow the instructions on the screen to configure buffering.
  • If PI Buffer Subsystem 4.3 is already configured, use the Microsoft Windows Services snap-in to start the PI Buffer Subsystem service.
PISDK Buffering is not active PI SDK Utility > Buffering > PI SDK Buffering Configuration This message appears when the Enable PI SDK Buffering check box in the PI SDK Buffering Configuration dialog box is not selected. This means PI SDK buffering is not enabled.

Steps to resolve:

In the PI SDK Buffering Configuration dialog box, select the Enable PI SDK Buffering check box.

PISDK Buffering is active. Use Tools/Buffering Manager to manage buffering settings PI SDK Utility > Buffering > PI SDK Buffering Configuration This message appears when PI SDK buffering is enabled and PI Buffer Subsystem is running.

Steps to resolve:

No action is required unless you need to modify buffering settings or add a PI Server that will receive buffered data. You can use Buffering Manager to complete those tasks. In the PI SDK Buffering Configuration dialog box, click Tools > Buffering Manager.

PI Buffer Subsystem is not running. Please enable by going to the "Tools|Buffering Manager..." menu PI SDK Utility > Buffering > PI SDK Buffering Configuration This message appears when PI SDK buffering is enabled but PI Buffer Subsystem is not running. (This corresponding message also appears in the message log: Failed to retrieve the list of capabilities from pibufss. [-10727] PINET: RPC is Non-Existent.)
Steps to resolve:
  • If you have not yet configured PI Buffer Subsystem 4.3, then in PI SDK Utility, click Buffering > PI SDK Buffering Configuration. In the PI SDK Buffering Configuration window, click Tools > Buffering Manager and follow the instructions on the screen to configure buffering.
  • If PI Buffer Subsystem 4.3 is already configured, use the Microsoft Windows Services snap-in to start the PI Buffer Subsystem service.
Unable to load missing assemblies:OSIsoft.PISDK... etc PI SMT Certain files installed with PI SDK 2010 R2 are a different version than those used by PI SMT versions 3.2 and 3.3.
Steps to resolve:
  • Install PI SMT 2010 SP1

    -or-

  • Copy the files located in the PIHOME\PISDK\Interops1300 folder to %windir%\assembly.
Enabling Operational Intelligence