3.3.11

SAP Note 24177 - OSS1: Message S1452: Connection to Message Server

Symptom:

When you try to log on to the OSS system using Transaction OSS1, the error message S1452 appears: 'Unable to connect to OSS message server. Default connection will be used ...'.

Cause and prerequisites

Program 'lgtst' not installed
or
configuration not correct. Solution

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Program 'lgtst' not installed
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Please install the program 'lgtst', which is available on the 2.2D CD, in the executables directory of your system (usually this is /usr/sap/[SID]/SYS/exe/run ).

This program is used by Transaction OSS1 to establish the connection to the OSS message server and determine the logon groups available and the OSS application server with the best performance. When this program is missing, the connection to the message server cannot be established, i.e., the server cannot be determined. The system will then log you on to the standard OSS application server.

The program 'lgtst' should be started manually only when problems occur.

To start the program manually, enter the following command at the shell level of the database or application server:
/usr/sap/[SID]/SYS/exe/run/lgtst
-H /H/[YS]/S/[YSS]/H/[sapservX]/S/sapdp99/H/oss001/S/sapmsO01
-S x -W 30000

Please note:

      a) This is ONE command with many parameters.
      b) [SID] must be replaced by the system ID (e.g. C11) of your system.
      c) [YS] must be replaced by the name of the computer on which the SAPRouter runs (YS = Your SAPRouter).
      d) [YSS] must be replaced by the service under which the SAPRouter runs, usually 'sapdp99'
      (YSS = Your SAPRouter's Service).
      e) If you are working with two SAProuters, please repeat /H/[YS]/S/[YSS] with the data of the second SAProuter before the sapserv specifications.
      f) [sapservx] must be replaced by the IP address of the server that you are connected to.
      g) Make sure that you replace [YS], [YSS] and [sapservx] with the same data that you have configured in OSS1.


      The following output should appear on your screen:

      using trcfile: dev_lg
      list of reachable application servers
      -------------------------------------
      [oss001_O01_01] [oss001] [155.56.5.5] [sapdp01] [3201] [DIA ]
      [hs2130_O01_01] [hs2130] [155.56.5.33] [sapdp01] [3201] [DIA VB ENQ BTC
      [oss002_O01_01] [oss002] [155.56.5.53] [sapdp01] [3201] [DIA ]
      [oss003_O01_01] [oss003] [155.56.5.47] [sapdp01] [3201] [DIA ]

      list of selectable login-classes with favorites
      -----------------------------------------------
      [PUBLIC] [155.56.5.53] [3201] []



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Configuration not correct
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

In cases where the program 'lgtst' has been installed correctly, but the connection to the message server cannot be built up, the configuration is not correct.

There are many possible reasons. The most frequent causes:

      a) Technical OSS1 settings
      b) Service entries missing in /etc/services
      c) Incorrect SAPRouter configuration


      To find out the reason why the attempt to establish the connection to the message server has failed, choose 'Tools -> Case, Test -> Developer trace' (Transaction ST11). The trace contains an entry for 'dev_lg'; this file contains the error log. If a line 'LOCATION' exists, the computer where the error occurred is described there. The problem is described in the line 'ERROR'.


Examples:
~~~~~~~~~
************************************************************************
*
* ERROR partner not reached (host abc.def.gh.i, service sapdp99)
*
* TIME Thu Aug 10 09:17:57 1995
* RELEASE 21J
* COMPONENT NI (network interface)
* VERSION 15
* RC -10
* MODULE niuxi.c
* LINE 773
* DETAIL NiPConnect
* SYSTEM CALL connect
* ERRNO 239
* ERRNO TEXT Connection refused
* COUNTER 1
*
************************************************************************

In this case, the system was unable to reach the SAPRouter, i.e., under Service 99 (Port 3299) no SAPRouter can be reached on the host with the IP address abc.def.gh.i. The SAPRouter process is not running, or the IP address is configured incorrectly in OSS1.


************************************************************************
*
* ERROR service 'sapdp99' unknown
*
* TIME Thu Aug 10 09:22:00 1995
* RELEASE 30A
* COMPONENT NI (network interface)
* VERSION 17
* RC -3
* MODULE niuxi.c
* LINE 404
* DETAIL NiPServToNo
* SYSTEM CALL getservbyname
* COUNTER 1
*
************************************************************************

