Hi guys,
Just updated to 14.01
Several test that have a 'Use "Warning" status if..' setting now give errors like:
Invalid expression: ConditionEval: Unknown operator:
followed by the condition value itself.
These are Shell scripts, returning a value from the script, either a string or numeric value.
It happens with both string and numeric condition.
Maybe something changed in the syntax?
When I remove the 'Use warning' setting, the tests run fine, returning the actual value of the test.
V 14.01: Errors when using 'Use warning status if'
An actual test (not a ShellScript btw):
Windows Performance Counter (Exchange Queue size):
\MSExchangeTransport Queues(_total)\External Aggregate Delivery Queue Length (All External Queues)
--> The test returns a 2-decimal numeric value (e.g. 0.00 or 7.00 or whatever...)
Use warning if expression:
%SuggestedReply% > 0 and %SuggestedReply% < 10
--> Test status 'bad' after 10 fails
Test result:
13/07/2023 10:35:22 Exchange External Delivery Queue Length (PerfCounter) Unknown Invalid expression: ConditionEval: Unknown operator: "0,00" Perf Counter test (External Aggregate Delivery Queue Length (All External Queues))
If you need more info, just let me know
Windows Performance Counter (Exchange Queue size):
\MSExchangeTransport Queues(_total)\External Aggregate Delivery Queue Length (All External Queues)
--> The test returns a 2-decimal numeric value (e.g. 0.00 or 7.00 or whatever...)
Use warning if expression:
%SuggestedReply% > 0 and %SuggestedReply% < 10
--> Test status 'bad' after 10 fails
Test result:
13/07/2023 10:35:22 Exchange External Delivery Queue Length (PerfCounter) Unknown Invalid expression: ConditionEval: Unknown operator: "0,00" Perf Counter test (External Aggregate Delivery Queue Length (All External Queues))
If you need more info, just let me know
1) you forgot to use "" or '' around %SuggestedReply%
This may work when Reply is correct number but in case of some problem Reply may return text, not a number, e.g. "Access is denied" error. So expression will not be processed
2) If your system is uses dot as decimal separator (0.00 and 7.00 in your sentence above) then 0,00 is not a valid number. That's why error raised.
In other words: use expression like ("%SuggestedReply%" > 0) and ("%SuggestedReply%" < 10)
Regards
Alex
This may work when Reply is correct number but in case of some problem Reply may return text, not a number, e.g. "Access is denied" error. So expression will not be processed
2) If your system is uses dot as decimal separator (0.00 and 7.00 in your sentence above) then 0,00 is not a valid number. That's why error raised.
In other words: use expression like ("%SuggestedReply%" > 0) and ("%SuggestedReply%" < 10)
Regards
Alex
