Develop > Document Engine Guide > Troubleshooting overview > Research application errors

Research application errors

Processes call a number of RAD applications and execute a number of expressions, with a possibility of invoking more Processes afterwards. If any of the applications or expressions caused an error exit due to wrong syntax or wrong logic, this information can be found in the sm.log file.

Log sample:

Process panel run.pre.exp in RAD se.call.process encountered error in line 1 (se.call.process,run.pre.exp)
Cannot evaluate expression (se.call.process,run.pre.exp)
Cannot evaluate expression (se.call.process,run.pre.exp)
Bad arg(2) oper = (se.call.process,run.pre.exp)
Cannot evaluate expression (se.call.process,run.pre.exp)
Cannot evaluate expression (se.call.process,run.pre.exp)
Bad arg(2) oper = (se.call.process,run.pre.exp)
Cannot evaluate expression (se.call.process,run.pre.exp)
Bad arg(2) oper nullsub (se.call.process,run.pre.exp)
Cannot evaluate expression (se.call.process,run.pre.exp)
Bad arg(2) oper  in  (se.call.process,run.pre.exp)
Cannot evaluate expression (se.call.process,run.pre.exp)
Unrecoverable error in application:  se.search.objects on panel call.list.engine
Unrecoverable error in application:  se.list.engine on panel call.process.1
Unrecoverable error in application:  se.call.process on panel run.pre.exp

In this example (not out-of-box), the error occurred in se.call.process, run.pre.exp, or in other words, while evaluating the initial expressions of the Process. To find out which Process was causing the issue, go through the steps outlined above and note the process from the line:

DBACCESS - Cache Find against file Process found 1 record, query: process="upgrade.pcs"

Go to the Process record by the name of upgrade.pcs and check for any statements on the initial expressions tab. In this specific case, the expression will include the word nullsub. For example, the expression in question for this test may be

$L.icount=nullsub($L.icount, anynumberIwant)

The variable, anynumberIwant, is not a valid field, literal or variable, so it will have to be changed to prevent this issue.