Error en Dispatcher

[SarandaP]

Hola a todos,

Les cuento que tuve que instalar en el servidor donde tengo el sistema productivo el antivirus McAfee debido a que estaba infectado con el virus Conficker.
Apenas termino la instalación el sistema se detuvo y no lo pude volver a iniciar, por suerte mi solución estaba en cluster por lo que moví los recursos al otro nodo y el sistema se inicio sin problemas.

Al revisar el Log del dispatcher encontré lo siguiente:

Sat Jul 25 03:13:33 2009
*** ERROR => NiPBind: bind failed (socket=1476) (10013: Unknown error) [ninti.c 948]
***LOG Q0I=> NiPBind: bind (10013: WSAEACCES: Permission denied) [ninti.c 949]
*** ERROR => NiIBind: service 'sapdp00' (3200) in use [nixxi.cpp 3901]
*** ERROR => NiIListen: NiBind (rc=-4) [nixxi.cpp 793]
*** ERROR => DpCommInit: NiBufListen (rc=-4) [dpxxdisp.c 8358]
*** DP_FATAL_ERROR => DpSapEnvInit: DpCommInit
*** DISPATCHER EMERGENCY SHUTDOWN ***

No tengo idea que puede estar sucediendo, espero que alguno de ustedes me pueda ayudar. Ya que si bien tengo el sistema arriba este nodo se encuentra infectado con el virus por lo que me urge solucionar el tema.

Mil gracias por su ayuda.

Silvana

[SarandaP]

Hola,

Les dejo la solución.

Dispatcher does not start due to a port conflict

No work processes (disp+work.exe) exist in Task Manager.

Dispatcher shows status "stopped" in the SAP MMC.

Errors found in "dev_disp":

LOG Q0I=> NiPBind: bind (10048: WSAEADDRINUSE: Address already in use) [ninti.c 1488]
*** 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: Address already in use Service sapdp00 in use The TCP port number assigned in the "services" file is being occupied by another application. Due to the conflict, the dispatcher shuts down.

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.


Saludos,