AVEVA™ Products Feedback Portal

Welcome to our new 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, select the product of your interest in the left column. Then 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 will first be moderated before they are made visible to other users of this portal.

This page is for feedback for specific AVEVA solutions, excluding PI Systems and Data Hub. For links to these other feedback portals, please see the tab RESOURCES below.

Add a new idea Subscribe
Status Future consideration
Portfolio area Enterprise SCADA Server
Products Administration / Installation
Created by Serge LeBlanc
Created on Sep 14, 2023

RELATED IDEAS

Address nuisance error log messages related to the Trend BLT

Detailed Description


Request that the Recordset open error be moved to ALWAYS as it does provide insight into an issue with trending a point

  • 2022-05-16 12:18:36.744 [TID=0x299c] WARNING: Trend: numCollects: Recordset open (execute) failed [-2147217900]:< Error collection entries - 0: [-2147217900] - Unable to find collect point: analog.CL00_CELT0612_ER_TK3801_LVL.curval> {C:\Agents\C2_ADO\_work\199\s\ServiceFramework\source\libBLTRPC\rpcBase.cpp:359}


Request the STATE_INIT message be moved to WARNING, in its current state as it provides no actionable information

  • 2022-05-16 12:18:36.744 [TID=0x299c] ALWAYS: Trend: Recordset processing failure; state: STATE_INIT {C:\Agents\C1\_work\3\s\Service\source\Applications\Trending\BLT\Trend\Trend.cpp:3494}



Expectation

Errog verbosity is adjusted
Idea business value

Customers have long complained about the verbosity of the error logs.

A clean error log is easier to use, and enables customers to focus on the actionable messages. A very verbose log can grow to a size that can introduce instability in the system.
Idea Type Improvement
Idea priority 2 – Limited use to my company
Work in
OASYS-542 Address nuisance error log messages related to the Trend BLT
Work status
  • Attach files
  • Admin
    Jake Hawkes
    Reply
    |     Sep 14, 2023

    These error messages are from an older version of the product. Are they still happening?