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

Similar Messages

  • Error while starting services in SAP MMC

    Hi Everybody,
    I had Installed SAP ECC6 version in my laptop, after installation(not restarted laptop) services are already on, i had installed sap gui, and everything i configured, user id and access key of abap developer.
    But when i want to stop or start services in SAP MMC, it prompts me for webservice authentication such as OS USER & Password, when i gave my OS user id and password , error message i got as Stop Failed , Invalid credentials.
    Please help me on this...
    Thanks in Advance
    Regards
    Sudheer

    Hi
    Consier your laptop as a server which is hosting the sap application
    So you need to always use sidadm for any such administration as we basis normally do
    Sucess!!
    Ganesh

  • The "J2EE process table" node not visible  in the SAP MMC

    For Netweaver 7.0 - The "J2EE process table" node not visible  in the SAP MMC.
    Details for below
    SAP Systems Manager
    SAP AG
    Version: 7100.109.15.8983
    Window Xp
    Any suggestions would be apperecited.
    Thanks
    Srini

    It's hard to say without seeing the code for TreeTable. But they probably have something like an addNode mothod for the TreeTableNode which will take care of all the updates for you. If you want to do it youself, you will probably have to get the data Model (tree.getModel()???)behind the TreeTable and use one of the fire... methods on it like fireRowChanged(???) or fireTableChanged(???). I would suspect Sun would do it this way.

  • Driver Deployment..but SDM not starting up

    Hi All,
    We were trying to deploy some jdbc jar on jee server but our SDM is not starting up. It up on waiting for SDM to start.?
    message coming is ..on running startserver.bat..is
    Server not up in 5 seconds. waiting for anther 5 seconds..
    what could be the reason..?
    I am not Basis person but XI person..

    Hi Ranjeet,
    Check if these threads can help u out,
    /people/community.user/blog/2007/02/13/sdm-unveiled
    software deployment manager to deploy JDBC driver
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/55a1e525-0c01-0010-ad85-e4d5862f2800
    /thread/175849 [original link is broken]
    ****Reward points if usefull***

  • Cannot start Process in sap mmc

    Hello Sap Gurus,
    In RZ10 I have coped default profile into zdefault made some changes in it and have activated it. After this when i tried to start my processes, they are not starting.
    I went to SAP-> ecc->Profiles and again reverted my changes in default profile. Even then my processes are not starting.
    Please tell me how to resolve this. I am new to this field. So please elaborate the solution so that it can be easily understood by lay men like me.
    I am getting the below in process list:
    In process list : msg_server.exe : stopped
    disp+work.exe : stopped
    igswd.exe : stopped
    Thanks,
    SriNitya,

    Hi,
    As subhash said you should revert the profile, if you have a backup just replace the file  in <drive>/usr/sap/SYS/profile.
    if not then you should be able to open the File using wordpad / notepad there you can see the Changes done last time as it will be written in file as commented line.
    Just undo the changes by using # which will comment the parameter.
    Further what was the change that you did in default profile?? still not working please paste Dev_ms log file.
    Thanks,
    Balaji.S

  • Java dispatcher & SDM not starting

    I am getting foll errors when starting java instance in
    Eportal development server 6.0
    Developer trace file contents of Java instance during startup :-
    trc file: "F:\usr\sap\J2D\JC00\work\dev_jcontrol", trc level: 1, release: "640"
    node name   : jcontrol
    pid         : 4220
    system name : J2D
    system nr.  : 00
    started at  : Tue Feb 05 15:57:16 2008
    arguments   :
        arg[00] : F:\usr\sap\J2D\JC00\j2ee\os_libs\jcontrol.exe
        arg[01] : pf=F:\usr\sap\J2D\SYS\profile\J2D_JC00_epserver
    [Thr 4216] Tue Feb 05 15:57:16 2008
    [Thr 4216] *** ERROR => Invalid property value [box.number/J2DJC00epserver] [jstartxx.c   789]
    [Thr 4216] *** ERROR => Invalid property value [en.host/epserver] [jstartxx.c   789]
    [Thr 4216] *** ERROR => Invalid property value [en.port/3201] [jstartxx.c   789]
    [Thr 4216] *** ERROR => Invalid property value [system.id/0] [jstartxx.c   789]
    this is few lines extract from the developer trace of java
    instance
    Also we are able to start IGS service successfully.
    Plz help asap thnk u
    Regards
    Sagar S Manjrekar

    Hi Sagar,
    you may need to restart at OS level...
    thn perform follo...
    in command prompt....
    go for this... folder...
    \usr\sap\epd\jc00\sdm\program\
    type following...
    sdm jstartup "mode=integrated"
    this can start sdm in integrated mode while running thru SAP Management..
    and if you dont want to start it at that level and manually start the same do following...
    instead of integrated type standalone...
    thn go to sdm folder and run remote gui
    this will start on with sdm...
    hope this might solve ur error...
    Regards,
    Purav

  • Fail stop-start trex since sap MMC

    If I try to stop trex since TREX admnstration console, and MMC option, a Remote Authenticacion screen appear with Username: txdadm user and I need to write the password, after write it correctly, a second screen appear with this error message 'Invalid Credentials', I was looking for a solution, and I found this ...
    'Starting/stopping TREX via sap managment console or sapcontrol executable
    or TREX python admin tool returns 'invalid credentials'. ...
    solution:
    Create a file /etc/pam.d/sapstartsrrv as root user with the following content:
    #%PAM-1.0
    auth requisite pam_unix_auth.so
    Change the file permission with 'chmod 0644 sapstartsrv'.
    I did it, but I continue with the same problem.
    We have the trex version 7.0.44 (7044000506), and our O.S. is a solaris 10g 64bits sparc.

    If I try to stop trex since TREX admnstration console, and MMC option, a Remote Authenticacion screen appear with Username: txdadm user and I need to write the password, after write it correctly, a second screen appear with this error message 'Invalid Credentials', I was looking for a solution, and I found this ...
    'Starting/stopping TREX via sap managment console or sapcontrol executable
    or TREX python admin tool returns 'invalid credentials'. ...
    solution:
    Create a file /etc/pam.d/sapstartsrrv as root user with the following content:
    #%PAM-1.0
    auth requisite pam_unix_auth.so
    Change the file permission with 'chmod 0644 sapstartsrv'.
    I did it, but I continue with the same problem.
    We have the trex version 7.0.44 (7044000506), and our O.S. is a solaris 10g 64bits sparc.

  • SDM Not Starting

    When I try and load SDM, I enter password, hostname and port and click connect. It just says "Attempting to login" at the bottom and never fully loads.

    <!LOGHEADER[START]/>
    <!HELP[Manual modification of the header may cause parsing problem!]/>
    <!LOGGINGVERSION[1.5.3.7185 - 630]/>
    <!NAME[C:\usr\sap\S01\JC01\SDM\program\log\sdmlog20070620.log]/>
    <!PATTERN[sdmlog20070620.log]/>
    <!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
    <!ENCODING[Cp1252]/>
    <!LOGHEADER[END]/>
    Jun 20, 2007 9:22:45 AM  Info:
    Jun 20, 2007 9:22:45 AM  Info: ============================================
    Jun 20, 2007 9:22:45 AM  Info: =   Starting to execute command 'server'   =
    Jun 20, 2007 9:22:45 AM  Info: ============================================
    Jun 20, 2007 9:22:45 AM  Info: Starting SDM - Software Deployment Manager...
    Jun 20, 2007 9:22:46 AM  Info: tc/SL/SDM/SDM/sap.com/SAP AG/7.0007.20060301165555.0000
    Jun 20, 2007 9:22:52 AM  Info: SDM operation mode successfully set to: Integrated
    Jun 20, 2007 9:22:54 AM  Info: JStartupFramework is requesting to start the SDM Server.
    Jun 20, 2007 9:22:54 AM  Info: Start the SDM Server integrated in the JStartupFramework.
    Jun 20, 2007 9:22:54 AM  Info: Initializing Network Manager (50117)
    Jun 20, 2007 9:22:54 AM  Info: Starting SDM Server listening on port 50118
    Jun 20, 2007 9:22:54 AM  Info: SDM started successfully.
    Jun 20, 2007 9:58:52 AM  Info: ====================================
    Jun 20, 2007 9:58:52 AM  Info: JControl is shutting SDM Server down
    Jun 20, 2007 9:58:52 AM  Info: ====================================
    Jun 20, 2007 9:58:52 AM  Info: Server finished sending back the answer of the ShutdownRequest.
    Jun 20, 2007 9:58:52 AM  Info: Shutting dispatcher down
    Jun 20, 2007 10:03:42... Info:
    Jun 20, 2007 10:03:42... Info: ============================================
    Jun 20, 2007 10:03:42... Info: =   Starting to execute command 'server'   =
    Jun 20, 2007 10:03:42... Info: ============================================
    Jun 20, 2007 10:03:43... Info: Starting SDM - Software Deployment Manager...
    Jun 20, 2007 10:03:44... Info: tc/SL/SDM/SDM/sap.com/SAP AG/7.0007.20060301165555.0000
    Jun 20, 2007 10:03:49... Info: SDM operation mode successfully set to: Integrated
    Jun 20, 2007 10:03:50... Info: JStartupFramework is requesting to start the SDM Server.
    Jun 20, 2007 10:03:50... Info: Start the SDM Server integrated in the JStartupFramework.
    Jun 20, 2007 10:03:51... Info: Initializing Network Manager (50117)
    Jun 20, 2007 10:03:51... Info: Starting SDM Server listening on port 50118
    Jun 20, 2007 10:03:51... Info: SDM started successfully.
    Jun 20, 2007 10:39:44... Info:
    Jun 20, 2007 10:39:44... Info: ===============================================
    Jun 20, 2007 10:39:44... Info: =   Starting to execute command 'remotegui'   =
    Jun 20, 2007 10:39:44... Info: ===============================================
    Jun 20, 2007 10:39:48... Info: SDM started successfully.
    Jun 20, 2007 10:40:08... Info: Opened client connection to SUSOSG112.na.o-i.test (IP address SUSOSG112.na.o-i.test/10.104.96.118, remote port 1562)
    Jun 20, 2007 10:40:08... Info: Request for Logon as admin accepted
    Jun 20, 2007 11:40:45... Info:
    Jun 20, 2007 11:40:45... Info: ===============================================
    Jun 20, 2007 11:40:45... Info: =   Starting to execute command 'remotegui'   =
    Jun 20, 2007 11:40:45... Info: ===============================================
    Jun 20, 2007 11:40:47... Info: SDM started successfully.
    Jun 20, 2007 11:41:39... Info: Opened client connection to SUSOSG112.na.o-i.test (IP address SUSOSG112.na.o-i.test/10.104.96.118, remote port 2275)
    Jun 20, 2007 11:41:39... Error: Cannot log in. There are already active sessions:
    Session id 0 / An administrator logged in via GUI /
    Jun 20, 2007 11:41:56... Info: Close client connection to SUSOSG112.na.o-i.test/10.104.96.118, remote port 2275
    Jun 20, 2007 11:42:46... Info: ====================================
    Jun 20, 2007 11:42:46... Info: JControl is shutting SDM Server down
    Jun 20, 2007 11:42:46... Info: ====================================
    Jun 20, 2007 11:42:46... Info: Server finished sending back the answer of the ShutdownRequest.
    Jun 20, 2007 11:42:46... Info: Shutting dispatcher down
    Jun 20, 2007 11:42:53... Info:
    Jun 20, 2007 11:42:53... Info: ============================================
    Jun 20, 2007 11:42:53... Info: =   Starting to execute command 'server'   =
    Jun 20, 2007 11:42:53... Info: ============================================
    Jun 20, 2007 11:42:53... Info: Starting SDM - Software Deployment Manager...
    Jun 20, 2007 11:42:54... Info: tc/SL/SDM/SDM/sap.com/SAP AG/7.0007.20060301165555.0000
    Jun 20, 2007 11:42:58... Info: SDM operation mode successfully set to: Integrated
    Jun 20, 2007 11:42:59... Info: JStartupFramework is requesting to start the SDM Server.
    Jun 20, 2007 11:42:59... Info: Start the SDM Server integrated in the JStartupFramework.
    Jun 20, 2007 11:42:59... Info: Initializing Network Manager (50117)
    Jun 20, 2007 11:43:00... Info: Starting SDM Server listening on port 50118
    Jun 20, 2007 11:43:00... Info: SDM started successfully.
    Jun 20, 2007 11:43:23... Info: Opened client connection to SUSOSG112.na.o-i.test (IP address SUSOSG112.na.o-i.test/10.104.96.118, remote port 2296)
    Jun 20, 2007 11:43:23... Info: Request for Logon as admin accepted
    Jun 20, 2007 11:51:48... Info: Opened client connection to 10.96.235.87 (IP address 10.96.235.87/10.96.235.87, remote port 4973)
    Jun 20, 2007 11:51:48... Error: Cannot log in. There are already active sessions:
    Session id 0 / An administrator logged in via GUI /
    Jun 20, 2007 11:51:52... Info: Close client connection to 10.96.235.87/10.96.235.87, remote port 4973
    Jun 20, 2007 11:54:14... Info: ====================================
    Jun 20, 2007 11:54:14... Info: JControl is shutting SDM Server down
    Jun 20, 2007 11:54:14... Info: ====================================
    Jun 20, 2007 11:54:14... Info: Server finished sending back the answer of the ShutdownRequest.
    Jun 20, 2007 11:54:14... Info: Shutting dispatcher down
    Jun 20, 2007 11:54:21... Info:
    Jun 20, 2007 11:54:21... Info: ============================================
    Jun 20, 2007 11:54:21... Info: =   Starting to execute command 'server'   =
    Jun 20, 2007 11:54:21... Info: ============================================
    Jun 20, 2007 11:54:21... Info: Starting SDM - Software Deployment Manager...
    Jun 20, 2007 11:54:22... Info: tc/SL/SDM/SDM/sap.com/SAP AG/7.0007.20060301165555.0000
    Jun 20, 2007 11:54:26... Info: SDM operation mode successfully set to: Integrated
    Jun 20, 2007 11:54:27... Info: JStartupFramework is requesting to start the SDM Server.
    Jun 20, 2007 11:54:27... Info: Start the SDM Server integrated in the JStartupFramework.
    Jun 20, 2007 11:54:27... Info: Initializing Network Manager (50117)
    Jun 20, 2007 11:54:28... Info: Starting SDM Server listening on port 50118
    Jun 20, 2007 11:54:28... Info: SDM started successfully.
    Jun 20, 2007 11:54:43... Info: Opened client connection to 10.96.235.87 (IP address 10.96.235.87/10.96.235.87, remote port 1087)
    Jun 20, 2007 11:54:43... Error: Request for Logon rejected because of version conflict  - Server version 1.60 , Gui version 1.70
    Jun 20, 2007 11:54:47... Info: Close client connection to 10.96.235.87/10.96.235.87, remote port 1087
    Jun 20, 2007 11:54:58... Info: Opened client connection to 10.96.235.87 (IP address 10.96.235.87/10.96.235.87, remote port 1104)
    Jun 20, 2007 11:54:58... Error: Request for Logon rejected because of version conflict  - Server version 1.60 , Gui version 1.70
    Jun 20, 2007 11:54:59... Info: Close client connection to 10.96.235.87/10.96.235.87, remote port 1104
    Jun 20, 2007 11:56:07... Info: Opened client connection to 10.96.235.87 (IP address 10.96.235.87/10.96.235.87, remote port 1127)
    Jun 20, 2007 11:56:55... Info: -
    Starting deployment -
    Jun 20, 2007 11:56:55... Info: Error handling strategy: OnErrorStop
    Jun 20, 2007 11:56:55... Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
    Jun 20, 2007 11:56:55... Info: Update strategy: UpdateAllVersions
    Jun 20, 2007 11:56:55... Info: Starting deployment prerequisites:
    Jun 20, 2007 11:56:55... Info: Loading selected archives...
    Jun 20, 2007 11:56:55... Info: Loading archive 'C:\usr\sap\S01\JC01\SDM\program\temp\temp63662MDMJAVAAPI05_1.sca'
    Jun 20, 2007 11:57:06... Info: Selected archives successfully loaded.
    Jun 20, 2007 11:57:06... Info: Actions per selected component:
    Jun 20, 2007 11:57:06... Info: Update: Selected development component 'com.sap.mdm.tech.mdm4j'/'sap.com'/'SAP AG'/'5.50.20070605165506.0000' updates currently deployed development component 'com.sap.mdm.tech.mdm4j'/'sap.com'/'localhost'/'2006.04.23.12.11.53'.
    Jun 20, 2007 11:57:06... Info: Update: Selected development component 'com.sap.mdm.tech.connector'/'sap.com'/'SAP AG'/'5.50.20070605165506.0000' updates currently deployed development component 'com.sap.mdm.tech.connector'/'sap.com'/'SAP AG'/'2006.04.23.12.11.53'.
    Jun 20, 2007 11:57:06... Info: Initial deployment: Selected software component 'MDM_JAVA_API'/'sap.com'/'SAP AG'/'1000.5.50.5.1.20070605171216' will be deployed.
    Jun 20, 2007 11:57:06... Info: Ending deployment prerequisites. All items are correct.
    Jun 20, 2007 11:57:07... Info: Saved current Engine state.
    Jun 20, 2007 11:57:07... Info: Starting: Update: Selected development component 'com.sap.mdm.tech.mdm4j'/'sap.com'/'SAP AG'/'5.50.20070605165506.0000' updates currently deployed development component 'com.sap.mdm.tech.mdm4j'/'sap.com'/'localhost'/'2006.04.23.12.11.53'.
    Jun 20, 2007 11:57:07... Info: SDA to be deployed: C:\usr\sap\S01\JC01\SDM\root\origin\sap.com\com.sap.mdm.tech.mdm4j\SAP AG\5.50.20070605165506.0000\com.sap.mdm.tech.mdm4j.sda
    Jun 20, 2007 11:57:07... Info: Software type of SDA: library
    Jun 20, 2007 11:57:08... Info: ***** Begin of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
    Jun 20, 2007 11:57:14... Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
    Jun 20, 2007 11:57:14... Error: Aborted: development component 'com.sap.mdm.tech.mdm4j'/'sap.com'/'SAP AG'/'5.50.20070605165506.0000', grouped by :
    Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
    com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [SUSOSG112] with user name: [Administrator]
                        Check your login information.
                        Exception is:
    com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.]
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineCompOnlineDeployerImpl.checkLoginCredentials.DMEXC)
    Jun 20, 2007 11:57:18... Info: Starting: Initial deployment: Selected software component 'MDM_JAVA_API'/'sap.com'/'SAP AG'/'1000.5.50.5.1.20070605171216' will be deployed.
    Jun 20, 2007 11:57:18... Error: Aborted: software component 'MDM_JAVA_API'/'sap.com'/'SAP AG'/'1000.5.50.5.1.20070605171216':
    No further description found.
    Jun 20, 2007 11:57:21... Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
    Jun 20, 2007 11:57:21... Error: -
    At least one of the Deployments failed -
    Jun 20, 2007 11:57:23... Info: Delete the files from the <SDM_HOME>/temp
    Jun 20, 2007 11:57:24... Info: Close client connection to 10.96.235.87/10.96.235.87, remote port 1127
    Jun 20, 2007 12:00:50... Info:
    Jun 20, 2007 12:00:50... Info: ===============================================
    Jun 20, 2007 12:00:50... Info: =   Starting to execute command 'remotegui'   =
    Jun 20, 2007 12:00:50... Info: ===============================================
    Jun 20, 2007 12:00:54... Info: SDM started successfully.
    Jun 20, 2007 12:01:57... Info: Opened client connection to SUSOSG112.na.o-i.test (IP address SUSOSG112.na.o-i.test/10.104.96.118, remote port 2570)
    Jun 20, 2007 12:01:57... Info: Request for Logon as admin accepted

  • Problem with SAP service not starting

    Hi
    The service SAP<sid>_00 service in services.msc is  not running and when i try to start it, it is throwing message like <b>"Some services stop automatically when they have no work to do"</b>. The startup type is automatic. What shall i do to start this service. The SAP system as a result not getting listed in SAP MMC.
    Please advise me in this regard
    Thanks,
    Ganesh N

    it will check the existence of $(DIR_INSTANCE)\work and will change its current working directory to this directory.
    the service is started using a Startprofile.
    If $(DIR_INSTANCE) is not explicitly is set in the Startprofile it defaults to
    saplocalhost\saploc\$(SAPSYSTEMNAME)\$(INSTANCE_NAME).
    saplocalhost\saploc is translated to the directory structure if a share saploc exists on the local computer.
    the share saploc was recreated (in other words you create a share named SAPLOC pointing to a different directory than <sapdrive>:\usr\sap) you will get this error message.
    $(xxx) are possible profile parameters in start and instance profiles.
    DIR_INSTANCE is normally not set
    SAPSYSTEMNAME and INSTANCE_NAME are set in any case.
    Peter
    SAPLOC can only exist once on an application server.
    regards
    Peter

  • Message bean does not start automatically during application server startup

    I have a message bean that does not start up during application server startup. I am able to successfully start the application manually using the visual admin tool.I searched the logs and found the following error. The error references the "QueueConnectionFactory" is not deployed or is not started. I have check and the "QueueConnectiopnFactory" is deployed. Is this a problem with the application trying to start before the "QueueConnectionFactory"? Is thier a way to define a dependency on my application not to start until the "QueueConnectionFactory" has been started, if so can how would I define this dependency. Please provide and example.
    Thanks,
    Bill
    #1.5 #001CC4695AD8001A000000100000079C00045DB6C93D4DAD#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Connecting Model Repository ...#
    #1.5 #001CC4695AD8001A000000110000079C00045DB6C93D4E1D#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Checking source path: halliburton.com/hal~usrgrpap#
    #1.5 #001CC4695AD8001A000000120000079C00045DB6C93D4EAC#1228939548538#System.err##System.err#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Error##Plain###[RunTask] The source file/path doesn't exist: halliburton.com/hal~usrgrpap#
    #1.5 #001CC4695AD8001A000000130000079C00045DB6C93D4EF5#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Opening connection to MMR ...#
    #1.5 #001CC4695AD8001A000000140000079C00045DB6C93D69D0#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Start local transaction ...#
    #1.5 #001CC4695AD8001A000000150000079C00045DB6C93D6B5A#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Commit ...#
    #1.5 #001CC4695AD8001A000000160000079C00045DB6C93D6C8B#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Running task 'com.sap.ip.mmr.db.tasks.TaskUndeployFromDB' ...#
    #1.5 #001CC4695AD8001A000000170000079C00045DB6C93D8E6C#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Close connection to Model Repository ...#
    #1.5 #001CC4695AD8001A000000180000079C00045DB6C93D8EE5#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###done.#
    #1.5 #001CC4695AD80018000000000000171400045DBBE9BCCED0#1228961568691#com.sap.engine.services.connector##com.sap.engine.services.connector######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error##Plain###ResourceObjectFactory.getObjectInstance(), Error: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                    at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                    at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                    at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                    at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                    at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                    at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    #1.5 #001CC4695AD80018000000010000171400045DBBE9BCE3CD#1228961568691#com.sap.engine.services.jndi##com.sap.engine.services.jndi######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Warning#1#/System/Audit#Java###Exception #1#com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                    at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                    at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                    at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                    at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                    at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                    at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                    ... 24 more
    #1.5 #001CC4695AD80018000000030000171400045DBBE9BDBF4A#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#deploy_5029##Exception in operation startApp with application halliburton.com/halusrgrpap.#2#startApp#halliburton.com/halusrgrpap#
    #1.5 #001CC4695AD80018000000040000171400045DBBE9BDC46C#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception in operation startApp with application halliburton.com/hal~usrgrpap.
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:394)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:367)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                    at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                    at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                    at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                    ... 12 more
    Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
                    at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                    at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                    ... 16 more
    Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                    ... 19 more
    Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                    ... 20 more
    Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                    at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                    ... 24 more
    #1.5 #001CC4695AD80018000000060000171400045DBBE9BE0AF5#1228961568769#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Plain###
    Operation startApp over application halliburton.com/hal~usrgrpap finished with errors on server 105677750. For more detailed information see traces of Deploy Service.#
    #1.5 #001CC4695AD80018000000080000171400045DBBE9BE27D1#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#ejb_2119##Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.#1#com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP#
    #1.5 #001CC4695AD80018000000090000171400045DBBE9BE2842#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                    at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                    at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                    at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                    at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                    at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                    at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
                    at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                    at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                    at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                    ... 16 more
    Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
                    at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                    ... 19 more
    Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at javax.naming.InitialContext.lookup(InitialContext.java:347)
                    at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                    ... 20 more
    Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                    at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                    at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                    ... 24 more
    #1.5 #001CC4695AD80019000000000000171400045DBBEB38B908#1228961593581#com.sap.jpe.engine.impl.common.AnalyzerModel#sap.com/com.sapportals.supportplatform#com.sap.jpe.engine.impl.common.AnalyzerModel#Administrator#67####43c8e9d0c72911ddcedd001cc4695ad8#SAPEngine_Application_Thread[impl:3]_38##0#0#Error##Plain###Exception while loading class: com.sapportals.supportplatform.plugins.portal.connectors.ConnectorGatewayServiceCheck
    java.lang.NoClassDefFoundError: com/sapportals/portal/prt/resource/ResourceException
                    at java.lang.Class.getDeclaredConstructors0(Native Method)
                    at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)
                    at java.lang.Class.getConstructor0(Class.java:1930)
                    at java.lang.Class.newInstance0(Class.java:278)
                    at java.lang.Class.newInstance(Class.java:261)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadClass(PluginCollector.java:881)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:387)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:274)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadPluginsFromJarFile(PluginCollector.java:169)
                    at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadFromExtDirectory(PluginCollector.java:121)
                    at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:411)
                    at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:399)
                    at com.sapportals.supportplatform.SupportPlatform.init(SupportPlatform.java:81)
                    at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:59)
                    at java.security.AccessController.doPrivileged(Native Method)
                    at javax.security.auth.Subject.doAs(Subject.java:379)
                    at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:141)
                    at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
                    at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
                    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                    at java.security.AccessController.doPrivileged(Native Method)
                    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

    I though the same thing, but XE LISTENER is running on localhost and port 1522. On the other hand XE have local_listener explicitly set to the very same connection descriptor. Even XE installation was second on this server.
    I've could change that yes, but the startup script doesn't seemed to have this mind.
    Regards,
    Sve

  • PI7.11(PI7.1 EHP1) sapcpe.exe can not start after upgrade tokenerl  patch65

    Hi,
      When I upgrade PI7.11 kernel (On Operator system WIN2003 server x64 64BIT) from patch level 62 to patch level 65
      or higher level 67 or71   with JSPM,
      after deploy SAP can't be started with error that sapcpe.exe can not start and in 'RED' status.
      It's worked before patch level 62.
      Did anybody occur the same problem?
      Can you give me some advice?
      In my WIN2003 server x64, I have the follow DLL libraries:
      Microsoft redistributable runtime DLLs VS2005 SP1(X86)
      Microsoft redistributable runtime DLLs VS2005 SP1(X86_X64)
      Microsoft redistributable runtime DLLs VS2005(X86)
      Microsoft Visual C++ 2005 redistributable
      Microsoft Visual C++ 2005 redistributable(X64)
      Microsoft Visual C++ 2008 redistributable SP1(X64)
    Edited by: IBM China on Feb 4, 2010 12:56 PM

    >   after deploy SAP can't be started with error that sapcpe.exe can not start and in 'RED' status.
    Please check your event log and see if you use the current runtime. A new runtime library is necessary to fix an ATL security issue, see
    Note 1375494 - SAP system does not start after applying SAP kernel patch
    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 
    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.

  • 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

  • A4H and HDB systems not starting in SAP MMC for BW on HANA trial

    Hi,
    I followed all the steps to create an account in AWS and activate a trial version of SAP BW 7.4 on HANA and SAP BO 4.1. The instance activated correctly in the SAP CAL with a green status. The instance was created in the region us-east-1c. I am currently in Australia.
    But when I logon with the remote desktop, and go to the SAP MMC, I see that the A4H and HDB systems have not started and are not green. When I try to start them manually I get the error below. Please help. My SDN userid is P052405.

    Hi All,
    The error was fixed after I rebooted the instance in the SAP CAL.

  • SDM will not start when mode is "standalone"

    SolMan 7.1, Windows 2008 R2, SQL Server 2008
    I'm attempting to deploy the SCA files that came with the SPS03 on the install kit.  The SDM is running OK in integrated mode, and I can stop and start the SDM via the Windows MMC or the command line.
    However, after I change the mode to "standalone", I cannot get the SDM to start
    Logs follow in subsequent posts to this thread.
    NOTE Despite what it says in the log and at the end of the command output, when the Operationmode for JStartupFramework is set to "standalone"...
    There is no Return Code line
    The StartServer command does not complete, and
    the SDM is not available,
    The dev_sdm and std.sdm files only contain information from when SDM is running, in integrated mode.
    Any information or suggestions will be greatfully received.
    Edited by: Martin English on Dec 21, 2011 9:30 AM

    Output from StartServer.bat
    E:\usr\sap\MSM\DVEBMGS10\SDM\program>StartServer.bat
    E:\usr\sap\MSM\DVEBMGS10\SDM\program>set sdm_java_home=C:/j2sdk1.4.2_34-x64
    E:\usr\sap\MSM\DVEBMGS10\SDM\program>set sdm_64bit_switch=
    E:\usr\sap\MSM\DVEBMGS10\SDM\program>set sdm_heap_size=512
    E:\usr\sap\MSM\DVEBMGS10\SDM\program>set sdm_java_params=
    E:\usr\sap\MSM\DVEBMGS10\SDM\program>set sdm_memory_switch=-Xmx512M
    E:\usr\sap\MSM\DVEBMGS10\SDM\program>set sdm_com="C:/j2sdk1.4.2_34-x64\bin\java" -Xmx512M -Dsun.java2d.noddraw=true -Duser.language=en -jar "E:\usr\sap\MSM\DVEBMGS10\SDM\program\bin\SDM.jar"
    E:\usr\sap\MSM\DVEBMGS10\SDM\program>"C:/j2sdk1.4.2_34-x64\bin\java" -Xmx512M -Dsun.java2d.noddraw=true -Duser.language=en -jar "E:\usr\sap\MSM\DVEBMGS10\SDM\program\bin\SDM.jar" server "sdmhome=E:\usr\sap\MSM\DVEBMGS10\SDM\program"
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItemstartServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    Starting SDM - Software Deployment Manager...
    tc/SL/SDM/SDM/sap.com/SAP AG/7.0204.20100323143211.0000
    JStartupFramework is active
    Operation mode of SDM in JStartupFramework is "Standalone". Simply start the server.
    Initializing Network Manager (51017)
    Starting SDM Server listening on port 51018
    SDM started successfully.
    Redirecting output to the two files "E:\usr\sap\MSM\DVEBMGS10\SDM\program\log\sdm_server.out" and "E:\usr\sap\MSM\DVEBMGS10\SDM\program\log\sdm_server.err" respectively.

