AVEVA™ PI System™ Feedback Portal

Welcome to our feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas and comments are visible to all other users.


This page is for feedback specifically for AVEVA PI System. For links to our other feedback portals, please see the tab RESOURCES below.

Add a new idea Subscribe
Status No status
Product AVEVA™ PI Server
Categories Data Archive
Created by Guest
Created on Aug 20, 2022

RELATED IDEAS

PI Archive ability to recover from drive disconnect

With everyone having virtual servers these days the host VM and SAN storage are on separate devices. When the storage device is unavailable or disconnected even briefly, the PI Archive process errors and gets DISABLED and can ONLY be restarted by a manual restart of the PI Archive Subsystem. You will see Snapshot updates since the VM is still running fine, but nothing gets into or out of the Archives. The requested enhancement is for the Archive Subsystem to be able to recover from this situation on its own. Here is the error message you will get when this happens to you: The request could not be performed because of an I/O device error. was detected while accessing archive file D:\PIArchives\PI_Archive_2018-09-16_18-25-13.arc. Archiving is disabled.
  • Attach files
  • Joe Staublin
    Aug 28, 2025

    I have a similar problem when older, read-only archive files are accessed from a remote share. Periodically, the files become unavailable to query. There is no indication in PI-SMT that anything is wrong. We sometimes see a PI MessageLog entry "Failed to access the archive file" when this happens.

    unregistering & re-registering the archive file seems to be the only way to recover access to the file. This seems to be related to a change of anti-malware software on our servers.

    Scheduling a search for the PI Message Log entry and automatically repairing seems to help some.

    Reply
  • GaryYegiazaryan
    Nov 7, 2022

    This directly impacts the resiliency of the PI data archive. Its inability to recover its own archive files results in an impact on critical users who are querying for data.

    Reply