sapevt - how to use internal port for message server?

[Former Member]

Hello,

I had the problem, that a transport did not stop importing as the event from sapevt did not raise. After having read several notes I realised that I used

/etc/services:

sapmsP01 3601/tcp #blabla ...

/profile/DEFAULT.PFL

rdisp/msserv = sapmsP01

rdisp/msserv_internal=3901

The note 821875 tells me, that an application server should login with internal port, but it does not use this internal port though I have set it:

dev_evt:

Tue Jan 22 14:19:42 2008

Trace File of External Event Raiser (Level=0, Append=1)

EventID: SAP_TRIGGER_RDDIMPDP

SAP message server host: sapp01

SAP message server service (old): sapmsP01

• ERROR ***: MsSndTypeOnce, rc = -20

• ERROR ***: Event raise failed

dev_ms:

[Thr 5192] Tue Jan 22 14:19:42 2008

[Thr 5192] *** ERROR => MsSClientHandle: client 192.168.12.32 (192.168.12.32) is EXTERNAL, access denied [msxxserv.c 4857]

By overriding the profile manually by using the console and setting the message server service to 3901 it succeeds

sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=P01 msserv=3901

dev_evt:

Tue Jan 22 14:20:54 2008

Trace File of External Event Raiser (Level=0, Append=1)

EventID: SAP_TRIGGER_RDDIMPDP

SAP message server host: myhost

SAP message server service (new): 3901

SAP message server service (old): sapmsP01

Event sent to server myhost_P01_01

So, what do I have to do and where do I have to configure something for using automatically the internal port to login?

Thanks in advance!

Michael

Edited by: Michael Zetzsch on Jan 22, 2008 2:47 PM

Edited by: Michael Zetzsch on Jan 22, 2008 2:48 PM

[Former Member · Accepted solution]

Hi Michael,

Your question made me discover this new message server internal port.

I've checked on my systems : it does not exist in WAS 6.20 and exists in Netweaver 7.0.

We have it on XI 7.0 and we did not do anything special for the transport imports to raise the event.

Do you have an ACL list defined in parameter ms/acl_info ?

In my XI system, The list is set to

HOST=*

I check it with SMMS -> Goto -> Security Settings -> Access Control -> Display

Regards,

Olivier

[Former Member · Accepted solution]

Hi Olivier,

ms/acl_info is NOT defined anywhere! Neither DEFAULT nor INSTANCE profile

Do I need it?

But I have found this file on my file system. And using you menue use I saw, that the entry is like yours "HOST=*"

[Former Member · Accepted solution]

>Do I need it?

>But I have found this file on my file system. And using you menue use I saw, that the entry is like >yours "HOST=*"

No, you don't need it. You have the standard value "HOSTS=*" which means there is no control of IP addresses.

It should not forbid the connection. So there is something else to find out !

Olivier

[Former Member]

Hello All,

I have started Dialog Server installation and encountered the below error.

and the dev_ms.log file has the below error

please advice.

[Former Member]

Hello All,

Many thanks for your reply. In may case I am using 640 kernel and none of the ms/* parameter exists

they are unknown to the system. I did not have to add these parameters, files on any of my previous app servers. The thing I found out is while installing SAPInst will automatically create acl files in

/sapmnt/SID/global file system which will be used by other app server. In that file HOST should be ' * '.

Now the issues is resolved.

Thanks and regards

[Former Member]

Hi Michael!

I had the same problem.

In my case it solved when I put the rdisp/msserv_internal in DEFAULT.PFL profile.

Check the next notes:

826779 and 802172.

I hope this help you.

Edorta.

[Former Member]

Hey my friends,

I have done several things, actually I don't know the exact solution for my problem, but now it works.

I have put all parameters for msserv and msserv_internal into the DEFAULT.PFL and deleted these parameters from the Instanceprofile.

I exchanged the sapevt.exe and sapevents.dll with the latest files from marketplace and restarted the system. Now it works. Thanks for all your help

[former_member204746]

I have deleted parameter rdisp/msserv_internal from SAP profiles and restarted SAP...

and Voilà! problem corrected.