Dispatcher started but not connected to message server

[Former Member]

Dear all,

I know that questions related to dispatcher problem have been posted by several users but I am unable to find a solution, thats why I am starting this thread. At our development server SAP was working fine but after the installation of windows updates one of the instances of SAP is not working. Whenever I am trying to start it the dispatcher stopped with an error of unable to connect to message server. Details of my server are as follows:

Windows Platforms with Server 2003 SP2

ECC version 7.0

Platform AFS

The trace for the same is:

-

---

trc file: "dev_disp", trc level: 1, release: "700"

-

---

sysno 00

sid NUD

systemid 562 (PC with Windows NT)

relno 7000

patchlevel 0

patchno 201

intno 20050900

make: multithreaded, Unicode, 64 bit, optimized

pid 1960

Mon Jan 03 13:29:34 2011

kernel runs with dp version 242000(ext=110000) (@(#) DPLIB-INT-VERSION-242000-UC)

length of sys_adm_ext is 576 bytes

• SWITCH TRC-HIDE on ***

***LOG Q00=> DpSapEnvInit, DPStart (00 1960) [dpxxdisp.c 1287]

Mon Jan 03 13:29:35 2011

shared lib "dw_xml.dll" version 201 successfully loaded

shared lib "dw_xtc.dll" version 201 successfully loaded

shared lib "dw_stl.dll" version 201 successfully loaded

shared lib "dw_gui.dll" version 201 successfully loaded

shared lib "dw_mdm.dll" version 201 successfully loaded

rdisp/softcancel_sequence : -> 0,5,-1

use internal message server connection to port 3900

Mon Jan 03 13:29:39 2011

• WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 4 seconds

***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 5518]

MtxInit: 30000 0 0

DpSysAdmExtInit: ABAP is active

DpSysAdmExtInit: VMC (JAVA VM in WP) is not active

DpIPCInit2: start server >numerodeb_NUD_00 <

DpShMCreate: sizeof(wp_adm) 29792 (1752)

DpShMCreate: sizeof(tm_adm) 5912704 (29416)

DpShMCreate: sizeof(wp_ca_adm) 24064 (80)

DpShMCreate: sizeof(appc_ca_adm) 8000 (80)

DpCommTableSize: max/headSize/ftSize/tableSize=500/16/552064/552080

DpShMCreate: sizeof(comm_adm) 552080 (1088)

DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0

DpShMCreate: sizeof(slock_adm) 0 (104)

DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0

DpShMCreate: sizeof(file_adm) 0 (72)

DpShMCreate: sizeof(vmc_adm) 0 (1864)

DpShMCreate: sizeof(wall_adm) (41664/36752/64/192)

DpShMCreate: sizeof(gw_adm) 48

DpShMCreate: SHM_DP_ADM_KEY (addr: 000000000F210050, size: 6614144)

DpShMCreate: allocated sys_adm at 000000000F210050

DpShMCreate: allocated wp_adm at 000000000F212270

DpShMCreate: allocated tm_adm_list at 000000000F2196D0

DpShMCreate: allocated tm_adm at 000000000F219730

DpShMCreate: allocated wp_ca_adm at 000000000F7BCFB0

DpShMCreate: allocated appc_ca_adm at 000000000F7C2DB0

DpShMCreate: allocated comm_adm at 000000000F7C4CF0

DpShMCreate: system runs without slock table

DpShMCreate: system runs without file table

DpShMCreate: allocated vmc_adm_list at 000000000F84B980

DpShMCreate: allocated gw_adm at 000000000F84BA00

DpShMCreate: system runs without vmc_adm

DpShMCreate: allocated ca_info at 000000000F84BA30

DpShMCreate: allocated wall_adm at 000000000F84BA40

MBUF state OFF

DpCommInitTable: init table for 500 entries

rdisp/queue_size_check_value : -> off

ThTaskStatus: rdisp/reset_online_during_debug 0

EmInit: MmSetImplementation( 2 ).

MM global diagnostic options set: 0

<ES> client 0 initializing ....

<ES> InitFreeList

<ES> block size is 4096 kByte.

<ES> Info: em/initial_size_MB( 8191MB) not multiple of em/blocksize_KB( 4096KB)

<ES> Info: em/initial_size_MB rounded up to 8192MB

Using implementation view

<EsNT> Using memory model view.

<EsNT> Memory Reset disabled as NT default

<ES> 2047 blocks reserved for free list.

ES initialized.

Mon Jan 03 13:29:40 2011

mm.dump: set maximum dump mem to 96 MB

rdisp/http_min_wait_dia_wp : 1 -> 1

***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c 1694]

*****************************************************************************

*

• LOCATION SAP-Dispatcher numerodeb_NUD_00 on host numerodeb

• ERROR mserrno received (MSEACCESSDENIED)

*

• TIME Mon Jan 03 13:29:40 2011

• RELEASE 700

• COMPONENT MS (message handling interface, multithreaded)

• VERSION 4

• RC -24

• MODULE msxxi.c

• LINE 810

• COUNTER 5

*

*****************************************************************************

• ERROR => not allowed to connect to message server via port 3900 [dpxxdisp.c 12488]

• ERROR => Please check your configuration (profile parameter rdisp/msserv_internal) [dpxxdisp.c 12489]

DpHalt: shutdown server >numerodeb_NUD_00 < (normal)

Stop work processes

Mon Jan 03 13:29:50 2011