Maybe you are looking for

  • Problem in assigning Chart of Dep to Co. Code

    Hi, I'm not able to assign Chart of Dep to Co. Code (T Code : OAOB). Every time I'm getting the following message:- <i>"Inconsistency between FI company code VIKI and chart of deprec. VIKI"</i> Please help. Regards, Vikas Malhotra

  • Jagged text when displaying PDF in Acrobat or Reader, not Preview

    when viewing PDFs inside Acrobat 9 or Reader X, most fonts appear jagged, whereas they look perfect in Preview.  this problem persists, even at even resolutions like 100%, 150%, 200%, and 400%.  everything looks great when printed from Acrobat, Reade

  • 870A-G54 Wont Detect IDE

    Trying to boot up a brand new 870A and it wont detect my IDE CD drive. I've tried 2 different drives and still nothing. The sata HDD is fine. Any suggestions?

  • E-mail to contact Apple?

    i want to provide positive feedback to apple regarding a support employee, does anyone have an e-mail i can contact them on?

  • Unofficial chargers causing jerky / choppy / jumpy / inaccurate iPhone touchscreen

    Today I finally discovered the cause of an issue that has bugged me for over a year and wanted to share it here. Basically I was having lots of issues with the touchscreen being jerky / choppy / jumpy... It kept being inaccurate, thinking I was tappi