Togglebutton: Script triggered by parameter from element threw an unhandled exception.

Solved1.12K viewsexception QAction unhandled
0
0 Comments

Hi all,

Driver: Generic Ping

Version: 3.1.2.3

DM version: DM 9.6 CU23 with HF

We have a parameter executing a qaction that seems to be failing before the qaction even starts. See the logging below:

2022/07/06 15:04:28.435|SLProtocol – 13832 – Ping Manager|6556|CQAction::RunWrapped|DBG|-1|Script 1062 triggered by parameter 1072 from element ‘Ping Manager’ threw an unhandled exception. Please check the element log-file.

The element log file is the log file that the log is found, so it’s a bit confusing as to what we should check, although this error seems vaguely familiar.

Other parameter sets on the same table are working, but only param 1072 executes qaction 1062 which appears to be the only qaction that’s failing like this.

What could be causing this? There is a multithreaded timer executing a separate qaction in this driver, but I’m not sure that those are related. Is there a log I could check to be sure?

Any help would be greatly appreciated!

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 13th July 2023

1 Answer

1
3.60K 2 Comments

Hi Alex,

Is it possible that the qaction (sl scripting) is triggered before the element is up and running (sl protocol)

Or do you encounter this every time the qaction needs to run?

Also note that our catalog already has a newer version that contains multiple fixes: 3.1.2.7 https://catalog.dataminer.services/result/driver/530

Is the problem still present when using this latest released version?

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 13th July 2023
Alex Johnson [SLC] [DevOps Advocate] commented

Hi Mieke, thanks for the reply.

This is encountered every time the qaction is run. The newer driver version unfortunately wouldn’t be able to run without reference errors, since they’re running a 9.6 system and the newer version runs class library of 1.2.0.8 which I believe has a minimum DMA of at least 10.0. This was changed from class library 1.0.1.3 in driver version 3.1.2.6 it looks like.

I can ask them to upgrade to 3.1.2.5, but I’m not sure that will help since it appears their SLProtocol Log is gone. I will work with IOC to determine why this is happening.
Alex Johnson [SLC] [DevOps Advocate] commented

Following up on this: it appears a dataminer restart with slnet solved the initial issue.

However the SLProtocol.txt log still isn’t present…