Connect to message server host failed Connect_PM TYPE=B MSHOST=hmsnsw00

When i deploy "TutWD_FlightBooking" Sample WebDynpro application I get following error.
I have following setup.
NetWeaver developer Studio (NWDS) Version: 2.0.9
J2EE server running on the same machine where i have NWDS Version: SAP J2EE Engine/7.00 PatchLevel 105053.42
SLD Version: 7.0009.20060621180635.0000
Build: 20060622 2041, Depot: //sdt/com.sap.lcr/645_SP_REL, Changelist: 345651
ABAP R/3 system is on remote system (accessing clients R/3 system) on the network.
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=hmsnsw00 GROUP=PUBLIC R3NAME=DEV MSSERV=sapmsDEV PCS=1 ERROR timeout while pending for route completion TIME Tue Mar 13 12:04:14 2007 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -12 DETAIL NiErrSet COUNTER 1
    at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:457)
    at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:989)
    at com.sap.mw.jco.JCO$Client.connect(JCO.java:3193)
    at com.sap.dictionary.runtime.mdi.DataProvider.<init>(DataProvider.java:90)
    at com.sap.dictionary.runtime.mdi.DataProvider.<init>(DataProvider.java:122)
    ... 62 more
I get same error message when i test the JCo Metadata connection, Model data connection works fine.
The message server value under WebDynpro content admin is created with right values as i checked with Basis person.
My service file in C:/windows/system32/drivers/etc has entries for both J2EE stack entry and ABAP stack (on remote server) entry with port numbers.
When i ping the ABAP (remote server) from my machine command prompt I get response.
I am running out of options. I really appreciate your inputs.
Ramesh

Hi, I think this might have todo with the fact that your Java stack wants to connect with a server from the same logon group called "PUBLIC".
Please make sure you added the same logon group "PUBLIC" to the ABAP Server. Try transaction SMLG.
Also as posted above the SLD needs this info aswell.
After using the transaction SMLG, log in and out 5 times in a row to your ABAP stack using SAP GUI. This might actually force an update to the SLD.
Greetings,
Robbert
Message was edited by:
Robbert van Waveren

Similar Messages

(102) RFC_ERROR_COMMUNICATION: Connect to message server host failed

Hello,
I'm almost giving up on this...I've been messing with this for too long now...
I get this error message:
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM
TYPE=B MSHOST=exts0002 GROUP=PUBLIC R3NAME=ANB MSSERV=sapmsANB PCS=1 ERROR       hostname 'exts0002' unknown TIME
Tue Feb 14 16:40:02 2006 RELEASE     640 COMPONENT   NI (network interface) VERSION     37 RC          -2 MODULE      ninti.c
LINE        332 DETAIL      NiPGetHostByName2: hostname 'exts0002' not found SYSTEM CALL gethostbyname_r COUNTER     1
I try to get the flightlist demo to work. I've put in "sapmsANB         3600/tcp" in services file locally in my machine (I'm using Sneak Preview SP11).
I've also done everything in "/people/sugree.phatanapherom/blog/2005/08/14/configuring-sld-in-sneak-preview-sap-netweaver-04-sneak
I've done everything possible to get this to work, but no luck.
What is wrong here?, please help

