Can't login into NW after a new patch.

[Former Member]

Hi experts.

Yestoday I installed a new patch KB70010,after that use command SGEN to compile all source in component BASIS.This process began and said theres 2 hours left to complete.

But this morning i can't login into the system,seems the SGEN not successful or sth else.....

disp+work is in yellow status with a message: Running but not connected to Message Server.J2EE status info unavailable.

here's the developer trace.

-

---

trc file: "dev_disp", trc level: 1, release: "700"

-

---

sysno 01

sid ER1

systemid 560 (PC with Windows NT)

relno 7000

patchlevel 0

patchno 75

intno 20050900

make: multithreaded, Unicode, optimized

pid 6112

Tue Jun 03 10:51:31 2008

kernel runs with dp version 217000(ext=109000) (@(#) DPLIB-INT-VERSION-217000-UC)

length of sys_adm_ext is 572 bytes

• SWITCH TRC-HIDE on ***

***LOG Q00=> DpSapEnvInit, DPStart (01 6112) [dpxxdisp.c 1237]

shared lib "dw_xml.dll" version 75 successfully loaded

shared lib "dw_xtc.dll" version 75 successfully loaded

shared lib "dw_stl.dll" version 75 successfully loaded

shared lib "dw_gui.dll" version 75 successfully loaded

shared lib "dw_mdm.dll" version 75 successfully loaded

rdisp/softcancel_sequence : -> 0,5,-1

use internal message server connection to port 3901

Tue Jun 03 10:51:36 2008

• WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds

***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 5273]

MtxInit: 30000 0 0

DpSysAdmExtInit: ABAP is active

DpSysAdmExtInit: VMC (JAVA VM in WP) is not active

Tue Jun 03 10:51:41 2008

• ERROR => OpenProcess PID 3180 failed for checking semaphore 4

ERROR_INVALID_PARAMETER: The parameter is incorrect. [semnt.c 1892]

DpIPCInit2: start server >EXXEPT01_ER1_01 <

DpShMCreate: sizeof(wp_adm) 26752 (1408)

DpShMCreate: sizeof(tm_adm) 3994272 (19872)

DpShMCreate: sizeof(wp_ca_adm) 24000 (80)

DpShMCreate: sizeof(appc_ca_adm) 8000 (80)

DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528056/528064

DpShMCreate: sizeof(comm_adm) 528064 (1048)

DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0

DpShMCreate: sizeof(file_adm) 0 (72)

DpShMCreate: sizeof(vmc_adm) 0 (1440)

DpShMCreate: sizeof(wall_adm) (38456/34360/64/184)

DpShMCreate: sizeof(gw_adm) 48

DpShMCreate: SHM_DP_ADM_KEY (addr: 073F0040, size: 4661816)

DpShMCreate: allocated sys_adm at 073F0040

DpShMCreate: allocated wp_adm at 073F1E40

DpShMCreate: allocated tm_adm_list at 073F86C0

DpShMCreate: allocated tm_adm at 073F86F0

DpShMCreate: allocated wp_ca_adm at 077C7990

DpShMCreate: allocated appc_ca_adm at 077CD750

DpShMCreate: allocated comm_adm at 077CF690

DpShMCreate: system runs without file table

DpShMCreate: allocated vmc_adm_list at 07850550

DpShMCreate: allocated gw_adm at 07850590

DpShMCreate: system runs without vmc_adm

DpShMCreate: allocated ca_info at 078505C0

DpShMCreate: allocated wall_adm at 078505C8

MBUF state OFF

DpCommInitTable: init table for 500 entries

EmInit: MmSetImplementation( 2 ).

MM global diagnostic options set: 0

<ES> client 0 initializing ....

<ES> InitFreeList

<ES> block size is 1024 kByte.

Using implementation flat

<EsNT> Memory Reset disabled as NT default

<ES> 511 blocks reserved for free list.

ES initialized.

J2EE server info

start = TRUE

state = STARTED

pid = 1632

argv[0] = D:\usr\sap\ER1\DVEBMGS01\exe\jcontrol.EXE

argv[1] = D:\usr\sap\ER1\DVEBMGS01\exe\jcontrol.EXE

argv[2] = pf=D:\usr\sap\ER1\SYS\profile\ER1_DVEBMGS01_EXXEPT01

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=1351

argv[5] = -DSAPSYSTEM=01

argv[6] = -DSAPSYSTEMNAME=ER1

argv[7] = -DSAPMYNAME=EXXEPT01_ER1_01

argv[8] = -DSAPPROFILE=D:\usr\sap\ER1\SYS\profile\ER1_DVEBMGS01_EXXEPT01

argv[9] = -DFRFC_FALLBACK=ON

argv[10] = -DFRFC_FALLBACK_HOST=localhost

start_lazy = 0

start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

rdisp/http_min_wait_dia_wp : 1 -> 1

***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c 1623]

