After an SAP Kernel update or any manual SAP executable exchange (like saprouter, SAP Web Dispatcher, brtools, ....) , the following will be shown in a RDP session:
- When starting an SAP executable, a pop-up window will appear with the following error message:
The application was unable to start correctly (0xc000007b)
The program can´t start because MSVCR120.dll is missing (or other MSVCXXXX.dll missing depending on the SAP executable release)
- While starting an SAP system, an error similar to this one (depending on the executable and version) in Windows Event Viewer (application log) will be logged:
Faulting application name: sapcpe.EXE, version: 7450.300.26.556, time stamp: 0x57e0266b
Faulting module name: ntdll.dll, version: 6.3.9600.18438, time stamp: 0x57ae642e
Exception code: 0xc000007b
- If the executable (saprouter.exe, sapwebdisp.exe, sapstartsrv.exe ....) is started in a Windows Service also you can find this error :
ERROR 1053 : The service did not respond to the start of control request in timely fashion
ERROR 1067 : The process terminated unexpectly
Running SAP executables on Windows platforms
0xc000007b, code: 0xc000007b, The application was unable to start correctly, vcredist, c-runtime, error 1053, error 1067, MSVCP120.DLL, MSVCR120.DLL, , MSVCP140.DLL, MSVCR140.DLL, VCRUNTIME140.dll, brtools, sap web dispatcher, saprouter, 14001, windows , KBA , BC-OP-NT , Windows , BC-CST , Client/Server Technology , BC-INS-NT , SAP Netweaver based Solutions on Windows , 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.