Now I've put in "193.183.156.17     PetJoh     PetJoh.afab.local" in Hosts -> rebooted -> but still can't ping exts0002 (or the fully resolved name to it) I can't ping the actual IP nr either.
I can, however use JCO java code like:
import com.sap.mw.jco.*;
public class R3Connect extends Object {
     JCO.Client mConnection;
     public R3Connect() {
          try {
               // Change the logon     information     to your     own     system/user
               mConnection     =
               JCO.createClient(
               "100",                                        // SAP client
               "rfcuser",                                   // userid
               "jakob",                                   // password
//               null,                                        // language
               "en",                                        // language
               "anb.af.hosting.emtab.com",               // application server host name
               "00");                                        // system number
               mConnection.connect();
               System.out.println(mConnection.getAttributes());
               mConnection.disconnect();
          } catch (Exception ex) {
               ex.printStackTrace();
               System.exit(1);
     public static     void main (String args[]) {
               R3Connect app =     new     R3Connect();
This works perfectly fine to connect, Why doesn't SLD?

RFC_ERROR_COMMUNICATION: Connect to message server host failed

We are trying to create JCO destination
and we are getting the below problem
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=sappw2ci GROUP=PUBLIC R3NAME=PW2 MSSERV=sapmsPW2 PCS=1 ERROR service 'sapmsPW2' unknown TIME Thu Jan 10 23:34:05 2008 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -3 MODULE nixxhsl.cpp LINE 776 DETAIL NiHsLGetServNo: service name cached as unknown COUNTER 1
we added sapmsPW2 in the services file still we are facing the problem
i saw all the related posts in the forum but nothing worked
please help me in resolving this issue and points will be awarded for sure
Bala

Hi,
This JCO Exception caused by network problems, connection breakdowns, gateway problems, unavailability of the remote SAP system, etc.
What you can do is: Get the host of the SAP System from dev_jrfc.trc or the JRFC trace; ping the SAP system from command line; check routers, gateways, SAP systems
If an error has occurred on a lower communication layer, for example an RFC_ERROR_COMMUNICATION or RFC_ERROR_SYSTEM_FAILURE exception, have a look at the dev_jrfc.trc files. These files are written by JRFC and can be found in the directories j2ee/cluster/server* of the J2EE Application Server Installation.
Please check this blog and link:
The specified item was not found.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.highlightedcontent?documenturi=%2fhelp%2fsdn_help_nw04s%2fsaphelp_nw04s%2fhelpdata%2fen%2f3a%2f3b1b40fcdd8f5ce10000000a155106%2fcontent.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.highlightedcontent?documenturi=%2fhelp%2fsdn_help_nw04s%2fsaphelp_nw04s%2fhelpdata%2fen%2f94%2f3c1b40fcdd8f5ce10000000a155106%2fcontent.htm
Hope it helps....
Regards,
Mona

Connect to message server host failed;WSAECONNREFUSED: Connection refused

Hi All,
I am getting the following error when I tried to test the system connectivity from the portal to NSP instance.
Connection failed. Make sure that Single Sign-On is configured correctly
I found the following entry in the logs
Error> occured >Wed Feb 03 22:43:49,875<
RfcException:
    message: Connect to message server host failed
Connect_PM TYPE=B MSHOST=abchome.abcsap.local GROUP=SPACE R3NAME=NSP MSSERV=sapmsNSP PCS=1
ERROR       partner '192.xxx.xxx.123:sapmsNSP' not reached
TIME        Wed Feb 03 22:43:49 2010
RELEASE     700
COMPONENT   NI (network interface)
VERSION     38
RC          -10
MODULE      nixxi.cpp
LINE        2823
DETAIL      NiPConnect2
SYSTEM CALL connect
ERRNO       10061
ERRNO TEXT WSAECONNREFUSED: Connection refused
COUNTER     1
    Return code: RFC_FAILURE(1)
    error group: 102
    key: RFC_ERROR_COMMUNICATION
Both NSP and J2E instances are on the same server. OS - win2k3.
I checked the services file and have the sapmsNSP entry.
I am able to launch an SAP transaction from System Administration -> Support
RZ70 from NSP also fails JCo error. SLD_UC RFC itself works fine and the JCo RFC provider SLD_UC program is running
WEB AS & ITS connections work fine.
User authentication is from backend, NSP.
I think I have gone thru all the logs but could not resolve the issue.
I appreciate any help on this,
Victor

I tried to go thru the thread. I did not find any clue as why only server connectivity is failing. ABAP trial version is running fine and the NW trial version is working fine too. These run without crashing. I did a lot of customizing on the portal but dont see any issues except the System Connectivity. Like I mentioned I did UME configuration to point to NSP ABAP instance and I can log into the portal with user credentials that I use to login to ABAP. I can launch webgui etc without any issues.

NW2004s Connect to Message Server Host Failed - BW to Portals connection

Hi,
I am trying to connect a SAP BW NW2004s Patch 8 system to a NW2004s Portal. All of the checks in RSPOR_SETUP are successful.
However when I try to launch a query from Bex Query it fails with the following message.
"Connect to message server host failedConnect_PM TYPE=B MSHOST=SAPMSCR6 GROUP=webshop1_biw R3NAME=CR6 MSSERV=01 PCS=1"
The message server entry in the System Landscape object for the BW Server is "SAPMSCR6". Is this right?
I have searched for information about this and can't find anything. I am sure it is something basic. As anyone else resolved this issue or do they have an idea what might be causing the problem?
Any suggestions gratefully received.
Dave

Guys look at the below SAP note. it will help
SAP Note Number: 764881 Inf. Broad.Connect to message server host failed - sapms

Connect to message server (host/3900) failed: NIEHOST_UNKNOWN.. br SOLUTION

I am trying to install SLM as DISTRIBUTED SYSTEM. I have installed CENTRAL SERVICES INSTANCE on host 1 and DB instance on host 2.
and trying to install CENTRAL SERVICE on host 3.
CENTRAL SERVICES INSTANCE and DB instance install successfully.
I am getting this error message when installing CENTRAL SERVICE.
here is my sapinst_dev.log
=======================
Connect to message server (host/3900) failed: NIEHOST_UNKNOWN.
======================================================
here is my dev
=========================================================
trc file: "dev_ms", trc level: 1, release: "700"
[Thr 16384] Tue Feb 26 20:51:13 2008
[Thr 16384] MsSSetTrcLog: trc logging active, max size = 20971520 bytes
systemid   387 (Intel x86 with Linux)
relno      7000
patchlevel 0
patchno    110
intno      20050900
make:      multithreaded, Unicode, optimized
pid        5846
[Thr 16384] ***LOG Q01=> MsSInit, MSStart (Msg Server 1 5846) [msxxserv_mt. 1824]
[Thr 16384] SigISetDefaultAction : default handling for signal 17
[Thr 16384] load acl file = /usr/sap/KGB/SYS/global/ms_acl_info
[Thr 16384] MsGetOwnIpAddr: my host addresses are :
[Thr 16384]   1 : [1XX.10.10.222] host1.mycompanyname.com (HOSTNAME)
[Thr 16384]   2 : [1XX.0.0.1] localhost.localdomain (LOCALHOST)
[Thr 16384] MsHttpInit: full qualified hostname = host1.mycompanyname.com
[Thr 16384] HTTP logging is switch off
[Thr 16384] set HTTP state to LISTEN
[Thr 16384] MsHttpOwnDomain: own domain[1] = host1.mycompanyname.com
[Thr 16384] ms/icf_info_server : deleted
[Thr 16384] *** I listen to internal port 3900 (3900) ***
[Thr 16384] *** HTTP port 8100 state LISTEN ***
[Thr 16384] CUSTOMER KEY: >T0444609119<
=========================================================
I have changed the hostname in all the file (1) hostname ,(2)/etc/sysconfig/network file . i even checked my hostname and it shows hostname as "HOST1" so i am confused even though hostname is "HOST1" but in dev_ms the IP ADRESS is resolving to "host1.mycompanyname.com"
3. Also when i am trying to run "startsap" or "stopsap" from host1 where central service instance is installed. It gives me "command not found" although i see all the exe file in /usr/sap/SID/SYS/exe/run. why my command not running.
. I have added the sapmsSID 3900/tcp entries in both HOST1 and HOST3 services file.

Only that
When I grep on Error from the file I get
more sapinst_dev.log |grep error
Error number 8 error type SPECIFIC_CODE
Error number 211 error type SPECIFIC_CODE
pci_error_tolerance_time                 1440 Default      Immed
Registering Profile directory /usr/sap/MBA/SYS/profile for beeing one of the sources of additional files to be collected in case of errors
hth72231:mbaadm 25> more sapinst_dev.log | grep error |more
Error number 8 error type SPECIFIC_CODE
Error number 211 error type SPECIFIC_CODE
pci_error_tolerance_time                 1440 Default      Immed
Registering Profile directory /usr/sap/MBA/SYS/profile for beeing one of the sources of additional files to be collected in case of errors
Standard input: END
other
TRACE[E]   2014-06-25 10:08:17.327 [syuxcuser.cpp:2762]
           CSyUserImpl_setOsInfos(iastring sName, iastring sID, tSyUserInfo& msUserNewinfo)
           lib=syslib module=syslib
FSL-05014 Command '/usr/sbin/usermod' with parameters '-G "adm,bin,daemon,lp,mail,other,root,sys,users,sapinst" root' failed with return code 8: Login root
is currently in use
But that is not the issue

Connect to SAP gateway failed Connect_PM TYPE=B

Hi experts,
I get the following error when i ping through JCO destinations on portals.
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=B MSHOST=imtsapdev01 GROUP=CLUST R3NAME=DMI MSSERV=sapmsDMI PCS=1 LOCATION    CPIC (TCP/IP) on local host with Unicode ERROR       partner '127.0.0.1:3310' not reached TIME        Tue Jan 27 16:39:54 2009 RELEASE     700 COMPONENT   NI (network interface) VERSION     38 RC          -10 MODULE      nixxi.cpp LINE        2823 DETAIL      NiPConnect2 SYSTEM CALL connect ERRNO       10061 ERRNO TEXT WSAECONNREFUSED: Connection refused COUNTER     1
However my JCO destinations were working perfectly until recently. I checked on the logon group. I have one called CLUST, which i use for this purpose.
I have also checked both service files and they have the following for the ECC server im connecting to.
3610 because its system number 10 i am connecting to.
sapmsDMI 3610/tcp
From the JCE destinations screen i cannot even ping the server. I can though when i log on to the server through remote desktop.
thanks and regards
dilanke
as a reply to nishants posts.
goto rz70
give hostname -->
service --> sapgw00 (sapgw(instance number)
execute it
click on yes
check rfc call (success or failed)
I have done this. i left hostname as "blank" gave service as "sapgw10"
The following is what i got as the output.
    0: IMTSAPDEV01_DMI_10                        : Execute program: SLDRFC
    0: IMTSAPDEV01_DMI_10                        : Execute program: SLDMSGSRV
    0: IMTSAPDEV01_DMI_10                        : Execute program: SLDIPSERV
    0: IMTSAPDEV01_DMI_10                        : Execute program: SLDINSTSP
    0: IMTSAPDEV01_DMI_10                        : Execute program: SLDINSTSC
    0: IMTSAPDEV01_DMI_10                        : Execute program: SLDGWSRV
    0: IMTSAPDEV01_DMI_10                        : Execute program: SLDDBSYS
    0: IMTSAPDEV01_DMI_10                        : Execute program: SLDCOMPSYS
    0: IMTSAPDEV01_DMI_10                        : Execute program: SLDCLIENT
    0: IMTSAPDEV01_DMI_10                        : Execute program: SLDBCSYS
    0: IMTSAPDEV01_DMI_10                        : Execute program: SLDAPPL_SERV
    0: IMTSAPDEV01_DMI_10                        : Execute program: SLDASSOC
    0: IMTSAPDEV01_DMI_10                        : Collection of SLD data finished
    0: IMTSAPDEV01_DMI_10                        : Data collected successfully
    0: IMTSAPDEV01_DMI_10                        : RFC data prepared
    0: IMTSAPDEV01_DMI_10                        : Used RFC destination: SLD_NUC
    0: IMTSAPDEV01_DMI_10                        : RFC call failed: Error opening an RFC connection.
    0: IMTSAPDEV01_DMI_10                        : Existing periodic jobs removed. Number: 1
    0: IMTSAPDEV01_DMI_10                        : Program scheduled: 20090127 184357
    1: IMTSAPDEV01_DMI_10                        : Event-controlled job already exists; scheduling not necessary
so i guess its not successful. when i look at rz70 of a server where this works correctly its not succsessful either
if it is success then technical system name will be in sld
to restart sld --> /sld --> administration --> stop server --> restart server
or check in VA --> SLD data supplier value --> Runtime
I checked this and i do not see aa problem. you have configuration status as valid and send reult as Success
Services file is locted on OS level of R3 system--> Goto --> Start --> Run -> (type)Drivers(enter) --> etc -> (here is services file)
check ur r/3 server entry is there or not,
I have the followng in the service file for the server
sapmsDMI 3610/tcp
if not add it

Hi Experts,
when ilook at the remote gateway properties in SMGW this is what i see on the R/3 server. ive looked at my other system which i can connect to and there isnt much of a difference in the parameters. How can test this to see if it works?
                                                                                Details of remote gateway
entry                         = 0
state                         = CONNECTED
local                         = 1
system type                   = REMOTE_GATEWAY
client                        = FALSE
wait for frag write           = 0
suspended                     = 0
read/write socket             = 4
HANDLE                        = 4
TIME                          = Sun Oct 19 18:54:14 2008
SOCKET                        = 1352
STAT                          = NI_CONNECTED
TYPE                          = STREAM IPv4
OUT                           = 48225 messages 48225 bytes
IN                            = 1 messages 64 bytes
LOCAL                         = 127.0.0.1:3310
REMOTE                        = 127.0.0.1:1297
OPTIONS                       =
connect                       = Sun Oct 19 18:52:17 2008
last request                  = Thu Jan 29 13:09:58 2009
conversation no               = 0
thanks and regards,
dilanke

Connect to SAP gateway failed Connect_PM TYPE=A

In past 4-5 days, some of messages are not processed in our XI production server.
I got the following error in the falied messages:
Seem to be some parameter need to be update for sap gateway.
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=dbcinpr SYSNR=15 GWHOST=dbcinpr GWSERV=sapgw15 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR connection to host dbcinpr, service sapgw15 timed out TIME Sun Oct 21 09:09:50 2007 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -12 MODULE nixxi_r_mt.cpp LINE 1067 DETAIL NiPConnect COUNTER 1</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
Pls let us know if it is parameter related prolem or some other issue.
Regards
Amar

Hi Amar!
Test the status of the RFC destinations in transaction SM59 of XI and R/3 systems.
Also check this thread, I think they might be helpful:
Communication channel not working
RFC Receiver Adapter Error
JCO Destination creation error
RFC_ERROR_COMMUNICATION - time out
Reg Jco connections
RFC Adaptive Model,JCO destinations error
Regards,
Matias
PS: please award points if helpful.

RFC_ERROR_COMMUNICATION: Connect to message server failed

Hi,
I think this is the most common error that one can face and have seen quite a few threads in the forum. Still, i couldn't resolve my problem.
I am getting the following error when i tried to connect to SAP using SAP JCO connector with load balancing.
(102) RFC_ERROR_COMMUNICATION: Connect to message server failed
Connect_PM MSHOST=sapserver, R3NAME=D11, GROUP=Group1
LOCATION    CPIC (TCP/IP) on local host
ERROR       partner not reached (host sapserver, service sapmsD11)
TIME        Wed Jun 24 16:05:49 2009
I added the service sapmsD11 in the services file of my client as well as in R/3 server.
I got the above error when i tried to connect using load balancing. Without load balancing, i was able to connect to R/3 server successfully. Can any one tell how to figure out the message server host name ?
Can the application server host name and message server host name be same ?
PS: I am able to ping my R/3 server from my client.
Thanks,
Prasad.

Hi,
Check that you have configured properly using the below document. And check the message server of R/3 is configured properly in the SLD.
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0c1d495-048e-2b10-babd-924a136f56b5
Function module to get the message server host name and port in R/3.
SLDAG_GET_MESSAGE_SERVER_INFO
See this thread also..
Re: Jco Destination
Regards,
Charan

Error in wizard to create new RFC model: connect to message server failed

Hi,
I am trying to create a new RFC model in my Web Dynpro project in NWDS. In the wizard, I reach the step where I am required to enter the SAP login information. I then enter the details in the Load Balancing tab and click Next. The error message I get is:
Connect to message server failed
Connect_PM MSHOST=****, R3NAME=*, GROUP=**
LOCATION CPIC (TCP/IP) on local host ***
ERROR service '***" unknown
(Note: the *** are client-specific and therefore confidential info so I am removing them).
The thing is, a colleague of mine is also doing the same thing, but he is not encountering this error.
Can someone help me troubleshoot this?

Hi
The user you use to connect in the RFC should have the authorization to S_RFC. In the Duet installation guide look for the section about defining a system user ID in UME. This section has details about the authorization required for the user.
Thanks

The original exception was: wapsmod.ms.MsAttachFailed: Connect to message server (pdirmba1/3900) failed: MSENILAYER.

When trying to install an extra dialog instance to our BW environment in the second step when giving the profile parameter after reading the profiles it comes with the message:
An exception occurred while connecting to the message server instance MBA/DVEBMGS00 on host pdirmba1, port 3900. DIAGNOSIS: The original exception was: wapsmod.ms.MsAttachFailed: Connect to message server (pdirmba1/3900) failed: MSENILAYER.. SOLUTION: Make sure that the message server is started.
Message server is started as CI and second DI are already running.
HP-UX, Oralce11.
Did set the temp directory and SAPINST_USE_HOSTNAME parameter into the environment of root.
already tried niping from di to ci on the port and thats working ok

Only that
When I grep on Error from the file I get
more sapinst_dev.log |grep error
Error number 8 error type SPECIFIC_CODE
Error number 211 error type SPECIFIC_CODE
pci_error_tolerance_time                 1440 Default      Immed
Registering Profile directory /usr/sap/MBA/SYS/profile for beeing one of the sources of additional files to be collected in case of errors
hth72231:mbaadm 25> more sapinst_dev.log | grep error |more
Error number 8 error type SPECIFIC_CODE
Error number 211 error type SPECIFIC_CODE
pci_error_tolerance_time                 1440 Default      Immed
Registering Profile directory /usr/sap/MBA/SYS/profile for beeing one of the sources of additional files to be collected in case of errors
Standard input: END
other
TRACE[E]   2014-06-25 10:08:17.327 [syuxcuser.cpp:2762]
           CSyUserImpl_setOsInfos(iastring sName, iastring sID, tSyUserInfo& msUserNewinfo)
           lib=syslib module=syslib
FSL-05014 Command '/usr/sbin/usermod' with parameters '-G "adm,bin,daemon,lp,mail,other,root,sys,users,sapinst" root' failed with return code 8: Login root
is currently in use
But that is not the issue

Sapwebdispatcher: ERROR: Connection to message server failed

Hi Team,
We have been facing an issue on the webdispatcher. Web-disaptcher is notable to communicate with the Message Server[PRD-XI].
=====================
Environment: Set-up =
=====================
1. The Webdispatcher is in DMZ. We have opened the port 8100 at the firewall.
==========================================================================
ERROR MESSAGE
==========================================================================
[Thr 2058] Fri Jan 11 18:53:27 2008
[Thr 2058] *** ERROR => NiBufIConnect: non-buffered connect pending after
5000ms (hdl 4;10.1.10.56:8100) [nibuf.cpp 4611]
[Thr 2058] *** ERROR => Connection request from (-1/65535/0) to host:
10.1.10.56, service: 8100 failed (NIECONN_REFUSED)
[icxxconn_mt.c 2738]
[Thr 2058] *** ERROR => IcmConnClientRqCreate() failed (rc=-8)
[icrxx_mt.c 5100]
[Thr 2058] *** ERROR => Could not connect to SAP Message Server at
10.1.10.56. URL=/msgserver/text/logon?version=1.2 [icrxx_mt.c 2459]
[Thr 2058] *** ERROR => rc=-1, HTTP response code: 0 [icrxx_mt.c 2460][Thr 2058] *** ERROR => see also OSS note 552286 [icrxx_mt.c 2461]
==========================================================================
SAPWEBDISPATCHER VERSION DETAILS:
==========================================================================
wd011:wpiadm 73> sapwebdisp -v
SAP Web Dispatcher Version 7.00.10, multithreaded, ASCII, 64 BIT
kernel information
system name =
kernel release = 700
database library =
compiled on = AIX 2 5 005DD9CD4C00
compile time = May 19 2007 01:59:47
update level = 0
patch number = 110
source id = 0.111
supported environment
operating system
AIX 1 5
AIX 2 5
AIX 3 5
=============================================================================
TEST OUTPUT
==========================================================================
wd011:wpiadm 71> sapwebdisp -bootstrap
SAP Web Dispatcher Bootstrap
============================
This bootstrap will perform the following steps:
1. create profile file "sapwebdisp.pfl"for SAP Web Dispatcher (if not
already existing)
2. create user for web based administration in file "icmauth.txt"(if notalready exisiting)
3. start SAP Web Dispatcher with the created profile
After the bootstrap you can use the web based administration
Generating Profile "sapwebdisp.pfl"
Hostname of Message Server (rdisp/mshost): 10.1.10.56
HTTP Port of Message Server (ms/http_port): 8100
Checking connection to message server...
ERROR: Connection to message server failed: NIECONN_REFUSED
Do you want to continue with these settings? no
==========================================================================
BACK-END APPLICATION MESSAGE SERVER DETAILS: SID: PPI [PI/XI]
==========================================================================
icm/server_port_0 PROT=HTTP,PORT=80$$
ms/server_port_0 PROT=HTTP,PORT=81$$
trc file: "dev_ms", trc level: 1, release: "700"
[Thr 1] Thu Jan 3 15:31:05 2008
[Thr 1] WLM Tag 'PPI/MSG' successfully set for this process
[Thr 1] MsSSetTrcLog: trc logging active, max size = 20971520 bytes
systemid 324 (IBM RS/6000 with AIX)
relno 7000
patchlevel 0
patchno 110
intno 20050900
make: multithreaded, Unicode, 64 bit, optimized
pid 2519162
[Thr 1] ***LOG Q01=> MsSInit, MSStart (Msg Server 1 2519162)
[msxxserv_mt. 1824]
[Thr 1] SigISetDefaultAction : default handling for signal 20
[Thr 1] load acl file = /usr/sap/PPI/SYS/global/ms_acl_info
[Thr 1] MsGetOwnIpAddr: my host addresses are :
[Thr 1] 1 : [10.1.10.56] pi100 (HOSTNAME)
[Thr 1] 2 : [127.0.0.1] loopback (LOCALHOST)
[Thr 1] 3 : [10.1.99.4] pi100v (NILIST)
[Thr 1] MsHttpInit: full qualified hostname = pi100
[Thr 1] HTTP logging is switch off
[Thr 1] set HTTP state to LISTEN
[Thr 1] ms/icf_info_server : deleted
[Thr 1] *** I listen to port sapmsPPI (3600) ***
[Thr 1] *** I listen to internal port 3900 (3900) ***
[Thr 1] *** HTTP port 8100 state LISTEN ***
[Thr 1] CUSTOMER KEY: >R1306811094<
[Thr 1] Thu Jan 3 15:31:28 2008
[Thr 1] MsHttpReadUrl2: H-1 url = /sap/public/icf_info/urlprefix (403
Forbidden)
[Thr 1] MsHttpReadUrl2: H-1 url = /sap/public/icf_info/logon_groups (403
Forbidden)
======================+++++++++++++++++++++++++++==============================
Please find the attached file for a better understanding of the trace file.
A quick action on this would be much appreciated.
Please let me know for any information required.
Thank you.
Regards,
~sagar

Vipin,
I don't have access to our firewall myself to confirm what ports and services we opened (I worked with our Network Operations team to get this done), but if I recall correctly, it was pretty limited, just http and https over tcp ports 80, 443, 8100, and 8101. Probably could even restrict that to just https over 443 and 8101. However, from your configuration, you don't yet have your web dispatcher configured to talk to your message server over https, only http. I would recommend that you get the web dispatched completely configured and working in as close to your final desired configuration as possible while keeping it inside your firewall, not your dmz. Then move it to the dmz and see what breaks, and that way you know it's just the firewall that needs configuration at that point.
To configure the SSL termination, the following are the parameters required and the way that I configured them in our scenario (which terminates incoming SSL requests and re-encrypts them when sending them on to the backend, and also uses SSL for message server communication):
rdisp/mshost = mshost.domain.org
ms/https_port = 8101
wdisp/server_info_protocol = https
wdisp/group_info_protocol = https
wdisp/url_map_protocol = https
icm/server_port_1 = PROT=HTTPS,PORT=443,TIMEOUT=30,PROCTIMEOUT=600
icm/server_port_2 = PROT=HTTPS,PORT=8101,TIMEOUT=30,PROCTIMEOUT=600
icm/host_name_full = wdhost.domain.org (note, use the externally visible name as registered on your SSL certificate for web dispatcher here; does not need to match the actual machine hostname, but must be resolvable in external DNS)
icm/HTTP/admin_0 = PREFIX=/sap/admin,DOCROOT=\usr\sap\RW1\W00\data\icmanroot/admin,AUTHFILE=\usr\sap\RW1\SYS\global\security\data\icmauth.txt,PORT=8101
ssl/ssl_lib = $(DIR_EXECUTABLE)\sapcrypto.dll
ssl/server_pse = $(DIR_INSTANCE)\sec\SAPSSLS.pse
ssl/client_pse = $(DIR_INSTANCE)\sec\SAPSSLC.pse
wdisp/ssl_encrypt = 2
wdisp/ssl_auth = 1
is/HTTP/show_detailed_errors = FALSE
wdisp/permission_table = $(DIR_INSTANCE)\sec\ptab
On the backend host I have the following parameters:
sec/libsapsecu = \usr\sap\RP1\DVEBMGS00\exe\sapcrypto.dll
ssl/ssfapi_lib = \usr\sap\RP1\DVEBMGS00\exe\sapcrypto.dll
ssl/ssl_lib = \usr\sap\RP1\DVEBMGS00\exe\sapcrypto.dll
ssf/name = SAPSECULIB
icm/server_port_2 = PROT=HTTPS,PORT=443,PROCTIMEOUT=-1
ms/server_port_1 = PROT=HTTPS,PORT=8101
Naturally, a server certificate is configured on the backend that the web dispatcher trusts (it can be an internally generated certificate; the outside public just needs to trust the web dispatcher's certificate, so that one should come from a recognized CA). Port 8101 is NOT open from the outside, just from the dmz and only to/from the web dispatcher host (this does allow me to use the webadmin interface from the inside). The https service also has to be activated on the backend in SMICM.
There's good advice about security setup for the web dispatcher in Note 870127, and troubleshooting advice in the Note mentioned in your tracefile output, 552286. Fairly complete documentation is in the online help at http://help.sap.com/saphelp_nw70/helpdata/en/de/89023c59698908e10000000a11402f/frameset.htm. Note 538405 is also good, more for performance configuration than security.
I hope you find this helpful.
--Matt

NIECONN_REFUSED - Connect to message server failes while installing AS

Hi all,
during installation of an additional application server ABAP+JAVA,
I obtain this message error:
Connection to message server (<Central istance>) failed: NIECONN_REFUSED.
can anyone help me?
The Message Server into central istance has not error and is online.
best regards,
Davide

Hi,
Check you have the connection to network and also firewall settings. May be you can stop antivirus (if there is any) and give a try.
If it is loopback adapter then you may need to check the configuration.
Manoj

I upgraded to Lion yesterday. Now I keep getting and error message: there was a problem connecting to the server. URLs with type "file:" are not supported. What server?

I upgraded to Lion yesterday. Now I keep getting and error message: there was a problem connecting to the server. URLs with type "file:" are not supported. What server? How do I get rid of this.

Take a look at this link, https://discussions.apple.com/message/16156214#16156214

Connect to message server failed

If there is a huge traffic to the webapplication server, we are getting the follwoing error
Connect to message server failed_ Connect_PM MSHOST=..., R3NAME=..., GROUP=CRM_ _ LOCATION CPIC (TCP/IP) on local host_ ERROR internal error_ (this retcode should be handled by caller of NI-layer)_ _ TIME Thu Jan 11 19:40:21 2007_ RELEASE 640_ COMPONENT NI (network interface)_ VERSION 37_ RC -8_ MODULE nixxi_r.cpp_ LINE 3977_ DETAIL NiCreateHandle: no free handle_ COUNTER 212_ ]]>
<source>SAP.Connector</source>
<stacktrace> at SAP.Connector.Connection.Open()_ _ at SAP.Connector.Connection.BeforeCall(SAPClient sapclient)_ _ at SAP.Connector.SAPClient.BeforeCall()_ _ at SAP.Connector.SAPClient.SAPInvoke(String method, Object[] methodParamsIn)_ _ at RFC call
We have enabled connecion pooling.
Any help would be appreciated.
Thanks,
Sandy

Hi,
pls check the IP address and better do not login in the LOOPBACKADAPTER
make one more new lan connection and give the folowing IP adress
192.168.100.10 or some 100.200
this will help you
Regards,
srikanth

Connect to message server host failed Connect_PM TYPE=B MSHOST=hmsnsw00

Similar Messages

Maybe you are looking for