MBC's using module process (eprocess.s4) get an error when trying to execute. Examples: procengine(procengine(sealsnet_pkzip_cre))
PROCESS_START: failed to start process "/opt/pkzip/pkzip25", procengine(procengine(sealsnet_pkzip_cre))
PROCESS_START: failed to start process "mkdir", procengine(procengine(teu_gnupgsecure_cre))
PROCESS_START: failed to start process "/opt/xip/xib/local/security/pgp/bin/gpg", procengine(procengine(teu_gnupgdesecure_cre))
PROCESS_START: failed to start process "/opt/xip/xib/local/security/pgp/bin/gpg". The errors do not com all the time but when the first one has been reported then every message gets it.

We found that this type of problem occurs when trying to start a process and that executable file path  is not set in the PATH environment variable.

PROCESS.STARTCOMMAND(<command>) when used in an MBC tries to find the path of command in PATH environment variable. If it do not find that command , it reports the error "failed to start process : command".