- The dispatcher shows status "stopped" in the SAP MMC.
- The "dev_disp" file shows these errors:
***LOG Q0A=> NiIServToNo, service_unknown (sapdp00) [nixxi.c 2580]
*** ERROR => DpCommInit: NiDgBind [dpxxdisp.c 7326]
*** DP_FATAL_ERROR => DpSapEnvInit: DpCommInit
*** DISPATCHER EMERGENCY SHUTDOWN ***
The keyword in the messages above is "service unknown" followed by the entry name "sapdp00". The dispatcher entry "sapdp00" is missing in the "services" file. Example: sapdp00 3200/tcp
Add the necessary entry in the "services" file. Example: sapdp00 3200/tcp Then, re-start the instance.
TROUBLESHOOTING SAP STARTUP PROBLEMS
Scenario 1: Dispatcher does not start due to a port conflict
Scenario 2: Dispatcher dies due to a database connection problem
Scenario 3: SAP does not start at all: no message server and no dispatcher
Scenario 4: Users get 'No logon possible' messages when they attempt to log in
Scenario 5: The message server starts but the dispatcher doesn't
Scenario 6: Work processes die soon after they start
Review: Conclusion and more resources