Scenario 1: Dispatcher does not start due to a port conflict
There's probably nothing worse than not being able to start your SAP system. Where's the problem? The operating system? The database server? Or perhaps it is time to dive into the dark corners of SAP to get some answers? This handy troubleshooting guide by veteran site expert Giovanni Davila will help you figure out what's going on.
- No work processes (disp+work.exe) exist in Task Manager.
- Dispatcher shows status "stopped" in the SAP MMC.
- Errors found in "dev_disp":
*** ERROR => NiIBind: service sapdp00 in use [nixxi.c 3936]
*** ERROR => NiIDgBind: NiBind (rc=-4) [nixxi.c 3505]
*** ERROR => DpCommInit: NiDgBind [dpxxdisp.c 7326]
*** DP_FATAL_ERROR => DpSapEnvInit: DpCommInit
*** DISPATCHER EMERGENCY SHUTDOWN ***
Problem Analysis
I highlighted the keywords in the error messages above:
Continue Reading This Article
Enjoy this article as well as all of our content, including E-Guides, news, tips and more.
- Address already in use
- Service sapdp00 in use
Solution
If your server has a firewall client, disable it and attempt to start the SAP instance again.
If the instance starts successfully you can enable the client firewall back again.
If there is no firewall client at all, or if disabling it did not resolve the problem, edit the "services" file and check what port the appropriate "sapdp" is using.
If the instance number is 00, look for sapdp00. If the instance number is 01 look for sapdp01 and so on. You can use the following OS command to help you resolve port conflicts:
netstat -p TCP
There are also utilities on the Internet that can help you list all the TCP and UDP ports a system is using.
TROUBLESHOOTING SAP STARTUP PROBLEMS
Home: Introduction
Start the conversation
0 comments