Alarm Server Error

Hi @carlos-migu0845,
It sounds like there is an error getting the tag data.
Here is some feedback from another customer issue which might help:

The trace in question occurs when reading the tag values of a digital alarm's
VarA or VarB in order to process the digital alarm.

"Error evaluating 450" where 450 is the error code which stands for
INVALID_TAG_DATA. This occurs when there is an error reading either m_VarA or
m_VarB.

This error trace is printed when trace log is running with
[Debug]SeverityFilterMode=Error. If this is set to
[Debug]SeverityFilterMode=Warning, then additional logging is also provided
which will indicate whether the problem is with m_VarA or m_VarB.

I hope enabling more logging will help you track down the source of the problem.

Hello Olivier

Thank you for your feedback. 

In these three examples, a tried to check if there are troubles to read data from IOserver but using the tag debugging, we don't get any trouble.

Regards

Miguel

Hello Agian

Using another filter in debug, including the warning, we got the following error:

The can't see the trouble between IOserver and Client. Should be a trouble between IOServer and AlarmServer. 

We got a reading error in variable A and B for same alarm.

Thank you

Miguel  

Just an idea but are the VarA and VarB in the same cluster as the original tag? You may need to enable inter-cluster comms in your computer setup.
You could check that you've EXPLICITLY specify the vars as "CLUSTER.VarA" and "CLUSTER.VarB"?

Hi Miguel 

Did you get a solution to this?