Release notes

4.7.3.1

Overview

PI Universal Interface (UniInt) is the underlying framework for most PI interfaces. This maintenance release of the UniInt framework consists of minor bug fixes and security enhancements.

Fixes and Enhancements

Fixes

There are no fixes with this release of PI Universal Interface (UniInt).

Enhancements

This section lists enhancements as part of the PI Universal Interface (UniInt) release:

Known Issues

For performance counters to work properly, you must install the pictrdll.dll file in the following directories:

• If you are running on a 32-bit machine, install the file in the Windows\system32 directory.

• If you are running on a 64-bit machine, install the file in the Windows\sysWOW64 directory.

Security information and guidance

We are committed to releasing secure products. This section is intended to provide relevant security-related information to guide your installation or upgrade decision.

We proactively disclose aggregate information about the number and severity of security vulnerabilities addressed in each release. The tables below provide an overview of security issues addressed and their relative severity based on standard scoring.

Overview of New Vulnerabilities Found or Fixed

This section is intended to provide relevant security-related information to guide your installation or upgrade decision. We proactively disclose aggregate information about the number and severity of the security vulnerabilities that are fixed in this release.

There are no security vulnerabilities fixed in this release.

Technical support and feedback

For technical assistance, contact OSIsoft Technical Support at +1 510-297-5828 or log a case through the OSIsoft Customer Portal. Additionally, the Contact Us page on the portal offers contact options for customers outside of the United States.

When you contact OSIsoft Technical Support, be prepared to provide this information:

• Product name, version, and build numbers

• Computer platform (CPU type, operating system, and version number)

• Time that the difficulty started

• Log files at that time

• Details of any environment changes prior to the start of the issue

• Summary of the issue, including any relevant log files during the time the issue occurred