Cause : Execution not possible comes when the macro cannot be executed. Fault value (r0949, interpret hexadecimal):

ccccbbaa hex:
cccc = preliminary parameter number, bb = supplementary information, aa = fault cause

Fault causes for the trigger parameter itself:
19: Called file is not valid for the trigger parameter.
20: Called file is not valid for parameter 15.
21: Called file is not valid for parameter 700.
22: Called file is not valid for parameter 1000.
23: Called file is not valid for parameter 1500.
24: Data type of a TAG is incorrect (e.g. Index, number or bit is not U16).

Fault causes for the parameters to be set:
25: Error level has an undefined value.
26: Mode has an undefined value.
27: A value was entered as string in the tag value that is not "DEFAULT".
31: Entered drive object type unknown.
32: A device was not able to be found for the determined drive object number.
34: A trigger parameter was recursively called.
35: It is not permissible to write to the parameter via macro.
36: Check, writing to a parameter unsuccessful, parameter can only be read, not available, incorrect data type, value range or assignment incorrect.
37: Source parameter for a BICO interconnection was not able to be determined.
38: An index was set for a non-indexed (or CDS-dependent) parameter.
39: No index was set for an indexed parameter.
41: A bit operation is only permissible for parameters with the parameter format DISPLAY_BIN.
42: A value not equal to 0 or 1 was set for a BitOperation.
43: Reading the parameter to be changed by the BitOperation was unsuccessful.
51: Factory setting for DEVICE may only be executed on the DEVICE.
61: The setting of a value was unsuccessful.

- check the parameter involved.
- check the macro file and BICO interconnection.
See also: p0015, p1000, p1500