AL00326 - PI Data Archive 2017 SP1 is unavailable

(Updated September 14, 2017)

OSIsoft has released a Hotfix to fix this issue. Please consult the Release Announcement RL01245.

(Updated September 8, 2017)

OSIsoft Product Management issued a letter summarizing progress towards a resolution and next steps to all customers who downloaded PI Data Archive 2017 or PI Data Archive 2017 SP1 and may have been impacted by the issue described in this alert. You can download the letter here.

(Updated August 17, 2017)

OSIsoft is providing a temporary solution for our customers who may be affected by the issue described in this alert.

To apply the solution, download PI Data Archive 2017 Archive Check, a ZIP file that includes:
  • ArchiveCheck_2017.ps1  A PowerShell script that identifies corrupted archive files as well as archive files that are vulnerable to the bug but are not yet corrupt. 
  • PI2017AHF.exe  A utility that will protect vulnerable archive files from becoming corrupt.  If you do find that you have corrupted archive files caused by this bug, you can either restore them from a backup or use this utility to enable them to be reprocessed and loaded. 
  • ArchiveCheck2017_Instructions.pdf  Instructions for using the script and utility.
OSIsoft is committed to providing a permanent hotfix to resolve this issue as quickly as possible. We will update this alert as information becomes available.  If you have any questions, please contact OSIsoft Tech Support.

(Updated August 16, 2017)

OSIsoft was made aware of an issue with PI Data Archive 2017 and PI Data Archive 2017 SP1 that, under certain conditions, might cause corrupt archives and potential data loss.

 We have determined that this bug does not impact real-time data collection and archiving.
The bug impacts archives when backfilling is performed under some specific conditions (for example, when the archives being backfilled do not already have data for the tag being backfilled). Since these conditions are not easy to detect by looking at tag and archive configuration, we are working to provide tools to identify and possibly remedy the issue. When the bug does occur, the impacted archives might lead to backup failure. If the archive subsystem is restarted those archives might fail to load, resulting in unexpected archive gaps. For a detailed description of the issue, please consult Known Issue 176830.
For now, all customers who are using PI Data Archive 2017 and PI Data Archive 2017 SP1 should avoid performing any operations that may write data to non-primary archives until we provide a hotfix. For example, avoid any backfill operations such as those involving history-recovery/backfill interfaces (for example, PI to PI or PI Interface for RDBMS), analytics backfills or recalculations.
It is currently our highest priority to provide a fix for this issue. OSIsoft will take the following steps in the coming days and update this alert as we make progress:
  1. Provide a script that customers can run to detect archives that have been corrupted as well as archives that are vulnerable to the bug but are not yet corrupt. OSIsoft will also provide a tool to protect vulnerable archives. The corrupted archives will either need to be restored from a backup or reprocessed using the tool to allow them to be loaded again.
  2. Provide a hotfix. 
We apologize for the inconvenience and will continue to provide updates as information becomes available. If you have any questions, please contact OSIsoft Technical Support.

(August 10, 2017)

OSIsoft recently received a report of a critical bug in PI Data Archive 2017 SP1. While we investigate the nature of this bug and identify a resolution, downloads of PI Data Archive 2017 SP1 are disabled until further notice. We apologize for the inconvenience.

We will update our Technical Support site as more information becomes available.