Unable to create tickt in service desk - Solution manage.

Hello,
I have implemented service desk ( Solution manager) and It is working fine for most of the system but i am getting error while creating a ticket in service desk for one system.
Due to some RFC connection problem i have regenerated the RFC ( trusted , Read and TMW) from Solman to Satellite system.
and now I am not bale to create ticket for that system.
Error message :
The URL http://cismp.cargotec.com:8014/sap/bc/bsp/sap/dswpnotifcreate/msg_new.do was not called due to an error.
Note
The following error text was processed in the system SMP : Error SYSTEM_CORE_DUMPED occured. P1=11
The error occurred on the application server cismp_SMP_14 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: MSG_SUBMIT of program CL_DSMOP_BSP_NOTI_MODEL=======CP
Method: DO_HANDLE_EVENT of program CL_DSMOP_BSP_NOTI_CTRL========CP
Method: DISPATCH_INPUT of program CL_BSP_CONTROLLER2============CP
Method: DO_REQUEST of program CL_DSMOP_BSP_NOTI_CTRL========CP
Method: DO_REQUEST of program CL_BSP_CTRL_ADAPTER===========CP
Method: ON_REQUEST of program CL_BSP_RUNTIME================CP
Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_HTTP_EXT_BSP===============CP
Method: EXECUTE_REQUEST_FROM_MEMORY of program CL_HTTP_SERVER================CP
Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
Module: %_HTTP_START of program SAPMHTTP
Can any body guide me what should be done to resolve the issue.

Hi Prakhar,
As i mentioned workcenter is working fine for all other systems. and user have all roles same as in other  systems.
BP is created and we are trying to create ticket from Solman itself  so there is no point to maintain bCOS_CUST table.
but still we are not able to create ticket only for one system.
Error Message :
Error when processing your request
What has happened?
The URL http://cismp.cargotec.com:8014/sap/bc/bsp/sap/dswpnotifcreate/msg_new.do was not called due to an error.
Note
The following error text was processed in the system SMP : Error SYSTEM_CORE_DUMPED occured. P1=11
The error occurred on the application server cismp_SMP_14 and in the work process 1 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: MSG_SUBMIT of program CL_DSMOP_BSP_NOTI_MODEL=======CP
Method: DO_HANDLE_EVENT of program CL_DSMOP_BSP_NOTI_CTRL========CP
Method: DISPATCH_INPUT of program CL_BSP_CONTROLLER2============CP
Method: DO_REQUEST of program CL_DSMOP_BSP_NOTI_CTRL========CP
Method: DO_REQUEST of program CL_BSP_CTRL_ADAPTER===========CP
Method: ON_REQUEST of program CL_BSP_RUNTIME================CP
Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_HTTP_EXT_BSP===============CP
Method: EXECUTE_REQUEST_FROM_MEMORY of program CL_HTTP_SERVER================CP
Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
Module: %_HTTP_START of program SAPMHTTP
What can I do?
If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system SMP in transaction ST22.
If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server cismp_SMP_14 in transaction SM21.
If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 1 in transaction ST11 on the application server cismp_SMP_14 . In some situations, you may also need to analyze the trace files of other work processes.
If you do not yet have a user ID, contact your system administrator.
Error code: ICF-IE-http -c: 011 -u: XABHYABH -l: E -s: SMP -i: cismp_SMP_14 -w: 1 -d: 20091006 -t: 141511 -v: RABAX_STATE -e: SYSTEM_CORE_DUMPED
Regards,
Bhavesh