This message indicates that the service 'sapdp99' has not been entered in /etc/services. Please add this entry to /etc/services. The entry must exist on all R/3 servers and all frontends.


************************************************************************
*
* LOCATION SapRouter on abc.def.gh.i
* ERROR route permission denied (XXXXXXXX to sapservX, sapdp99)
*
* TIME Thu Aug 10 09:37:44 1995
* RELEASE 30A
* COMPONENT NI (network interface)
* VERSION 17
* RC -94
* MODULE nixxrout.c
* LINE 1426
* COUNTER 1
*
************************************************************************

In this case the 'routtab' where the valid connections are specified is not correct. The SAPRouter on the host abc.def.gh.i does not build up the connection to sapservX. Please check the 'routtab' of the SAPRouter. 'routtab' must contain all R/3 servers and all frontends.


************************************************************************
*
* LOCATION SapRouter on abc.def.gh.i
* ERROR internal error
*
* TIME Thu Aug 10 10:50:18 1995
* RELEASE 21J
* COMPONENT NI (network interface)
* VERSION 15
* RC -93
* MODULE niuxi.c
* LINE 773
* DETAIL NiPConnect
* SYSTEM CALL connect
* ERRNO 242
* ERRNO TEXT No route to host
* COUNTER 1
*
************************************************************************

This error message indicates that the host abc.def.gh.i cannot handle the IP address of the next host configured in OSS1.
When the SAPRouter error message appears and the next host is sapservX, please check the IP address for sapservX.
OSS1 is delivered with the default setting 'sapserv3' and the IP address '147.204.64.1'. Change this IP address to IP address 147.204.2.5. IP addresses 147.204.63.1 and 147.204.64.1 no longer exist.


************************************************************************
*
* ERROR internal error
*
* TIME Thu Nov 23 00:11:20 1995
* RELEASE 21J
* COMPONENT NI (network interface)
* VERSION 15
* RC -1
* COUNTER 1
*
************************************************************************

This message indicates that for at least one of the SAPRouters defined in the technical settings of OSS1 the specified instance number is not correct. The default instance number for SAPRouter is '99'. Do not specify the instance number of your R/3 System under any circumstances! For the sapservX computers the specification of instance number '99' is mandatory; otherwise logon to OSS is not possible.


************************************************************************
*
* LOCATION SapRouter on sapservX
* ERROR route permission denied (XXXXXX to oss003, sapmsO01)
*
* TIME Mon Nov 27 19:25:54 1995
* RELEASE 30A
* COMPONENT NI (network interface)
* VERSION 15
* RC -94
* MODULE nixxrout.c
* LINE 1390
* COUNTER 1
* ************************************************************************

An incorrect server was specified for the O01 message server, in this example the server oss003. oss01 is the message server for O01.


These examples do not cover all possible cases; other error messages may occur. In individual cases the reason for the problem may be different from the reason specified in the examples.


Example for the technical settings of OSS1:

Router data for logging on to OSS

+-SAPRouter (customer) -----------------------------------------+
| +-SAPRouter 1------------------+ +-SAPRouter 2-----------------+ |
| | Name XYZ | | Name | |
| | IP address a.b.c.d | | IP address | |
| | Instance no. 99 | | Instance no. | |
| +------------------------------+ +-----------------------------+ |
+---------------------------------------------------------------------+

+-SAPRouter and OSS Message Server------------------------------------+
| +-SAPRouter (SAP)--------------+ +-OSS Message Server----------+ |
| | Name sapserv3 | | Name oss001 | |
| | IP address 147.204.2.5 | | DB name O01 | |
| | Instance no. 99 | | Instance no. 01 | |
| +------------------------------+ +-----------------------------+ |
+---------------------------------------------------------------------+


In this example the following situation is assumed:

      a) A customer SAPRouter is running on the host XYZ with the IP address a.b.c.d. Please adjust the host name and IP address accordingly. If you have not reconfigured your SAPRouter for another instance, the instance number '99' is correct.
b) You are connected to sapserv3, IP address 147.204.2.5. If you are connected to sapserv3 under another IP address (147.204.64.1 or 147.204.63.1) or another sapservX (sapserv4, sapserv5, sapserv6 or sapserv7), please choose the appropriate connection from the menu 'SAPRouter (SAP)'.

No comments:

Post a Comment