on 09-13-2010 2:15 PM
Hi,
I have a problem with my CE server. I can't manage to start it properly (it was working before). I am on a virtual machine, on windows server 2003. Each time I try to start the server, jstart.exe ends up with the stopped status.
The database is up and running fine, and has a blue icone in the sapmmc. Here is the developer trace dev_jstart:
-
trc file: "dev_jstart.1864", trc level: 1, release: "720"
-
-
trc file: "dev_jstart.new", trc level: 1, release: "720"
-
sysno 00
sid C72
systemid 560 (PC with Windows NT)
relno 7200
patchlevel 0
patchno 18
intno 20020600
make multithreaded, Unicode, optimized
profile C:\usr\sap\C72\SYS\profile\C72_J00_eozence72
pid 1864
*
ACTIVE TRACE LEVEL 1
ACTIVE TRACE COMPONENTS All, egi
*
Mon Sep 13 14:38:53 2010
*
trace logging activated, max size = 52428800 bytes, 2 versions
*
arguments :
arg[ 0] : C:\usr\sap\C72\SYS\exe\uc\NTI386\jstart.EXE
arg[ 1] : pf=C:\usr\sap\C72\SYS\profile\C72_J00_eozence72
F
F Mon Sep 13 14:38:53 2010
F ********************************************************************************
F Java environment properties (C:\usr\sap\C72\J00\work\jstart.jvm)
F root directory : C:\usr\sap\C72\SYS\exe\jvm\NTI386\sapjvm_6.1.005/sapjvm_6
F vendor : SAP AG
F version : 1.6.0_07
F cpu : x86
F java vm type : server
F java vm version : 6.1.005
F jvm library name : jvm.dll
F library path :
:\usr\sap\C72\SYS\exe\jvm\NTI386\sapjvm_6.1.005\sapjvm_6\jre\bin\server;C:\usr\sap\C72\SYS\exe\jvm\NTI386\sapjvm_6.1.0
5\sapjvm_6\jre\bin
F executable path : C:\usr\sap\C72\SYS\exe\jvm\NTI386\sapjvm_6.1.005\sapjvm_6\bin
F ********************************************************************************
F SAP extensions : available
F ********************************************************************************
I [Thr 208] MtxInit: 30002 0 2
-
trc file: "dev_jstart", trc level: 1, release: "720"
-
*
ACTIVE TRACE LEVEL 1
ACTIVE TRACE COMPONENTS All, egi
*
F [Thr 208] *** LOG => connected to Enqueue Server.
F [Thr 208] *** LOG => connected to Message Server.
F [Thr 208] *** LOG => Starting run level 1.
F
F Mon Sep 13 14:39:04 2010
F ********************************************************************************
F Java process [deployment] properties:
F section name : deployment
F config file : C:\usr\sap\C72\SYS\exe\uc\NTI386\startup.properties
F node name : Deploy_offline
F home directory : C:\usr\sap\C72\J00\j2ee\cluster
F shutdown timeout : 136000 ms
F exit timeout : 7000 ms
F debuggable : false
F debugger active : false
F ********************************************************************************
F [Thr 208] *** LOG => Instance state is "Deploying offline components" (STARTING @ 0, INACTIVE).
F [Thr 208] *** LOG => Starting nodes: runlevel 1.
F
F Mon Sep 13 14:39:05 2010
F ********************************************************************************
F Starting process: C:\usr\sap\C72\SYS\exe\uc\NTI386\jstart.EXE
F arg[ 1] = -nodeId=0
F arg[ 2] = pf=C:\usr\sap\C72\SYS\profile\C72_J00_eozence72
F arg[ 3] = -hostvm
F arg[ 4] = -nodeName=deployment
F arg[ 5] = -file=C:\usr\sap\C72\SYS\exe\uc\NTI386\startup.properties
F arg[ 6] = -jvmFile=C:\usr\sap\C72\J00\work\jstart.jvm
F arg[ 7] = -traceFile=C:\usr\sap\C72\J00\work\dev_deployment
F arg[ 8] = -javaOutFile=C:\usr\sap\C72\J00\work\jvm_deployment.out
F env : JStart/ReserveSize=0x60000000
F env : NODNSSAPTRANSHOST=1
F exePath :
PATH=C:\usr\sap\C72\SYS\exe\jvm\NTI386\sapjvm_6.1.005\sapjvm_6\bin;C:\usr\sap\C72\SYS\exe\uc\NTI386;C:\Program
Files\Java\jdk1.6.0_17\bin;C:\j2sdk1.4.2_17\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
F libPath :
PATH=C:\usr\sap\C72\SYS\exe\jvm\NTI386\sapjvm_6.1.005\sapjvm_6\jre\bin\server;C:\usr\sap\C72\SYS\exe\jvm\NTI386\sapjv
6.1.005\sapjvm6\jre\bin;C:\usr\sap\C72\J00\j2ee\os_libs;C:\usr\sap\C72\SYS\exe\jvm\NTI386\sapjvm_6.1.005\sapjvm_6\bin;
C:\usr\sap\C72\SYS\exe\uc\NTI386;C:\Program
Files\Java\jdk1.6.0_17\bin;C:\j2sdk1.4.2_17\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
F stdout : C:\usr\sap\C72\J00\work\std_deployment.out
F stderr : C:\usr\sap\C72\J00\work\std_deployment.out
F console : no
F debugger: no
F nice : yes
F ********************************************************************************
F Process Deploy_offline started with pid 476
F ********************************************************************************
F [Thr 208] *** LOG => Process deployment started (pid 476).
F
F [Thr 208] Mon Sep 13 14:39:35 2010
F [Thr 208] *** WARNING => SfCJavaProcHandler(deployment)::onTimer: connect from deployment timed out (30000 ms) - stopping the process. [sfxxproc.hpp 1290]
F [Thr 208] *** LOG => Send SIGINT to Deploy_offline (pid 476).
F [Thr 208] *** WARNING => SfCWinProcHandle::sendSignal: failed to send signal 2 to Deploy_offline (pid 476) (rc = -1).
[sfxxlib.hpp 4472]
F [Thr 208] *** WARNING => SfCWinProcHandle::sendSignal: failed to send signal 2 to Deploy_offline (pid 476) (rc = -1).
[sfxxlib.hpp 4472]
F [Thr 208] *** WARNING => SfCWinProcHandle::sendSignal: failed to send signal 2 to Deploy_offline (pid 476) (rc = -1).
[sfxxlib.hpp 4472]
F [Thr 208] *** LOG => Process deployment stopping (pid 476).
F
F [Thr 2040] Mon Sep 13 14:45:55 2010
F [Thr 2040] *** WARNING => process Deploy_offline (pid 476) died (exit code 0). [sfntlib.hpp 835]
F [Thr 2040] *** LOG => Signal 13 SIGCHLD.
F
F [Thr 208] Mon Sep 13 14:45:55 2010
F [Thr 208] *** LOG => Process deployment died (pid 476).
F [Thr 208] *** WARNING => Node deployment failed: result 1, exit code 0. [sfxxnode.hpp 1011]
F ********************************************************************************
F Native process [snapshot] properties:
F section name : snapshot
F config file : C:\usr\sap\C72\SYS\exe\uc\NTI386\startup.properties
F node name : snapshot
F home directory : C:\usr\sap\C72\J00\work
F shutdown timeout : 122000 ms
F sf support : false
F ********************************************************************************
F ********************************************************************************
F Starting process: C:\usr\sap\C72\SYS\exe\uc\NTI386\sapcontrol.EXE
F arg[ 1] = -prot
F arg[ 2] = PIPE
F arg[ 3] = -nr
F arg[ 4] = 00
F arg[ 5] = -function
F arg[ 6] = CreateSnapshot
F arg[ 7] = Servercrash
F arg[ 8] = postmortem?node=deployment&exitcode=0
F arg[ 9] = 1
F arg[10] = 10000
F arg[11] = ""
F arg[12] = ""
F arg[13] = DEFAULT
F env : NODNSSAPTRANSHOST=1
F exePath : PATH=C:\usr\sap\C72\SYS\exe\uc\NTI386;C:\Program
Files\Java\jdk1.6.0_17\bin;C:\j2sdk1.4.2_17\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
F libPath : PATH=C:\usr\sap\C72\SYS\exe\uc\NTI386;C:\Program
Files\Java\jdk1.6.0_17\bin;C:\j2sdk1.4.2_17\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
F stdout : C:\usr\sap\C72\J00\work\std_snapshot.out
F stderr : C:\usr\sap\C72\J00\work\std_snapshot.out
F console : no
F debugger: no
F nice : yes
F ********************************************************************************
F Process snapshot started with pid 2988
F ********************************************************************************
F [Thr 208] *** LOG => Process snapshot started (pid 2988).
F [Thr 208] *** LOG => Process snapshot running (pid 2988).
F
F [Thr 208] Mon Sep 13 14:46:04 2010
F [Thr 208] *** LOG => SAP Start Service (pid 1444) connected.
F [Thr 208] *** LOG => SAP Start Service (pid 1444) disconnected.
F
F [Thr 2584] Mon Sep 13 14:46:28 2010
F [Thr 2584] *** LOG => Signal 13 SIGCHLD.
F
F [Thr 208] Mon Sep 13 14:46:28 2010
F [Thr 208] *** LOG => Process snapshot stopped (pid 2988).
F [Thr 208] *** LOG => Instance state is "Deploying offline components" (STOPPING @ 0, INACTIVE).
F [Thr 208] *** LOG => Run level 1 completed.
F [Thr 208] *** LOG => Instance state is "Some processes failed" (STOPPED @ 0, INACTIVE).
I [Thr 208] MPI: dynamic quotas disabled.
I [Thr 208] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
F
F ********************************************************************************
F *** ERROR => Node 'deployment' failed with exit code 0.
F ***
F *** Please see section 'Failures in the 'deploying offline components' phase'
F *** in SAP Note 1316652 for additional information and trouble shooting advice.
F ********************************************************************************
F
F [Thr 208] *** LOG => exiting (exitcode 22002, retcode 1).
Can anyone give me a hand on that problem ? Thanks in advance for trying.
Thibault
Edited by: Thibault Schalck on Sep 13, 2010 3:16 PM
Hello
As the error is occurring with "deploying", and there should be some log files with name deploy..log and deploy..trc, under the folder of C:\usr\sap\C72\J00\work.
Please check the lastest deploy..log and deploy..trc for more info, or probably you can also paste the conents here.
And just a remind for Rafa, the SDM settings does not exist as of CE7.1.
Thanks and Best Regards
Thunder
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Thibault,
installing CE 7.2 directly into Windows7 x64 is until now impossible. A solution will be delivered by SAP until March 2011.
But you are perfectly able to install it in XPMode into Windows7x64. This works perfectly. First install XPMode and then install
VirtualPC. After that install Java 6JDKx32 and the corresponding x32 6 Java policy file. Then set the virtual RAM for XPMode to 3700 -> AllPrograms -> VirtualPC -> XPMode -> right click settings -> RAM Options. After that set the maximal swap size to 4095.
Then install CE 7.2 Server and DevelopperStudio 7.2. Don't forget to change Services -> MaxDB (fast) from manual to automatic!!!
Best regards
Axel Arnold Bangert - Herzogenrath 2010
Thibault,
As your log indicates, please check out sapnote 1316652 section 'Failures in the 'deploying offline components'. This indicates that you have to create a message.
link: https://service.sap.com/sap/support/notes/1316652
Kind regards,
Ted
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry for that bad display, I am not able to make it better.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Thibault,
You can check the mode you have the SDM (standalone/integrated).
The startup may or may not be successful based on if SDM is currently in running status in standlone mode or not.
1) Execute sdm.bat jstartup "mode=integrated"
2) Restart the j2ee engine (the SDM will start with the engine since now it is in the integrated mode).
Check if this helps.
Regards,
Rafa
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.