Skip to Main Content
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.

Status No status
Categories PI OLEDB Enterprise
Created by Kenneth Barber
Created on Oct 3, 2026

Allow the PI AF Application Service and the PI OLEDB Enterprise Server Agent to use different service accounts

In the release notes of PI SQL Data Access Server (RTQP Engine) 2024 R2, the solutions to known issues 3076509 and 3076508 form an awkward situation. The PI AF Application Service and the PI OLEDB Enterprise Server Agent must run as the same account, but since the latter service needs permission to the PI Asset Framework, it means that the account needs permission within one of the services that it runs, which is awkward. However, the solution to known issue 3076509 is to warn the user that the accounts must match during the installation of the PI OLEDB Enterprise Server Agent. I feel that AVEVA can do better.

Please fully solve this issue by allowing these services to use different service accounts so that each service can be given separate permissions. Until this is done, consider populating the service account of the PI OLEDB Enterprise Server Agent with the service account of the PI AF Application Service by default during installation.

  • Attach files