SOLUTION MANAGER 7.2 JAVA INSTALLATION- J2EE startup issue

[Former Member]

Dear Friends,

Our customer requested to proceed with SOLMAN 7.2 installation.WE had installed ABAP successfully and we are able to login to ABAP successfully without ny isssue,

While doing installation of JAVA we got struck while starting J2EE.Below is the trans log file details for reference.Kindly guide us how can we proceed.

ETW000 R3trans version 6.25 (release 745 - 27.11.15 - 20:15:12).

4 ETW000 unicode enabled version

4 ETW000 ===============================================

4 ETW000

4 ETW000 date&time   : 28.08.2016 - 07:09:10

4 ETW000 control file: <no ctrlfile>

4 ETW000 R3trans was called as follows: R3trans -d

4 ETW000  trace at level 1 opened for a given file pointer

4 ETW000  [     dev trc,00000]  Sun Aug 28 07:09:10 2016

4 ETW000  [     dev trc,00000]  Loading DB library '/usr/sap/TSJ/SYS/exe/run/dbsybslib.so' ...

4 ETW000  [     dev trc,00000]  Library '/usr/sap/TSX/SYS/exe/run/dbsybslib.so' loaded

4 ETW000  [     dev trc,00000]  Version of '/usr/sap/TSX/SYS/exe/run/dbsybslib.so' is "745.04", patchlevel (0.100)

4 ETW000  [     dev trc,00000]  read_con_info_ssfs(): DBSL supports extended connect protocol

4 ETW000                         ==> connect info for default DB will be read from ssfs

4 ETW000  [     dev trc,00000]  load of SQLLEN8 SYB library libsybdrvodb8.so successful.

4 ETW000  [     dev trc,00000]  database is local: connect_timeout: 3

4 ETW000  [     dev trc,00000]  lib_dbsl 745 02/15/2016 12:25:00

4 ETW000  [     dev trc,00000]  dbsybslib.dll patch info

4 ETW000  [     dev trc,00000]    SAP patchlevel  0

4 ETW000  [     dev trc,00000]    SAP patchno  100

4 ETW000  [     dev trc,00000]    Last SYBASE DBSL patchlevel 0

4 ETW000  [     dev trc,00000]    Last SYBASE DBSL patchno         100

4 ETW000  [     dev trc,00000]    Last SYBASE DBSL patchcomment SAP Support Package Stack Kernel 7.45 Patch Level 100 (2276394)

4 ETW000  [     dev trc,00000]  ERROR: -1 in function SQLConnectWithRetry (SQLConnectWithRetry) [line 5110]

4 ETW000  [     dev trc,00000]  (4002) [ZZZZZ] [SAP][ASE ODBC Driver][Adaptive Server Enterprise]Login failed.

4 ETW000  [     dev trc,00000]  Connection 0 failed using DRIVER={Adaptive Server Enterprise};server=TDCSRVSM01;port=4905;uid=SAPBAQ;db=TSJ;pwd=xxxxxxxxx;TextSize=2147483647;CRC=0;FetchArraySize=1000;ReleaseLocksOnCursorClose=1;DynamicPrepare=1;QuotedIdentifier=1;UseCursor=2;homogeneousbatch=1;charset=utf8;EncryptPassword=1;EnableLOBLocator=0;app=R3 000 00 comm rd ODBC;logintimeout=3;ProtocolCapture=cap_p16353_comm_rd;supresstdscontroltokens=1;SuppressRowFormat=1;SuppressParamFormat=1;

4 ETW000  [    dblink  ,00000]  ***LOG BY2=>sql error 4002   performing CON