***LOG Q0K=> DpMsAttach, mscon ( EXXEPT01) [dpxxdisp.c 11586]

DpStartStopMsg: send start message (myname is >EXXEPT01_ER1_01 <)

DpStartStopMsg: start msg sent

CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

CCMS: Initalizing shared memory of size 60000000 for monitoring segment.

CCMS: start to initalize 3.X shared alert area (first segment).

DpMsgAdmin: Set release to 7000, patchlevel 0

MBUF state PREPARED

MBUF component UP

DpMBufHwIdSet: set Hardware-ID

***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1050]

DpMsgAdmin: Set patchno for this platform to 75

Release check o.K.

Tue Jun 03 10:52:21 2008

DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

Tue Jun 03 10:52:41 2008

J2EE server info

start = TRUE

state = STARTED

pid = 2056

argv[0] = D:\usr\sap\ER1\DVEBMGS01\exe\jcontrol.EXE

argv[1] = D:\usr\sap\ER1\DVEBMGS01\exe\jcontrol.EXE

argv[2] = pf=D:\usr\sap\ER1\SYS\profile\ER1_DVEBMGS01_EXXEPT01

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=1407

argv[5] = -DSAPSYSTEM=01

argv[6] = -DSAPSYSTEMNAME=ER1

argv[7] = -DSAPMYNAME=EXXEPT01_ER1_01

argv[8] = -DSAPPROFILE=D:\usr\sap\ER1\SYS\profile\ER1_DVEBMGS01_EXXEPT01

argv[9] = -DFRFC_FALLBACK=ON

argv[10] = -DFRFC_FALLBACK_HOST=localhost

start_lazy = 0

start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

[Former Member · Accepted solution]

Hi Steiner,

There are several reasons may occur that kind of problem. First of all, could you check work process logs? Not dev_disp but dev_w0. Can you login to ABAP stack?

Could you provide dev_w0 log?

Best regards,

Orkun Gedik

[Former Member · Accepted solution]

Hi rohit.

I find nothing like that parameter in profile....

Hi Orkun.

Here's the dev_w0 log.

Thanks a lot ^ ^

-

---

trc file: "dev_w0", trc level: 1, release: "700"

-

---

*

• ACTIVE TRACE LEVEL 1

• ACTIVE TRACE COMPONENTS all, MJ

*

B

B Tue Jun 03 14:09:34 2008

B create_con (con_name=R/3)

B Loading DB library 'D:\usr\sap\ER1\DVEBMGS01\exe\dbsdbslib.dll' ...

B Library 'D:\usr\sap\ER1\DVEBMGS01\exe\dbsdbslib.dll' loaded

B Version of 'D:\usr\sap\ER1\DVEBMGS01\exe\dbsdbslib.dll' is "700.08", patchlevel (0.68)

B New connection 0 created

M sysno 01

M sid ER1

M systemid 560 (PC with Windows NT)

M relno 7000

M patchlevel 0

M patchno 75

M intno 20050900

M make: multithreaded, Unicode, optimized

M pid 4056

M

