cancel
Showing results for 
Search instead for 
Did you mean: 

Error in disp+work.EXE - Running, Message Server connection ok...

joo_migueldimas
Active Participant
0 Kudos

Hello gurus,

System: Solution Manager

OS: Windows 2003 server R2 X32

DB: Microsoft SQL server 2005

I have an error when I tried to start my solution manager system, after having done a kernel upgrade (for the level 201)

I donu00B4t know why but the error (as you see in following image) itu00B4s in the java stack more particularly in disp+work.EXE Dispatcher with the status "Running, Message Server connection ok, Dialog Queue time: 0.00 sec, J2EE status info unavailable".

http://img6.imageshack.us/img6/7067/solmanj2eeerror.png

Can you help me whatu00B4s the problem here?

This next text itu00B4s a dev_disp log... maybe with this you get the error and the solution for that! :

---------------------------------------------------
trc file: "dev_disp", trc level: 1, release: "700"
---------------------------------------------------
sysno      01
sid        PSM
systemid   560 (PC with Windows NT)
relno      7000
patchlevel 0
patchno    201
intno      20050900
make:      multithreaded, ASCII, optimized
pid        756


Sun Jul 05 21:08:44 2009
kernel runs with dp version 242(ext=110) (@(#) DPLIB-INT-VERSION-242)
length of sys_adm_ext is 364 bytes
*** SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (01 756) [dpxxdisp.c   1287]
	shared lib "dw_xml.dll" version 201 successfully loaded
	shared lib "dw_xtc.dll" version 201 successfully loaded
	shared lib "dw_stl.dll" version 201 successfully loaded
	shared lib "dw_gui.dll" version 201 successfully loaded
	shared lib "dw_mdm.dll" version 201 successfully loaded
rdisp/softcancel_sequence :  -> 0,5,-1
use internal message server connection to port 3901

Sun Jul 05 21:08:49 2009
*** 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  5518]
MtxInit: 30000 0 0
DpSysAdmExtInit: ABAP is active
DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
DpIPCInit2: start server >salzburgo_PSM_01                        <
DpShMCreate: sizeof(wp_adm)		16464	(1176)
DpShMCreate: sizeof(tm_adm)		3786880	(18840)
DpShMCreate: sizeof(wp_ca_adm)		18048	(60)
DpShMCreate: sizeof(appc_ca_adm)	6000	(60)
DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528040/528048
DpShMCreate: sizeof(comm_adm)		528048	(1048)
DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
DpShMCreate: sizeof(slock_adm)		0	(96)
DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
DpShMCreate: sizeof(file_adm)		0	(72)
DpShMCreate: sizeof(vmc_adm)		0	(1296)
DpShMCreate: sizeof(wall_adm)		(22440/34344/56/100)
DpShMCreate: sizeof(gw_adm)	48
DpShMCreate: SHM_DP_ADM_KEY		(addr: 055C0040, size: 4419544)
DpShMCreate: allocated sys_adm at 055C0040
DpShMCreate: allocated wp_adm at 055C1BF8
DpShMCreate: allocated tm_adm_list at 055C5C48
DpShMCreate: allocated tm_adm at 055C5C78
DpShMCreate: allocated wp_ca_adm at 059624F8
DpShMCreate: allocated appc_ca_adm at 05966B78
DpShMCreate: allocated comm_adm at 059682E8
DpShMCreate: system runs without slock table
DpShMCreate: system runs without file table
DpShMCreate: allocated vmc_adm_list at 059E9198
DpShMCreate: allocated gw_adm at 059E91D8
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 059E9208
DpShMCreate: allocated wall_adm at 059E9210
MBUF state OFF
DpCommInitTable: init table for 500 entries
rdisp/queue_size_check_value :  -> off
ThTaskStatus: rdisp/reset_online_during_debug 0
EmInit: MmSetImplementation( 2 ).
MM global diagnostic options set: 0
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 1024 kByte.
Using implementation view
<EsNT> Using memory model view.
<EsNT> Memory Reset disabled as NT default
<ES> 511 blocks reserved for free list.
ES initialized.
mm.dump: set maximum dump mem to 96 MB
J2EE server info
  start = TRUE
  state = STARTED
  pid = 5700
  argv[0] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
  argv[1] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
  argv[2] = pf=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
  argv[3] = -DSAPSTART=1
  argv[4] = -DCONNECT_PORT=65000
  argv[5] = -DSAPSYSTEM=01
  argv[6] = -DSAPSYSTEMNAME=PSM
  argv[7] = -DSAPMYNAME=salzburgo_PSM_01
  argv[8] = -DSAPPROFILE=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
  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 Q0K=> DpMsAttach, mscon ( salzburgo) [dpxxdisp.c   12527]
DpStartStopMsg: send start message (myname is >salzburgo_PSM_01                        <)
DpStartStopMsg: start msg sent
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
CCMS: Initalizing shared memory of size 40000000 for monitoring segment.
CCMS: Checking Downtime Configuration of Monitoring Segment.
CCMS: start to initalize 3.X shared alert area (first segment).
DpJ2eeLogin: j2ee state = CONNECTED
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 201
Release check o.K.

Sun Jul 05 21:08:55 2009
MBUF state ACTIVE
DpModState: change server state from STARTING to ACTIVE

Sun Jul 05 21:08:57 2009
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
*** ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1444
    (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:2040) [nixxi.cpp    4424]
*** ERROR => DpJ2eeMsgProcess: NiRead failed (NIECONN_BROKEN) [dpxxj2ee.c   1212]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

Sun Jul 05 21:09:29 2009
DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

Sun Jul 05 21:09:49 2009
J2EE server info
  start = TRUE
  state = STARTED
  pid = 2168
  argv[0] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
  argv[1] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
  argv[2] = pf=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
  argv[3] = -DSAPSTART=1
  argv[4] = -DCONNECT_PORT=64999
  argv[5] = -DSAPSYSTEM=01
  argv[6] = -DSAPSYSTEMNAME=PSM
  argv[7] = -DSAPMYNAME=salzburgo_PSM_01
  argv[8] = -DSAPPROFILE=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
  argv[9] = -DFRFC_FALLBACK=ON
  argv[10] = -DFRFC_FALLBACK_HOST=localhost
  start_lazy = 0
  start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED

Sun Jul 05 21:09:52 2009
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
*** ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1440
    (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:2126) [nixxi.cpp    4424]
*** ERROR => DpJ2eeMsgProcess: NiRead failed (NIECONN_BROKEN) [dpxxj2ee.c   1212]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

Sun Jul 05 21:10:09 2009
DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

Sun Jul 05 21:10:29 2009
J2EE server info
  start = TRUE
  state = STARTED
  pid = 5484
  argv[0] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
  argv[1] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
  argv[2] = pf=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
  argv[3] = -DSAPSTART=1
  argv[4] = -DCONNECT_PORT=64997
  argv[5] = -DSAPSYSTEM=01
  argv[6] = -DSAPSYSTEMNAME=PSM
  argv[7] = -DSAPMYNAME=salzburgo_PSM_01
  argv[8] = -DSAPPROFILE=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
  argv[9] = -DFRFC_FALLBACK=ON
  argv[10] = -DFRFC_FALLBACK_HOST=localhost
  start_lazy = 0
  start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED

Sun Jul 05 21:10:32 2009
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
*** ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1532
    (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:2133) [nixxi.cpp    4424]
*** ERROR => DpJ2eeMsgProcess: NiRead failed (NIECONN_BROKEN) [dpxxj2ee.c   1212]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

Sun Jul 05 21:10:49 2009
DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

Sun Jul 05 21:11:09 2009
J2EE server info
  start = TRUE
  state = STARTED
  pid = 3348
  argv[0] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
  argv[1] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
  argv[2] = pf=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
  argv[3] = -DSAPSTART=1
  argv[4] = -DCONNECT_PORT=64996
  argv[5] = -DSAPSYSTEM=01
  argv[6] = -DSAPSYSTEMNAME=PSM
  argv[7] = -DSAPMYNAME=salzburgo_PSM_01
  argv[8] = -DSAPPROFILE=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
  argv[9] = -DFRFC_FALLBACK=ON
  argv[10] = -DFRFC_FALLBACK_HOST=localhost
  start_lazy = 0
  start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED

Sun Jul 05 21:11:12 2009
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
*** ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1436
    (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:2144) [nixxi.cpp    4424]
*** ERROR => DpJ2eeMsgProcess: NiRead failed (NIECONN_BROKEN) [dpxxj2ee.c   1212]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

Sun Jul 05 21:11:29 2009
DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

Sun Jul 05 21:11:49 2009
J2EE server info
  start = TRUE
  state = STARTED
  pid = 1868
  argv[0] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
  argv[1] = D:\usr\sap\PSM\DVEBMGS01\exe\jcontrol.EXE
  argv[2] = pf=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
  argv[3] = -DSAPSTART=1
  argv[4] = -DCONNECT_PORT=64995
  argv[5] = -DSAPSYSTEM=01
  argv[6] = -DSAPSYSTEMNAME=PSM
  argv[7] = -DSAPMYNAME=salzburgo_PSM_01
  argv[8] = -DSAPPROFILE=D:\usr\sap\PSM\SYS\profile\PSM_DVEBMGS01_salzburgo
  argv[9] = -DFRFC_FALLBACK=ON
  argv[10] = -DFRFC_FALLBACK_HOST=localhost
  start_lazy = 0
  start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED

Sun Jul 05 21:11:52 2009
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
*** ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1444
    (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:2152) [nixxi.cpp    4424]
*** ERROR => DpJ2eeMsgProcess: NiRead failed (NIECONN_BROKEN) [dpxxj2ee.c   1212]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

Sun Jul 05 21:12:09 2009
DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

Sun Jul 05 21:12:29 2009
DpEnvCheckJ2ee: switch off j2ee start flag

Best regards,

Jou00E3o Dimas - Portugal

Edited by: Jou00E3o Dimas on Jul 5, 2009 11:39 PM

Accepted Solutions (0)

Answers (6)

Answers (6)

Former Member
0 Kudos

Hi Dimas

I am getting the same error. Can you explain the steps you followed to resolve the error you were getting..

Many thanks for your help in advance.

Regards

Denis.

Former Member
0 Kudos

Hi Dimas

I am getting the same error. Can you explain the steps you followed to resolve the error you were getting..

Many thanks for your help in advance.

Regards

Denis.

Former Member
0 Kudos

Hi

Have a look at below link, not sure but may help you

Regards

Uday

joo_migueldimas
Active Participant
0 Kudos

I uday kumar and David,

I already solve the problem... It was due to the way how I did the kernel upgrade, this is in fact due to my inexperience... was in files that I overwrite when I copy the new kernel to directory of kernel .../NUC and .../UC!

The other problem in the opening of the config tools it´s because JAVA_HOME variable wasn´t defined on system variables and isn´t exist in variable path, it was only defined in user variables! This type of variables should always be defined in System variables of your operation system and not in the user variables, and this action should be made during the installation!

Thank you all for the attempt of help

Best regards,

João Dimas - Portugal

Edited by: João Dimas on Jul 12, 2009 6:14 PM

Former Member
0 Kudos

Hi

Have you checked SAPJSF and J2ee_admin user exist through SU01?

Check the profile parameters once,try change the JVM setting and check were you able to start the server

Regards

Uday

joo_migueldimas
Active Participant
0 Kudos

Hi uday kumar,

First thank you to tried to help me!

--> So... I have a problem... in that checked that you asked, I donu00B4t have acess to all clients in system... Iu00B4m only able to login to client 000 and 100 and in that clients that two users SAPJSF and J2ee_admin donu00B4t exist!! But maybe in 001... I donu00B4t know!! Itu00B4s any other way to know that? I think through configtool in j2ee directory... but I donu00B4t get that, maybe because I donu00B4t have the JAVA part active!!

--> And other thing, you recommed me to "Check the profile parameters once, try change the JVM setting and check were you able to start the server"... What you want to say with JVM setting.. sorry Iu00B4m still newest in sap world... can you explain me better what you wanted to say..?! Thanks.

--> Other think and the last... I checked the sapstartsrv.log in D:\usr\sap\PSM\SCS00\work directory path and in that it said this:

-


trc file: "sapstartsrv.log", trc level: 0, release: "700"

-


Mon Mar 09 11:13:46 2009

<<- ERROR: SapSSLInit(read_profile=1)==SSSLERR_LIB_NOT_FOUND

Can you help me?!... thanks a lot!

Best regards,

Jou00E3o Dimas - Portugal

Former Member
0 Kudos

Configtool should always be able to start.

You don't need a running j2ee for that.

Also checking the log on the ABAP-side probably won't really help you out.

As it is your java-engine that doesn't start.

Everywhere I checked, the error mentioned in your java log file indicates some sort of network issue.

I understand you can ping the server without any problems, but the issue is internally.

joo_migueldimas
Active Participant
0 Kudos

Hi uday kumar,

Regarding this message of you, I already able to login in client 001 and so I verify the user SAPJSF exist and was not blocked, but the user J2EE_ADMIN it was blocked!! I unblocked this user!

Regarding the problem that I report in last message, I don´t get acess to configtool in j2ee directory because it show me a message in prompt window after I click de configtool.bat, which you can see in the following two images:

http://img195.imageshack.us/img195/8977/image1ypm.png

http://img195.imageshack.us/img195/2153/imagem2jyx.png

Best regards,

João Dimas - Portugal

joo_migueldimas
Active Participant
0 Kudos

Hi David Kroone,

As you see in my last message which I sent to Uday Kumar,

I don´t get acess to configtool in j2ee directory because it show me a message in prompt window after I click the icon of configtool.bat, which you can see in the following two images:

http://img195.imageshack.us/img195/8977/image1ypm.png

http://img195.imageshack.us/img195/2153/imagem2jyx.png

So... like you said before "Configtool should always be able to start", this is true! So, why I´m not be able to open the configtools ?! :- |

Best regards,

João Dimas - Portugal

Former Member
0 Kudos

Hi

disp+work.EXE* Dispatcher with the status "Running, Message Server connection ok, Dialog Queue time: 0.00 sec, J2EE status info unavailable

Were you able to open WEB application page http://<Host>:5<Instancenumber>00 ?

R u able to login to SAP ? if so try restart the JAVA engine through Tocde SMICM

Regards

Uday

joo_migueldimas
Active Participant
0 Kudos

Hi uday kumar,

No Unday I´m not able to open WEB application due to that situation... the disp+work.EXE is in yellow state at SAP MMC console with the status "Running, Message Server connection ok, Dialog Queue time: 0.00 sec, J2EE status info unavailable".

http://img6.imageshack.us/img6/7067/solmanj2eeerror.png

Yes, I´m able to login SAP, and I already tried to restart through SMICM but without sucess I open the windows task manager and the process launch.exe doesn´t exist !! Other thing that seems to me a little weird is the fact of sqlservr.exe process have 1.295.250 of memory usage.

Can you help me what´s the problem here?

(By the way... for the moderator/administrators of this forum, I don´t know why my message on top of this thread remain a little confused!!)

Best Regards

João Dimas - Portugal

Former Member
0 Kudos

As I already said Joao, your j2ee-engine isn't starting.

So the fact that you can't reach the url mentioned by uday is logical.

j2ee has a problem connecting to your message server and shuts down.

Most likely due to a network error, or perhaps it just takes a very long time (over 5 mins) and fails due to the settings of your timeout parameter.

joo_migueldimas
Active Participant
0 Kudos

David...

I had already read your first post/answer... but I think this error doesn´t any relationship with network problems, because before kernel upgrade this were fine!!

The network is fine... I ping the server and it replys well, without any problem!!

Best regards,

João Dimas - Portugal

Former Member
0 Kudos

Hi Joao,

You should check out the following thread:

It looks like you might have some sort of network problem......

Regards,

David