SAP Knowledge Base Article - Preview

1537366 - Universe Connections Message Server

Symptom

  • Connect to SAP connection service 'sapmsOSS' not found:
  • SAP message server connection error

A service name is unknown, in this example sapmsOSS. The trace file contains the following entry:

***LOG Q0I=> NiPGetServByName: service 'sapmsOSS' not found: getservbyname [niuxi.c 1669]


or

***LOG Q0I=> NiPGetServByName: 'sapmsOSS' not found: getaddrinfo [niuxi.c 1617]
*** ERROR => GwIAsyncConn: GwBufConnect to oss001 / sapmsOSS failed (rc=NIESERV_UNKNOWN) [gwxx.c       1113]


or

****************************************************************
*
*  LOCATION    SAP-Gateway on host ld0168 / sapgw53
*  ERROR       service 'sapmsOSS' unknown
*
*  TIME        Wed Jan 11 13:22:35 2006
*  RELEASE     710
*  COMPONENT   NI (network interface)
*  VERSION     39
*  RC          -3
*  MODULE      nixxhsl.cpp
*  LINE        643
*  DETAIL      NiHsLGetServNo: service name cached as unknown
*  COUNTER     293
*
****************************************************************


Or the following SAP GUI error message occurs:

service 'sapmsOSS' unknown

Other terms

service unknown, sapms, sapgw, sapdp, getservbyname, getservbyname_r, getservbyport, getservbyport_r, getaddrinfo, getnameinfo, NiPServToNo, NiPNoToServ, NiPGetServByName, NiPGetServByName2, NiPGetServByPort, NiPGetServByPort2, NIESERV_UNKNOWN

Reason and Prerequisites

A lookup for the specified service name is not possible for the corresponding port number. In most cases the error occurs during the connection to a server (for example, message server, dispatcher, gateway, SAProuter , and so on) in which a service name is specified instead of a port number. Since the service name is unknown, the connection cannot be established.

You can use the 'niping' program to reproduce the error. Call the program as follows:

niping -v -S <service name>


For sapmsOSS, the program displays the following:

:/> niping -v -S sapmsOSS
...
Servicename/Serviceport verification:
=======================================
 
Lookup of service: sapmsOSS                        (NiServToNo)
 
Wed Jan 11 13:44:35 2006
***LOG Q0I=> NiPGetServByName: service 'sapmsOS2' not found: getservbyname [niuxi.c 1669]
    --> **** FAILED ****
...


In case of a successful lookup (in this example, port number 3616 is assigned to the sapmsOSS service name), the program displays the following:

:/> niping -v -S sapmsOSS
...
Servicename/Serviceport verification:
=======================================
 
Lookup of service: sapmsOSS                        (NiServToNo)
    --> Number: 3616
...


You can choose any assignment of a service name to a port number. The default values for the SAP service names are usually within the following port number ranges:

Dispatcher:

sapdp<instance number> range from 3200 to 3298

Gateway:

sapgw<instance number> range from 3300 to 3398

Message server:

sapms<SID> range from 3600 to 3698

Read more...

Environment

  • BusinessObjects Enterprise
  • Universe Designer
  • SAP Netweaver

Product

SAP BusinessObjects Enterprise XI 3.1

Keywords

KBA , BI-BIP-SL , Semantic Layer , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.