SAP DS, job fails with error LOAD_PROGRAM_NOT_FOUND, only on applicationserver

[Former Member]

Hello,

When I'm starting the batch job for Business Objects in "generate_and_execute mode" then it runs perfect when all the jobs run on the central instance. When the jobs run on the application server then there is the chance that job get canceled/aborted. Strange thing is that it is not the same job that gets aborted. There are also jobs that run perfect on the application server.

Here some parts of  the job log:

Runtime error	LOAD_PROGRAM_NOT_FOUND
Datum en tijd	26.02.2015 14:40:26

Korte tekst

Program "ZW16000660" not found.

Wat is er gebeurd?

There are several possibilities:

Error in the ABAP Application Program

	The current ABAP program "RSBTCRTE" had to be terminated because it has
	come across a statement that unfortunately cannot be executed.
	or
	Error in the SAP kernel.

	The current ABAP "RSBTCRTE" program had to be terminated because the
	ABAP processor detected an internal system error.

434 * was successful or not:

435

436 * d023157  13.4.2004  auskommentiert; siehe Meldung 215477 / 2004

437

438 *     LOAD REPORT STEP_TBL-PROGNAME PART 'HEAD' INTO ABAP_PROG_LOAD.

439 *     IF SY-SUBRC > 0.

440 *        IF SY-SUBRC = 4. "Load not there or not updated

441 *           MESSAGE I524.

442 *        ENDIF.

443 *        GENERATE REPORT STEP_TBL-PROGNAME.

444 *            IF SY-SUBRC > 0.

445 *               MESSAGE A525.

446 *            ENDIF.

447 *     ENDIF. "report exists and is generated

448 * end of prolog

449 * d023157  13.4.2004

450

451 * passing the recent date for archiving

452     MOVE sy-datum TO out_archive_params-datum.

453

454     SUBMIT (step_tbl-progname)

455       TO SAP-SPOOL WITHOUT SPOOL DYNPRO

456       USER step_tbl-authcknam

457       USING SELECTION-SET step_tbl-variant

458       SPOOL PARAMETERS out_print_params

459       ARCHIVE PARAMETERS out_archive_params

460

461       AND RETURN.

462

463 * insert WO

>>>>     IF trace_level > btc_trace_level1.

465       CALL 'WriteTrace'

466        ID 'CALL' FIELD caller

467        ID 'PAR1' FIELD sy-langu.

468     ENDIF.

469

470 * d023157  13.4.2004

471     IF sy-subrc NE 0.

472       MESSAGE i645 WITH 'SUBMIT: sy-subrc =' sy-subrc.      "#EC NOTEXT

473       MESSAGE a525.

474     ENDIF.

475 * d023157  13.4.2004

476

477   ENDIF.

478   SET EXTENDED CHECK OFF. "ToDo:in applications this is not allowed

479   FREE MEMORY.

480   SET EXTENDED CHECK ON.

481 ENDLOOP.

482

483 * Begin c5020400  15.4.2004

[campomat]

Dear All,

have someone faced the same issue?

Currently we are facing it and no idea on how to solve it.

Mattia

[Former Member]

Markus,

Since the batch job is in the 'Generate and Execute' mode, one possible issue could be that the program is initially triggered, then the connection to ECC is lost or the application server goes down and on reconnecting, the generated program is not found. You can possibly check with your BASIS team if this is happening.

Also, can you check running your jobs against the app server with 'execute-in-background' option set to No.

-Chaitanya