- SAP Community
- Products and Technology
- Technology
- Technology Q&A
- J2ee server0 not starting
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
J2ee server0 not starting
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 12-01-2007 7:35 AM
Hi Experts,
I ve run into a problem in a ECC6 server(Abap+Java). It gives a dump when logging into it from GUI - "CALL_TRANSACTION_SICK". When i execute transaction SICK, i am getting the following result...
SAP System Check
R/3 release 001 is not supported with this kernel (700)
Severe problems were detected during initial system check.
Please, do not use that system before fixing these problems.
The Java server processes (server0, server1) are also not starting. When I checked the default trace, i got the following details..
#1.5#0014221E209B00010000000700001B6C00043FF6D1FD03E2#1196229224391#com.sap.engine.core.service630.container.ServiceRunner##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_72##0#0#Error#1#/System/Server#Java###Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
[EXCEPTION]
#1#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.
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Wrong repository version = 1 encountered
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:356)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
... 6 more
#
#1.5#0014221E209B00010000000800001B6C00043FF6D1FD07E5#1196229224391#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_72##0#0#Fatal#1#/System/Server#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#
Also, when i execute the command R3trans -d, the result is
This is r3trans version 6.14 (release 700 - 29.05.07 - 13:40:00).
unicode enabled version
1AETW000 ERROR: third character of SAP-Release is not a letter, but 1
2EETW000 Please contact the SAP support.
Have any of you gone through this problem earlier? Please enlight me on what could be the reason for this...
Thanks in advance,
Basker
- SAP Managed Tags:
- NW AS Java Administrator (NWA)
Accepted Solutions (1)
Accepted Solutions (1)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Basker,
Can you please have a check at kernel version? This needs to be addressed first before you start looking for J2EE issue. Also try to send the syslog entry in SM21.
Cheers,
Rajeev
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Answers (6)
Answers (6)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi ppl,
The issue is sorted out. Actually, the problem was with the release, as suggested by the error message. there is no such release as 001. the actual entry should have been 700 (as for ecc6). But, this data had been changed by somebody with developer access [hopefully, by mistake :-)]. So, we went to database level and changed the entry back to 700. it worked out!!! After this was done, the java engine to started without any problem!!!
Thanks,
Basker
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Did you use the right DVD/CDs to install ECC6.0 ? Even if the java is down you should be able to login to ABAP stack without any issues
Thanks
Prince Jsoe
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Juan,
Posting the default trace below....
#
#1.5#0014221E209B00010000000400001B6C00043FF6D1FCEBE2#1196229224391#com.sap.security.core.server.ume.service.UMEServiceFrame##com.sap.security.core.server.ume.service.UMEServiceFrame#######SAPEngine_System_Thread[impl:5]_72##0#0#Error#1#/System/Security/Usermanagement#Plain###UME initialization failed.#
#1.5#0014221E209B00010000000500001B6C00043FF6D1FCEF9B#1196229224391#com.sap.security.core.server.ume.service.UMEServiceFrame##com.sap.security.core.server.ume.service.UMEServiceFrame.start()#######SAPEngine_System_Thread[impl:5]_72##0#0#Error##Java###UME initialization failed.
[EXCEPTION]
#1#com.sap.security.core.persistence.datasource.PersistenceException: Wrong repository version = 1 encountered at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178) at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446) at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:356) at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156) at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109) at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56) at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266) at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279) at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31) at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214) at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144) at com.sap.engine.frame.core.thread.Task.run(Task.java:64) at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79) at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105) -
caused by -
com.sap.mw.jco.JCO$Exception: (108) JCO_ERROR_INTERNAL: Wrong repository version = 1 encountered at com.sap.security.core.persistence.datasource.imp.r3persistence.R3JCo640Proxy$Repository640.getFunctionTemplate(R3JCo640Proxy.java:648) at com.sap.security.core.persistence.datasource.imp.R3Persistence.localInitialization(R3Persistence.java:311) at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:424) at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:356) at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156) at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109) at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56) at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266) at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279) at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31) at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214) at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144) at com.sap.engine.frame.core.thread.Task.run(Task.java:64) at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79) at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105) # #1.5#0014221E209B00010000000600001B6C00043FF6D1FCFCC3#1196229224391#com.sap.engine.core.service630.container.ServiceRunner##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_72##0#0#Error#1#/System/Server#Plain###Service com.sap.security.core.ume.service error. Nested exception is: com.sap.engine.frame.ServiceException: <
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Wrong repository version = 1 encountered
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:356)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
... 6 more
#
#1.5#0014221E209B00010000000800001B6C00043FF6D1FD07E5#1196229224391#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_72##0#0#Fatal#1#/System/Server#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#
Thanks,
Basker
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Juan / Vijay,
Yeah, i ve checked it already. DB is up and running fine. Listener is ok. I ve checked the settings in config tool and compared them with a working server. everything seems to be fine. but still the server process is not starting. Could there be any other reason?
Thanks,
Basker
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
hi Basker,
As juan said i also think that there is a problem in DB only,Because,This service if for setting the db port. <b>Core service com.sap.security.core.ume.service</b> .This is failed in your sytem.
So if you are using SQL DB means Go to SQL Network analyser and then check the properties of TCP/IP and check the value is 1433 or 1380.If it s not there set the values and restart the server.
Check it configtool.bat also.
The same service with the same value which you have mentioned above
Thanks and Regards
Vijay
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Basker,
This looks like a problem with the DB.
What DB are you using?
Check that the DB is online and is mounting and openning correctly, also check that theres enough space in all tablespaces... If using oracle, check that the listener is starting.
regards
Juan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- SAP JAVA component patch update(SCA) using telnet #ATR in Technology Blogs by Members
- Manage SAP on GCP with SAP LaMa Adapter for GCP – Part 1 in Technology Blogs by Members
- SAP MacGyver - Installing SAP SolMan 7.2 in Technology Blogs by SAP
- Error while while deploying b2b AS2 adapter in Technology Q&A
- ELSTER Modules for PI/PO with ERiC libraries in Technology Blogs by SAP
| User | Count |
|---|---|
| 101 | |
| 13 | |
| 13 | |
| 11 | |
| 11 | |
| 7 | |
| 6 | |
| 5 | |
| 4 | |
| 4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.