4 ETW000  [    dblink  ,00000]  ***LOG BY0=>[ASE Error SQL4002][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Login failed.

2EETW169 no connect possible: "DBMS = SYBASE --- "

Reagrds

Pankaj

[Sriram2009 · Accepted solution]

Hi Pankaj.

Could you share the SAPinst log as attachment.

BR

SS

[Former Member · Accepted solution]

Hi Sriram,

Below is the log i am attaching for reference,its unable to connect to message server:

Spliting of JAVA stack makes a crazy installation..

LOG from dev_jstart:

M  [Thr 140737353873248] *              Please check the trace file of the message server

M  [Thr 140737353873248] *              Please check hostname and/or service for typing errors

M  [Thr 140737353873248] *              Please check whether a network filter has been activated

M  [Thr 140737353873248] *              (parameter ms/acl_file_int)

M  [Thr 140737353873248] *

M  [Thr 140737353873248] *  TIME        Sun Aug 28 13:53:47 2016

M  [Thr 140737353873248] *  RELEASE     745

M  [Thr 140737353873248] *  COMPONENT   MS (message handling interface, multithreaded)

M  [Thr 140737353873248] *  VERSION     4

M  [Thr 140737353873248] *  RC          -35

M  [Thr 140737353873248] *  MODULE      /bas/745_REL/src/krn/ms/msxxi.c

M  [Thr 140737353873248] *  LINE        2773

M  [Thr 140737353873248] *  COUNTER     52

M  [Thr 140737353873248] *

M  [Thr 140737353873248] *****************************************************************************

M  [Thr 140737353873248]

M  [Thr 140737353873248] *** ERROR => MsIAttachEx: MsINiWrite (rc=MSECONNECTFAILED) [msxxi.c      1108]

M  [Thr 140737353873248] *** ERROR => MsPrvGetHdl2: not_attached [msxxi.c      2370]

M

M [Thr 140737353873248] Sun Aug 28 13:53:52 2016

M  [Thr 140737353873248] ***LOG Q0I=> NiPConnect2: 192.168.54.235:3903: connect (111: Connection refused) [/bas/745_REL/src/base/ni/nixxi.cpp 3377]

M  [Thr 140737353873248] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 65/sock 15

    (SI_ECONN_REFUSE/111; I4; ST; 192.168.54.235:3903) [nixxi.cpp    3377]

M  [Thr 140737353873248] ***LOG Q0I=> NiPConnect2: 192.168.54.235:3203: connect (111: Connection refused) [/bas/745_REL/src/base/ni/nixxi.cpp 3377]

M  [Thr 140737353873248] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 59/sock 14

    (SI_ECONN_REFUSE/111; I4; ST; 192.168.54.235:3203) [nixxi.cpp    3377]

E  [Thr 140737353873248] *** ERROR => EnqTCDisconnect: EnqTCIGetConn failed; invalid TChdl 59 [enxxtc.c     394]

M  [Thr 140737353873248]

M  [Thr 140737353873248] *****************************************************************************

M  [Thr 140737353873248] *

M  [Thr 140737353873248] *  ERROR       The connection to the specified message server (TXXXXXM01 /

M  [Thr 140737353873248] *              3903) failed.

M  [Thr 140737353873248] *              Please check the trace file of the message server

M  [Thr 140737353873248] *              Please check hostname and/or service for typing errors

M  [Thr 140737353873248] *              Please check whether a network filter has been activated

M  [Thr 140737353873248] *              (parameter ms/acl_file_int)

M  [Thr 140737353873248] *

M  [Thr 140737353873248] *  TIME        Sun Aug 28 13:53:52 2016

M  [Thr 140737353873248] *  RELEASE     745

M  [Thr 140737353873248] *  COMPONENT   MS (message handling interface, multithreaded)

M  [Thr 140737353873248] *  VERSION     4

M  [Thr 140737353873248] *  RC          -35

Regards

Pankaj

[Former Member · Accepted solution]

Hi sriram,

Below is the Sapinst log getting error,as stated unable to connect to message server.

27.08.2016 13:24:10

GetProcessList

OK

name, description, dispstatus, textstatus, starttime, elapsedtime, pid

jstart, J2EE Server, YELLOW, Connecting to message server, 2016 08 27 13:22:41, 0:01:29, 27841

igswd_mt, IGS Watchdog, GREEN, Running, 2016 08 27 13:22:41, 0:01:29, 27842

WARNING 2016-08-27 13:24:20.256 (root/sapinst) id=wapsmod.ms.MsAttachFailed

Connect to message server (TxxxxxxxxSM01/3903) failed: MSENILAYER.

INFO 2016-08-27 13:24:20.305 (root/sapinst)

Node sapcontrol_TSX_J02.log already exists.

INFO 2016-08-27 13:24:20.329 (root/sapinst)

Output of /usr/sap/TSX/SCS03/exe/sapcontrol -prot NI_HTTP -nr 02 -function GetProcessList is written to the logfile sapcontrol_TSX_J02.log.

INFO 2016-08-27 13:24:20.372 (root/sapinst)

Execution of the command "/usr/sap/TSX/SCS03/exe/sapcontrol -prot NI_HTTP -nr 02 -function GetProcessList" finished with return code 0. Output:

27.08.2016 13:24:20

GetProcessList

OK

name, description, dispstatus, textstatus, starttime, elapsedtime, pid

jstart, J2EE Server, YELLOW, Connecting to message server, 2016 08 27 13:22:41, 0:01:39, 27841

igswd_mt, IGS Watchdog, GREEN, Running, 2016 08 27 13:22:41, 0:01:39, 27842

WARNING 2016-08-27 13:24:30.383 (root/sapinst) id=wapsmod.ms.MsAttachFailed

Connect to message server (TxxxxXXXM01/3903) failed: MSENILAYER.

INFO 2016-08-27 13:24:30.434 (root/sapinst)

Node sapcontrol_TSX_J02.log already exists.

INFO 2016-08-27 13:24:30.459 (root/sapinst)

Output of /usr/sap/TSX/SCS03/exe/sapcontrol -prot NI_HTTP -nr 02 -function GetProcessList is written to the logfile sapcontrol_TSX_J02.log.

Regards

Pankaj

[Former Member · Accepted solution]

Hi,

Can you also check the port 3903 is open and allowed in your firewall.

Regards,

Ganesan

[Former Member · Accepted solution]

Hi Ganesan,

I am checking  that only from our  network team. Willl update you status in couple of minutes.

Regards

Pankaj

[Sriram2009 · Accepted solution]

Hi Pankaj.

Is it possible to do the full system restart and then start the installation where its sopped.

BR

SS

[Reagan · Accepted solution]

M  [Thr 140737353873248] *  ERROR       The connection to the specified message server (TXXXXXM01 /
M  [Thr 140737353873248] *              3903) failed.
M  [Thr 140737353873248] *              Please check the trace file of the message server

Have you checked the message server trace file (dev_ms)?. What does it say?

[Former Member · Accepted solution]

Hello Reagan,

We had resolved the issue,there was mistakenly wrong client no given while doing installation .

Then we had uninstalled and reinstalled the system with client001 mentioning in system client in JAVA installation.Now we had pass the issue.

Installation is going finally smooth.

Regards

Pankaj

[Former Member · Accepted solution]

Hi Sriram,

Thanks for the inputs and help.

We had resolved the issue,there was mistakenly wrong client no given while doing installation .

Then we had uninstalled and reinstalled the system with client001 mentioning in system client in JAVA installation.Now we had pass the issue.

Installation is going finally smooth.

Regards

Pankaj

[former_member182967]

Hi Sai,

R3trans -d does not work in pure java stack. This is normal.

Please be patient and see if it is stopped with any error in this step.

Regards,

Ning

[Former Member]

Hi Ning,

Thanks for the qucik reply,Sure i am checking the Sapinst log and java startup log will share in couple of minutes.

Regards

Pankaj

[Former Member]

Hi Ning,

Below is the Sapinst log getting error,as stated unable to connect to message server.

27.08.2016 13:24:10

GetProcessList

OK

name, description, dispstatus, textstatus, starttime, elapsedtime, pid

jstart, J2EE Server, YELLOW, Connecting to message server, 2016 08 27 13:22:41, 0:01:29, 27841

igswd_mt, IGS Watchdog, GREEN, Running, 2016 08 27 13:22:41, 0:01:29, 27842

WARNING 2016-08-27 13:24:20.256 (root/sapinst) id=wapsmod.ms.MsAttachFailed

Connect to message server (TxxxxxxxxSM01/3903) failed: MSENILAYER.

INFO 2016-08-27 13:24:20.305 (root/sapinst)

Node sapcontrol_TSX_J02.log already exists.

INFO 2016-08-27 13:24:20.329 (root/sapinst)

Output of /usr/sap/TSX/SCS03/exe/sapcontrol -prot NI_HTTP -nr 02 -function GetProcessList is written to the logfile sapcontrol_TSX_J02.log.

INFO 2016-08-27 13:24:20.372 (root/sapinst)

Execution of the command "/usr/sap/TSX/SCS03/exe/sapcontrol -prot NI_HTTP -nr 02 -function GetProcessList" finished with return code 0. Output:

27.08.2016 13:24:20

GetProcessList

OK

name, description, dispstatus, textstatus, starttime, elapsedtime, pid

jstart, J2EE Server, YELLOW, Connecting to message server, 2016 08 27 13:22:41, 0:01:39, 27841

igswd_mt, IGS Watchdog, GREEN, Running, 2016 08 27 13:22:41, 0:01:39, 27842

WARNING 2016-08-27 13:24:30.383 (root/sapinst) id=wapsmod.ms.MsAttachFailed

Connect to message server (TxxxxXXXM01/3903) failed: MSENILAYER.

INFO 2016-08-27 13:24:30.434 (root/sapinst)

Node sapcontrol_TSX_J02.log already exists.

INFO 2016-08-27 13:24:30.459 (root/sapinst)

Output of /usr/sap/TSX/SCS03/exe/sapcontrol -prot NI_HTTP -nr 02 -function GetProcessList is written to the logfile sapcontrol_TSX_J02.log.

Regards

Pankaj