SoftCancel request for T0 U1 M0 received from DISPATCHER

SoftCancel request for T2 U3 M0 received from DISPATCHER

SoftCancel request for T3 U4 M0 received from DISPATCHER

SoftCancel request for T4 U5 M0 received from DISPATCHER

SoftCancel request for T5 U6 M0 received from DISPATCHER

SoftCancel request for T6 U7 M0 received from DISPATCHER

SoftCancel request for T7 U8 M0 received from DISPATCHER

SoftCancel request for T8 U9 M0 received from DISPATCHER

SoftCancel request for T9 U10 M0 received from DISPATCHER

SoftCancel request for T10 U11 M0 received from DISPATCHER

SoftCancel request for T11 U12 M0 received from DISPATCHER

SoftCancel request for T12 U13 M0 received from DISPATCHER

SoftCancel request for T13 U14 M0 received from DISPATCHER

SoftCancel request for T14 U15 M0 received from DISPATCHER

SoftCancel request for T15 U16 M0 received from DISPATCHER

SoftCancel request for T16 U17 M0 received from DISPATCHER

Mon Jan 03 13:29:51 2011

Stop gateway

Stop icman

Terminate gui connections

wait for end of work processes

wait for end of gateway

waiting for termination of gateway ...

Mon Jan 03 13:29:52 2011

wait for end of icman

waiting for termination of icman ...

Mon Jan 03 13:29:53 2011

waiting for termination of icman ...

Mon Jan 03 13:29:54 2011

waiting for termination of icman ...

Mon Jan 03 13:29:55 2011

waiting for termination of icman ...

Mon Jan 03 13:29:56 2011

waiting for termination of icman ...

Mon Jan 03 13:29:57 2011

waiting for termination of icman ...

Mon Jan 03 13:29:58 2011

waiting for termination of icman ...

Mon Jan 03 13:29:59 2011

waiting for termination of icman ...

Mon Jan 03 13:30:00 2011

waiting for termination of icman ...

Mon Jan 03 13:30:01 2011

waiting for termination of icman ...

Mon Jan 03 13:30:02 2011

waiting for termination of icman ...

Mon Jan 03 13:30:03 2011

not attached to the message server

cleanup EM

***LOG Q05=> DpHalt, DPStop ( 1960) [dpxxdisp.c 11071]

Please do help as it is causing a lot of problems and is effecting our work a lot.

[moidmohammed]

Hi

Yes the issue is due to MS_ACL_INFO file corruption.

[Former Member]

The issue was resolved as the file "ms_acl_info.dat" was corrupted. Now have replaced it.

[Former Member]

Thanks Mohit,

i was facing same issue, isue has been resloved  after renaming the file "ms_acl_info" under global dir.

[former_member189546]

Hello,

ERROR => Please check your configuration (profile parameter rdisp/msserv_internal)

Check

1. 967123 - SAP NetWeaver 7.0 / Business Suite 2005 SR2: Windows

Section 18/APR/06>

You can check on Windows level whether the chosen port number is not

used by an other appication (e.g. via "netstat -ano findstr 3910" or

in "%windir%\system32\drivers\etc\services" file, etc...)

regards,

John Feely

[Former Member]

Dear Subhash and John,

AS per your instructions I have checked for the port 3900 but this port is not assigned to any process and have restarted the DB and SAP Instance again but nothing. Our other SAP Instance Development Retail runs on the same server and uses the port 3901 and it is working fine, but only this problem is not getting solved.

Is it possible to change the port in the default profile to some other one through which it can connect to the message server? If yes can you please tell me the procedure for the same?

[Former Member]

Please check the log of the message server once you restarted the instance cleanly to check that it runs correct and has bound the correct port.

If there is an error displayed in the message server trace, paste it here.

Kind regards,

[Former Member]

Thanks Sven,

The problem has been resolved. Thanks a lot all you guys.

[Former Member]

The error in the trace file is quite clear:

ERROR => not allowed to connect to message server via port 3900 [dpxxdisp.c 12488]

ERROR => Please check your configuration (profile parameter rdisp/msserv_internal)

You should check whether that port config is correct and whether or not something blocks that port. Especially after you installed new Windows Patches you should check if some MS security tools have started their work and now block connections required by the SAP system.

Kind regards,

[Former Member]

Thanks for quick response. We have removed all the current updates because the port 3900 was open, but still dispatcher is showing the same error of unable to connect the message server. Can you please tell me how to check the profile parameter as I am unable to login to the system.

[Former Member]

Check the profiles directly via notepad from the profile directory (e.g. <DRIVE>:\usr\sap\SID\SYS\profile). You can directly edit the profile there as well.

But if you do so remember to import the profiles again into the system once it starts again.

Kind regards,

[Former Member]

Thanks Sven,

I have checked the profile and the said parameter "rdisp/msserv_internal" is not there. SHould I install this manually using notepad? If yes, what value should I provide?

[Former Member]

First check all profiles carefully - and make a backup of your profiles (just in case).

If it is really not there then set it according to your installation. If 00 is your instance number then use port 3900 as requested by the dispatcher. If your instance number is different then use 39xx where xx is your instance number.

Kind regards,

[Former Member]

hi,

Check whether R3trans -d is returning 000 , check the trans.log once .

Since it was working fine before patching i hope it should n't be a profile issue , check the ports once any ports are busy .. or blocked ..

Stop all the process cleanly ,clean the IPC and restart the DB & CI..

Thanks,

Subhash.G