My SAP MMC is not showing server instance01

Hello Experts,
My SAP MMC is not showing server instance01.
I am running Netweaver 2004s SP17.
It was working fine earlier, and after a system reboot, I tried to start the server again, but MMC does not show server instance in NSP node.
I had tried starting the server from Administrative tools->Services   SAPNSP_01
but, its not starting and showing and message as
       Could not start the SAPNSP_01 service on Local Computer.
       Error 5: Access is denied.
where as SAPNSP_00 in  Administrative tools->Services started and showing that in MMC console also.
Is there a way for me to fix this?
Regards
Sunil

I managed to fix the problem - I ran sapstartsrv.exe from windows explorer (located in \usr\sap\NSP\DVEBMGS00\exe)
Here I entered the following:
Operation: -Install Service and register COM interface & Start Service
SID: NSP
NR: 00
Start Profile: C:\usr\sap\NSP\SYS\profile\START_DVEBMGS00_<ServerName> (where <ServerName> is your computer name)
User: <ServerName>\<UserName> (where <ServerName> is your computer name, and <UserName> is your windows login name)
Password: windows login password
Startup Type: Automatic

Similar Messages

  • I cant see any thing any SAP MMC for my XI server.

    Hi All,
    I cant see any thing any SAP MMC for my XI server.
    I checked the services SAPXID_00 and SAPXID_01, those sevices were not running. when i try to start the service I am getting error 1067: The process terminated unexpectedly. I have uninstalled and reinstalled the service with sapstartsrv.exe but no luck.
    I have also check SAP Note 82751
    when i checked the log sapstartsrv.log, I saw this error
    MSETCLXIDEV\xidadm is starting SAP System at 2011/01/17 16:16:47
    SAP HA Trace: FindClusterResource: OpenCluster failed: 1753 [sapwinha.cpp, line 212]
    SAP HA Trace: SAP_HA_FindSAPInstance returns: SAP_HA_FAIL [sapwinha.cpp, line 907]
    Error: 13, Open Logging-File "sapstart.log". EACCES*: Permission denied OR: The data is invalid. 
    Please help to resolve this issue.
    Thanks
    Rehan
    Edited by: Rehan  Manzoor on Jan 19, 2011 12:39 PM

    Hi,
    Is it that there is no entry in SAP MMC for the system? Can you try to manually add the System in SAP MMC and check?I or is it that the system is already added and there is no info in SAP MMC. It is possible that the MMC is not working properly. You can reinstall the SAP MMC or better install the latest one. If the SAP MMC is not the issue here then it is possible that tthere is a some permission issue involved here.Could you check the whether the user with which the services are being started have correct permissions or not.
    I had an issue where my SAP MMC was installed in a windows system and my SAP system was in Linux(Redhat). And because of the firewall and a security feature called SElinux my SAP MMC was not showing any information.There was a similar issue where i had to upgrade the LM tools. You can download the latest Lifecycle management software from SMP.
    Regards,
    Jyotish

  • 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

  • SAP MMC does not start and red in color

    Hi Gurus,
    We are in a process of installing EhP4 and there were lots of errors. We reverted back to old version.
    After moving back to old state i.e., EhP3, system does not start.
    1. SAPosCol does not start acutomatically in the service
    2. sapmmc does not show database details
    3. When I try to start the server through SAPMMC, all esmart03 0, esmart03 1 turns to red.
    Please let me know how i can fix this problem.
    I want to post screen shot, but i am not sure how i can post the same here.
    Thanks in advance.
    Regards
    Shreeshail

    Thanks Sunny for your reply.
    We had taken system system backup (complete "E" drive) where SAP server is installed. I had to stop EhP4 process as we got a requirement to bringup NWBC.
    We restored the "E" drive content and then restarted the SAP server.
    After that servies did not start and MMC does not show up Database details.
    Do i need to create services and MMC to fix the issues??
    Thanks in advance.
    Regards
    Shreeshail

  • Icm trace level if smicm and SAP MMC are not available ( CE system on Unix)

    Hi Experts,
    Could you please let me know how will I increase the icm trace level if SMICM transaction code and SAP MMC are not available.
    I have an CE 7.2 system running on HP UNIX.
    Thanks and Regards
    Syam

    http://help.sap.com/saphelp_nw70/helpdata/en/0b/6aedff404d6b4a8cac8f1359e1b47c/frameset.htm
    kill -USR2 <pid>
    Markus

  • 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 [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 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 [Thr 7652] Mon Oct 08 10:03:19 2012
    F  [Thr 7652] *** LOG => Process deployment stopping (pid 7968).

    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 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 [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 [Thr 7652] Mon Oct 08 10:04:10 2012
    F  [Thr 7652] *** LOG => Process bootstrap stopping (pid 7952).

    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 [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 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 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 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 [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 [Thr 7280] Mon Oct 08 12:28:33 2012
    F  [Thr 7280] *** LOG => Command DUMP_THREADS 0 {}.

    J  ================================================================================
    J  Java thread dump : Mon Oct 08 12:28:33 2012

    J  ================================================================================
    F  [Thr 7280] *** LOG => Result for DUMP_THREADS 0 {}: 0 ok, 00000000.

    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 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 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 [Thr 500] Mon Oct 08 12:29:02 2012
    F  [Thr 500] *** LOG => Command DUMP_THREADS 0 {}.

    J  ================================================================================
    J  Java thread dump : Mon Oct 08 12:29:02 2012

    J  ================================================================================
    F  [Thr 500] *** LOG => Result for DUMP_THREADS 0 {}: 0 ok, 00000000.

    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 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 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.

  • SAP management console not showing AS java

    Hello all,
    I have made a NW04s installation system test (linux+oracle). I then installed as java add-in EP and BI (AS JAVA, EP CORE, EP, BI JAVA). It was NW04s SR2 with SPC13 and kernel not changed: 700 patch 111.
    In the SAP management console there were 3 entries: one for database, one for abap instance and one for java instance.
    In the abap instance node I was able to see an entry for "AS java"  which was whowing two process (SDM and another one...).
    I made a new test installation similar to the previous one and in the SAP management console I do not see any entry for "AS Java". Of course AS java is installed and running !
    How can I get SAP management console show "AS java" ????
    Thank you
    Jean

    Hi Jean,
    Start Services.msc from run prompt (if this is windows based installation)
    and look for <SID>services, where <SID> is your instance name..
    Please do the following and let me know if this of any success
    You get back your MMC , please do the following steps.
    1. Go to Run and type MMC.
    2.Go to file and select add/remove snap in ( alt+m).
    3.Click on add
    4.Select the SAP system from there.
    Save the MMC console which you have created now....This should work fine.
    Thanks
    Pankaj

  • GlassFish Tools - Eclipse console does not show server log output

    Hi,
    I just installed the latest Glassfish Tools (6.2.1.201308190137) on Eclipse Kepler and Glassfish Server 3.1.2.  But when I start the server and open the console ('view log file' button) there is no output displayed (also not during deployment). When I open the server.log file in a text editor I can clearly see the log output. Re-starting Eclipse, re-opening the console view didn't help. I have this bug both on Windows 8 and OSX 10.8.4.
    Is there something obvious that I am missing? In my previous pre-kepler Eclipse installation this works like a charm (using the same glassfish server). Also the path to the log file displayed on the top of the console view is correct.
    This might be related to the following thread:
    GlassFish > View Log File opens in editor instead of console
    Will have to use my old eclipse installation until this is resolved. Any help is appreciated.
    -- Mike

    Apparently, the GlassFish Tools for eclipse is expecting the log messages in 'ODLLogFormatter' format only, and will refuse to show any logs messages that don't adhere to this format.
    I've tried configuring my logback messages to match this format, and that works until an exception is thrown and a log message is entered somewhere using the 'UniformLogFormatter' format, which then causes the server.log parser to refuse to show any more messages.
    This is a bug, but I'm unsure where to report bugs now since the move to OEPE.  (Was https://java.net/jira/browse/GLASSFISHPLUGINS)

  • "SAP Systems" selection not showing in SAPinst welcome screen

    I recently purchased a NetWeaver Development subscription and am following the installation guide for SAP NetWeaver 2004s SR3 ABAP+Java on Windows with MS SQL Server. However, in the Welcome menu of SAPinst under the NetWeaver selection, I am not seeing the "SAP Systems" selection  as it is described in section 4.3 "Installing a SAP system using SAPinst". I only see the selections "Standalone Engines", "Optional Standalone Units", and "Software Life-Cycle Options". Could someone please tell me how I can install a "Central System" on a Windows 2003 Server? Thanks.

    Hi and thank you very much for quick reply...
    We have also concluded that the note suddently is "gone"?
    So the deal is to install a SR2 and then upgrade...Lucky i still have SR2 installs...
    I wonder what the solution would be if we didn't still had the install files for SR2. And what is the official
    reaction from SAP when installing SR2 win 32 bit for a customer, since the customer do not currently supports 64bit?
    I have tried to talk the customer intto 64 bit, but no luck so fare  
    On the other hand if they have a large environment running WM ware, then it can be a big job to upgrade!
    Thank you very much...

  • SAP MMC console not working.

    Hi All,
       While opening the management console of the SAP,
    I'm encountring an error given below:
    "MMC can't open the file "C:\WINDOWS\SAPMMC.MSC."
    This may be because the file doesnot exist, is not an MMC console, or was created by later version of MMC. This may also be because you don't have sufficientaccess rigths to the file.
    Plz help
    Thanks in advance.
    Edited by: Mohnish Kapoor on May 17, 2008 3:07 PM

    Problem solved.

  • Sap m select not showing all values from gateway

    Hello Experts,
    This is the code for my select:
    var SelectCondType = new sap.m.Select("SelectCondType", {
       width : "200px"
       var oItemSelectTemplate1 = new sap.ui.core.Item({ 
                 key : "{ID}", 
                 text : "{Name}" 
      var sServiceUrl = "blablabla.com:8000/sap/opu/odata/sap/YXM_GWS_BART_SRV";
      var oModel = new sap.ui.model.odata.ODataModel(sServiceUrl, false,
      "user", "pass");
      SelectCondType.setModel(oModel);
      SelectCondType.bindAggregation("items","/cond_type",oItemSelectTemplate1);
    The select is showing around 50 (didn't really count em) items while there are like 500 in the gateway...
    Any Ideas ?
    Kind Regards,
    Bart

    Nevermind,
    awiedemann.com &amp;bull; SAPUI5 / oData / JSON model - set size limit
    Kind Regards,
    Bart

  • SAP ProComp model not showing up in ID

    Hello,
    I have created a model of type "SAP ProComp model " in ESB. Now when I try to use this as template while creating a Configuration Scenario in ID, I do not see it.
    I am trying to locate it under "SAP Process Component Interaction Model".
    But when I create a model of type "SAP ProComp Interaction model", I am able to see it.
    This seems logical, but I am able to see SAP provided models of type "SAP ProComp model" here.
    I am on PI 7.1 EHP1.
    Please advise.
    Thank you.

    Is it because SAP Pro Comp model is not supported in EHP1. Now I tried creating my own SAP Pro Comp Interactive Model and when I try to load that, I get the below errors.
    Process Component Interaction Model 'XXX': Error in reading Process Component object definition - set name and ID to null and type to internal
    Please advise.
    Thank you.

  • SAP Crystal Reports not showing up in Safari?

    I am trying to get to access my business Crystal Reports from home on my Mac in Safari, I am able to log in and see my choices, but the reports are coming up with the little blue lego logo with the question mark in the middle. I can access from work on PC but not on Mac. Any ideas?
    Thanks

    If it's actual crystal reports try the viewer, if it's a crystal reports driven website try changing changing User Agent to IE 6. If your Safari doesn't have Develop in menubar go to Preferences/Advanced and check Show Develop.
    I have to do this with a website that uses a crystal backed website.

  • MMC does not show Database Node in EP system!

    Dear all,
    I am facing a serious problem.
    In my MMC as all the systems got disappeared, i tried adding the instances for the EP system in MMC.
    so 2 instances were added but there is <b>no database node</b> for the EP system in MMC.
    Can someone guide me to get the Database node in the EP system in MMC?
    Thanks in advance,
    -Tejas

    Hi,
    Changing the Configuration of the MMC
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/43/2591f972634e86e10000000a422035/frameset.htm
    Further Documentation and Troubleshooting
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/58/7d8f671e0fa54db744991e200f9111/frameset.htm
    Regards,
    Siddhesh

  • Urgent SAP Help menu not showing option "Create Support Message"

    Hi all,
    We are running SAP 4.6c landscape (dev,qa,prd), and have solution manager installed .
    Now when i want to create a support messge from any system in my landscape i dont get the option "Create Support Message" in the SAP Help menu, and we create a support message using Help->Feedback option . Is this the correct was or is there any other settings or notes i need to make/apply on my landscape to get this option.
    Message was edited by: Kamran Ellahi

    Hi guys,
    Thanks for your answers... But is it possible to call transaction NOTIF_CREATE from an external system?
    I have done something already so that those 3 fields will be automatically populated for a message sent from an external system.
    I changed the screen and called FM BAPI_NOTIFICATION_CREATE(a remote enabled FM which is the one being used by transaction NOTIF_CREATE to create a message) inside FM BCOS_SEND_MSG.
    I populated the category, subject and solution in the FM export parameters as well as the solution number in the sap data table. I put a destination also..
    This FM calls another FM DNO_OW_CREATE_NOTIFICATION which is the one being used from the external system but do not cater the functionality to send the 3 fields that we need.
    As you will notice, there are lots of standard objects that I've changed. =)
    My problem now is that the system data sent is the same with the system data if you create the message using NOTIF_CREATE. Some system that were sent when a message is sent from an external system is missing but at least the sap system and client ID is sent. There is no external reference number also. But hopefullly, the users will accept it. Can't find any other solution to this.
    Thanks,
    Eric

Maybe you are looking for