M kernel runs with dp version 217000(ext=109000) (@(#) DPLIB-INT-VERSION-217000-UC)

M length of sys_adm_ext is 572 bytes

M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 4056) [dpxxdisp.c 1299]

I MtxInit: 30000 0 0

M DpSysAdmExtCreate: ABAP is active

M DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active

M DpShMCreate: sizeof(wp_adm) 26752 (1408)

M DpShMCreate: sizeof(tm_adm) 3994272 (19872)

M DpShMCreate: sizeof(wp_ca_adm) 24000 (80)

M DpShMCreate: sizeof(appc_ca_adm) 8000 (80)

M DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528056/528064

M DpShMCreate: sizeof(comm_adm) 528064 (1048)

M DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0

M DpShMCreate: sizeof(file_adm) 0 (72)

M DpShMCreate: sizeof(vmc_adm) 0 (1440)

M DpShMCreate: sizeof(wall_adm) (38456/34360/64/184)

M DpShMCreate: sizeof(gw_adm) 48

M DpShMCreate: SHM_DP_ADM_KEY (addr: 073F0040, size: 4661816)

M DpShMCreate: allocated sys_adm at 073F0040

M DpShMCreate: allocated wp_adm at 073F1E40

M DpShMCreate: allocated tm_adm_list at 073F86C0

M DpShMCreate: allocated tm_adm at 073F86F0

M DpShMCreate: allocated wp_ca_adm at 077C7990

M DpShMCreate: allocated appc_ca_adm at 077CD750

M DpShMCreate: allocated comm_adm at 077CF690

M DpShMCreate: system runs without file table

M DpShMCreate: allocated vmc_adm_list at 07850550

M DpShMCreate: allocated gw_adm at 07850590

M DpShMCreate: system runs without vmc_adm

M DpShMCreate: allocated ca_info at 078505C0

M DpShMCreate: allocated wall_adm at 078505C8

X EmInit: MmSetImplementation( 2 ).

X MM global diagnostic options set: 0

X <ES> client 0 initializing ....

X Using implementation flat

M <EsNT> Memory Reset disabled as NT default

X ES initialized.

M

M Tue Jun 03 14:09:35 2008

M ThInit: running on host EXXEPT01

M

M Tue Jun 03 14:09:36 2008

M calling db_connect ...

C

C DBSDBSLIB : version 700.08, patch 0.068 (Make PL 0.75)

C MAXDB shared library (dbsdbslib) patchlevels (last 10)

C (0.068) MaxDB DBSL patch collection 1 2006 (note 962708)

C (0.051) DB50 perm block defect (note 934194)

C (0.046) ADBC: invalid data when fetching cursor with hold (note 925337)

C (0.045) Signal 11 during creation of BIA index (note 920743)

C (0.038) MaxDB DBSL patch collection 2 2005 (note 908602)

C (0.034) Livecache unicode connect (use SDK 7.6.0 b11) (note 901576)

C (0.028) Disable LVC codepage checking (note 882788)

C (0.019) UPDSTAT optimized (note 870327)

C (0.010) MaxDB DBSL patch collection 1 2005 (note 850830)

C (0.009) New stream compression available with LVC 7.6.0 b12 (note 835809)

C

C

C Loading SQLDBC client runtime ...

C SQLDBC SDK Version : SQLDBC.H 7.6.0 BUILD 002-121-083-965

C SQLDBC Library Version : libSQLDBC 7.6.0 BUILD 035-123-139-084

C SQLDBC client runtime is MaxDB 7.6.0.035 CL 139084

C SQLDBC supports new DECIMAL interface : 0

C INFO : SQLOPT= -I 0 -t 0 -S SAPR3

C Try to connect (DEFAULT) on connection 0 ...

C Attach to SAP DB : Kernel 7.6.00 Build 035-123-139-084

C Database release is SAP DB 7.6.00.035

C INFO : Database 'ER1' instance is running on 'exxept01'

C INFO : SAP DB Packet_Size = 131072

C INFO : SAP DB Min_Reply_Size = 4096

C INFO : SAP DB Comm_Size = 126976

C INFO : DBSL buffer size = 126976

C INFO : SAP DB MaxLocks = 300000

C INFO : Connect to DB as 'SAPER1'

C Command info enabled

C Now I'm connected to SAP DB

C 00: exxept01-ER1, since=20080603140936, ABAP= <unknown> (0)

B Connection 0 opened (DBSL handle 0)

B Wp Hdl ConName ConId ConState TX PRM RCT TIM MAX OPT Date Time DBHost

B 000 000 R/3 000000000 ACTIVE NO YES NO 000 255 255 20080603 140936 exxept01

C INFO : SAP RELEASE (DB) = 700

M db_connect o.k.

M ICT: exclude compression: .zip,.cs,.rar,.arj,.z,.gz,.tar,.lzh,.cab,.hqx,.ace,.jar,.ear,.war,.css,.pdf,.js,.gzip,.uue,.bz2,.iso,.sda,.sar,.gif

[Former Member · Accepted solution]

I found a suspicious log dev_jcontrol, maybe it will do some help.

There's some deadlock at end....

-

---

trc file: "D:\usr\sap\ER1\DVEBMGS01\work\dev_jcontrol", trc level: 1, release: "700"

-

---

node name : jcontrol

pid : 2612

system name : ER1

system nr. : 01

started at : Tue Jun 03 14:13:53 2008

arguments :

arg[00] : D:\usr\sap\ER1\DVEBMGS01\exe\jcontrol.EXE

arg[01] : pf=D:\usr\sap\ER1\SYS\profile\ER1_DVEBMGS01_EXXEPT01

arg[02] : -DSAPSTART=1

arg[03] : -DCONNECT_PORT=3675

arg[04] : -DSAPSYSTEM=01

arg[05] : -DSAPSYSTEMNAME=ER1

arg[06] : -DSAPMYNAME=EXXEPT01_ER1_01

arg[07] : -DSAPPROFILE=D:\usr\sap\ER1\SYS\profile\ER1_DVEBMGS01_EXXEPT01

arg[08] : -DFRFC_FALLBACK=ON

arg[09] : -DFRFC_FALLBACK_HOST=localhost

[Thr 4756] Tue Jun 03 14:13:53 2008

[Thr 4756] *** WARNING => INFO: Unknown property [instance.box.number=ER1DVEBMGS01exxept01] [jstartxx.c 841]

[Thr 4756] *** WARNING => INFO: Unknown property [instance.en.host=EXXEPT01] [jstartxx.c 841]

[Thr 4756] *** WARNING => INFO: Unknown property [instance.en.port=3202] [jstartxx.c 841]

[Thr 4756] *** WARNING => INFO: Unknown property [instance.system.id=1] [jstartxx.c 841]

**********************************************************************

JStartupReadInstanceProperties: read instance properties [D:\usr\sap\ER1\DVEBMGS01\j2ee\cluster\instance.properties;D:\usr\sap\ER1\DVEBMGS01\SDM\program\config\sdm_jstartup.properties]

-> ms host : EXXEPT01

-> ms port : 3902

-> OS libs : D:\usr\sap\ER1\DVEBMGS01\j2ee\os_libs

-> Admin URL :

-> run mode : NORMAL

-> run action : NONE

-> enabled : yes

**********************************************************************

**********************************************************************

Used property files

-> files [00] : D:\usr\sap\ER1\DVEBMGS01\j2ee\cluster\instance.properties

-> files [01] : D:\usr\sap\ER1\DVEBMGS01\SDM\program\config\sdm_jstartup.properties

**********************************************************************

**********************************************************************

Instance properties

-> ms host : EXXEPT01

-> ms port : 3902

-> os libs : D:\usr\sap\ER1\DVEBMGS01\j2ee\os_libs

-> admin URL :

-> run mode : NORMAL

-> run action : NONE

-> enabled : yes

**********************************************************************

**********************************************************************

Bootstrap nodes

-> [00] bootstrap : D:\usr\sap\ER1\DVEBMGS01\j2ee\cluster\instance.properties

-> [01] bootstrap_ID11381200 : D:\usr\sap\ER1\DVEBMGS01\j2ee\cluster\instance.properties

-> [02] bootstrap_ID11381250 : D:\usr\sap\ER1\DVEBMGS01\j2ee\cluster\instance.properties

**********************************************************************

**********************************************************************

Worker nodes

-> [00] ID11381200 : D:\usr\sap\ER1\DVEBMGS01\j2ee\cluster\instance.properties

-> [01] ID11381250 : D:\usr\sap\ER1\DVEBMGS01\j2ee\cluster\instance.properties

-> [02] sdm : D:\usr\sap\ER1\DVEBMGS01\SDM\program\config\sdm_jstartup.properties

**********************************************************************

[Thr 4756] *** WARNING => JsfOpenShm: ShmCreate (69, 295952, CREATE) failed(rc = 4 SHM segment already exists) [jsfxxshm.c 715]

[Thr 4756] *** ERROR => JsfOpenShm: Shm version mismatch (shm "JSF-ADM-CORRUPT", code "JSF-ADM-015") [jsfxxshm.c 761]

[Thr 4756] *** ERROR => Can't create shared memory segment 69 (rc = 😎 [jcntrxx.c 1714]

[Thr 4756] *** ERROR => Can't initialize JControl Administration [jcntrxx.c 271]

[Thr 4756] JControlCloseProgram: started (exitcode = -1)

[Thr 4756] *** ERROR => JsfCloseShm: FiDetachIndex(SESSION) failed (rc = 6 invalid argument) [jsfxxshm.c 1243]

[Thr 4756] *** ERROR => JsfCloseShm: FiDetachIndex(ALIAS) failed (rc = 6 invalid argument) [jsfxxshm.c 1250]

[Thr 4756] *** ERROR => JsfCloseShm: FiDetachIndex(SERVICE) failed (rc = 6 invalid argument) [jsfxxshm.c 1257]

[Thr 4756] JControlCloseProgram: good bye... (exitcode = -1)

[Thr 3152] Tue Jun 03 14:22:52 2008

[Thr 3152] WARNING: MtxLock 02550988 JSF-PROC -2 deadlock ?

[Thr 3152] Tue Jun 03 14:37:56 2008

[Thr 3152] WARNING: MtxLock 02550988 JSF-PROC -2 deadlock ?

[Thr 3152] Tue Jun 03 14:53:01 2008

[Thr 3152] WARNING: MtxLock 02550988 JSF-PROC -2 deadlock ?

[Thr 3152] Tue Jun 03 15:08:05 2008

[Thr 3152] WARNING: MtxLock 02550988 JSF-PROC -2 deadlock ?

[Thr 3152] Tue Jun 03 15:23:09 2008

[Thr 3152] WARNING: MtxLock 02550988 JSF-PROC -2 deadlock ?

[Former Member · Accepted solution]

Hi Steiner,

Did you hard boot your system after you applied patches? I restart the system or NT services that belongs to SAP when I face with shared memory problems. That may help to solve the shared memory problem.

Best regards,

Orkun Gedik

[Former Member]

Compare the current profile with the backup profiles (extension .BAK) to see if any parameters were added or removed.

J. Haynes

[nelis]

Did you not perhaps run our of database space or log space during SGEN ? I've seen this many times..

The first thing I would do is execute a database structure check(DB13) and then take things from there..

Other area's for logging to check would be in /usr/sap/<SID>/<INSTANCE>/j2ee/cluster/system.log etc

You could also try executing SGEN again and hopefully this time it will complete and possibly "overwrite" any problems that exist currently with certain programs(ABAP loads). With MaxDB you can also disable logging during SGEN.

Nelis

[Former Member]

Thankyou for your replys~

I've reboot sevaral times and the profile seems no problem...

In SAPMMC,the tag "J2EE Process Table" has 3 process, dispatch and server can't be started correctly,they always end with an error and try to start again.

The error in server.0.log is:

Caused by: com.sap.security.core.persistence.datasource.PersistenceException:Connect to SAP gateway failed

Connect_PM TYPE=A ASHOST=localhost SYSNR=01 GWHOST=localhost GWSERV=sapgw01 PCS=1

no SAP ErrInfo available

PS. my window service sapccmsr.01 can't be start too.because the same error as above....

Regards.

[Former Member]

Hi,

Seems to be issue with you have change some parameters when your sap was up and running.

ERROR_INVALID_PARAMETER: The parameter is incorrect. http://semnt.c 1892

Could you check with above paarameters may be profile related.

Provide point if issue solve.

Regards,

Rohit Mehta