How to append SAP instance in SAP MMC

Hi,
We had two instances running in one host.
After a reboot one system is up and running and can be seen in MMC but the other instance niether starting nor appearing in MMC.
Can any one tell me how to append the instance in MMC with the existing up & running Instance?
Regads,
Souren

Hi,
In the properties widow select the fixed tab and add the hosttname and the instance number and then press ADD.
The SAP instance may not be listed in the MMC if the sapservices fails to start due to logon failure. Please check whether the services SAP<SID>_<Instance Number> has been started and if not please check whether the password for the user .\sapservice<SID> is valid.
Regards,
Varadhu

Similar Messages

  • How to make database instances available in the SAP MMC

    Hello,
    I have been trying to figure out on how to make a database instance, which I installed on the MSSQL Server, available in the SAP Management Console in order to start the instance. I am able to view the instance over the Enterprise Manager of the MSSQL Sever, but I cannot start it from there (this is only possible from the SAP MMC). I have the SAP MMC installed on my computer, but just cannot figure out on how to control the instance from there because I cannot see it.
    I hope someone can help me on this matter!
    Thanks....
    Katharina

    Hello Katharina,
    Run SAP MMC and right-click to SAP R/3 Systems.
    Choose properties and go to Fixed tab.
    In 'System' field enter Your SID (e.g. EBP)
    In 'Instance' field enter hostname<space>instance number (e.g. epb01 10) Remember, there is space between ebp01 and 10.
    Click on 'Add' button and then OK.
    Best Regards,
    Marcin Gajewski

  • Instance Status Yellow on SAP MMC Console

    Dear Experts,
    We are installing NW 7.0 dialog instance on Windowsx64 bit platform, Central instance is running on Aix64 bit,
    NW 7.0 Java add-in has installed on Central instance,
    I want to start only abap instance on new windows application server, i set rdisp/j2ee_start parameter to "0",
    Now java process do not start but SAP mmc console status is yellow because of it, disp+dowk process message is J2EE status info unavaliable,
    How can unistall Java instance from newly instaled application server ?
    Best Regards

    Hi,
    Regarding the MMC display "J2EE status info unavailable", as you don't want a dual stack remove the entry icm/HTTP/j2ee_0 from the instance profile and set the parameter 'is/HTTP/default_root_hdl = abap'.
    Please reboot your system (bounce OS) to see if this helps.
    If this does not help please try this.
    1. Stop the SAP service
    2. Open a command prompt
    3. Go to usr\sap\<SID>\...\exe\run
    4. call 'sapstartsrv.exe -t' from the command line
    5. Confirm the dialog window
    6. Start the service again
    Best Regards
    Niraj

  • How to divide SAPS when having two instances on same host

    Hello
    I wander how to divide SAPS when having two instances on same host. By looking at st06?
    Thank you in advance

    Yes SAPS is nothing but the CPU power used by the SAP systems. SO if you have 2 SAP systems stacked on the same server, check the CPU utilization over a period of 7 - 10 days, average out & that should give you a fair bit of idea.
    - Regards, Dibya

  • SAP MMC problem on database instance

    Hi,
       We successfully installed the solution manager ehp1 on distributed environmnet(windows with sql) and also iam able to login SAP,but iam unable to see the system on SAP MMC on database instance.
    Thanku

    Can you please download and install new SAP MMC.
    You can manually configure it to see all systems you installed..
    But SAP MMC will not automatically install on DB instances.
    Yogesh

  • Problem with SAP MMC unable to start

    Hi Experts,
    When I open the MMC console a popup comes with a message
    At least one service or driver failed during system start up. Use Event Viewer to examine the event log for details
    And then I see that one node is missing under central instance node.
    I checked event viewer
    Application >Error>Description - Faulting application sapstartsrv.exe version 0.0.0.0. faulting module unknown, version 0.0.0.0. fault address 0X00000000
    System>Error->Description -  The SAPDM0_01 service terminated unexpectedly. It has done this 2 time(s).
    I am unable to start the server and login, how to fix this ??
    Many Thanks,
    Vikky

    Found the solution in this thread
    SAP MMC Server Node Missing
    but still dispatcher not starting...
    opening a new thread
    Thanks,
    Vikky

  • Update SAP MMC as prerrequisite for EHP for ERP Installation

    Hello experts,
    I have operative system windows x64, AN ERP 6.0  with Netweaver 7.0
    Following the ehpi installation guide to up the ERP to EHP5, i read this text in prerrequisites!
    Meeting the Operating System-Specific Requirements Procedure: Windows
    You need to install a new SAP MMC package (sapmmc<Platform>.msi) on all application servers. The package is available for download as SAPMMCMSI_<nr>.SAR file on SAP Service Marketplace at http://service.sap.com/swdc   Download Support Packages and Patches Entry by Application Group Additional Components  SAP Kernel SAP KERNEL 64-BIT UNICODE  SAP KERNEL <rel> 64-BIT UNICODE  Windows Server on <Platform> 64bit#  Database independent.
    , But, in that route  I don´t find the file SAPMMCMSI_.SAR
    I search in In all the marketplace and the only SSAPMM package that i find was  this:
    000002      View content info Add to download basket   SAPMMCMSI_127-10004213.SAR   SAPMMCMSI
           Support Package SAP KERNEL 7.10 64-BIT UNICODE Windows Server on x64 64bit #Database in
    But  as i say i have kernel 7.00 and this is for kernel 7.10...
    THen the questions are:
    1. How can i check my current release of sapmmc
    and
    2. How can i fulfill the requirement of update  sapmmc to latest version?  can I apply the 7.10 SAPMMCMSI?

    No sap note, by in this sdn page, you can find the downward thing...
    SAP MMC Snap-In [original link is broken]
    and additionally i see that after 7.10 the download name change and is no more SAPMMCMSI is sapmmc_7-20005871.msi
    you can obtain it in :
    SAP MMC 7.20
    https://websmp110.sap-ag.de/~form/handler?_APP=00200682500000001943&_EVENT=DISPHIER&HEADER=N&FUNCTIONBAR=N&EVENT=TREE&TMPL=01200314690200011561&V=MAINT
    And FInally, remember that is downward compatible , then you have install SAP MMC 7.20 in a SAP 7.0 netweaver system.

  • SAP MMC  disk + work Stop(Ecc6( Adap+jav),win 2003 -32 bit , oracle-10.2)

    Hi Friends,
    I hope somebody can help.
    I have an Ides Ecc6(java+adap) installation on Oracle 10..*.os win 2003 32 bit
    Then I try to start the System in mmc the dispatcher is stopping (first yeloow then grey) and no error  messages
    when is see sys log in SAP MMC
    erro: SAP-Basis System: Initialization           DB-Connect Failed, Return Code  000256
    when i try R3trans-d
    Log:
    C:\Documents and Settings\accadm>r3trans -d
    This is r3trans version 6.14 (release 700 - 15.06.07 - 15:50:00)
    unicode enabled version
    2EETW000 sap_dext called with msgnr "2":
    2EETW000 -
    db call info -
    2EETW000 function:   db_ntab
    2EETW000 fcode:      NT_RDTDESCR
    2EETW000 tabname:    TADIR
    2EETW000 len (char): 5
    2EETW000 key:        TADIR
    2EETW000 retcode:    2
    r3trans finished (0012)
    Dev_wo.lo file
    trc file: "dev_w0", trc level: 1, release: "700"
    ACTIVE TRACE LEVEL           1
    ACTIVE TRACE COMPONENTS      all, MJ
    B 
    B Thu Apr 16 14:07:43 2009
    B  create_con (con_name=R/3)
    B  Loading DB library 'D:\usr\sap\ACC\DVEBMGS00\exe\dboraslib.dll' ...
    B  Library 'D:\usr\sap\ACC\DVEBMGS00\exe\dboraslib.dll' loaded
    B  Version of 'D:\usr\sap\ACC\DVEBMGS00\exe\dboraslib.dll' is "700.08", patchlevel (0.107)
    B  New connection 0 created
    M sysno      00
    M sid        ACC
    M systemid   560 (PC with Windows NT)
    M relno      7000
    M patchlevel 0
    M patchno    111
    M intno      20050900
    M make:      multithreaded, Unicode, optimized
    M pid        3724
    M
    M  kernel runs with dp version 229000(ext=109000) (@(#) DPLIB-INT-VERSION-229000-UC)
    M  length of sys_adm_ext is 576 bytes
    M  ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 3724) [dpxxdisp.c   1301]
    I  MtxInit: 30000 0 0
    M  DpSysAdmExtCreate: ABAP is active
    M  DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
    M 
    M Thu Apr 16 14:07:44 2009
    M  DpShMCreate: sizeof(wp_adm)          18672     (1436)
    M  DpShMCreate: sizeof(tm_adm)          4232256     (21056)
    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  DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
    M  DpShMCreate: sizeof(slock_adm)          0     (96)
    M  DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
    M  DpShMCreate: sizeof(file_adm)          0     (72)
    M  DpShMCreate: sizeof(vmc_adm)          0     (1536)
    M  DpShMCreate: sizeof(wall_adm)          (38456/34360/64/184)
    M  DpShMCreate: sizeof(gw_adm)     48
    M  DpShMCreate: SHM_DP_ADM_KEY          (addr: 06810040, size: 4892312)
    M  DpShMCreate: allocated sys_adm at 06810040
    M  DpShMCreate: allocated wp_adm at 06812090
    M  DpShMCreate: allocated tm_adm_list at 06816980
    M  DpShMCreate: allocated tm_adm at 068169B0
    M  DpShMCreate: allocated wp_ca_adm at 06C1FDF0
    M  DpShMCreate: allocated appc_ca_adm at 06C25BB0
    M  DpShMCreate: allocated comm_adm at 06C27AF0
    M  DpShMCreate: system runs without slock table
    M  DpShMCreate: system runs without file table
    M  DpShMCreate: allocated vmc_adm_list at 06CA89B0
    M  DpShMCreate: allocated gw_adm at 06CA89F0
    M  DpShMCreate: system runs without vmc_adm
    M  DpShMCreate: allocated ca_info at 06CA8A20
    M  DpShMCreate: allocated wall_adm at 06CA8A28
    X  EmInit: MmSetImplementation( 2 ).
    X  MM global diagnostic options set: 0
    X  <ES> client 0 initializing ....
    X  Using implementation view
    X  <EsNT> Using memory model view.
    M  <EsNT> Memory Reset disabled as NT default
    X  ES initialized.
    M  ThInit: running on host oiam
    M 
    M Thu Apr 16 14:07:46 2009
    M  calling db_connect ...
    C  Prepending D:\usr\sap\ACC\DVEBMGS00\exe to Path.
    C  Oracle Client Version: '10.2.0.1.0'
    C  Client NLS settings: AMERICAN_AMERICA.UTF8
    C  Logon as OPS$-user to get SAPSR3's password
    C  Connecting as /@ACC on connection 0 (nls_hdl 0) ... (dbsl 700 250407)
    C  Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
    C    0 UTF8                                                      1   06DF1478   06DF6A14   06DF629C
    C  Attaching to DB Server ACC (con_hdl=0,svchp=06DF61E8,srvhp=06E07DD4)
    C  Starting user session (con_hdl=0,svchp=06DF61E8,srvhp=06E07DD4,usrhp=06E53768)
    C  Now '/@ACC' is connected (con_hdl 0, nls_hdl 0).
    C  Got SAPSR3's password from OPS$-user
    C  Disconnecting from connection 0 ...
    C  Closing user session (con_hdl=0,svchp=06DF61E8,usrhp=06E53768)
    C  Now I'm disconnected from ORACLE
    C  Connecting as SAPSR3/<pwd>@ACC on connection 0 (nls_hdl 0) ... (dbsl 700 250407)
    C  Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
    C    0 UTF8                                                      1   06DF1478   06DF6A14   06DF629C
    C  Starting user session (con_hdl=0,svchp=06DF61E8,srvhp=06E07DD4,usrhp=06E53768)
    C  Now 'SAPSR3/<pwd>@ACC' is connected (con_hdl 0, nls_hdl 0).
    C  Database NLS settings: AMERICAN_AMERICA.UTF8
    C  DB instance ACC is running on OIAM with ORACLE version 10.2.0.1.0 since APR 16, 2009, 14:07:26
    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 20090416 140746 OIAM           
    C  OCI-call failed with -1=OCI_ERROR
    C     SQL error 376: 'ORA-00376: file 25 cannot be read at this time
    C  ORA-01110: data file 25: 'D:\ORACLE\ACC\SAPDATA1\SR3_22\SR3.DATA22''
    C  *** ERROR => Error 376 in stmt_fetch() from oci_execute_stmt(), orpc=0
    [dbsloci.c    12714]
    C  *** ERROR => ORA-376 occurred when executing SQL stmt (parse error offset=0)
    [dbsloci.c    12733]
    C  sc_p=06D44E98,no=0,idc_p=00000000,con=0,act=1,slen=26,smax=256,#vars=0,stmt=06E1C138,table=SVERS                        
    C  SELECT VERSION FROM SVERS ;
    C  sc_p=06D44E98,no=0,idc_p=00000000,con=0,act=1,slen=26,smax=256,#vars=0,stmt=06E1C138,table=SVERS                        
    C  prep=0,lit=0,nsql=0,lobret=0,#exec=1,dbcnt=0,upsh_p=00000000,ocistmth_p=06E0FC68
    C  IN : cols=0,rmax=1,xcnt=0,rpc=0,rowi=0,rtot=0,upto=-1,rsize=0,vmax=0,bound=0,iobuf_p=00000000,vda_p=00000000
    C       lobs=0,lmax=0,lpcnt=0,larr=00000000,lcurr_p=00000000,rret=0
    C  OUT: cols=1,rmax=1,xcnt=1,rpc=0,rowi=0,rtot=0,upto=-1,rsize=144,vmax=32,bound=1,iobuf_p=003F2DC8,vda_p=06E1C3A8
    C       lobs=0,lmax=0,lpcnt=0,larr=00000000,lcurr_p=00000000,rret=0
    C  SELECT VERSION FROM SVERS ;
    B  ***LOG BZA=> table SVERS      does not exist on database            [dblink#3 @ 1299] [dblink  1299 ]
    M  ***LOG R19=> ThInit, db_connect ( DB-Connect 004096) [thxxhead.c   1426]
    M  in_ThErrHandle: 1
    M  *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   10283]
    M 
    M  Info for wp 0
    M 
    M    stat = WP_RUN
    M    waiting_for = NO_WAITING
    M    reqtype = DP_RQ_DIAWP
    M    act_reqtype = NO_REQTYPE
    M    rq_info = 0
    M    tid = -1
    M    mode = 255
    M    len = -1
    M    rq_id = 65535
    M    rq_source =
    M    last_tid = 0
    M    last_mode = 0
    M    semaphore = 0
    M    act_cs_count = 0
    M    csTrack = 0
    M    csTrackRwExcl = 0
    M    csTrackRwShrd = 0
    M    control_flag = 0
    M    int_checked_resource(RFC) = 0
    M    ext_checked_resource(RFC) = 0
    M    int_checked_resource(HTTP) = 0
    M    ext_checked_resource(HTTP) = 0
    M    report = >                                        <
    M    action = 0
    M    tab_name = >                              <
    M    req.vm = no VM
    M    attachedVm = no VM
    M 
    M  *****************************************************************************
    M  *
    M  *  LOCATION    SAP-Server oiam_ACC_00 on host oiam (wp 0)
    M  *  ERROR       ThInit: db_connect
    M  *
    M  *  TIME        Thu Apr 16 14:07:46 2009
    M  *  RELEASE     700
    M  *  COMPONENT   Taskhandler
    M  *  VERSION     1
    M  *  RC          13
    M  *  MODULE      thxxhead.c
    M  *  LINE        10486
    M  *  COUNTER     1
    M  *
    M  *****************************************************************************
    M 
    M  PfStatDisconnect: disconnect statistics
    M  Entering TH_CALLHOOKS
    M  ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
    M  *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c   720]
    M  *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c  260]
    M  Entering ThSetStatError
    M  ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
    M  Entering ThReadDetachMode
    M  call ThrShutDown (1)...
    M  ***LOG Q02=> wp_halt, WPStop (Workproc 0 3724) [dpnttool.c   327]
    thanks for support
    keshava

    Hi Rohit
    trc file: "dev_disp", trc level: 1, release: "700"
    sysno      00
    sid        ACC
    systemid   560 (PC with Windows NT)
    relno      7000
    patchlevel 0
    patchno    111
    intno      20050900
    make:      multithreaded, Unicode, optimized
    pid        3452
    Fri Apr 17 14:17:27 2009
    kernel runs with dp version 229000(ext=109000) (@(#) DPLIB-INT-VERSION-229000-UC)
    length of sys_adm_ext is 576 bytes
    SWITCH TRC-HIDE on ***
    ***LOG Q00=> DpSapEnvInit, DPStart (00 3452) [dpxxdisp.c   1239]
         shared lib "dw_xml.dll" version 111 successfully loaded
         shared lib "dw_xtc.dll" version 111 successfully loaded
         shared lib "dw_stl.dll" version 111 successfully loaded
         shared lib "dw_gui.dll" version 111 successfully loaded
         shared lib "dw_mdm.dll" version 111 successfully loaded
    rdisp/softcancel_sequence :  -> 0,5,-1
    use internal message server connection to port 3900
    Fri Apr 17 14:17:32 2009
    WARNING => DpNetCheck: NiHostToAddr(www.doesnotexist0225.qqq.nxst) took 5 seconds
    Fri Apr 17 14:17:36 2009
    WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 4 seconds
    ***LOG GZZ=> 2 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c  5361]
    MtxInit: 30000 0 0
    DpSysAdmExtInit: ABAP is active
    DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
    DpIPCInit2: start server >oiam_ACC_00                             <
    DpShMCreate: sizeof(wp_adm)          18672     (1436)
    DpShMCreate: sizeof(tm_adm)          4232256     (21056)
    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)
    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     (1536)
    DpShMCreate: sizeof(wall_adm)          (38456/34360/64/184)
    DpShMCreate: sizeof(gw_adm)     48
    DpShMCreate: SHM_DP_ADM_KEY          (addr: 06810040, size: 4892312)
    DpShMCreate: allocated sys_adm at 06810040
    DpShMCreate: allocated wp_adm at 06812090
    DpShMCreate: allocated tm_adm_list at 06816980
    DpShMCreate: allocated tm_adm at 068169B0
    DpShMCreate: allocated wp_ca_adm at 06C1FDF0
    DpShMCreate: allocated appc_ca_adm at 06C25BB0
    DpShMCreate: allocated comm_adm at 06C27AF0
    DpShMCreate: system runs without slock table
    DpShMCreate: system runs without file table
    DpShMCreate: allocated vmc_adm_list at 06CA89B0
    DpShMCreate: allocated gw_adm at 06CA89F0
    DpShMCreate: system runs without vmc_adm
    DpShMCreate: allocated ca_info at 06CA8A20
    DpShMCreate: allocated wall_adm at 06CA8A28
    MBUF state OFF
    DpCommInitTable: init table for 500 entries
    Fri Apr 17 14:17:37 2009
    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.
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 3652
      argv[0] = D:\usr\sap\ACC\DVEBMGS00\exe\jcontrol.EXE
      argv[1] = D:\usr\sap\ACC\DVEBMGS00\exe\jcontrol.EXE
      argv[2] = pf=D:\usr\sap\ACC\SYS\profile\ACC_DVEBMGS00_oiam
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=1045
      argv[5] = -DSAPSYSTEM=00
      argv[6] = -DSAPSYSTEMNAME=ACC
      argv[7] = -DSAPMYNAME=oiam_ACC_00
      argv[8] = -DSAPPROFILE=D:\usr\sap\ACC\SYS\profile\ACC_DVEBMGS00_oiam
      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   1629]
    ***LOG Q0K=> DpMsAttach, mscon ( oiam) [dpxxdisp.c   11753]
    DpStartStopMsg: send start message (myname is >oiam_ACC_00                             <)
    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 111
    Release check o.K.
    Fri Apr 17 14:17:38 2009
    DpJ2eeLogin: j2ee state = CONNECTED
    Fri Apr 17 14:18:25 2009
    MBUF state ACTIVE
    DpModState: change server state from STARTING to ACTIVE
    Fri Apr 17 14:19:53 2009
    J2EE server info
      start = TRUE
      state = ACTIVE
      pid = 3652
      http = 50000
      https = 50001
      load balance = 1
      start_lazy = 0
      start_control = SAP J2EE startup framework

  • SAP MMC Java with Solution Manager

    Dear experts,
    i have installed a SAP Solution Manager 7.0 in WAS ABAP + JAVA in Windows Server 2003 SR2 Enterprise Edition 64 bits + MS SQL 2005.
    I try to connect to the SAP MMC in Java (http://localhost:52113/) but i have a message error:
    Your browser is completely ignoring the <APPLET> tag!
    I already installed the jdk for SAP and x64 (J2sdk version 1.4.2.17 version x64) on http://java.sun.com/j2se/1.4.2/SAPsite/download.html
    How can i access?
    Thank you in advance
    Best regards.
    Pascal.

    Hello,
    i found my error: i have installed a jdk but didn't a jre...
    Sorry for this thread.
    Thank you.
    Pascal.

  • SDM not starting up in SAP MMC

    Hi There,
    I have PI7 installed on win 2003 server with MS Sql server database. Since yesterday after I rebooted the system for some reason my SDM server is not running. I can see its status "stopped" in SAP MMC. Even i am forcely restarting it but its stopping again. Below are the trace findings .
    *********sdmlog file*************
    Jan 3, 2009 10:25:41 AM Info: = Starting to execute
    command 'server' =
    Jan 3, 2009 10:25:41 AM Info:
    ============================================
    Jan 3, 2009 10:25:41 AM Info: Starting SDM - Software Deployment
    Manager...
    Jan 3, 2009 10:25:41 AM Info: tc/SL/SDM/SDM/sap.com/SAP
    AG/7.0016.20080423161536.0000
    Jan 3, 2009 10:25:43 AM Info: SDM operation mode successfully set to:
    Standalone
    Jan 3, 2009 10:25:43 AM Info: JStartupFramework is requesting to start
    the SDM Server.
    Jan 3, 2009 10:25:43 AM Info: SDM is currently detached from
    JStartupFramework. Forward this information to the JStartupFramekwork
    (disable SDM process).
    Jan 3, 2009 10:25:43 AM Info: disabling SDM Process with
    JStartupFramework
    Jan 3, 2009 10:25:43 AM Info: disabled SDM Process with
    JStartupFramework
    Jan 3, 2009 10:25:43 AM Info: Waiting up to 60 seconds for shutdown by
    JControl before exiting myself.
    Jan 3, 2009 10:25:43 AM Info: ====================================
    Jan 3, 2009 10:25:43 AM Info: JControl is shutting SDM Server down
    Jan 3, 2009 10:25:43 AM Info: ====================================
    Jan 3, 2009 10:25:43 AM Info: Server finished sending back the answer
    of the ShutdownRequest.
    Jan 3, 2009 10:25:43 AM Info: Shutting dispatcher down
    *******dev_sdm*********
    [Thr 7056] JHVM_RedirectStreams: redirect JVM output into file
    D:\usr\sap\SXD\DVEBMGS00\work\jvm_sdm.out
    [Thr 9212] Sat Jan 03 10:41:38 2009
    [Thr 9212] JLaunchRequestFunc: receive command:17, argument:0 from
    pid:8868
    [Thr 9212] JLaunchIShutdownInvoke: set shutdown interval
    (stop:1230968498/end:1230968618/TO:120)
    [Thr 9212] JLaunchProcessCommand: Invoke VM Shutdown
    [Thr 9212] JHVM_FrameworkShutdownDirect: invoke direct shutdown
    [Thr 9212] JHVM_RegisterNatives: registering methods in
    com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 9212] JHVM_NativeSetState: set process state to 5
    [Thr 9212] JLaunchISetState: change state from [Initial (0)] to
    [Stopping (5)]
    [Thr 9480] JLaunchIExitJava: exit hook is called (rc = 0)
    [Thr 9480] JsfCloseShm: JsfCloseShm() -> 0
    [Thr 9480] JLaunchCloseProgram: good bye (exitcode = 0)
    [Thr 8284] [Node: SDM] java home is set by profile parameter
    Java Home: C:\j2sdk1.4.2_14-x64
    [Thr 8284] SlicGetHwid called
    [Thr 8284] SlicGetHwId: sysname: Windows NT nodename: SAPXIDEV machine:
    2x AMD64 Level 6 (Mod 15 Step 6)
    [Thr 8284] release: 5.2 version: 3790 Service Pack 2
    [Thr 8284] SlicGetHwId: ID >S-21404795425364284499--1598442986-
    SAPXIDEV<
    [Thr 8284] SlicGetHwId: CUSTOMER KEY: >L0724656190<
    [Thr 8284] JStartupICheckFrameworkPackage: can't find framework package
    D:\usr\sap\SXD\DVEBMGS00\exe\jvmx.jar
    I CHECKED THIS FILE DOESN'T EXISTS IN THE ABOVE PATH AND I HAVE NOT
    REMOVED IT. HOW TO BRING BACK THIS FILE?
    **********JVM_SDM (out file) trace file*************
    Starting SDM - Software Deployment Manager...
    tc/SL/SDM/SDM/sap.com/SAP AG/7.0016.20080423161536.0000
    JStartupFramework is requesting to start the SDM Server.
    SDM is currently detached from JStartupFramework. Forward this
    information to the JStartupFramekwork (disable SDM process).
    Waiting up to 60 seconds for shutdown by JControl before exiting myself.JControl is shutting SDM Server down
    Asynchroneously processing shutdown request.
    Server finished sending back the answer of the ShutdownRequest.
    Shutting dispatcher down
    Bye, bye!
    I gave the command :
    D:\>sdm jstartup sdmhome=D:\usr\sap\SXD\DVEBMGS00\SDM\program\
    mode=integrated
    and
    D:\>sdm jstartup sdmhome="D:\usr\sap\SXD\DVEBMGS00\SDM\program"
    mode="integrated"
    BUT ITS GIVING "Syntax error. Return code:12"
    Could you please help me on this ASAP. My ABAP and java server is running fine.
    Just I want my SDM server to run so that my complete system backs to normal.
    Thanks,
    Naj

    Hi,
    See this thread SDM Error when Deploying Web Dynpro Application
    Try parameter as "mode=integrated" attention for double quotes on all parameter.
    Best regards

  • System is not visible in SAP MMC

    Hellu Guys ,
    System  is up ad running fine ,but it is not visible in SAP MMC .
    Kindly let me know that how to activate in MMC .

    You cam add snapshot in MMC , check in menu
    File --> Add/Remove Snap-in -->Add --> SAP System
    Provide detail as required.
    Regards,

  • Jstart.exe process in sap mmc is not getting started

    Hi,
    The jstart.exe process of sap mmc (management console/server) is not getting started.
    The status for this process is "starting the processes". Need help!
    The developer trace is as follows :
    trc file: "dev_jstart.7668", trc level: 1, release: "720"
    trc file: "dev_jstart.new", trc level: 1, release: "720"
    sysno      02
    sid        SV1
    systemid   562 (PC with Windows NT)
    relno      7200
    patchlevel 0
    patchno    63
    intno      20020600
    make       multithreaded, Unicode, 64 bit, optimized
    profile    \\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
    pid        7668
    *  ACTIVE TRACE LEVEL           1
    *  ACTIVE TRACE COMPONENTS      All, egi
    Mon Oct 08 10:03:13 2012
    *  trace logging activated, max size = 52428800 bytes, 2 versions
    arguments :
      arg[ 0] : C:\usr\sap\SV1\J02\exe\jstart.EXE
      arg[ 1] : pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
    F Mon Oct 08 10:03:13 2012
    F  ********************************************************************************
    F  Java environment properties (C:\usr\sap\SV1\J02\work\jstart.jvm)
    F    root directory    : C:\usr\sap\SV1\J02\exe\sapjvm_6
    F    vendor            : SAP AG
    F    version           : 1.6.0_17
    F    cpu               : amd64
    F    java vm type      : server
    F    java vm version   : 6.1.018
    F    jvm library name  : jvm.dll
    F    library path      : C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin
    F    executable path   : C:\usr\sap\SV1\J02\exe\sapjvm_6\bin
    F  ********************************************************************************
    F    SAP extensions    : available
    F  ********************************************************************************
    I  [Thr 7652] MtxInit: 30002 0 2
    trc file: "dev_jstart", trc level: 1, release: "720"
    *  ACTIVE TRACE LEVEL           1
    *  ACTIVE TRACE COMPONENTS      All, egi
    F 
    F [Thr 7652] Mon Oct 08 10:03:14 2012
    F  [Thr 7652] *** LOG => connected to Enqueue Server.
    F  [Thr 7652] *** LOG => connected to Message Server.
    F  [Thr 7652] *** LOG => Starting run level 1.
    F  ********************************************************************************
    F  Java process [deployment] properties:
    F    section name     : deployment
    F    config file      : C:\usr\sap\SV1\J02\exe\startup.properties
    F    node name        : Deploy_offline
    F    home directory   : C:\usr\sap\SV1\J02\j2ee\cluster
    F    shutdown timeout : 136000 ms
    F    exit timeout     : 7000 ms
    F    debuggable       : false
    F    debugger active  : false
    F  ********************************************************************************
    F  [Thr 7652] *** LOG => Instance state is "Deploying offline components" (STARTING @ 0, INACTIVE).
    F  [Thr 7652] *** LOG => Starting nodes: runlevel 1.
    F 
    F Mon Oct 08 10:03:15 2012
    F  ********************************************************************************
    F  Starting process: C:\usr\sap\SV1\J02\exe\jstart.EXE
    F    arg[ 1] = -nodeId=0
    F    arg[ 2] = pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
    F    arg[ 3] = -hostvm
    F    arg[ 4] = -nodeName=deployment
    F    arg[ 5] = -file=C:\usr\sap\SV1\J02\exe\startup.properties
    F    arg[ 6] = -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
    F    arg[ 7] = -traceFile=C:\usr\sap\SV1\J02\work\dev_deployment
    F    arg[ 8] = -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_deployment.out
    F    env   : NODNSSAPTRANSHOST=1
    F  exePath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F  libPath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F  stdout  : C:\usr\sap\SV1\J02\work\std_deployment.out
    F  stderr  : C:\usr\sap\SV1\J02\work\std_deployment.out
    F  console : no
    F  debugger: no
    F  nice    : no
    F  ********************************************************************************
    F  Process Deploy_offline started with pid 7968
    F  ********************************************************************************
    F  [Thr 7652] *** LOG => Process deployment started (pid 7968).
    F 
    F [Thr 7652] Mon Oct 08 10:03:19 2012
    F  [Thr 7652] *** LOG => Process deployment stopping (pid 7968).
    F 
    F [Thr 6972] Mon Oct 08 10:03:19 2012
    F  [Thr 6972] *** LOG => Signal 13 SIGCHLD.
    F  [Thr 7652] *** LOG => Process deployment stopped (pid 7968).
    F  [Thr 7652] *** LOG => Instance state is "Deploying offline components" (STOPPING @ 0, INACTIVE).
    F  [Thr 7652] *** LOG => Run level 1 completed.
    F  [Thr 7652] *** LOG => Starting run level 2.
    F  ********************************************************************************
    F  Java process [bootstrap] properties:
    F    section name     : bootstrap
    F    config file      : C:\usr\sap\SV1\J02\exe\startup.properties
    F    node name        : Instance_bootstrap
    F    home directory   : C:\usr\sap\SV1\J02\j2ee\cluster
    F    shutdown timeout : 136000 ms
    F    exit timeout     : 7000 ms
    F    debuggable       : false
    F    debugger active  : false
    F  ********************************************************************************
    F  [Thr 7652] *** LOG => Instance state is "Synchronizing binaries" (STARTING @ 0, INACTIVE).
    F  [Thr 7652] *** LOG => Starting nodes: runlevel 2.
    F 
    F Mon Oct 08 10:03:20 2012
    F  ********************************************************************************
    F  Starting process: C:\usr\sap\SV1\J02\exe\jstart.EXE
    F    arg[ 1] = -nodeId=0
    F    arg[ 2] = pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
    F    arg[ 3] = -hostvm
    F    arg[ 4] = -nodeName=bootstrap
    F    arg[ 5] = -file=C:\usr\sap\SV1\J02\exe\startup.properties
    F    arg[ 6] = -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
    F    arg[ 7] = -traceFile=C:\usr\sap\SV1\J02\work\dev_bootstrap
    F    arg[ 8] = -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_bootstrap.out
    F    env   : NODNSSAPTRANSHOST=1
    F  exePath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F  libPath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F  stdout  : C:\usr\sap\SV1\J02\work\std_bootstrap.out
    F  stderr  : C:\usr\sap\SV1\J02\work\std_bootstrap.out
    F  console : no
    F  debugger: no
    F  nice    : no
    F  ********************************************************************************
    F  Process Instance_bootstrap started with pid 7952
    F  ********************************************************************************
    F  [Thr 7652] *** LOG => Process bootstrap started (pid 7952).
    F 
    F [Thr 7652] Mon Oct 08 10:03:47 2012
    F  [Thr 7652] *** LOG => Process bootstrap running (pid 7952).
    F  [Thr 7652] *** LOG => Instance state is "Synchronizing binaries" (RUNNING @ 0, INACTIVE).
    F 
    F [Thr 7652] Mon Oct 08 10:04:10 2012
    F  [Thr 7652] *** LOG => Process bootstrap stopping (pid 7952).
    F 
    F [Thr 4436] Mon Oct 08 10:04:10 2012
    F  [Thr 4436] *** LOG => Signal 13 SIGCHLD.
    F  [Thr 7652] *** LOG => Process bootstrap stopped (pid 7952).
    F  [Thr 7652] *** LOG => Instance state is "Synchronizing binaries" (STOPPING @ 0, INACTIVE).
    F  [Thr 7652] *** LOG => Run level 2 completed.
    F  [Thr 7652] *** LOG => Starting run level 3.
    F  ********************************************************************************
    F  Java process [debugproxy] properties:
    F    section name     : debugproxy
    F    config file      : C:\usr\sap\SV1\J02\exe\dproxy.properties
    F    node name        : Debug_Proxy
    F    home directory   : C:\usr\sap\SV1\J02/j2ee/rdbg.proxy
    F    shutdown timeout : 136000 ms
    F    exit timeout     : 7000 ms
    F    debuggable       : false
    F    debugger active  : false
    F  ********************************************************************************
    F  ********************************************************************************
    F  ICM process [icm] properties:
    F    section name     : icm
    F    config file      : C:\usr\sap\SV1\J02\exe\icm.properties
    F    node name        : ICM
    F    home directory   : C:\usr\sap\SV1\J02\work
    F    shutdown timeout : 122000 ms
    F    exit timeout     : 7000 ms
    F  ********************************************************************************
    F  ********************************************************************************
    F  Java process [server0] properties:
    F    section name     : ID24836450
    F    config file      : C:\usr\sap\SV1\J02\j2ee\cluster\instance.properties
    F    node name        : server0
    F    home directory   : .
    F    shutdown timeout : 136000 ms
    F    exit timeout     : 7000 ms
    F    debuggable       : true
    F    debugger active  : false
    F  ********************************************************************************
    F  [Thr 7652] *** LOG => Instance state is "Starting the processes" (STARTING @ 0, INACTIVE).
    F  [Thr 7652] *** LOG => Starting nodes: runlevel 3, phase 0.
    F  ********************************************************************************
    F  Starting process: C:\usr\sap\SV1\J02\exe\icman.EXE
    F    arg[ 1] = pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
    F    arg[ 2] = -nodeId=1
    F    arg[ 3] = -f
    F    arg[ 4] = C:\usr\sap\SV1\J02\work\\dev_icm
    F    env   : NODNSSAPTRANSHOST=1
    F  exePath : PATH=C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F  libPath : PATH=C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F  stdout  : C:\usr\sap\SV1\J02\work\std_icm.out
    F  stderr  : C:\usr\sap\SV1\J02\work\std_icm.out
    F  console : no
    F  debugger: no
    F  nice    : no
    F  ********************************************************************************
    F  Process ICM started with pid 7336
    F  ********************************************************************************
    F  [Thr 7652] *** LOG => Process icm started (pid 7336).
    F 
    F [Thr 7652] Mon Oct 08 10:04:12 2012
    F  [Thr 7652] *** LOG => Process icm running (pid 7336).
    F  [Thr 7652] *** LOG => Starting nodes: runlevel 3, phase 1.
    F 
    F Mon Oct 08 10:04:16 2012
    F  ********************************************************************************
    F  Starting process: C:\usr\sap\SV1\J02\exe\jstart.EXE
    F    arg[ 1] = -nodeId=2
    F    arg[ 2] = pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
    F    arg[ 3] = -DSAPINFO=SV1_02_server0
    F    arg[ 4] = -hostvm
    F    arg[ 5] = -nodeName=ID24836450
    F    arg[ 6] = -file=C:\usr\sap\SV1\J02\j2ee\cluster\instance.properties
    F    arg[ 7] = -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
    F    arg[ 8] = -traceFile=C:\usr\sap\SV1\J02\work\dev_server0
    F    arg[ 9] = -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_server0.out
    F    env   : NODNSSAPTRANSHOST=1
    F  exePath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F  libPath : PATH=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F  stdout  : C:\usr\sap\SV1\J02\work\std_server0.out
    F  stderr  : C:\usr\sap\SV1\J02\work\std_server0.out
    F  console : no
    F  debugger: no
    F  nice    : no
    F  ********************************************************************************
    F  Process server0 started with pid 7616
    F  ********************************************************************************
    F  [Thr 7652] *** LOG => Process server0 started (pid 7616).

    Hi Ravi,
    Thanks for your quick response.
    Where do I find the default trace for this?
    The server0 process status is "Waiting to start". The developer trace for server0 is as follows :
    trc file: "dev_server0", trc level: 1, release: "720"
    sysno      02
    sid        SV1
    systemid   562 (PC with Windows NT)
    relno      7200
    patchlevel 0
    patchno    63
    intno      20020600
    make       multithreaded, Unicode, 64 bit, optimized
    profile    \\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
    pid        7616
    *  ACTIVE TRACE LEVEL           1
    *  ACTIVE TRACE COMPONENTS      All, egi
    Mon Oct 08 10:04:17 2012
    *  trace logging activated, max size = 52428800 bytes, 2 versions
    arguments :
      arg[ 0] : C:\usr\sap\SV1\J02\exe\jstart.EXE
      arg[ 1] : -appTrc
      arg[ 2] : -nodeId=2
      arg[ 3] : pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
      arg[ 4] : -DSAPINFO=SV1_02_server0
      arg[ 5] : -hostvm
      arg[ 6] : -nodeName=ID24836450
      arg[ 7] : -file=C:\usr\sap\SV1\J02\j2ee\cluster\instance.properties
      arg[ 8] : -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
      arg[ 9] : -traceFile=C:\usr\sap\SV1\J02\work\dev_server0
      arg[10] : -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_server0.out
    F 
    F Mon Oct 08 10:04:17 2012
    F  ********************************************************************************
    F  Java environment properties
    F    root directory    : C:\usr\sap\SV1\J02\exe\sapjvm_6
    F    vendor            : SAP AG
    F    version           : 1.6.0_17
    F    cpu               : amd64
    F    java vm type      : server
    F    java vm version   : 6.1.018
    F    jvm library name  : jvm.dll
    F    library path      : C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin
    F    executable path   : C:\usr\sap\SV1\J02\exe\sapjvm_6\bin
    F    SAP extensions    : available
    F  ********************************************************************************
    I  [Thr 7280] MtxInit: 10002 0 2
    I  [Thr 7280] MPI: dynamic quotas disabled.
    I  [Thr 7280] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
    M  [Thr 7280] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)
    M  [Thr 7280] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Ext.
    M  [Thr 7280] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Ext.
    M  [Thr 7280] CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    M  [Thr 7280] CCMS: CCMS Monitoring Initialization finished, rc=0.
    F 
    F Mon Oct 08 10:04:17 2012
    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 68, changelist 1198183, NTAMD64, optU (Oct 20 2010, 01:55:49)
    F    arg[ 6] = -Xjvmx
    F    arg[ 7] = -XsapSystem:02
    F    arg[ 8] = -DSAPSTARTUP=1
    F    arg[ 9] = -DSAPSYSTEM=02
    F    arg[10] = -DSAPSYSTEMNAME=SV1
    F    arg[11] = -DSAPMYNAME=INLD50787371A_SV1_02
    F    arg[12] = -DSAPDBHOST=INLD50787371A
    F    arg[13] = -DSAPINFO=SV1_02_server0
    F    arg[14] = -Dj2ee.dbhost=INLD50787371A
    F    arg[15] = -Dsun.java.launcher=jstart
    F    arg[16] = -Dsun.java.command=com.sap.engine.boot.Start 
    F    arg[17] = -Djstartup.mode=JSTART
    F    arg[18] = -Djstartup.whoami=server
    F    arg[19] = -Djstartup.ownProcessId=7616
    F    arg[20] = -Djstartup.ownHardwareId=Q0723431166
    F    arg[21] = -Djstartup.debuggable=yes
    F    arg[22] = -DLoadBalanceRestricted=no
    F    arg[23] = -XdebugPortRange:50221-50221
    F    arg[24] = -Denv.class.path=
    F    arg[25] = -Dsys.global.dir=C:\usr\sap\SV1\SYS\global
    F    arg[26] = -Dapplication.home=C:\usr\sap\SV1\J02\exe
    F    arg[27] = -Djava.class.path=C:\usr\sap\SV1\J02\exe\jstart71.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx_tools.jar;C:\usr\sap\SV1\J02\exe\jre\lib\iqlib.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\tools.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\sap.com~tc~bl~jkernel_boot~impl.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\jaas.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\system\sap.com~tc~bl~bytecode~library.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\memoryanalyzer.jar
    F    arg[28] = -Djava.library.path=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F    arg[29] = -XX:PermSize=1024m
    F    arg[30] = -Xmx2048m
    F    arg[31] = -XX:MaxNewSize=410m
    F    arg[32] = -XX:MaxPermSize=1024m
    F    arg[33] = -Xms2048m
    F    arg[34] = -XX:NewSize=410m
    F    arg[35] = -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    F    arg[36] = -Djavax.management.builder.initial=com.sap.pj.jmx.server.interceptor.InterceptorChainBuilder
    F    arg[37] = -Djmx.invoke.getters=true
    F    arg[38] = -Djava.security.policy=./../bin/kernel/java.policy
    F    arg[39] = -Djava.security.egd=file:/dev/urandom
    F    arg[40] = -Djava.awt.headless=true
    F    arg[41] = -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    F    arg[42] = -Drdbms.driverLocation=C:\sapdb\clients\SV1\runtime\jar\sapdbc.jar
    F    arg[43] = -Djava.io.tmpdir=./temp
    F    arg[44] = -Dsun.lang.ClassLoader.allowArraySyntax=true
    F    arg[45] = -Djava.protocol.handler.pkgs=com.sap.engine.httpdsrclient.protocols|iaik.protocol
    F    arg[46] = -Dnetworkaddress.cache.ttl=10
    F    arg[47] = -DSAPJVM_EXTENSION_COMMAND_HANDLER=com.sap.tools.memory.protocol.ProtocolHandler
    F    arg[48] = -Djco.jarm=1
    F    arg[49] = -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    F    arg[50] = -agentpath:C:\PROGRA~1\JPROFI~1\bin\WINDOW~1\jprofilerti.dll==port=8849
    F    arg[51] = -XX:+UseConcMarkSweepGC
    F    arg[52] = -XX:TargetSurvivorRatio=90
    F    arg[53] = -verbose:gc
    F    arg[54] = -XX:+DumpDetailedClassStatisticOnOutOfMemory
    F    arg[55] = -XX:+PrintGCDetails
    F    arg[56] = -XX:MaxErrorQueueLength=200
    F    arg[57] = -XX:+PrintGCTimeStamps
    F    arg[58] = -XX:+DisableExplicitGC
    F    arg[59] = -XX:SoftRefLRUPolicyMSPerMB=1
    F    arg[60] = -XX:-StringInternTableInPermGen
    F    arg[61] = -XX:SurvivorRatio=9
    F    arg[62] = -XX:+HeapDumpOnOutOfMemoryError
    F    arg[63] = -XX:HeapDumpPath=OOM.hprof
    F    arg[64] = -XX:-TraceClassUnloading
    F    arg[65] = -Xss2097152
    F  ignore unrecognized options : no
    F  ********************************************************************************
    J  JVMX version - Sep 16 2010 15:40:24 - 61_REL - optU - windows amd64 - 6 - bas2:142976 (mixed mode)
    J  Error occurred during initialization of VM
    J  Could not find agent library in absolute path: C:\PROGRA?1\JPROFI?1\bin\WINDOW?1\jprofilerti.dll
    F  [Thr 7364] *** LOG => SfCJavaVm: abort hook is called.
    F 
    F [Thr 7280] Mon Oct 08 12:28:13 2012
    F  [Thr 7280] *** LOG => Command STOP 0 {}.
    F  [Thr 7280] *** LOG => Result for STOP 0 {}: 0 ok, 00000000.
    F 
    F [Thr 7280] Mon Oct 08 12:28:33 2012
    F  [Thr 7280] *** LOG => Command DUMP_THREADS 0 {}.
    J 
    J  ================================================================================
    J  Java thread dump : Mon Oct 08 12:28:33 2012
    J 
    J  ================================================================================
    F  [Thr 7280] *** LOG => Result for DUMP_THREADS 0 {}: 0 ok, 00000000.
    M 
    M [Thr 684] Mon Oct 08 12:28:33 2012
    M  [Thr 684] CCMS: CCMS Monitoring Cleanup finished successfully.
    trc file: "dev_server0", trc level: 1, release: "720"
    sysno      02
    sid        SV1
    systemid   562 (PC with Windows NT)
    relno      7200
    patchlevel 0
    patchno    63
    intno      20020600
    make       multithreaded, Unicode, 64 bit, optimized
    profile    \\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
    pid        5508
    *  ACTIVE TRACE LEVEL           1
    *  ACTIVE TRACE COMPONENTS      All, egi
    Mon Oct 08 12:28:34 2012
    *  trace logging activated, max size = 52428800 bytes, 2 versions
    arguments :
      arg[ 0] : C:\usr\sap\SV1\J02\exe\jstart.EXE
      arg[ 1] : -appTrc
      arg[ 2] : -nodeId=2
      arg[ 3] : pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
      arg[ 4] : -DSAPINFO=SV1_02_server0
      arg[ 5] : -hostvm
      arg[ 6] : -nodeName=ID24836450
      arg[ 7] : -file=C:\usr\sap\SV1\J02\j2ee\cluster\instance.properties
      arg[ 8] : -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
      arg[ 9] : -traceFile=C:\usr\sap\SV1\J02\work\dev_server0
      arg[10] : -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_server0.out
    F 
    F Mon Oct 08 12:28:34 2012
    F  ********************************************************************************
    F  Java environment properties
    F    root directory    : C:\usr\sap\SV1\J02\exe\sapjvm_6
    F    vendor            : SAP AG
    F    version           : 1.6.0_17
    F    cpu               : amd64
    F    java vm type      : server
    F    java vm version   : 6.1.018
    F    jvm library name  : jvm.dll
    F    library path      : C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin
    F    executable path   : C:\usr\sap\SV1\J02\exe\sapjvm_6\bin
    F    SAP extensions    : available
    F  ********************************************************************************
    I  [Thr 500] MtxInit: 10002 0 2
    I  [Thr 500] MPI: dynamic quotas disabled.
    I  [Thr 500] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
    M  [Thr 500] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)
    M  [Thr 500] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Ext.
    M  [Thr 500] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Ext.
    M  [Thr 500] CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    M  [Thr 500] CCMS: CCMS Monitoring Initialization finished, rc=0.
    F 
    F Mon Oct 08 12:28:34 2012
    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 68, changelist 1198183, NTAMD64, optU (Oct 20 2010, 01:55:49)
    F    arg[ 6] = -Xjvmx
    F    arg[ 7] = -XsapSystem:02
    F    arg[ 8] = -DSAPSTARTUP=1
    F    arg[ 9] = -DSAPSYSTEM=02
    F    arg[10] = -DSAPSYSTEMNAME=SV1
    F    arg[11] = -DSAPMYNAME=INLD50787371A_SV1_02
    F    arg[12] = -DSAPDBHOST=INLD50787371A
    F    arg[13] = -DSAPINFO=SV1_02_server0
    F    arg[14] = -Dj2ee.dbhost=INLD50787371A
    F    arg[15] = -Dsun.java.launcher=jstart
    F    arg[16] = -Dsun.java.command=com.sap.engine.boot.Start 
    F    arg[17] = -Djstartup.mode=JSTART
    F    arg[18] = -Djstartup.whoami=server
    F    arg[19] = -Djstartup.ownProcessId=5508
    F    arg[20] = -Djstartup.ownHardwareId=Q0723431166
    F    arg[21] = -Djstartup.debuggable=yes
    F    arg[22] = -DLoadBalanceRestricted=no
    F    arg[23] = -XdebugPortRange:50221-50221
    F    arg[24] = -Denv.class.path=
    F    arg[25] = -Dsys.global.dir=C:\usr\sap\SV1\SYS\global
    F    arg[26] = -Dapplication.home=C:\usr\sap\SV1\J02\exe
    F    arg[27] = -Djava.class.path=C:\usr\sap\SV1\J02\exe\jstart71.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx_tools.jar;C:\usr\sap\SV1\J02\exe\jre\lib\iqlib.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\tools.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\sap.com~tc~bl~jkernel_boot~impl.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\jaas.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\system\sap.com~tc~bl~bytecode~library.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\memoryanalyzer.jar
    F    arg[28] = -Djava.library.path=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F    arg[29] = -XX:PermSize=1024m
    F    arg[30] = -Xmx2048m
    F    arg[31] = -XX:MaxNewSize=410m
    F    arg[32] = -XX:MaxPermSize=1024m
    F    arg[33] = -Xms2048m
    F    arg[34] = -XX:NewSize=410m
    F    arg[35] = -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    F    arg[36] = -Djavax.management.builder.initial=com.sap.pj.jmx.server.interceptor.InterceptorChainBuilder
    F    arg[37] = -Djmx.invoke.getters=true
    F    arg[38] = -Djava.security.policy=./../bin/kernel/java.policy
    F    arg[39] = -Djava.security.egd=file:/dev/urandom
    F    arg[40] = -Djava.awt.headless=true
    F    arg[41] = -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    F    arg[42] = -Drdbms.driverLocation=C:\sapdb\clients\SV1\runtime\jar\sapdbc.jar
    F    arg[43] = -Djava.io.tmpdir=./temp
    F    arg[44] = -Dsun.lang.ClassLoader.allowArraySyntax=true
    F    arg[45] = -Djava.protocol.handler.pkgs=com.sap.engine.httpdsrclient.protocols|iaik.protocol
    F    arg[46] = -Dnetworkaddress.cache.ttl=10
    F    arg[47] = -DSAPJVM_EXTENSION_COMMAND_HANDLER=com.sap.tools.memory.protocol.ProtocolHandler
    F    arg[48] = -Djco.jarm=1
    F    arg[49] = -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    F    arg[50] = -agentpath:C:\PROGRA~1\JPROFI~1\bin\WINDOW~1\jprofilerti.dll==port=8849
    F    arg[51] = -XX:+UseConcMarkSweepGC
    F    arg[52] = -XX:TargetSurvivorRatio=90
    F    arg[53] = -verbose:gc
    F    arg[54] = -XX:+DumpDetailedClassStatisticOnOutOfMemory
    F    arg[55] = -XX:+PrintGCDetails
    F    arg[56] = -XX:MaxErrorQueueLength=200
    F    arg[57] = -XX:+PrintGCTimeStamps
    F    arg[58] = -XX:+DisableExplicitGC
    F    arg[59] = -XX:SoftRefLRUPolicyMSPerMB=1
    F    arg[60] = -XX:-StringInternTableInPermGen
    F    arg[61] = -XX:SurvivorRatio=9
    F    arg[62] = -XX:+HeapDumpOnOutOfMemoryError
    F    arg[63] = -XX:HeapDumpPath=OOM.hprof
    F    arg[64] = -XX:-TraceClassUnloading
    F    arg[65] = -Xss2097152
    F  ignore unrecognized options : no
    F  ********************************************************************************
    J  JVMX version - Sep 16 2010 15:40:24 - 61_REL - optU - windows amd64 - 6 - bas2:142976 (mixed mode)
    J  Error occurred during initialization of VM
    J  Could not find agent library in absolute path: C:\PROGRA?1\JPROFI?1\bin\WINDOW?1\jprofilerti.dll
    F  [Thr 4136] *** LOG => SfCJavaVm: abort hook is called.
    F 
    F [Thr 500] Mon Oct 08 12:29:02 2012
    F  [Thr 500] *** LOG => Command DUMP_THREADS 0 {}.
    J 
    J  ================================================================================
    J  Java thread dump : Mon Oct 08 12:29:02 2012
    J 
    J  ================================================================================
    F  [Thr 500] *** LOG => Result for DUMP_THREADS 0 {}: 0 ok, 00000000.
    M 
    M [Thr 5068] Mon Oct 08 12:29:02 2012
    M  [Thr 5068] CCMS: CCMS Monitoring Cleanup finished successfully.
    trc file: "dev_server0", trc level: 1, release: "720"
    sysno      02
    sid        SV1
    systemid   562 (PC with Windows NT)
    relno      7200
    patchlevel 0
    patchno    63
    intno      20020600
    make       multithreaded, Unicode, 64 bit, optimized
    profile    \\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
    pid        7704
    *  ACTIVE TRACE LEVEL           1
    *  ACTIVE TRACE COMPONENTS      All, egi
    Mon Oct 08 12:29:17 2012
    *  trace logging activated, max size = 52428800 bytes, 2 versions
    arguments :
      arg[ 0] : C:\usr\sap\SV1\J02\exe\jstart.EXE
      arg[ 1] : -appTrc
      arg[ 2] : -nodeId=2
      arg[ 3] : pf=\\INLD50787371A\sapmnt\SV1\SYS\profile\SV1_J02_INLD50787371A
      arg[ 4] : -DSAPINFO=SV1_02_server0
      arg[ 5] : -hostvm
      arg[ 6] : -nodeName=ID24836450
      arg[ 7] : -file=C:\usr\sap\SV1\J02\j2ee\cluster\instance.properties
      arg[ 8] : -jvmFile=C:\usr\sap\SV1\J02\work\jstart.jvm
      arg[ 9] : -traceFile=C:\usr\sap\SV1\J02\work\dev_server0
      arg[10] : -javaOutFile=C:\usr\sap\SV1\J02\work\jvm_server0.out
    F 
    F Mon Oct 08 12:29:17 2012
    F  ********************************************************************************
    F  Java environment properties
    F    root directory    : C:\usr\sap\SV1\J02\exe\sapjvm_6
    F    vendor            : SAP AG
    F    version           : 1.6.0_17
    F    cpu               : amd64
    F    java vm type      : server
    F    java vm version   : 6.1.018
    F    jvm library name  : jvm.dll
    F    library path      : C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin
    F    executable path   : C:\usr\sap\SV1\J02\exe\sapjvm_6\bin
    F    SAP extensions    : available
    F  ********************************************************************************
    I  [Thr 4980] MtxInit: 10002 0 2
    I  [Thr 4980] MPI: dynamic quotas disabled.
    I  [Thr 4980] MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%
    M  [Thr 4980] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=32768;cur=2048)
    M  [Thr 4980] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Ext.
    M  [Thr 4980] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Ext.
    M  [Thr 4980] CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    M  [Thr 4980] CCMS: CCMS Monitoring Initialization finished, rc=0.
    F 
    F Mon Oct 08 12:29:17 2012
    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 68, changelist 1198183, NTAMD64, optU (Oct 20 2010, 01:55:49)
    F    arg[ 6] = -Xjvmx
    F    arg[ 7] = -XsapSystem:02
    F    arg[ 8] = -DSAPSTARTUP=1
    F    arg[ 9] = -DSAPSYSTEM=02
    F    arg[10] = -DSAPSYSTEMNAME=SV1
    F    arg[11] = -DSAPMYNAME=INLD50787371A_SV1_02
    F    arg[12] = -DSAPDBHOST=INLD50787371A
    F    arg[13] = -DSAPINFO=SV1_02_server0
    F    arg[14] = -Dj2ee.dbhost=INLD50787371A
    F    arg[15] = -Dsun.java.launcher=jstart
    F    arg[16] = -Dsun.java.command=com.sap.engine.boot.Start 
    F    arg[17] = -Djstartup.mode=JSTART
    F    arg[18] = -Djstartup.whoami=server
    F    arg[19] = -Djstartup.ownProcessId=7704
    F    arg[20] = -Djstartup.ownHardwareId=Q0723431166
    F    arg[21] = -Djstartup.debuggable=yes
    F    arg[22] = -DLoadBalanceRestricted=no
    F    arg[23] = -XdebugPortRange:50221-50221
    F    arg[24] = -Denv.class.path=
    F    arg[25] = -Dsys.global.dir=C:\usr\sap\SV1\SYS\global
    F    arg[26] = -Dapplication.home=C:\usr\sap\SV1\J02\exe
    F    arg[27] = -Djava.class.path=C:\usr\sap\SV1\J02\exe\jstart71.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\jvmx_tools.jar;C:\usr\sap\SV1\J02\exe\jre\lib\iqlib.jar;C:\usr\sap\SV1\J02\exe\sapjvm_6\lib\tools.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\sap.com~tc~bl~jkernel_boot~impl.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\jaas.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\system\sap.com~tc~bl~bytecode~library.jar;C:\usr\sap\SV1\J02\j2ee\cluster\bin\boot\memoryanalyzer.jar
    F    arg[28] = -Djava.library.path=C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin\server;C:\usr\sap\SV1\J02\exe\sapjvm_6\jre\bin;C:\usr\sap\SV1\J02\j2ee\os_libs;C:\usr\sap\SV1\J02\exe\sapjvm_6\bin;C:\usr\sap\SV1\J02\exe;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Java\jdk1.6.0_23\bin;C:\usr\sap\SV1\SYS\exe\uc\NTAMD64;C:\sapdb\clients\SV1\bin;C:\sapdb\clients\SV1\pgm;C:\sapdb\programs\bin
    F    arg[29] = -XX:PermSize=1024m
    F    arg[30] = -Xmx2048m
    F    arg[31] = -XX:MaxNewSize=410m
    F    arg[32] = -XX:MaxPermSize=1024m
    F    arg[33] = -Xms2048m
    F    arg[34] = -XX:NewSize=410m
    F    arg[35] = -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    F    arg[36] = -Djavax.management.builder.initial=com.sap.pj.jmx.server.interceptor.InterceptorChainBuilder
    F    arg[37] = -Djmx.invoke.getters=true
    F    arg[38] = -Djava.security.policy=./../bin/kernel/java.policy
    F    arg[39] = -Djava.security.egd=file:/dev/urandom
    F    arg[40] = -Djava.awt.headless=true
    F    arg[41] = -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    F    arg[42] = -Drdbms.driverLocation=C:\sapdb\clients\SV1\runtime\jar\sapdbc.jar
    F    arg[43] = -Djava.io.tmpdir=./temp
    F    arg[44] = -Dsun.lang.ClassLoader.allowArraySyntax=true
    F    arg[45] = -Djava.protocol.handler.pkgs=com.sap.engine.httpdsrclient.protocols|iaik.protocol
    F    arg[46] = -Dnetworkaddress.cache.ttl=10
    F    arg[47] = -DSAPJVM_EXTENSION_COMMAND_HANDLER=com.sap.tools.memory.protocol.ProtocolHandler
    F    arg[48] = -Djco.jarm=1
    F    arg[49] = -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    F    arg[50] = -agentpath:C:\PROGRA~1\JPROFI~1\bin\WINDOW~1\jprofilerti.dll==port=8849
    F    arg[51] = -XX:+UseConcMarkSweepGC
    F    arg[52] = -XX:TargetSurvivorRatio=90
    F    arg[53] = -verbose:gc
    F    arg[54] = -XX:+DumpDetailedClassStatisticOnOutOfMemory
    F    arg[55] = -XX:+PrintGCDetails
    F    arg[56] = -XX:MaxErrorQueueLength=200
    F    arg[57] = -XX:+PrintGCTimeStamps
    F    arg[58] = -XX:+DisableExplicitGC
    F    arg[59] = -XX:SoftRefLRUPolicyMSPerMB=1
    F    arg[60] = -XX:-StringInternTableInPermGen
    F    arg[61] = -XX:SurvivorRatio=9
    F    arg[62] = -XX:+HeapDumpOnOutOfMemoryError
    F    arg[63] = -XX:HeapDumpPath=OOM.hprof
    F    arg[64] = -XX:-TraceClassUnloading
    F    arg[65] = -Xss2097152
    F  ignore unrecognized options : no
    F  ********************************************************************************
    J  JVMX version - Sep 16 2010 15:40:24 - 61_REL - optU - windows amd64 - 6 - bas2:142976 (mixed mode)
    J  Error occurred during initialization of VM
    J  Could not find agent library in absolute path: C:\PROGRA?1\JPROFI?1\bin\WINDOW?1\jprofilerti.dll
    F  [Thr 4736] *** LOG => SfCJavaVm: abort hook is called.

  • Jcontrol.exe in SAP MMC turns "GREY" after start.--- Urgent

    Hi, I am facing one problem with SAP J2EE engine.
    In SAP MMC all services are green, only "Jcontrol.exe" is  Grey. I restarted the server several times but every time it starts and then just becomes "GREY" Below is the description of "Developer Trace" which I have copied from SAP MMC console.
    Any help in this regards would be highly appreciated. It is urgent.
    Thanks.
    Ashish Patel.
    JStartupStartJLaunch: program = D:\usr\sap\DNW\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[00] = D:\usr\sap\DNW\JC00/j2ee/os_libs/jlaunch.exe
    -> arg[01] = pf=D:\usr\sap\DNW\SYS\profile\DNW_JC00_dgntwas
    -> arg[02] = -DSAPINFO=DNW_00_bootstrap
    -> arg[03] = -file=D:\usr\sap\DNW\JC00\j2ee\cluster\instance.properties
    -> arg[04] = -nodeName=bootstrap_ID3314950
    -> arg[05] = -nodeId=-1
    -> arg[06] = -syncSem=JSTARTUP_WAIT_ON_3148
    -> arg[07] = -jvmOutFile=D:\usr\sap\DNW\JC00\work\jvm_bootstrap_ID3314950.out
    -> arg[08] = -stdOutFile=D:\usr\sap\DNW\JC00\work\std_bootstrap_ID3314950.out
    -> arg[09] = -locOutFile=D:\usr\sap\DNW\JC00\work\dev_bootstrap_ID3314950
    -> arg[10] = -mode=BOOTSTRAP
    -> arg[11] = pf=D:\usr\sap\DNW\SYS\profile\DNW_JC00_dgntwas
    -> lib path = PATH=C:\j2sdk14209\jre\bin\server;C:\j2sdk14209\jre\bin;D:\usr\sap\Python\.;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\80\Tools\BINN;D:\usr\sap\DNW\SCS01\exe;D:\usr\sap\DNW\JC00\exe;D:\usr\sap\DNW\SYS\exe\run
    -> exe path = PATH=C:\j2sdk14209\bin;D:\usr\sap\DNW\JC00\j2ee\os_libs;D:\usr\sap\Python\.;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\80\Tools\BINN;D:\usr\sap\DNW\SCS01\exe;D:\usr\sap\DNW\JC00\exe;D:\usr\sap\DNW\SYS\exe\run
    [Thr 3152] Wed Aug 23 15:01:34 2006
    [Thr 3152] *** ERROR => invalid return code of process [bootstrap_ID3314950] (exitcode=-2) [jstartxx.c   1433]
    [Thr 3152] JControlExecuteBootstrap: error executing bootstrap node [bootstrap_ID3314950] (rc=-2)
    [Thr 3152] JControlCloseProgram: started (exitcode = -2)
    [Thr 3152] JControlCloseProgram: good bye... (exitcode=-2)
    ==========================================

    Hi,
    Try this:
    1.Stop all SAP instances
    2.Stop the DB
    3.Stop the listner
    Logoff, and logon to the server as <sid>adm
    then:
    1.Start the listner (dos window ---> lsnrctl start)
    2.Start the DB
    3.Start the SAP Instances
    It should start correctly now.
    Kind Regards
    Ian Henderson

  • MMC hangs on Windows 2008 and SAP MMC console not coming up

    Hi All,
    We are running SAP CRM 7. After upgrading Windows 2003 to Windows 2008 R2, SAP is coming up on our J2ee engine. We are able to login to the SAP J2ee application, but SAP MMC hangs. After the reboot, SAP MMC does come up but it hangs while starting the SAP Server Processes. We have to close the MMC from CTRL-ALT-DEL (end process). After that SAP MMC does not come up. Although, we can number number of MMC.EXE running in task manager,but
    the SAP MMC window is not displayed.
    We have gone through OSS note Note 1326097 - SAP MMC Snap-In crash for certain operations and installed the new version of MMC. But still the error exists. Also, we have installed the VCREDLIST patch and have installed all the DLLs mentioned in OSS SS Note 684106 - Microsoft runtime DLLs.
    Also, the event viewer shows the following message
    Log Name: Application
    Source: Application Hang
    Date: 9/9/2011 8:32:30 AM
    Event ID: 1002
    Task Category: (101)
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: sap-xp-q01.com
    Description:
    The program mmc.exe version 6.1.7600.16385 stopped interacting with
    Windows and was closed. To see if more information about the problem is
    available, check the problem history in the Action Center control panel. Process ID: fcc
    Start Time: 01cc6f03c402c248
    Termination Time: 6
    Application Path: C:\Windows\system32\mmc.exe
    Report Id: e74f009f-daf8-11e0-afd2-000c29701b8a
    Also, we have upgraded the SAP Kernel to the latest patch level and installed MMC latest patch.
    Please suggest.
    Thanks,
    Antarpreet

    Hello,
    Try to re-create (re-register) the SAP Services (SAP instance services) in services.msc list. Then try to put SAP MMC up.
    Or, after recreation of sap instance services, try to reconfigure the sap mmc as well -
    http://help.sap.com/saphelp_nwpi71/helpdata/en/49/0eb43799b4740ee10000000a421937/content.htm
    Thanks

  • Updating new PID of thr process in SAP MMC

    Hello,
    There was an abrupt shutdown in process of rslgsend and igs*
    I have manually restarted the process and it is working on SAP level,although as a new process is started
    its PID is not updated in SAP MMC and hence it is displayed in grey status even though services are up and working fine
    Can anybody suggest, how to update the process with its new PID in SAP MMC
    regards,
    Dwipam

    thanks for your reply,
    Any other procedure to change the PID of the process associated to new PID. Because, process with old PID is expired and hence in SAP MMC it is displayed in stop mode
    Also if possible can you please provide a doc. which explains how and where PID of process are registered in SAP MMC, so that alter some alterations, we are able to get new status of process
    regards,
    Dwipam

