Trend FlushQueueLength too lar

Hi All,

I have system architecture like one redundant CitectSCADA 2016(Aug Update) with Historian server and communicating healthy. Here i am using only primary server for testing purpose as secondary server not available as of now.

My PC specification is as below:

OS: Windows 10 Pro (Build 10240) x64-based

RAM: 16GB

Hard Disk: 1.5 TB

My Disk usage is ~2-3%, Memory Usage is ~23-25% and CPU usage is ~9-15%.

I am getting continuous Hardware alarm as below:

Tag: Generic

Name: General

Desc: Low Physical memory

ErrPage: HealthCheck

ErrDesc:Trend FlushQueueLength too lar

Please suggest anyone know about this or any solution.

Parents

Olivier over 6 years ago

Hi Bhadresh,
If you are just running the Primary Server, you could try setting [Trend]EnableBackfill=0 for now. This should hopefully resolve the hardware alarm. Don't forget to remove this parameter when you get your secondary server up and running. Also, you might like to check out Technical Note 8549:
https://softwaresupportsp.schneider-electric.com/#/okmimarticle/docid/tn8549
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Reply

Olivier over 6 years ago

Hi Bhadresh,
If you are just running the Primary Server, you could try setting [Trend]EnableBackfill=0 for now. This should hopefully resolve the hardware alarm. Don't forget to remove this parameter when you get your secondary server up and running. Also, you might like to check out Technical Note 8549:
https://softwaresupportsp.schneider-electric.com/#/okmimarticle/docid/tn8549
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Children

No Data