|
1.
|
Installing or upgrading 64-bit PI SDK will stop pinetmgr and dependent services without warning
Issue
Installing or upgrading the 64-bit PI SDK will stop the PI Network Manager (pinetmgr) subsystem and any dependent services without warning. This problem affects all data acquisition nodes running PI SDK-dependent services including PI Interfaces running with the PI Buffer Subsystem (pibufss) as a service dependency. It could also potentially affect any PI SDK application that is currently running.
This issue does not affect interfaces installed in the following system configurations:
...
23-Jan-2013
|
|
2.
|
PI Server 2012 using High Availability PI Collective does not work with PI SDK 1.3.4 - 1.3.6
Issue
This issue only impacts PI Server 2012 in High Availability PI Collective when using PI SDK 1.3.4 to 1.3.6. The issue is manifested in the following ways:
Configuring a new PI Collective:When you add a collective using the PI Connection Manager with PI SDK 1.3.4 to 1.3.6, PI SDK does not recognize the PI collective and the server will be added as a single PI Server. In the following screenshot, the icon for DNPISRV2012 appears as a single PI Server, although this is actually the primar...
11-Dec-2012
|
|
3.
|
Security Bulletin - Windows Common Controls could allow remote code execution (2720573) (Microsoft Security Bulletin MS12-060)
Update: Oct 5, 2012
A fix to address the Microsoft Security Bulletin MS12-060 is incorporated into the OSIsoft Prerequisites Kit Patch 2.1.1.0 and made available from the OSIsoft Technical Support Download Center and any physical media that includes the OSIsoft Prerequisites Kit. This kit includes the updated MSRuntimes.msi version 3.1.8 which supersedes the MSRuntimes.msi distributed in the OSIsoft Prerequisite Kit 2.1.0.0 released on 11-Jul-2012. Download OSIsoft Prerequisites Kit Patch 2.1...
05-Oct-2012
|
|
4.
|
Problems using PI ICU 1.4.8 and earlier to configure buffering when PI SDK buffering is enabled
Enabling API buffering on a node that already has SDK buffering enabled can cause configuration conflicts, and potential data loss. Select one type of buffering per computer and upgrade to PI ICU 1.4.9 when available.
Issues using the PI Interface Configuration Utility (ICU) to configure buffering
There are some potentially serious issues when using PI ICU 1.4.8 and earlier to configure API buffering on a node that has SDK buffering enabled:
When you open the buffering dialog in PI IC...
15-Dec-2011
|
|
5.
|
PI ACE 2.x manual recalculations fail when run under PI SDK 1.3.8
IssueWhen running PI ACE 2.x with PI SDK 1.3.8.x, manual ACE recalculations fail and cause the PI ACE Scheduler (PIACENetScheduler) process to become unresponsive.
Programs that install PI SDK 1.3.8
Note that the current PI ACE release as of Sept 2010, version 2.1.32, includes PI SDK 1.3.6, and is not affected (unless the PI SDK is upgraded to 1.3.8 separately).
Many OSIsoft software releases shipped in the year 2010 include PI SDK 1.3.8, including:
PI DataLink 2010
PI Asset Framewo...
07-Sep-2010
|
|
6.
|
PI Products and Windows 7 Compatibility
Please see the following announcement: OSIsoft announces Windows 7 compatibility on the main OSIsoft website for information regarding PI software and Windows 7 compatibility.
For compatibility for any given product, please visit the individual System Requirements page for that given product.
18-Mar-2010
|
|
7.
|
PI SDK 1.3.6.364 shows a different version number in AboutPI-SDK
A characteristic of the PI SDK 1.3.6.364 release is that AboutPI-SDK will display the version as 1.3.6.363. See Explanation below for details. To verify whether PI SDK 1.3.6.364 was properly installed follow these steps: On Windows XP/2003
Go to "Control Panel".
Open "Add or Remove Programs".
Find the program "PI Software Development Kit (PI-SDK)".
Click on "Click here for support information".
Locate the version number.
On Windows Vista
...
26-Mar-2009
|
|
8.
|
Potential errors sending or receiving large messages in PI SDK 1.3.6.361 PINS (client or interface) nodes
Issue:PI SDK 1.3.6.361 (included with the interfaces listed below), installs a version of the pinetmgr.exe process that may fail to process the complete message when large amounts of data are sent to or received from the PI Server. As a result of the message processing failures, processes that use the PINS routing such as PI SDK programs or PI 3 utilities or services such as PIBufss (Buffer Subsystem) may report timeout errors when sending data to the PI Server. [-10722] PINET: Timeout on PI...
08-Dec-2008
|
|
9.
|
OSIsoft software compatibility with the Microsoft Vista operating system [updated]
OSIsoft has tested the installation and function of the following software and versions on Vista (RTM). In all cases Vista testing was performed as a subset of the testing on the primary OS for the release (Windows XP SP2). All of the below software can be installed and run on Vista. Any issues identified on Vista are noted in the product release notes:
PI SDK 1.3.4.333 and later
PI SMT 3.2.x.x
PI DataLink 3.1.6 and later
PI ProcessBook 3.0.15.7 and later
PI ActiveView 3.0.15.04 and l...
04-Feb-2008
|
|
10.
|
Upgrading to PR1 software on the PI Server may cause the Default PI Server to be incorrectly re-assigned when "localhost" is used in the Known Servers Table.
If you upgrade to any PR1 products on the PI Server, and you meet all the following conditions, then follow the instructions below. This issue does not apply to clients or interface nodes.You have an entry in your Known Servers Table (KST) named "localhost." Check this by running AboutPI-SDK.exe located in the pipc\dat directory.Your Default PI Server is set to "localhost." Check this setting by choosing Tools> Options in AboutPI-SDK.You have another entry in your KST that...
30-Jan-2007
|