At least one of the SAP processes is not starting.
The following trace entries are seen at "stderrX" file ("X" is a number starting from zero), at the "work" folder:
(<PID>) New Child Process created.
(<PID>) Starting local Command:
(<PID>) **** Failed to Start Local Command. No such file or directory ****
(<PID>) Exiting with Return-Code -106. (Local execution failed)
- "PID" would have been the ID of the process if it had not failed to start;
- "dw" is an example and is related to the Dispatcher process (disp+work).
This could be "ms" for the Message Server, "en" for the Enqueue Server, "ig" for the IGS, and so on.
The error message can also be:
**** Failed to Start Local Command. Exec format error ****
- SAP Netweaver release independent
- SAP running on Linux/UNIX servers
Exec format error , KBA , BC-CST-STS , Startup Service , BC-JAS-COR , Enterprise Runtime, Core J2EE Framework , BC-CST , Client/Server Technology , BC-OP-LNX , Linux , BC-OP-AIX , IBM AIX , BC-OP-HPX , HP-UX , BC-OP-SUN , SUN Solaris , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.