Maybe you are looking for

  • Blue Screen of Death in LightRoom 3.6

    I recently built a PC for photo editing, and I am receiving the BSOD at different points when Lightroom is open. The first time it happened was when I was moving about 1000 raw files from one folder to another (did it twice to me doing that). From th

  • What is this hidden "feature" in mobile Safari for and how can I use it?

    OK, one day, like any geek would, I was in the car messing with my iPod touch. I was playing in Safari, typing in email addresses and such to get the exciting "WARNING - PHISHING SITE" screen. So I then tried typing "/" into the address bar, and when

  • Windows will not restart after install of itunes & quicktime, what to do?

    I installed itunes and quicktime from the disc provided. After install the installer asked to restart the computer and I clicked yes. It has not booted since. Windows 2000 Pro locks up about 75% through process. I did hear the speakers activate then

  • S_ALR_87013543 report not showing line item correctly

    Hi all, The S_ALR_87013543 report or any other cost plan report not showing the line item report correctly. eg When the S_ALR_87013543 report executed it showing 100 as a plan value against one of cost element when we double click and go to line item

  • X58 Pro motherboard will not display video

    Just put together a computer and the video wont work. Here's the part list:     Intel Core i7 920 Nehalem 2.66GHz LGA 1366 130W Quad-Core Processor Model BX80601920     MSI X58 Pro LGA 1366 Intel X58 ATX Intel Motherboard     Western Digital Caviar R