Similar Messages

  • Update User Status at Service Desk Solution Manager SP17

    Hi, my name is Tomas Piqueres and I'm working with Solution Manager SP 17.
    Service Desk scenario is working but I have an issue that I explain below:
    I have a message that I'm not able to solve, so I send it to SAP. When SAP returns it to me, I have two status for the same message:
    -User status
    -Status SAP
    The job "refresh message status" is working, so Status SAP is refreshed successfully. The problem is that when Status SAP changes, the User Status doesn't change automatically.
    Please, could you help me?
    Thanks and regards,
    Tomas.

    Hey Rohit,
    I believe your first issue has been answered correctly. As far as your second issue is concerned.
    The SAP Status field only gets filled up when the message is forwarded to SAP Support. This field is set by SAP Support itself. You dont need to manage it.
    As far as Reported by is concerned, thats what you have to configure. For that to be working you first need to create business partners of your users in the satellite system. Eg.  If you are raising a message from userA from your production system. You need to create a business partner of that user in Solution Manager. A unique ID is maintained related to the user and system. Also you will have to maintain his "employee data" , specifically his SAP user id.
    Hope this helps.
    Regards,
    Bilal Nazir

  • Unable to create a business service from a jca file

    I have taken a jca file of a file adapter from Oracle JDeveloper and I am trying to create a business service though eclipse for OSB.
    But I am unable to create a business service as the jca protocol is NOT available in the "Transport Configuration" section of a business service.
    I have got OSB 11.1.1.3 and wls 10.3.3.0 installed along with the corresponding integrated eclipse(oepe_11gR1PS2).
    Pls suggest!

    Refer this for the solution
    Business service NOT getting configured from jca file in Windows 7

  • (model.cpp (4051)) SBL-DAT-00227: Unable to create the Business Service 'EAI Outbound Service'

    Hello,
    I'm self-study integrating Siebel with SOA
    I just set up windown 2003 Siebel 8.1.1.11 (32-bit)
    I start Siebel Server error log file:
    >>>>> InfraEAIOutbound_0021_22020098.log <<<<<
    2021 2014-04-15 11:27:34 0000-00-00 00:00:00 +0700 00000000 001 003f 0001 09 InfraEAIOutbound 22020098 724 4056 C:\Siebel\8.1.1.11.0\ses\siebsrvr\log\InfraEAIOutbound_0021_22020098.log 8.1.1.11 [23030] ENU
    ServerLog    LstnObjInherit    3    000064e0534c0428:0    2014-04-15 110    2014-04-15 11:27:34    Inherited listening object for port 49157
    ServerLog    LstnObjPrivCreate    3    000064e2534c0428:0    2014-04-15 110    2014-04-15 11:27:34    Created port 49170 for EAI Outbound Server
    GenericLog    GenericError    1    000064e2534c0428:0    2014-04-15 110    2014-04-15 11:27:53    [AUDIT_LOG]: Global audit cache load successful.
    ObjMgrLog    Error    1    000064e2534c0428:0    2014-04-15 110    2014-04-15 11:28:11    (model.cpp (4051)) SBL-DAT-00227: Unable to create the Business Service 'EAI Outbound Service'
    GenericLog    GenericError    1    000064e2534c0428:0    2014-04-15 110    2014-04-15 11:28:11    Object manager error: ([0] Unable to create the Business Service 'EAI Outbound Service'(SBL-DAT-00227) (0x7500e3))
    GenericLog    GenericError    1    000064e2534c0428:0    2014-04-15 110    2014-04-15 11:28:11    Object manager error: ([1] Could not find 'Class' named 'EAI Outbound Service'. This object is inactive or nonexistent.(SBL-DAT-00144) (0x750090))
    GenericLog    GenericError    1    000064e2534c0428:0    2014-04-15 110    2014-04-15 11:28:11    ( (0) err=2818155 sys=7667856) SBL-OMS-00107: Object manager error: ([1] Could not find 'Class' named 'EAI Outbound Service'. This object is inactive or nonexistent.(SBL-DAT-00144) (0x750090))
    GenericLog    GenericError    1    000064e2534c0428:0    2014-04-15 110    2014-04-15 11:28:11    ( (0) err=2818155 sys=7667939) SBL-OMS-00107: Object manager error: ([0] Unable to create the Business Service 'EAI Outbound Service'(SBL-DAT-00227) (0x7500e3))
    GenericLog    GenericError    1    000064e2534c0428:0    2014-04-15 110    2014-04-15 11:28:11    (bsvcmgr.cpp (941) err=2818250 sys=0) SBL-OMS-00202: Error 7667939 loading Business Service "EAI Outbound Service"
    GenericLog    GenericError    1    000064e2534c0428:0    2014-04-15 110    2014-04-15 11:28:11    (bsvcmgr.cpp (1044) err=2818250 sys=0) SBL-OMS-00202: Error 7667939 loading Business Service "EAI Outbound Service"
    GenericLog    GenericError    1    000064e2534c0428:0    2014-04-15 110    2014-04-15 11:28:11    (smimtsrv.cpp (1203) err=2818250 sys=0) SBL-OMS-00202: Error 7667939 loading Business Service "EAI Outbound Service"
    SmiLayerLog    Error    1    000064e2534c0428:0    2014-04-15 110    2014-04-15 11:28:11    Terminate process due to unrecoverable error: 2818250. (Main Thread)
    LOG FILE:
    >>>> SIEBELEVAL.Eval_1.log <<<<<
    2021 2014-04-15 11:27:05 0000-00-00 00:00:00 +0700 00000000 001 003f 0001 09 SiebSrvr 0 2404 2876 C:\Siebel\8.1.1.11.0\ses\siebsrvr\log\SIEBELEVAL.Eval_1.log 8.1.1.11 [23030] ENU
    ServerLog    ServerStartup    1    00006142534c0428:0    2014-04-15 110    2014-04-15 11:27:05    Siebel Enterprise Applications Server is starting up
    ServerLog    LstnObjCreate    1    00006231534c0428:0    2014-04-15 110    2014-04-15 11:27:05    Created port 49156 for Business Integration Batch Manager
    ServerLog    LstnObjCreate    1    00006231534c0428:0    2014-04-15 110    2014-04-15 11:27:05    Created port 49157 for EAI Outbound Server
    ServerLog    LstnObjCreate    1    00006232534c0428:0    2014-04-15 110    2014-04-15 11:27:05    Created port 49158 for JMS Receiver
    ServerLog    LstnObjCreate    1    00006232534c0428:0    2014-04-15 110    2014-04-15 11:27:05    Created port 49159 for Business Integration Manager
    ServerLog    LstnObjCreate    1    00006232534c0428:0    2014-04-15 110    2014-04-15 11:27:05    Created port 49160 for File System Manager
    ServerLog    LstnObjCreate    1    00006232534c0428:0    2014-04-15 110    2014-04-15 11:27:05    Created port 49161 for Server Request Processor
    ServerLog    LstnObjCreate    1    00006232534c0428:0    2014-04-15 110    2014-04-15 11:27:05    Created port 49162 for Siebel Administrator Notification Component
    ServerLog    LstnObjCreate    1    00006232534c0428:0    2014-04-15 110    2014-04-15 11:27:05    Created port 49163 for Server Request Broker
    ServerLog    LstnObjCreate    1    00006232534c0428:0    2014-04-15 110    2014-04-15 11:27:05    Created port 49164 for Server Manager
    ServerLog    LstnObjCreate    1    00006232534c0428:0    2014-04-15 110    2014-04-15 11:27:05    Created port 2321 for Siebel Connection Broker
    ServerLog    LstnObjCreate    1    00006233534c0428:0    2014-04-15 110    2014-04-15 11:27:05    Created port 49165 for Forecast Service Manager
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:05    SRBroker    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:05    ServerMgr    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:05    ServerMgr    INITIALIZED    Component has initialized (no spawned procs).
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:05    SiebSrvr    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:05    SiebSrvr    INITIALIZED    Component has initialized (no spawned procs).
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:05    SCBroker    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:05    SrvrSched    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:05    SrvrSched    INITIALIZED    Component has initialized (no spawned procs).
    ServerLog    ProcessCreate    1    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:05    Created multithreaded server process (OS pid =     2800    ) for SRBroker
    ServerLog    ProcessCreate    1    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:05    Created server process (OS pid =     2408    ) for SCBroker
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:05    SCBroker    INITIALIZED    Component has initialized.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:10    SRBroker    INITIALIZED    Component has initialized.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:10    FSMSrvr    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:10    SRProc    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:10    SvrTblCleanup    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:10    SvrTaskPersist    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:10    AdminNotify    STARTING    Component is starting up.
    ServerLog    ProcessCreate    1    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:10    Created multithreaded server process (OS pid =     3404    ) for FSMSrvr
    ServerLog    ProcessCreate    1    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:10    Created multithreaded server process (OS pid =     3796    ) for SRProc
    ServerLog    ProcessCreate    1    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:10    Created server process (OS pid =     3852    ) for SvrTblCleanup
    ServerLog    ProcessCreate    1    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:10    Created server process (OS pid =     3104    ) for SvrTaskPersist
    ServerLog    ProcessCreate    1    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:10    Created multithreaded server process (OS pid =     3876    ) for AdminNotify
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:10    FSMSrvr    INITIALIZED    Component has initialized.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:15    SRProc    INITIALIZED    Component has initialized.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    SvrTblCleanup    INITIALIZED    Component has initialized.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    SvrTaskPersist    INITIALIZED    Component has initialized.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    AdminNotify    INITIALIZED    Component has initialized.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    FINSObjMgr_enu    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    FINSeSalesObjMgr_enu    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    FINSeBrokerageObjMgr_enu    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    FINSConsoleObjMgr_enu    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    INSeServiceObjMgr_enu    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    FINSeChannelObjMgr_enu    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    FINSeBankingObjMgr_enu    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    FINSeEnrollmentObjMgr_enu    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    SSEObjMgr_enu    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    FINSeCustomerObjMgr_enu    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    MqSeriesAMIRcvr    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    MqSeriesAMIRcvr    INITIALIZED    Component has initialized (no spawned procs).
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    BusIntBatchMgr    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    SMCObjMgr_enu    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    MSMQRcvr    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    MSMQRcvr    INITIALIZED    Component has initialized (no spawned procs).
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    InfraEAIOutbound    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    MqSeriesSrvRcvr    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    MqSeriesSrvRcvr    INITIALIZED    Component has initialized (no spawned procs).
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    JMSReceiver    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    BusIntMgr    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    EIM    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    EIM    INITIALIZED    Component has initialized (no spawned procs).
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    EAIObjMgr_enu    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    CustomAppObjMgr_enu    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    SMQReceiver    STARTING    Component is starting up.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    SMQReceiver    INITIALIZED    Component has initialized (no spawned procs).
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    FcstSvcMgr    STARTING    Component is starting up.
    ServerLog    ServerStarted    1    00006499534c0428:0    2014-04-15 110    2014-04-15 11:27:16    Siebel Application Server is ready and awaiting requests
    ServerLog    ProcessCreate    1    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    Created server process (OS pid =     2488    ) for FINSObjMgr_enu
    ServerLog    ProcessCreate    1    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:16    Created server process (OS pid =     2540    ) for FINSeSalesObjMgr_enu
    ServerLog    ProcessCreate    1    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:17    Created server process (OS pid =     3568    ) for FINSeBrokerageObjMgr_enu
    ServerLog    ProcessCreate    1    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:17    Created server process (OS pid =     2640    ) for FINSConsoleObjMgr_enu
    ServerLog    ProcessCreate    1    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:17    Created server process (OS pid =     4092    ) for INSeServiceObjMgr_enu
    ServerLog    ProcessCreate    1    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:17    Created server process (OS pid =     2812    ) for FINSeChannelObjMgr_enu
    ServerLog    ProcessCreate    1    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:17    Created server process (OS pid =     316    ) for FINSeBankingObjMgr_enu
    ServerLog    ProcessCreate    1    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:17    Created server process (OS pid =     3068    ) for FINSeEnrollmentObjMgr_enu
    ServerLog    ProcessCreate    1    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:17    Created server process (OS pid =     2572    ) for SSEObjMgr_enu
    ServerLog    ProcessCreate    1    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:17    Created server process (OS pid =     2940    ) for FINSeCustomerObjMgr_enu
    ServerLog    ProcessCreate    1    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:17    Created multithreaded server process (OS pid =     1804    ) for BusIntBatchMgr
    ServerLog    ProcessCreate    1    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:17    Created server process (OS pid =     3288    ) for SMCObjMgr_enu
    ServerLog    ProcessCreate    1    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:18    Created multithreaded server process (OS pid =     724    ) for InfraEAIOutbound
    ServerLog    ProcessCreate    1    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:18    Created multithreaded server process (OS pid =     2296    ) for JMSReceiver
    ServerLog    ProcessCreate    1    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:18    Created multithreaded server process (OS pid =     2976    ) for BusIntMgr
    ServerLog    ProcessCreate    1    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:18    Created server process (OS pid =     3168    ) for EAIObjMgr_enu
    ServerLog    ProcessCreate    1    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:18    Created server process (OS pid =     2448    ) for CustomAppObjMgr_enu
    ServerLog    ProcessCreate    1    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:18    Created multithreaded server process (OS pid =     3080    ) for FcstSvcMgr
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:28    FINSObjMgr_enu    INITIALIZED    Component has initialized.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:28    FINSeBrokerageObjMgr_enu    INITIALIZED    Component has initialized.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:28    FINSConsoleObjMgr_enu    INITIALIZED    Component has initialized.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:33    FINSeSalesObjMgr_enu    INITIALIZED    Component has initialized.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:33    SSEObjMgr_enu    INITIALIZED    Component has initialized.
    ServerLog    ComponentUpdate    2    00001cbf534c0964:0    2014-04-15 110    2014-04-15 11:27:33    SMCObjMgr_enu    INITIALIZED 

    Hi Experts,
    How to configure and launch the Siebel EAI?
    I'm having problems with url: http://ws811/eai_enu/start.swe?SWECmd=Start&SWEHo=ws811
    HTTP 500 - Internal server error
    Internet Explorer
    And the other url is OK:
    http://ws811/sales_ENU/start.swe?SWECmd=Start&SWEHo=ws811
    Please provide solution the asap.

  • Creating a new user in solution manager?

    Dear All,
          How to create a new user in solution manager for creating an incident?

    prathish5,
    I did this in our SolMan by following the instructions provided by a SAP document called: "Service Desk VAR Setup Master Data". I got it from the Support Portal, though I can't seem to find it now so I can't provide a link at this time.
    Anyway, assuming that your SolMan is already able to download your master data (and/or your customers', if you are a VAR), these are the steps suggested by the guide:
    1) The message creator (aka Key User) should have the following authorization roles:
    SAP_SUPPDESK_CREATE
    SAP_SUPPCF_CREATE
    SAP_SMWORK_BASIC
    SAP_SMWORK_INCIDENT_MAN
    See also SAP note 834534.
    A best practice is to create a Z copy of all of these roles (use transaction PFCG), so you can manage them and change them around if you need to. Just make sure to "activate" all the authorizations of your copy of the roles:
    - Open the roles in tr. PFCG;
    - Select Authorizations, and choose Change authorization data;
    - If you get a yellow semaphore, be sure to review the authorizations and fill them according to your security policy. You can assign global permissions for all the authorization objects by double-clicking the yellow semaphore;
    - Generate the profile, then go back and save the role;
    2) Following the guide, with tr. SU01 I created a Template user and called it KEY_USER (make sure the user type is actually Template) and assigned to it the Z roles you created in the step above;
    3) If your SolMan is working properly, you can now use report AI_SDK_SP_GENERATE_BP (tr. SA38) to create the Business Partners and SAP users automatically. The report will log in the Support Portal and read the users which are authorized to open a SAP tickets, and create a BP and user for each of them. Use the Template user KEY_USER created in step 2 as a "Reference user" and all the new users will automatically get the correct autorizations. Also if your SAP Connect (tr. SCOT) is correctly configured, you can choose to send an automatic mail to each user, with their login and generated password.
    Otherwise, you can manually create a user with transactions SU01 and BP - be sure to fill the "Identities" table here - the report AI_SDK_SP_GENERATE_BP makes all these things automatically so it's definitely your best bet.
    4) Your users should now be able to log in with the SAPgui and use transaction CREATE_NOTIF to create a new message in your SolMan. Also if you have done the preparation steps correctly they should also be able to log in your Incident Manager using their browser, and open a message there and also review their past messages.
    Those are just a quick insight of the steps you need to do. This is NOT an easy thing to configure, at least it wasn't for me; if you don't have a reliable guide to follow you're going to struggle: I strongly suggest you browse through the SAP documentations (also the blogs) - http://service.sap.com/xsearch is your best friend!
    I hope this helps a little bit. Good luck.

  • Regarding Monitoring Service for Solution manager

    We need to configure "Monitoring" services in SAP solution manager 7.0.
    Could somebody suggest us what are the main tasks we need to consider for doing Monitoring settings.
    How many Minimum servers required to configure Monitoring services in solution manager system.
    Also if any good document reference for this?
    Thanks

    Hi Jai,
    welcome to sdn.
    COMPONENTS & TOOLS OF SAP NETWEAVER
    SAP Solution Manager
    The SAP Solution Manager application management solution facilitates technical support for distributed systems u2013 with functionality that covers all key aspects of solution deployment, operation, and continuous improvement. A centralized, robust application management and administration solution, SAP Solution Manager combines tools, content, and direct access to SAP to increase the reliability of solutions and lower total cost of ownership.
    With SAP Solution Manager, you can be sure your entire SAP solution environment is performing at its maximum potential. The toolset addresses your entire IT environment, supporting SAP and non-SAP software and covering current and forthcoming SAP solutions. And, as a customer of SAP, you have full access to the core SAP Solution Manager for no extra charge.
    SAP Solution Manager targets both technical and business aspects of your solutions, focusing strongly on core business processes. It supports the connection between business processes and the underlying IT infrastructure. As a result, it eases communication between your IT department and your lines of business. And it ensures that you derive the maximum benefits from your IT investments.
    SAP Solution Manager features and functions include:
    SAP Business Suite implementation and upgrades u2013 SAP Solution Manager provides content that accelerates implementation. Configuration information and a process-driven approach to implementation speed the blueprint, configuration, and final preparation phases. SAP Solution Manager enables efficient project administration and centralized control of cross-component implementations.
    Change control management u2013 SAP Solution Manager controls all software and configuration changes of the IT solution. This includes the approval process for change requests, the deployment of changes, and later analysis of changes. This ensures quality of the solution and enables traceability of all changes.
    Testing u2013 SAP Solution Manager speeds test preparation and execution. It provides a single point of access to the complete system landscape and enables centralized storage of testing material and test results to support cross-component tests.
    IT and application support u2013 The service desk included in SAP Solution Manager helps you manage incidents more efficiently and eases the settlement of support costs. Centralized handling of support messages makes the support organization more efficient.
    Root cause analysis u2013 The diagnostics functions in SAP Solution Manager allow identification, analysis, and resolution of problems, even in heterogeneous environments. This helps to isolate general performance bottlenecks, to isolate exceptional situations, to record the activity of single users or processes, and to identify changes to the productive landscape. As a result, problem resolution is accelerated and business availability increased.
    Solution monitoring u2013 SAP Solution Manager performs centralized, real-time monitoring of systems, business processes, and interfaces, which reduces administration effort. It can even monitor intersystem dependencies. Proactive monitoring helps you avoid critical situations, while automatic notifications enable fast response to issues.
    Service-level management and reporting u2013 SAP Solution Manager allows easy definition of service levels and provides automated reporting. Service reporting covers all systems in the solution landscape and provides a consolidated report containing the information you need to make strategic IT decisions.
    Service processing u2013 SAP Solution Manager makes appropriate service recommendations and delivers SAP support services. These include SAP Safeguarding, which helps you manage technical risk; SAP Solution Management Optimization, which helps you get the most from your SAP solutions; and SAP Empowering, which helps you manage your solutions.
    Administration u2013 Administration tasks are mainly executed locally on the involved systems, but can be accessed and triggered from a central administration console. The administration work center in SAP Solution Manager offers a central entry point and unified access to all SAP technology.
    SAP Solution Manager as the name suggests is for managing the whole gamut of SAP and Non-SAP solutions in the IT Landscape of an organisation. It provides you the tool, content and gateway to create, operate, manage and monitor your solutions over time.
    It provides a range of scenarios to support this. Extending from project management to Solution Monitoring to Service Desk to E-learning Management, it provides an efficient way to carry out a plethora of business tasks.
    SAP Solution Manager is the successor to ASAP ValueSAP. SAP Solution Manager helps in implementing and managing complex system landscapes. Globally systems are getting distributed across geographies and business processes cover more than one system. In such complex scenarios, integrating technical and business requirements is important for the success of IT. SAP Solution Manager provides SAP customers with an efficient means of handling both the technical and business process side of solution implementation .
    As part of SAP Solution Management Solutions, the customers receive best practices relating to:
    - Global Strategy and Service Level Management
    - Business Process Management
    - Management of MySAP Technology
    - Software Change Management
    - Support Desk Management
    SAP delivers this using support programs during implementation of the system solution. Some of the benefits of using SAP's Solution Manager are that it helps:
    - Manages the technical risk associated with the implementation of the solution ensuring technical robustness
    - Helps leverage users core competencies in implementing solutions
    - Ensures solution works as intended with best practices built in.
    see these links...
    http://www.ne-sap-solution-manager.com/
    http://www.saptechies.com/category/sap-solution-manager/
    thanks
    karthik
    reward me if usefull

  • Web service in SOlution Manager

    Hi¡¡¡
    Someone knows how to configurate the web service in solution manager???
    thanks!!!

    Aris´ "administration_guide_aris_s.pdf"
    Chapter 7.1.2.1.3 How to Activate Web Services
    Markus

  • Service Desk - Solution Database - Solution retreival

    I am trying to setup solution database for service desk.
    1. I have set up TREX on the same host
    2. Connected ABAP and TREX through a TCP/IP RFC
    3. Completed configuration for the solution database using the available wizards
    4. CRM_SAF_TOOL- all checks show greens
    I am able to create a solution in a transaction using the "create solution in solution database" link.
    My issue is:
    When I go to another transaction and try to search for a available solution I do get get any results of the search. The short text used of both the transaction for which the solution was created and the transaction from which I am searching the SDB are the same.
    What am I missing?
    Thanks
    Shabna

    Had to generate the index.

  • Service Desk Solution database Dump with Error

    Hi All,
    When i save any solution for service desk , i am getting below Error.Please help me.
    Error when processing your request
    What has happened?
    The URL http://stc.abc.com:8000/sap/bc/webdynpro/sap/wd_sdk_sdb_create_entry/ was not called due to an error.
    Note
         The following error text was processed in the system SOL : The ABAP/4 Open SQL array insert results in duplicate database records. records in the data base.
         The error occurred on the application server stc_SOL_00 and in the work process 0 .
         The termination type was: RABAX_STATE
         The ABAP call stack was:
    Function: ISMV_POST_SYMP of program SAPLISMV
    Function: ISMV_GENERATE_SYMPTOM of program SAPLISMV
    Form: GENERATE_SYMPTOM of program SAPLISMB
    Form: POST_SYMPTOM of program SAPLISMB
    Form: %_PROCESS_P_O_C of program SAPMSSY0
    Form: %_COMMIT of program SAPMSSY0
    Method: CREATE_SDB_SYM_SOL of program CL_SDK_SDB_NOTIFICATION=======CP
    Method: SAVE_WORK of program /1BCWDY/C9V7XAJL5XS3XH4Z7DS0==CP
    Method: IF_COMPONENTCONTROLLER~SAVE_WORK of program /1BCWDY/C9V7XAJL5XS3XH4Z7DS0==CP
    Method: ONACTIONBTN_SAVE of program /1BCWDY/C9V7XAJL5XS3XH4Z7DS0==CP
    What can I do?
         If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system SOL in transaction ST22.
         If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server stc_SOL_00 in transaction SM21.
         If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server stc_SOL_00 . In some situations, you may also need to analyze the trace files of other work processes.
         If you do not yet have a user ID, contact your system administrator.
    Error code: ICF-IE-http -c: 151 -u: ABCSOL -l: E -s: SOL -i: stc_SOL_00 -w: 0 -d: 20090102 -t: 183025 -v: RABAX_STATE -e: SAPSQL_ARRAY_INSERT_DUPREC
    HTTP 500 - Internal Server Error
    Your SAP Internet Communication Framework Team
    Regards
    Andrew

    Hi
    check the sap note  1124452 and implement the correction instruction or make a program with Zcode implementation.
    Reagrs,
    Vijay.

  • Unable to create PR with Service Line & also no entry in ESLH table using

    Hi Experts,
    I am using BAPI => BAPI_REQUISITION_CREATE to create PR and it is successful to create PR but when I try to create PO is become fail (proably missing entry in ESLH table).
    Now my requirement is to create PR with Service Line and an entry in ESLH table (should be filled by SAP automatically). I have been passing the service related/account assigment tables into BAPI but still not working.
    Will you please give a solution to create PR with Service Line and also need an entry in ESLH table (its important to my req)?
    Also provide some input on Service Line, if possible(How to check Service Line for PR + Account Assignment to Service Line + etc.)?
    Note that: If I create PR manually then there have entry in ESLH and hence I can create PO.
    Definately the quick solution help me lot...
    Thanks
    AKG

    Hi Experts,
    I am using BAPI => BAPI_REQUISITION_CREATE to create PR and it is successful to create PR but when I try to create PO is become fail (proably missing entry in ESLH table).
    Now my requirement is to create PR with Service Line and an entry in ESLH table (should be filled by SAP automatically). I have been passing the service related/account assigment tables into BAPI but still not working.
    Will you please give a solution to create PR with Service Line and also need an entry in ESLH table (its important to my req)?
    Also provide some input on Service Line, if possible(How to check Service Line for PR + Account Assignment to Service Line + etc.)?
    Note that: If I create PR manually then there have entry in ESLH and hence I can create PO.
    Definately the quick solution help me lot...
    Thanks
    AKG

  • Please Help! Unable to create a web service.

    Hi all,
    I have created a deployable proxy, a EJB with a stateless session bean, and a enterprise application project with the above ejb added. I add the deployable proxy into ejb, so that i can utilize the interface(web service) provided by the external party. After i implement the code to call the web service from external party in stateless session bean, i should create a web service by right click on session bean>New>Web Service. However, nothing was happened while a pop up window of web service creation wizard should appear. NWDS showed "End Point Doesn't Exist" when i tried to create the web service by File>New>Others>Web Service>Web Service (New VI and WSD).
    Anybody have any idea of it? Your help will be apperciated.
    Warmest Regards,
    Jane

    Hi all,
    I notice that once i implement the interface from deployable proxy, the problem of "SEI doen't exist" appeared.
    Anyone can help pls? anyone encounter the same problem before? It is urgent.
    Thank in advance.
    Warmest Regards,
    Jane

  • J2EE Service in Solution manager can not be started

    Dear Guru,
    I have a problem with my Solution manager J2EE Service. The J2EE can not be started. It's returned code is "-11113". My Solution Manager Server Specification is:
    - SAP Solution Manager 4.0
    - Software component:
    SAP_BASIS       700                     0013
    SAP_ABA              700                     0013
    PI_BASIS              2006_1_700     0003
    ST-PI              2005_1_700     0005
    SAP_BW              700                     0015
    SAP_AP              700                     0009
    BBPCRM              500                     0009
    CPRXRPM              400                     0009
    BI_CONT              703                     0007
    ST              400                     0013
    ST-A/PI              01K_CRM560     0000
    ST-ICO              150_700     0009
    ST-SER              700_2007_1     0004
    - OS: Ms Windows 2003 32 Bit
    - Database: ORACLE 10.2.0.2.0
    - RAM = 1 GByte
    The following is the error message when J2EE service is fail to run:
    Developer Trace:
    trc file: "D:\usr\sap\SMA\DVEBMGS00\work\dev_server0", trc level: 1, release: "700"
    node name   : ID3244050
    pid         : 7532
    system name : SMA
    system nr.  : 00
    started at  : Mon Feb 25 16:13:39 2008
    arguments       :
           arg[00] : D:\usr\sap\SMA\DVEBMGS00\exe\jlaunch.exe
           arg[01] : pf=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
           arg[02] : -DSAPINFO=SMA_00_server
           arg[03] : pf=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
           arg[04] : -DSAPSTART=1
           arg[05] : -DCONNECT_PORT=1130
           arg[06] : -DSAPSYSTEM=00
           arg[07] : -DSAPSYSTEMNAME=SMA
           arg[08] : -DSAPMYNAME=BKKT031A_SMA_00
           arg[09] : -DSAPPROFILE=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
           arg[10] : -DFRFC_FALLBACK=ON
           arg[11] : -DFRFC_FALLBACK_HOST=localhost
    [Thr 2320] Mon Feb 25 16:13:39 2008
    [Thr 2320] *** WARNING => INFO: Unknown property [instance.box.number=SMADVEBMGS00bkkt031a] [jstartxx.c   841]
    [Thr 2320] *** WARNING => INFO: Unknown property [instance.en.host=BKKT031A] [jstartxx.c   841]
    [Thr 2320] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c   841]
    [Thr 2320] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c   841]
    JStartupReadInstanceProperties: read instance properties [D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties]
    -> ms host    : BKKT031A
    -> ms port    : 3901
    -> OS libs    : D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Used property files
    -> files [00] : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : BKKT031A
    -> ms port    : 3901
    -> os libs    : D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID3244000  : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID3244050  : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID3244000            : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
    -> [01] ID3244050            : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
    [Thr 2320] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 2320] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 1544] JLaunchRequestFunc: Thread 1544 started as listener thread for np messages.
    [Thr 8088] WaitSyncSemThread: Thread 8088 started as semaphore monitor thread.
    [Thr 2320] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 2320] CPIC (version=700.2006.09.13)
    [Thr 2320] [Node: server0] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_14
    [Thr 2320] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\SMA\DVEBMGS00\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID3244050]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : C:\j2sdk1.4.2_14
    -> java parameters    : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -XX:MaxPermSize=192M -XX:PermSize=192M -XX:NewSize=86M -XX:MaxNewSize=86M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Dstartup.mode=SAFE -Dstartup.action=UPGRADE
    -> java vm version    : 1.4.2_14-b05
    -> java vm vendor     : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type       : server
    -> java vm cpu        : x86
    -> heap size          : 512M
    -> init heap size     : 512M
    -> root path          : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs
    -> main class         : com.sap.engine.boot.Start
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : D:\usr\sap\SMA\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\SMA\DVEBMGS00\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50021
    -> shutdown timeout   : 120000
    [Thr 2320] JLaunchISetDebugMode: set debug mode [no]
    [Thr 5408] JLaunchIStartFunc: Thread 5408 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 262144 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djava.security.policy=./java.policy
    -> arg[  4]: -Djava.security.egd=file:/dev/urandom
    -> arg[  5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[  6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[  7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[  8]: -Djco.jarm=1
    -> arg[  9]: -XX:MaxPermSize=192M
    -> arg[ 10]: -XX:PermSize=192M
    -> arg[ 11]: -XX:NewSize=86M
    -> arg[ 12]: -XX:MaxNewSize=86M
    -> arg[ 13]: -XX:+DisableExplicitGC
    -> arg[ 14]: -verbose:gc
    -> arg[ 15]: -Xloggc:GC.log
    -> arg[ 16]: -XX:+PrintGCDetails
    -> arg[ 17]: -XX:+PrintGCTimeStamps
    -> arg[ 18]: -Djava.awt.headless=true
    -> arg[ 19]: -Dsun.io.useCanonCaches=false
    -> arg[ 20]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 21]: -XX:SurvivorRatio=2
    -> arg[ 22]: -XX:TargetSurvivorRatio=90
    -> arg[ 23]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
    -> arg[ 24]: -Dstartup.mode=SAFE
    -> arg[ 25]: -Dstartup.action=UPGRADE
    -> arg[ 26]: -Dsys.global.dir=D:\usr\sap\SMA\SYS\global
    -> arg[ 27]: -Dapplication.home=D:\usr\sap\SMA\DVEBMGS00\exe
    -> arg[ 28]: -Djava.class.path=D:\usr\sap\SMA\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\SMA\DVEBMGS00\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 29]: -Djava.library.path=C:\j2sdk1.4.2_14\jre\bin\server;C:\j2sdk1.4.2_14\jre\bin;C:\j2sdk1.4.2_14\bin;D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs;C:\oracle\SMA\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\OpenSSH\bin;C:\Program Files\System Center Operations Manager 2007\;D:\usr\sap\SMA\SYS\exe\uc\NTI386
    -> arg[ 30]: -Dmemory.manager=512M
    -> arg[ 31]: -Xmx512M
    -> arg[ 32]: -Xms512M
    -> arg[ 33]: -DLoadBalanceRestricted=no
    -> arg[ 34]: -Djstartup.mode=JCONTROL
    -> arg[ 35]: -Djstartup.ownProcessId=7532
    -> arg[ 36]: -Djstartup.ownHardwareId=Y0571960686
    -> arg[ 37]: -Djstartup.whoami=server
    -> arg[ 38]: -Djstartup.debuggable=no
    -> arg[ 39]: -DSAPINFO=SMA_00_server
    -> arg[ 40]: -DSAPSTART=1
    -> arg[ 41]: -DCONNECT_PORT=1130
    -> arg[ 42]: -DSAPSYSTEM=00
    -> arg[ 43]: -DSAPSYSTEMNAME=SMA
    -> arg[ 44]: -DSAPMYNAME=BKKT031A_SMA_00
    -> arg[ 45]: -DSAPPROFILE=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
    -> arg[ 46]: -DFRFC_FALLBACK=ON
    -> arg[ 47]: -DFRFC_FALLBACK_HOST=localhost
    -> arg[ 48]: -DSAPSTARTUP=1
    -> arg[ 49]: -DSAPSYSTEM=00
    -> arg[ 50]: -DSAPSYSTEMNAME=SMA
    -> arg[ 51]: -DSAPMYNAME=BKKT031A_SMA_00
    -> arg[ 52]: -DSAPDBHOST=BKKT031A
    -> arg[ 53]: -Dj2ee.dbhost=BKKT031A
    Mon Feb 25 16:13:40 2008
    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/PortalServiceItem startServices
    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
    [Thr 5408] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 7188] Mon Feb 25 16:13:58 2008
    [Thr 7188] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 7188] Mon Feb 25 16:14:02 2008
    [Thr 7188] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 7188] JLaunchISetClusterId: set cluster id 3244050
    [Thr 7188] Mon Feb 25 16:14:03 2008
    [Thr 7188] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 7188] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 5436] Mon Feb 25 16:16:34 2008
    [Thr 5436] JLaunchIExitJava: exit hook is called (rc = -11113)
    [Thr 5436] **********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'
    for additional information and trouble shooting.
    [Thr 5436] Mon Feb 25 16:16:35 2008
    [Thr 5436] JLaunchCloseProgram: good bye (exitcode = -11113)
    trc file: "D:\usr\sap\SMA\DVEBMGS00\work\dev_server0", trc level: 1, release: "700"
    node name   : ID3244050
    pid         : 14568
    system name : SMA
    system nr.  : 00
    started at  : Mon Feb 25 16:16:46 2008
    arguments       :
           arg[00] : D:\usr\sap\SMA\DVEBMGS00\exe\jlaunch.exe
           arg[01] : pf=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
           arg[02] : -DSAPINFO=SMA_00_server
           arg[03] : pf=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
           arg[04] : -DSAPSTART=1
           arg[05] : -DCONNECT_PORT=1130
           arg[06] : -DSAPSYSTEM=00
           arg[07] : -DSAPSYSTEMNAME=SMA
           arg[08] : -DSAPMYNAME=BKKT031A_SMA_00
           arg[09] : -DSAPPROFILE=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
           arg[10] : -DFRFC_FALLBACK=ON
           arg[11] : -DFRFC_FALLBACK_HOST=localhost
    [Thr 14572] Mon Feb 25 16:16:46 2008
    [Thr 14572] *** WARNING => INFO: Unknown property [instance.box.number=SMADVEBMGS00bkkt031a] [jstartxx.c   841]
    [Thr 14572] *** WARNING => INFO: Unknown property [instance.en.host=BKKT031A] [jstartxx.c   841]
    [Thr 14572] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c   841]
    [Thr 14572] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c   841]
    JStartupReadInstanceProperties: read instance properties [D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties]
    -> ms host    : BKKT031A
    -> ms port    : 3901
    -> OS libs    : D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Used property files
    -> files [00] : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : BKKT031A
    -> ms port    : 3901
    -> os libs    : D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID3244000  : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID3244050  : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID3244000            : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
    -> [01] ID3244050            : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
    [Thr 14572] Mon Feb 25 16:16:47 2008
    [Thr 14572] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 14572] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 14664] JLaunchRequestFunc: Thread 14664 started as listener thread for np messages.
    [Thr 14668] WaitSyncSemThread: Thread 14668 started as semaphore monitor thread.
    [Thr 14572] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 14572] CPIC (version=700.2006.09.13)
    [Thr 14572] [Node: server0] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_14
    [Thr 14572] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\SMA\DVEBMGS00\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID3244050]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : C:\j2sdk1.4.2_14
    -> java parameters    : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -XX:MaxPermSize=192M -XX:PermSize=192M -XX:NewSize=86M -XX:MaxNewSize=86M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Dstartup.mode=SAFE -Dstartup.action=UPGRADE
    -> java vm version    : 1.4.2_14-b05
    -> java vm vendor     : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type       : server
    -> java vm cpu        : x86
    -> heap size          : 512M
    -> init heap size     : 512M
    -> root path          : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs
    -> main class         : com.sap.engine.boot.Start
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : D:\usr\sap\SMA\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\SMA\DVEBMGS00\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50021
    -> shutdown timeout   : 120000
    [Thr 14572] JLaunchISetDebugMode: set debug mode [no]
    [Thr 14716] JLaunchIStartFunc: Thread 14716 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 262144 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djava.security.policy=./java.policy
    -> arg[  4]: -Djava.security.egd=file:/dev/urandom
    -> arg[  5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[  6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[  7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[  8]: -Djco.jarm=1
    -> arg[  9]: -XX:MaxPermSize=192M
    -> arg[ 10]: -XX:PermSize=192M
    -> arg[ 11]: -XX:NewSize=86M
    -> arg[ 12]: -XX:MaxNewSize=86M
    -> arg[ 13]: -XX:+DisableExplicitGC
    -> arg[ 14]: -verbose:gc
    -> arg[ 15]: -Xloggc:GC.log
    -> arg[ 16]: -XX:+PrintGCDetails
    -> arg[ 17]: -XX:+PrintGCTimeStamps
    -> arg[ 18]: -Djava.awt.headless=true
    -> arg[ 19]: -Dsun.io.useCanonCaches=false
    -> arg[ 20]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 21]: -XX:SurvivorRatio=2
    -> arg[ 22]: -XX:TargetSurvivorRatio=90
    -> arg[ 23]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
    -> arg[ 24]: -Dstartup.mode=SAFE
    -> arg[ 25]: -Dstartup.action=UPGRADE
    -> arg[ 26]: -Dsys.global.dir=D:\usr\sap\SMA\SYS\global
    -> arg[ 27]: -Dapplication.home=D:\usr\sap\SMA\DVEBMGS00\exe
    -> arg[ 28]: -Djava.class.path=D:\usr\sap\SMA\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\SMA\DVEBMGS00\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 29]: -Djava.library.path=C:\j2sdk1.4.2_14\jre\bin\server;C:\j2sdk1.4.2_14\jre\bin;C:\j2sdk1.4.2_14\bin;D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs;C:\oracle\SMA\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\OpenSSH\bin;C:\Program Files\System Center Operations Manager 2007\;D:\usr\sap\SMA\SYS\exe\uc\NTI386
    -> arg[ 30]: -Dmemory.manager=512M
    -> arg[ 31]: -Xmx512M
    -> arg[ 32]: -Xms512M
    -> arg[ 33]: -DLoadBalanceRestricted=no
    -> arg[ 34]: -Djstartup.mode=JCONTROL
    -> arg[ 35]: -Djstartup.ownProcessId=14568
    -> arg[ 36]: -Djstartup.ownHardwareId=Y0571960686
    -> arg[ 37]: -Djstartup.whoami=server
    -> arg[ 38]: -Djstartup.debuggable=no
    -> arg[ 39]: -DSAPINFO=SMA_00_server
    -> arg[ 40]: -DSAPSTART=1
    -> arg[ 41]: -DCONNECT_PORT=1130
    -> arg[ 42]: -DSAPSYSTEM=00
    -> arg[ 43]: -DSAPSYSTEMNAME=SMA
    -> arg[ 44]: -DSAPMYNAME=BKKT031A_SMA_00
    -> arg[ 45]: -DSAPPROFILE=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
    -> arg[ 46]: -DFRFC_FALLBACK=ON
    -> arg[ 47]: -DFRFC_FALLBACK_HOST=localhost
    -> arg[ 48]: -DSAPSTARTUP=1
    -> arg[ 49]: -DSAPSYSTEM=00
    -> arg[ 50]: -DSAPSYSTEMNAME=SMA
    -> arg[ 51]: -DSAPMYNAME=BKKT031A_SMA_00
    -> arg[ 52]: -DSAPDBHOST=BKKT031A
    -> arg[ 53]: -Dj2ee.dbhost=BKKT031A
    Mon Feb 25 16:16:48 2008
    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/PortalServiceItem startServices
    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
    [Thr 14716] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 6068] Mon Feb 25 16:16:58 2008
    [Thr 6068] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 6068] Mon Feb 25 16:17:01 2008
    [Thr 6068] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 6068] JLaunchISetClusterId: set cluster id 3244050
    [Thr 6068] Mon Feb 25 16:17:02 2008
    [Thr 6068] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 6068] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 14728] Mon Feb 25 16:18:33 2008
    [Thr 14728] JLaunchIExitJava: exit hook is called (rc = -11113)
    [Thr 14728] **********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'
    for additional information and trouble shooting.
    [Thr 14728] JLaunchCloseProgram: good bye (exitcode = -11113)
    trc file: "D:\usr\sap\SMA\DVEBMGS00\work\dev_server0", trc level: 1, release: "700"
    node name   : ID3244050
    pid         : 13172
    system name : SMA
    system nr.  : 00
    started at  : Mon Feb 25 16:18:41 2008
    arguments       :
           arg[00] : D:\usr\sap\SMA\DVEBMGS00\exe\jlaunch.exe
           arg[01] : pf=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
           arg[02] : -DSAPINFO=SMA_00_server
           arg[03] : pf=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
           arg[04] : -DSAPSTART=1
           arg[05] : -DCONNECT_PORT=1130
           arg[06] : -DSAPSYSTEM=00
           arg[07] : -DSAPSYSTEMNAME=SMA
           arg[08] : -DSAPMYNAME=BKKT031A_SMA_00
           arg[09] : -DSAPPROFILE=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
           arg[10] : -DFRFC_FALLBACK=ON
           arg[11] : -DFRFC_FALLBACK_HOST=localhost
    [Thr 16204] Mon Feb 25 16:18:41 2008
    [Thr 16204] *** WARNING => INFO: Unknown property [instance.box.number=SMADVEBMGS00bkkt031a] [jstartxx.c   841]
    [Thr 16204] *** WARNING => INFO: Unknown property [instance.en.host=BKKT031A] [jstartxx.c   841]
    [Thr 16204] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c   841]
    [Thr 16204] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c   841]
    JStartupReadInstanceProperties: read instance properties [D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties]
    -> ms host    : BKKT031A
    -> ms port    : 3901
    -> OS libs    : D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Used property files
    -> files [00] : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : BKKT031A
    -> ms port    : 3901
    -> os libs    : D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID3244000  : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID3244050  : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID3244000            : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
    -> [01] ID3244050            : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
    [Thr 16204] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 16204] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 15796] JLaunchRequestFunc: Thread 15796 started as listener thread for np messages.
    [Thr 14860] WaitSyncSemThread: Thread 14860 started as semaphore monitor thread.
    [Thr 16204] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 16204] CPIC (version=700.2006.09.13)
    [Thr 16204] [Node: server0] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_14
    [Thr 16204] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\SMA\DVEBMGS00\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID3244050]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : C:\j2sdk1.4.2_14
    -> java parameters    : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -XX:MaxPermSize=192M -XX:PermSize=192M -XX:NewSize=86M -XX:MaxNewSize=86M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Dstartup.mode=SAFE -Dstartup.action=UPGRADE
    -> java vm version    : 1.4.2_14-b05
    -> java vm vendor     : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type       : server
    -> java vm cpu        : x86
    -> heap size          : 512M
    -> init heap size     : 512M
    -> root path          : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs
    -> main class         : com.sap.engine.boot.Start
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : D:\usr\sap\SMA\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\SMA\DVEBMGS00\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50021
    -> shutdown timeout   : 120000
    [Thr 16204] JLaunchISetDebugMode: set debug mode [no]
    [Thr 16180] JLaunchIStartFunc: Thread 16180 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 262144 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djava.security.policy=./java.policy
    -> arg[  4]: -Djava.security.egd=file:/dev/urandom
    -> arg[  5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[  6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[  7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[  8]: -Djco.jarm=1
    -> arg[  9]: -XX:MaxPermSize=192M
    -> arg[ 10]: -XX:PermSize=192M
    -> arg[ 11]: -XX:NewSize=86M
    -> arg[ 12]: -XX:MaxNewSize=86M
    -> arg[ 13]: -XX:+DisableExplicitGC
    -> arg[ 14]: -verbose:gc
    -> arg[ 15]: -Xloggc:GC.log
    -> arg[ 16]: -XX:+PrintGCDetails
    -> arg[ 17]: -XX:+PrintGCTimeStamps
    -> arg[ 18]: -Djava.awt.headless=true
    -> arg[ 19]: -Dsun.io.useCanonCaches=false
    -> arg[ 20]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 21]: -XX:SurvivorRatio=2
    -> arg[ 22]: -XX:TargetSurvivorRatio=90
    -> arg[ 23]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
    -> arg[ 24]: -Dstartup.mode=SAFE
    -> arg[ 25]: -Dstartup.action=UPGRADE
    -> arg[ 26]: -Dsys.global.dir=D:\usr\sap\SMA\SYS\global
    -> arg[ 27]: -Dapplication.home=D:\usr\sap\SMA\DVEBMGS00\exe
    -> arg[ 28]: -Djava.class.path=D:\usr\sap\SMA\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\SMA\DVEBMGS00\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 29]: -Djava.library.path=C:\j2sdk1.4.2_14\jre\bin\server;C:\j2sdk1.4.2_14\jre\bin;C:\j2sdk1.4.2_14\bin;D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs;C:\oracle\SMA\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\OpenSSH\bin;C:\Program Files\System Center Operations Manager 2007\;D:\usr\sap\SMA\SYS\exe\uc\NTI386
    -> arg[ 30]: -Dmemory.manager=512M
    -> arg[ 31]: -Xmx512M
    -> arg[ 32]: -Xms512M
    -> arg[ 33]: -DLoadBalanceRestricted=no
    -> arg[ 34]: -Djstartup.mode=JCONTROL
    -> arg[ 35]: -Djstartup.ownProcessId=13172
    -> arg[ 36]: -Djstartup.ownHardwareId=Y0571960686
    -> arg[ 37]: -Djstartup.whoami=server
    -> arg[ 38]: -Djstartup.debuggable=no
    -> arg[ 39]: -DSAPINFO=SMA_00_server
    -> arg[ 40]: -DSAPSTART=1
    -> arg[ 41]: -DCONNECT_PORT=1130
    -> arg[ 42]: -DSAPSYSTEM=00
    -> arg[ 43]: -DSAPSYSTEMNAME=SMA
    -> arg[ 44]: -DSAPMYNAME=BKKT031A_SMA_00
    -> arg[ 45]: -DSAPPROFILE=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
    -> arg[ 46]: -DFRFC_FALLBACK=ON
    -> arg[ 47]: -DFRFC_FALLBACK_HOST=localhost
    -> arg[ 48]: -DSAPSTARTUP=1
    -> arg[ 49]: -DSAPSYSTEM=00
    -> arg[ 50]: -DSAPSYSTEMNAME=SMA
    -> arg[ 51]: -DSAPMYNAME=BKKT031A_SMA_00
    -> arg[ 52]: -DSAPDBHOST=BKKT031A
    -> arg[ 53]: -Dj2ee.dbhost=BKKT031A
    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/PortalServiceItem startServices
    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
    [Thr 16180] Mon Feb 25 16:18:42 2008
    [Thr 16180] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 15648] Mon Feb 25 16:18:48 2008
    [Thr 15648] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 15648] Mon Feb 25 16:18:50 2008
    [Thr 15648] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 15648] JLaunchISetClusterId: set cluster id 3244050
    [Thr 15648] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 15648] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 14068] Mon Feb 25 16:19:57 2008
    [Thr 14068] JLaunchIExitJava: exit hook is called (rc = -11113)
    [Thr 14068] **********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'
    for additional information and trouble shooting.
    [Thr 14068] JLaunchCloseProgram: good bye (exitcode = -11113)
    trc file: "D:\usr\sap\SMA\DVEBMGS00\work\dev_server0", trc level: 1, release: "700"
    node name   : ID3244050
    pid         : 15808
    system name : SMA
    system nr.  : 00
    started at  : Mon Feb 25 16:20:03 2008
    arguments       :
           arg[00] : D:\usr\sap\SMA\DVEBMGS00\exe\jlaunch.exe
           arg[01] : pf=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
           arg[02] : -DSAPINFO=SMA_00_server
           arg[03] : pf=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
           arg[04] : -DSAPSTART=1
           arg[05] : -DCONNECT_PORT=1130
           arg[06] : -DSAPSYSTEM=00
           arg[07] : -DSAPSYSTEMNAME=SMA
           arg[08] : -DSAPMYNAME=BKKT031A_SMA_00
           arg[09] : -DSAPPROFILE=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
           arg[10] : -DFRFC_FALLBACK=ON
           arg[11] : -DFRFC_FALLBACK_HOST=localhost
    [Thr 15880] Mon Feb 25 16:20:03 2008
    [Thr 15880] *** WARNING => INFO: Unknown property [instance.box.number=SMADVEBMGS00bkkt031a] [jstartxx.c   841]
    [Thr 15880] *** WARNING => INFO: Unknown property [instance.en.host=BKKT031A] [jstartxx.c   841]
    [Thr 15880] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c   841]
    [Thr 15880] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c   841]
    JStartupReadInstanceProperties: read instance properties [D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties]
    -> ms host    : BKKT031A
    -> ms port    : 3901
    -> OS libs    : D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Used property files
    -> files [00] : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : BKKT031A
    -> ms port    : 3901
    -> os libs    : D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
    -> [01] bootstrap_ID3244000  : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
    -> [02] bootstrap_ID3244050  : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
    Worker nodes
    -> [00] ID3244000            : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
    -> [01] ID3244050            : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
    [Thr 15880] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 15880] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 12672] JLaunchRequestFunc: Thread 12672 started as listener thread for np messages.
    [Thr 15460] WaitSyncSemThread: Thread 15460 started as semaphore monitor thread.
    [Thr 15880] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 15880] CPIC (version=700.2006.09.13)
    [Thr 15880] [Node: server0] java home is set by profile parameter
         Java Home: C:\j2sdk1.4.2_14
    [Thr 15880] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\SMA\DVEBMGS00\exe\jvmx.jar
    JStartupIReadSection: read node properties [ID3244050]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : C:\j2sdk1.4.2_14
    -> java parameters    : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -XX:MaxPermSize=192M -XX:PermSize=192M -XX:NewSize=86M -XX:MaxNewSize=86M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Dstartup.mode=SAFE -Dstartup.action=UPGRADE
    -> java vm version    : 1.4.2_14-b05
    -> java vm vendor     : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type       : server
    -> java vm cpu        : x86
    -> heap size          : 512M
    -> init heap size     : 512M
    -> root path          : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\server0
    -> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> OS libs path       : D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs
    -> main class         : com.sap.engine.boot.Start
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : D:\usr\sap\SMA\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\SMA\DVEBMGS00\exe\jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50021
    -> shutdown timeout   : 120000
    [Thr 15880] JLaunchISetDebugMode: set debug mode [no]
    [Thr 12716] JLaunchIStartFunc: Thread 12716 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 262144 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djava.security.policy=./java.policy
    -> arg[  4]: -Djava.security.egd=file:/dev/urandom
    -> arg[  5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[  6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[  7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[  8]: -Djco.jarm=1
    -> arg[  9]: -XX:MaxPermSize=192M
    -> arg[ 10]: -XX:PermSize=192M
    -> arg[ 11]: -XX:NewSize=86M
    -> arg[ 12]: -XX:MaxNewSize=86M
    -> arg[ 13]: -XX:+DisableExplicitGC
    -> arg[ 14]: -verbose:gc
    -> arg[ 15]: -Xloggc:GC.log
    -> arg[ 16]: -XX:+PrintGCDetails
    -> arg[ 17]: -XX:+PrintGCTimeStamps
    -> arg[ 18]: -Djava.awt.headless=true
    -> arg[ 19]: -Dsun.io.useCanonCaches=false
    -> arg[ 20]: -XX:SoftRefLRUPolicyMSPerMB=1
    -> arg[ 21]: -XX:SurvivorRatio=2
    -> arg[ 22]: -XX:TargetSurvivorRatio=90
    -> arg[ 23]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
    -> arg[ 24]: -Dstartup.mode=SAFE
    -> arg[ 25]: -Dstartup.action=UPGRADE
    -> arg[ 26]: -Dsys.global.dir=D:\usr\sap\SMA\SYS\global
    -> arg[ 27]: -Dapplication.home=D:\usr\sap\SMA\DVEBMGS00\exe
    -> arg[ 28]: -Djava.class.path=D:\usr\sap\SMA\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\SMA\DVEBMGS00\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
    -> arg[ 29]: -Djava.library.path=C:\j2sdk1.4.2_14\jre\bin\server;C:\j2sdk1.4.2_14\jre\bin;C:\j2sdk1.4.2_14\bin;D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs;C:\oracle\SMA\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\OpenSSH\bin;C:\Program Files\System Center Operations Manager 2007\;D:\usr\sap\SMA\SYS\exe\uc\NTI386
    -> arg[ 30]: -Dmemory.manager=512M
    -> arg[ 31]: -Xmx512M
    -> arg[ 32]: -Xms512M
    -> arg[ 33]: -DLoadBalanceRestricted=no
    -> arg[ 34]: -Djstartup.mode=JCONTROL
    -> arg[ 35]: -Djstartup.ownProcessId=15808
    -> arg[ 36]: -Djstartup.ownHardwareId=Y0571960686
    -> arg[ 37]: -Djstartup.whoami=server
    -> arg[ 38]: -Djstartup.debuggable=no
    -> arg[ 39]: -DSAPINFO=SMA_00_server
    -> arg[ 40]: -DSAPSTART=1
    -> arg[ 41]: -DCONNECT_PORT=1130
    -> arg[ 42]: -DSAPSYSTEM=00
    -> arg[ 43]: -DSAPSYSTEMNAME=SMA
    -> arg[ 44]: -DSAPMYNAME=BKKT031A_SMA_00
    -> arg[ 45]: -DSAPPROFILE=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
    -> arg[ 46]: -DFRFC_FALLBACK=ON
    -> arg[ 47]: -DFRFC_FALLBACK_HOST=localhost
    -> arg[ 48]: -DSAPSTARTUP=1
    -> arg[ 49]: -DSAPSYSTEM=00
    -> arg[ 50]: -DSAPSYSTEMNAME=SMA
    -> arg[ 51]: -DSAPMYNAME=BKKT031A_SMA_00
    -> arg[ 52]: -DSAPDBHOST=BKKT031A
    -> arg[ 53]: -Dj2ee.dbhost=BKKT031A
    Mon Feb 25 16:20:04 2008
    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/PortalServiceItem startServices
    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
    [Thr 12716] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 15780] Mon Feb 25 16:20:09 2008
    [Thr 15780] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 15780] Mon Feb 25 16:20:11 2008
    [Thr 15780] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 15780] JLaunchISetClusterId: set cluster id 3244050
    [Thr 15780] Mon Feb 25 16:20:12 2008
    [Thr 15780] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 15780] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 4828] Mon Feb 25 16:21:17 2008
    [Thr 4828] JLaunchIExitJava: exit hook is called (rc = -11113)
    [Thr 4828] **********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'
    for additional information and trouble shooting.
    [Thr 4828] JLaunchCloseProgram: good bye (exitcode = -11113)
    trc file: "D:\usr\sap\SMA\DVEBMGS00\work\dev_server0", trc level: 1, release: "700"
    node name   : ID3244050
    pid         : 7528
    system name : SMA
    system nr.  : 00
    started at  : Mon Feb 25 16:27:52 2008
    arguments       :
           arg[00] : D:\usr\sap\SMA\DVEBMGS00\exe\jlaunch.exe
           arg[01] : pf=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
           arg[02] : -DSAPINFO=SMA_00_server
           arg[03] : pf=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
           arg[04] : -DSAPSTART=1
           arg[05] : -DCONNECT_PORT=1130
           arg[06] : -DSAPSYSTEM=00
           arg[07] : -DSAPSYSTEMNAME=SMA
           arg[08] : -DSAPMYNAME=BKKT031A_SMA_00
           arg[09] : -DSAPPROFILE=D:\usr\sap\SMA\SYS\profile\SMA_DVEBMGS00_BKKT031A
           arg[10] : -DFRFC_FALLBACK=ON
           arg[11] : -DFRFC_FALLBACK_HOST=localhost
    [Thr 7060] Mon Feb 25 16:27:52 2008
    [Thr 7060] *** WARNING => INFO: Unknown property [instance.box.number=SMADVEBMGS00bkkt031a] [jstartxx.c   841]
    [Thr 7060] *** WARNING => INFO: Unknown property [instance.en.host=BKKT031A] [jstartxx.c   841]
    [Thr 7060] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c   841]
    [Thr 7060] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c   841]
    JStartupReadInstanceProperties: read instance properties [D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties]
    -> ms host    : BKKT031A
    -> ms port    : 3901
    -> OS libs    : D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs
    -> Admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE
    -> enabled    : yes
    Used property files
    -> files [00] : D:\usr\sap\SMA\DVEBMGS00\j2ee\cluster\instance.properties
    Instance properties
    -> ms host    : BKKT031A
    -> ms port    : 3901
    -> os libs    : D:\usr\sap\SMA\DVEBMGS00\j2ee\os_libs
    -> admin URL  :
    -> run mode   : safe
    -> run action : UPGRADE

    Hi Bruyneel,
    I've solved the problem. I think while doing kernel or component upgrade SAP clear all configuration that connected from ABAP and JAVA. You can re-config from config tool.
    1. Goto \usr\sap\<SID>\<SIst.Num>\j2ee\configtool and execute go.bat
    2. cluster-data -> global server configuration -> services -> com.sap.security.core.ume.service.
    3. Configure:
    ume.login.guest_user.uniquefields with J2EE_GUEST, and make sure the user is already exist in ABAP
    ume.persistence.data_source_configuration     dataSourceConfiguration_abap.xml
    ume.r3.connection.master.ashost
    ume.r3.connection.master.client
    ume.r3.connection.master.passwd : with SAPJSF user's password
    ume.r3.connection.master.sysnr
    ume.r3.connection.master.user : SAPJSF User
    Refer for this link for help: http://help.sap.com/saphelp_nw04s/helpdata/en/20/361941edd5ef23e10000000a155106/frameset.htm
    Thanks & Best Regards,
    Yan

  • Services in Solution Manager

    Hello. I'm trying to configure Solution Manager services.
    In service solman, which includes defaultUser and GraphicData, which is the correct handler?
    I’m changing this and obtain different results, anyone ok. Sometimes it does nothing, another times says de URL needs a superior element. The transaction SOLUTION_MANAGER, Operations, System monitoring shows a program code…
    Do you know where can I get documentation related to the services definition?
    Thanks
    Cristina.

    Thanks Ragu for your answer.
    There is an example of what i'm tryin to say:
    I’m trying to define the solman service.
    Transaction SICF, path /default_host/sap/bc/, service solman, double click, Handler list.
    There is nothing here.
    In the Maintein service screen, right button, Test service.
    I get the message: "The message Service  Cannot Be Accessed !"
    So, again in the Handler list, F4, a list of handlers is displayed.
    I don’t know which handler choose. Looking for the word solman, the service CL_SA_HTTP_SOLMAN_GRAPHIC appears.
    Save.
    Test again, and now I receive an internet page, saying:
    "Page XML cannot be displayed
    Entrance XML with the style sheet cannot be seen. Correct the error and click in the button Update, or try again later.
    The XML document must have an element of superior level. Error when processing the resource http://forwadh1.cti:8000/sap/bc/sol..."
    This happens to me with all the services that I'm trying to configure.
    My problem is that I need to configure de Early Watch Alert, and transaction Solution_Manager is not  displayed as I hope. SAP OSS said that I must configure the services first.
    Well, I'm trying to do it, but i'm lost.
    Thanks
    Cristina.

  • How to create contact person on SAP Solution Manager

    Dear all.
    I installed SAP Solman SR3, I config solution manager for download support package. When I use the transaction AISUSER to assign user and contact person. I receive the information:" Partner 000xxxxxx not found". I saw in Solman SR2 didn't have this error.
    Now I want to define contact person ! Please help me if you know about this problem.
    thanks all so much.

    Hi Thao
    We have 2 column in AISUSER transaction table....
    one is USer in which userid for the person is entered
    sec is contact person in which S-Userid is entered(Delete the S and Leading Zeros from it)
    The error which you are facing is because when you enter the entry a check execute by the system is enquireing the table AIContacts which is update by a background job .....................so have you scheduled this standard job .........REFRESH_ADMIN_DATA_FROM_SUPPORT.
    Also posting the help log for the ur convenience....
    Procedure to remove the error
    Please check if you entered the correct number (S-User without S) or use the value help for this field. If the value help doesn't provide any data the report AI_SC_REFRESH_READ_ONLY_DATA has not been run yet. It should be scheduled daily with transaction SM_CONFIG_JOBS as job REFRESH_ADMIN_DATA_FROM_SUPPORT. However if you want to run this job successfully the user who created the job must be maintained in transaction AISUSER first. So you should ignore the warning for this purpose, maintain the partner for this user and continue maintaining this table after the job has fetched the contact data for the value help from SAP Support Portal successfully.
    Even then it can happen, that you don't find the partner number in the value help. The reason for this may be, that the user doesn't have enough authorizations for some actions, since only users with certaine authorizations are downloaded from SAP Support Portal. So you also may ignore the warning in this case, as long as there is no typo in the partner number.
    Hope it clarifies your doubt
    Regards
    Prakhar

  • Configuring Support Desk (Solution Manager 4.0)

    Hi,
    Anybody knows where can I find a guide to configuring the Support Desk in SAP Solution Manager 4.0 ?
    I've found several documents but for release 3.2.
    Thank's in advanced

    Hi
    <a href="https://websmp209.sap-ag.de/rkt-solman">Click here</a>..here u will get various simulations for configuring different scenerios in solman and its very informative
    Kind regards
    Umesh K

Maybe you are looking for

  • HP C4180 all-in-one, Windows Vista 64-bit, purple in photo prints out looking like blue

    Driving me crazy.  School colors are purple and white.  Anytime I print a photo of our football team, the purple turns out blue.  HELP!!

  • Want to move itunes libary files

    Is there no way to move the itunes library files, "iTunes Library.itl" and "iTunes Music Library.xml"? They are in a very stupid location on my computer, (a folder that should be used exclusively for work). I would really like to get the iTunes libra

  • Problems referencing a primary key field in a master-detail

    Hello, I am making an application where I have a master-detail page. In the detail section it is possible to add new rows using the standard "Add row"-button that the wizard creates. The detail section has a column with a link in it. This link leads

  • Problem in ACS 5.2 on Virtual Machine

    Hi Everyone ! I have a problem with the interface on the ACS 5.2 , The inferface work fine but going down unexpectedly and only if I make (for example) a ping to the default gateway it come back.   Please somebody can help me ?? Regards. Rodrigo

  • Should ADT create module components based on views?

    I have a function (representing a report) with Read usage on two entities, and one entity is implemented by a table and the other implemented by a view. When I run the Application Design Transformer, the resulting module has a module component based