on 11-14-2007 9:02 PM
Hi experts,
I'm facing a problem that when the server0 starts the framework it breaks with the error 11113 (which couldn't be more vague). I have this new Installation in a MS Cluster on Win2k3 with Oracle 10.2 DB. The installation was OK, after that I've restart the instance and was OK, I applied the Note 950743 and it still worked fine, I updated the kernell, and yet it was working after restart. But just before started the updates on SP I restarted again and the problem came up. This is what shows on log file. I hope someone can help me.
STD_SERVER0.OUT (Just before error and the main exceptions)
Loading services.:
Service cross started. (46 ms).
Service file started. (46 ms).
Service runtimeinfo started. (15 ms).
Service memory started. (46 ms).
Service timeout started. (31 ms).
Service trex.service started. (47 ms).
Service userstore started. (16 ms).
Service jmx_notification started. (16 ms).
Service p4 started. (94 ms).
Service classpath_resolver started. (15 ms).
Service log_configurator started. (2251 ms).
Service locking started. (0 ms).
Service http started. (157 ms).
Service naming started. (266 ms).
Service failover started. (31 ms).
Service appclient started. (46 ms).
Service javamail started. (62 ms).
Service ts started. (47 ms).
Service jmsconnector started. (78 ms).
Service licensing started. (62 ms).
Service connector started. (187 ms).
Service iiop started. (172 ms).
Service webservices started. (375 ms).
Service deploy started. (4738 ms).
Service MigrationService started. (16 ms).
Service configuration started. (32 ms).
Service bimmrdeployer started. (16 ms).
Service dbpool started. (1017 ms).
Nov 14, 2007 7:08:55 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_63] Fatal: User Management Engine (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed to connect to the ABAP backend system. Check that connection data are correct and the backend system is available. Error message: "Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=SAPGRPPI SYSNR=33 GWHOST=SAPGRPPI GWSERV=sapgw33 PCS=1
...
". Connection data (obtained from properties of UME service in section "ume.r3.connection.master.": "{
passwd=********
receiverid=master
sysnr=$$
client=001
poolmaxsize=10
user=SAPJSF
receiverid_guest=master
ashost=SAPGRPPI
poolmaxwait=10000
}
".
Nov 14, 2007 7:08:55 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_63] Fatal: Initialization of UME persistence adapter "R3_DATASOURCE" failed.
service com.sap.security.core.ume.service ================= ERROR =================
Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
...
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=SAPGRPPI SYSNR=33 GWHOST=SAPGRPPI GWSERV=sapgw33 PCS=1
DEV_SERVER0 (Just before error and the main exceptions)
**********************************************************************
JHVM_BuildArgumentList: main method arguments of node [server0]
**********************************************************************
[Thr 5840] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
[Thr 5840] Wed Nov 14 17:08:09 2007
[Thr 5840] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 5840] JLaunchISetClusterId: set cluster id 337420350
[Thr 5840] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 5840] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 3864] Wed Nov 14 17:08:19 2007
[Thr 3864] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
[Thr 6228] Wed Nov 14 17:08:55 2007
[Thr 6228] JLaunchRequestFunc: receive command:17, argument:0 from pid:7184
[Thr 6228] JLaunchIShutdownInvoke: set shutdown interval (stop:1195067335/end:1195067455/TO:120)
[Thr 6228] JLaunchProcessCommand: Invoke VM Shutdown
[Thr 6228] JHVM_FrameworkShutdownDirect: invoke direct shutdown
[Thr 3864] ***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4248]
[Thr 3864] *** ERROR => NiIRead: SiRecv failed for hdl 0 / sock 7028
(SI_ECONN_BROKEN/10054; I4; ST; 10.125.20.48:3333) [nixxi.cpp 4248]
[Thr 3864] *** ERROR => GwIConnect: GwRead to SAPGRPPI / sapgw33 failed, rc: NIECONN_BROKEN [gwxx.c 490]
[Thr 3864] ***LOG S90=> SAP_STINIT3, GwIConnect ( 223) [r3cpic.c 2006]
[Thr 3864]
*****************************************************************************
*
[Thr 3864] * LOCATION CPIC (TCP/IP) on local host with Unicode
[Thr 3864] * ERROR connection to partner 'SAPGRPPI:sapgw33' broken
[Thr 3864] *
TIME Wed Nov 14 17:08:55 2007
[Thr 3864] * RELEASE 700
[Thr 3864] * COMPONENT NI (network interface)
[Thr 3864] * VERSION 38
[Thr 3864] * RC -6
[Thr 3864] * MODULE gwxx.c
[Thr 3864] * LINE 480
[Thr 3864] * DETAIL NiIRead
[Thr 3864] * SYSTEM CALL NiRead
[Thr 3864] * ERRNO 10054
[Thr 3864] * ERRNO TEXT WSAECONNRESET: Connection reset by peer
[Thr 3864] * COUNTER 1
[Thr 3864] *
[Thr 3864] *****************************************************************************
[Thr 2904] Wed Nov 14 17:08:56 2007
[Thr 2904] JLaunchIExitJava: exit hook is called (rc = -11113)
[Thr 2904] **********************************************************************
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 2904] JLaunchCloseProgram: good bye (exitcode = -11113)
Hello!
Which UME Configuration are you using? It looks like the Java-Stack can't start because it cannot connect to the UME-Datasource properly. Is it the ABAP-Stack? If yes, is it up and running? I saw in an earlier posting something that could be read like ABAP was down.
Please check of your UME-Source is properly available.
Kind regards,
Jörg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Check for the two db users in the db.
one is sapr3db and aonther one is there.
You please unlock these two users from the oracle level
from SQLPLUS
eg:ALTER USER <username> ACCOUNT UNLOCK;
Then Start the SAP system .Then From abap stack check the status of SAPJSF user using su01, if it is locked please unlock the user and restart the instance.
Regards,
Arun
Hi Alex,
Can you check the status oracle 10g?
Is it up and running???
check the services using services.msc
By default for <b>Oracle10 g service will be in stoped (manual).</b>
So change the status to automatic and start the service and then start the mmc.
Regards,
Arun
Ps:Reward Points if this is helpfull.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is you SAP system up?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As I'm using MSCS installation I have ASCS, SCS and Enqueue Repication UP but the central ou Dialog Instance not, so I can't connect via SAP GUI to have a look on SAPJSF user.
By the way, I have already checked the parameter in ConfigTool related to com.sap.core.security.ume - ....master....(ashost, user,client).
Thanks for the quick reply
User | Count |
---|---|
76 | |
9 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.