cancel
Showing results for 
Search instead for 
Did you mean: 

SAP NW CE-7.2 post installation issue ('bootstrap' error code-503)

PrasannaGunji
Participant
0 Kudos

Hi,

We have installed SAP NW CE-7.2 server. After installation the AS-JAVA service was automatically running. In UME, using the Master user-id and password, we created few users in the system. Also, we were able to open Content Management and NW-Adminstrator pages. But when the machine was rebooted and when we tried to run the AS-Java again from SAP Management Console it is not starting. The developer trace shows this error message: "Node 'bootstrap' failed with exit code 503". Appreciate your help. Thanks, Prasanna

-


References:

-


Dump of "dev_bootstrap" file from /usr/sap///work directory:

-


trc file: "dev_bootstrap", trc level: 1, release: "720"

-


sysno 00 sid N72 systemid 560 (PC with Windows NT) relno 7200 patchlevel 0 patchno 22 intno 20020600 make multithreaded, Unicode, optimized profile D:\usr\sap\N72\SYS\profile\N72_J00_dell0908l-06 pid 3324 * * ACTIVE TRACE LEVEL 1 * ACTIVE TRACE COMPONENTS All, egi * Fri Jun 18 17:11:23 2010 * * trace logging activated, max size = 52428800 bytes, 2 versions * arguments : arg[ 0] : D:\usr\sap\N72\SYS\exe\uc\NTI386\jstart.EXE arg[ 1] : -appTrc arg[ 2] : -nodeId=0 arg[ 3] : pf=D:\usr\sap\N72\SYS\profile\N72_J00_dell0908l-06 arg[ 4] : -hostvm arg[ 5] : -nodeName=bootstrap arg[ 6] : -file=D:\usr\sap\N72\SYS\exe\uc\NTI386\startup.properties arg[ 7] : -jvmFile=D:\usr\sap\N72\J00\work\jstart.jvm arg[ 8] : -traceFile=D:\usr\sap\N72\J00\work\dev_bootstrap arg[ 9] : -javaOutFile=D:\usr\sap\N72\J00\work\jvm_bootstrap.out F F Fri Jun 18 17:11:23 2010 F ******************************************************************************** F Java environment properties F root directory : D:\usr\sap\N72\SYS\exe\jvm\NTI386\sapjvm_6.1.007/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.007 F jvm library name : jvm.dll F library path : D:\usr\sap\N72\SYS\exe\jvm\NTI386\sapjvm_6.1.007\sapjvm_6\jre\bin\server;D:\usr\sap\N72\SYS\exe\jvm\NTI386\sapjvm_6.1.007\sapjvm_6\jre\bin F executable path : D:\usr\sap\N72\SYS\exe\jvm\NTI386\sapjvm_6.1.007\sapjvm_6\bin F SAP extensions : available F ******************************************************************************** I [Thr 3432] MtxInit: 10000 0 2 M [Thr 3432] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048) M [Thr 3432] CCMS: Parameter "system/type" set to value: J2EE M [Thr 3432] CCMS: AlInitGlobals : alert/use_sema_lock = TRUE. M [Thr 3432] CCMS: Initalized shared memory of size 60000000 for monitoring segment. M [Thr 3432] CCMS: Checking Downtime Configuration of Monitoring Segment. M [Thr 3432] CCMS: AlMsUpload called by wp 1004. M [Thr 3432] CCMS: AlMsUpload successful for D:\usr\sap\N72\J00\log\ALMTTREE.DAT (281 MTEs). M [Thr 3432] CCMS: CCMS Monitoring Initialization finished, rc=0. F F Fri Jun 18 17:11:23 2010 F ******************************************************************************** F SAP Java VM arguments: F arg[ 0] = vfprintf F arg[ 1] = abort F arg[ 2] = exit F arg[ 3] = -XmonGcCallback F arg[ 4] = -XdebugStateChangeCallback F arg[ 5] = -DSAPJStartVersion=720, patch 24, changelist 1110390, NTintel, optU (Nov 10 2009, 00:45:29) F arg[ 6] = -verbose:gc F arg[ 7] = -XX:+HeapDumpOnOutOfMemoryError F arg[ 8] = -DSAPSTARTUP=1 F arg[ 9] = -DSAPSYSTEM=00 F arg[10] = -DSAPSYSTEMNAME=N72 F arg[11] = -DSAPMYNAME=dell0908l-06_N72_00 F arg[12] = -DSAPDBHOST=dell0908l-06 F arg[13] = -DSAPINFO=N72_00_bootstrap F arg[14] = -Dj2ee.dbhost=dell0908l-06 F arg[15] = -Dsun.java.launcher=jstart F arg[16] = -Dsun.java.command=com.sap.engine.offline.OfflineToolStart com.sap.engine.bootstrap.Bootstrap ./bootstrap F arg[17] = -Djstartup.mode=JSTART F arg[18] = -Djstartup.whoami=bootstrap F arg[19] = -Djstartup.ownProcessId=3324 F arg[20] = -Djstartup.ownHardwareId=L0830831051 F arg[21] = -Dmemory.manager=512 F arg[22] = -Xmx512m F arg[23] = -Xss262144 F arg[24] = -Djstartup.debuggable=no F arg[25] = -DLoadBalanceRestricted=no F arg[26] = -Denv.class.path= F arg[27] = -Dsys.global.dir=D:\usr\sap\N72\SYS\global F arg[28] = -Dapplication.home=D:\usr\sap\N72\SYS\exe\uc\NTI386 F arg[29] = -Djava.class.path=D:\usr\sap\N72\SYS\exe\uc\NTI386\jstart71.jar;D:\usr\sap\N72\SYS\exe\jvm\NTI386\sapjvm_6.1.007\sapjvm_6\lib\jvmx.jar;D:\usr\sap\N72\SYS\exe\uc\NTI386\jre\lib\iqlib.jar;D:\usr\sap\N72\SYS\exe\jvm\NTI386\sapjvm_6.1.007\sapjvm_6\lib\tools.jar;.\bootstrap\sap.comtcbloffline_launcherimpl.jar F arg[30] = -Djava.library.path=D:\usr\sap\N72\SYS\exe\jvm\NTI386\sapjvm_6.1.007\sapjvm_6\jre\bin\server;D:\usr\sap\N72\SYS\exe\jvm\NTI386\sapjvm_6.1.007\sapjvm_6\jre\bin;D:\usr\sap\N72\J00\j2ee\os_libs;D:\usr\sap\N72\SYS\exe\jvm\NTI386\sapjvm_6.1.007\sapjvm_6\bin;D:\usr\sap\N72\SYS\exe\uc\NTI386;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem F ignore unrecognized options : no F ******************************************************************************** F F [Thr 2480] Fri Jun 18 17:11:24 2010 F [Thr 2480] *** LOG => SfCJavaVm: Java VM started. F ******************************************************************************** F Main method call: F com/sap/engine/offline/OfflineToolStart.main() F arg[ 0] = com.sap.engine.bootstrap.Bootstrap F arg[ 1] = ./bootstrap F ******************************************************************************** J J Fri Jun 18 17:11:24 2010 J : [1352] 17:11:24 ***Warning: Loadavg: Could not collect performance query data. J [GC 3072K->832K(7680K), 0.0039796 secs] J [GC 3904K->2659K(7680K), 0.0034658 secs] J [Full GC 2659K->2651K(12864K), 0.0183037 secs] J [GC 5723K->4477K(12864K), 0.0022455 secs] J [GC 7547K->6276K(14592K), 0.0027543 secs] J [GC 11062K->9067K(14592K), 0.0041178 secs] J [Full GC 9067K->6399K(21952K), 0.0182406 secs] J [GC 11199K->9521K(27136K), 0.0033979 secs] F F [Thr 2480] Fri Jun 18 17:11:25 2010 F [Thr 2480] *** LOG => State changed from 0 (Initial) to 2 (Starting framework). F [Thr 2480] *** LOG state real time: 2.640 CPU time: 0.296 sys, 2.437 usr F [Thr 2480] *** LOG total real time: 2.640 CPU time: 0.296 sys, 2.437 usr F [Thr 2480] J J Fri Jun 18 17:11:25 2010 J [GC 16369K->10382K(27520K), 0.0051733 secs] J [GC 17226K->10516K(30272K), 0.0063617 secs] J [GC 19540K->10331K(30720K), 0.0059130 secs] J J Fri Jun 18 17:11:26 2010 J [GC 19355K->10405K(32640K), 0.0052470 secs] J [GC 21093K->11038K(32832K), 0.0070040 secs] F F [Thr 2480] Fri Jun 18 17:11:26 2010 F [Thr 2480] *** LOG => State changed from 2 (Starting framework) to 5 (Stopping). F [Thr 2480] *** LOG state real time: 1.968 CPU time: 0.171 sys, 1.968 usr F [Thr 2480] *** LOG total real time: 4.609 CPU time: 0.468 sys, 4.406 usr F [Thr 2480] F F [Thr 1352] Fri Jun 18 17:11:27 2010 F [Thr 1352] *** LOG => SfCJavaVm: exit hook is called. (rc = 503) F F ******************************************************************************** F *** ERROR => Java node 'Instance_bootstrap' terminated with exit code 503. F *** F *** Please see section 'Java program exit codes' F *** in SAP Note 1316652 for additional information and trouble shooting advice. F ******************************************************************************** F F [Thr 1352] *** LOG => exiting (exitcode 503, retcode 1). M [Thr 1352] CCMS: CCMS Monitoring Cleanup finished successfully.

Accepted Solutions (0)

Answers (2)

Answers (2)

0 Kudos

Have you installed SAP NW CE 7.2 on Max DB on Windows?

Please check if the Max DB services are running. Max DB services start option is set to "manual" during installation. So, the services are not started after restart of OS.

markus_doehr2
Active Contributor
0 Kudos

Read what you posted:

> ******************************************************************************** F *** ERROR => Java node 'Instance_bootstrap' terminated with exit code 503. F *** F *** Please see section 'Java program exit codes' F *** in SAP Note 1316652 for additional information and trouble shooting advice.

Markus

PrasannaGunji
Participant
0 Kudos

Markus,

As there is no facility to upload a text file in SDN forums, I had to copy-paste the error message that I got from "Developer Trace". Due to formatting issues the message looks different when you view in SDN's web-page.

I would once again like to clarify that the error message was not at all edited. However thanks for bringing this to my notice.

- Prasanna