cancel
Showing results for 
Search instead for 
Did you mean: 

SDM not coming up

Former Member
0 Kudos

Hi Experts,

We are facing strange problem. We are upgrading Solution Manager to SP17, which is a pre-requisite to EHP1.

While doing patch via JSPM, it stopped giving some error.As per SAP note 1231975, it was that we needed to deploy one patch first before the queue could be deplyed. We started using SDM, there it threw Admin password error.After saving password in Config Tool-Secure area, now SDM is not coming up.

First it threw authentication error. We thought somwhow the password is locked. We reset the password as given below-

./StopServer.sh

./sdm.sh jstartup "mode=standalone"

./sdm.sh changepassword "newpassword=<Enterthenewpassword>"

./sdm.sh jstartup "mode=integrated"

./StartServer.sh

But SDM is not coming up. Even we restart the instance also, it is not being started.

Please suggest.

Regards,

Sabita

Accepted Solutions (0)

Answers (1)

Answers (1)

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

Please make sure that you have maintained correct password in secure store in portal.

Thanks

Sunny

Former Member
0 Kudos

Yes password is correct, as we have not changed J2EE_ADMIN password.

One more thing we noticed that even java instance is not working.

server0 log says -

#1.5 #221C4DDDA97300500000004A000030DB0004A0EE77419F3D#1302845970291#/System/Server##com.sap.engine.core.service630.container.MemoryContainer#J2EE_GUEST#0#####Thread[Thread-46,5,main]##0#0#Info#1#com.sap.engine.core.service630.container.MemoryContainer#Plain###Service runtimeinfo stopped. (0 ms)#

#1.5 #221C4DDDA97300500000004B000030DB0004A0EE7741D793#1302845970305#/System/Server##com.sap.engine.core.configuration#J2EE_GUEST#0#####Thread[Thread-46,5,main]##0#0#Info#1#com.sap.engine.core.configuration#Java### stopped successfully#1#ConfigurationManager# #1.5 #221C4DDDA97300500000004C000030DB0004A0EE7741E00A#1302845970308#/System/Server##com.sap.engine.core.locking.AbstractLockingManagerImpl.removeAllLokcsForClusterIdLogException(clusterId)#J2EE_GUEST#0#####Thread[Thread-46,5,main]##0#0#Info#1#com.sap.engine.core.locking.AbstractLockingManagerImpl#Java###All locks for cluster-element removed successfully#1#39721850#

#1.5 #221C4DDDA97300500000004D000030DB0004A0EE7741E0F7#1302845970308#/System/Server##com.sap.engine.core.locking.AbstractLockingManagerImpl.shutDown(properties)#J2EE_GUEST#0#####Thread[Thread-46,5,main]##0#0#Info#1#com.sap.engine.core.locking.AbstractLockingManagerImpl#Java### stopped successfully#1#LockingManager#

#1.5 #221C4DDDA973006200000000000030DB0004A0EE7741E55E#1302845970309#/System/Server##com.sap.engine.core.cluster.impl6.ms.MSListenerQueue.run()#######SAP J2EE Engine|MS Queue Listener##0#0#Info#1#com.sap.engine.core.cluster.impl6.ms.MSListenerQueue#Plain###MSLib: Received error command to stop listener queue.#

#1.5 #221C4DDDA97300500000004F000030DB0004A0EE774F5FDD#1302845971192#/System/Server##com.sap.engine.core.thread.impl3.ThreadManagerImpl#J2EE_GUEST#0#####Thread[Thread-46,5,main]##0#0#Info#1#com.sap.engine.core.thread.impl3.ThreadManagerImpl#Plain###ThreadManager stopped.#

and dev_bootstrap log says-

[Thr 4] Fri Apr 15 14:30:08 2011

[Thr 4] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes

[Thr 6] Fri Apr 15 14:30:10 2011

[Thr 6] JLaunchIExitJava: exit hook is called (rc = 66)

[Thr 6] **********************************************************************

      • 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 6] SigISetIgnoreAction : SIG_IGN for signal 18

[Thr 6] JLaunchCloseProgram: good bye (exitcode = 66)

in other log files we found that -

      • ERROR => DpJ2eeMsgProcess: NiRead failed (NIECONN_BROKEN) [dpxxj2ee.c 1212

NiIWrite: SiSendV failed for hdl 1 / sock 11

DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

Any suggestions and solution are highly approciated.

Thanks in advance.

Sabita

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

Could you please paste fresh logs from default trace files ?

Thanks

Sunny

Former Member
0 Kudos

Hi Sunny,

It looks weired ot paste such huge content, still I am pasting it, please check- I have removed some repetetive contents

#1302788490312#com.sap.engine.services.deploy##com.sap.engine.services.deploy####n/a##e63ddc60669c11e0b40c221c4ddda973#SAPEngine_System_Thread[impl:5]_24##0#0#Error#1#/System/Server#Plain###Error occurred while initially starting application sap.com/tcsmdgloballicenseaudit:The application start is forbidden, because of the server mode and action.#

#1.5 #221C4DDDA97300360000031A000030DB0004A0E1152EC1AE#1302788490313#com.sap.engine.services.deploy##com.sap.engine.services.deploy####n/a##e63ddc60669c11e0b40c221c4ddda973#SAPEngine_System_Thread[impl:5]_24##0#0#Error#1#/System/Server#Plain###Error occurred while initially starting application sap.com/tcsmdlandscape~validation:The application start is forbidden, because of the server mode and action.#

#1.5 #221C4DDDA97300360000031C000030DB0004A0E1152EC2BF#1302788490313#com.sap.engine.services.deploy##com.sap.engine.services.deploy####n/a##e63ddc60669c11e0b40c221c4ddda973#SAPEngine_System_Thread[impl:5]_24##0#0#Error#1#/System/Server#Plain###Error occurred while initially starting application sap.com/tcsldstartup~app:The application start is forbidden, because of the server mode and action.#

#1.5 #221C4DDDA97300360000031E000030DB0004A0E1152EC3CC#1302788490313#com.sap.engine.services.deploy##com.sap.engine.services.deploy####n/a##e63ddc60669c11e0b40c221c4ddda973#SAPEngine_System_Thread[impl:5]_24##0#0#Error#1#/System/Server#Plain###Error occurred while initially starting application sap.com/com.sap.ip.bi.sdk.datasource.sys:The application start is forbidden, because of the server mode and action.#

#1.5 #221C4DDDA973003600000320000030DB0004A0E1152EC521#1302788490314#com.sap.engine.services.deploy##com.sap.engine.services.deploy####n/a##e63ddc60669c11e0b40c221c4ddda973#SAPEngine_System_Thread[impl:5]_24##0#0#Error#1#/System/Server#Plain###Error occurred while initially starting application sap.com/tclmwebadminmonitorcomplib~wd:The application start is forbidden, because of the server mode and action.#

#1.5 #221C4DDDA973004B0000000A000030DB0004A0E12670195C#1302788779808#com.sap.sl.ut##com.sap.sl.ut####n/a##91d09720669d11e0a03a221c4ddda973#SAPEngine_System_Thread[impl:5]_89##0#0#Info#1#/System/Server#Plain### Location :<com.sap.sl.ut> is initialized!#

#1.5 #221C4DDDA973004B0000000C000030DB0004A0E126701B01#1302788779808#com.sap.sl.ut##com.sap.sl.ut####n/a##91d09720669d11e0a03a221c4ddda973#SAPEngine_System_Thread[impl:5]_89##0#0#Info#1#/System/Server#Plain### Cotegory :</System/Server> is initialized and bound to Location: <com.sap.sl.ut>#

#1.5 #221C4DDDA973004B0000000E000030DB0004A0E1267076D5#1302788779832#com.sap.sl.ut##com.sap.sl.ut####n/a##91d09720669d11e0a03a221c4ddda973#SAPEngine_System_Thread[impl:5]_89##0#0#Info#1#/System/Server#Plain###Establishing db connection...#

products array ...#

#1302788780479#com.sap.sl.ut##com.sap.sl.ut####n/a##91d09720669d11e0a03a221c4ddda973#SAPEngine_System_Thread[impl:5]_89##0#0#Info#1#/System/Server#Plain###fillPartsForProduct: Adding part to product -NetWeaver ...#

#1.5 #221C4DDDA973004B0000002A000030DB0004A0E1267A6116#1302788780481#com.sap.sl.ut##com.sap.sl.ut####n/a##91d09720669d11e0a03a221c4ddda973#SAPEngine_System_Thread[impl:5]_89##0#0#Info#1#/System/Server#Plain###fillPartsForProduct: Adding part - EP - to product -NetWeaver ...#

#1.5 #221C4DDDA973004B0000002C000030DB0004A0E1267A622A#1302788780482#com.sap.sl.ut##com.sap.sl.ut####n/a##91d09720669d11e0a03a221c4ddda973#SAPEngine_System_Thread[impl:5]_89##0#0#Info#1#/System/Server#Plain###fillPartsForProduct: Adding #1302788780487#com.sap.sl.ut##com.sap.sl.ut####n/a##91d09720669d11e0a03a221c4ddda973#SAPEngine_System_Thread[impl:5]_89##0#0#Info#1#/System/Server#Plain###fillPartsForProduct: Adding part to product -ERP 2005 ...#

#1.5 #221C4DDDA973004B0000003E000030DB0004A0E1267A7C5F#1302788780488#com.sap.sl.ut##com.sap.sl.ut####n/a##91d09720669d11e0a03a221c4ddda973#SAPEngine_System_Thread[impl:5]_89##0#0#Info#1#/System/Server#Plain###fillPartsForProduct: Adding #1302788780493#com.sap.sl.ut##com.sap.sl.ut####n/a##91d09720669d11e0a03a221c4ddda973#SAPEngine_System_Thread[impl:5]_89##0#0#Info#1#/System/Server#Plain###fillProducts(): Product SRM 2005is added!#

#1.5 #221C4DDDA973004B00000052000030DB0004A0E1267A902A#1302788780493#com.sap.sl.ut##com.sap.sl.ut####n/a##91d09720669d11e0a03a221c4ddda973#SAPEngine_System_Thread[impl:5]_89##0#0#Info#1#/System/Server#Plain###fillProducts(): Adding product ...#

#1.5 #221C4DDDA973004B00000054000030DB0004A0E1267A92B5#1302788780494#com.sap.sl.ut##com.sap.sl.ut####n/a##91d09720669d11e0a03a221c4ddda973#SAPEngine_System_Thread[impl:5]_89##0#0#Info#1#/System/Server#Plain###fillProducts(): Product SCM 2005is added!#

#1.5 #221C4DDDA973004B00000056000030DB0004A0E1267A95FF#1302788780495#com.sap.sl.ut##com.sap.sl.ut####n/a##91d09720669d11e0a03a221c4ddda973#SAPEngine_System_Thread[impl:5]_89##0#0#Info#1#/System/Server#Plain###fillProducts(): Product arrey is filled!#

#1.5 #221C4DDDA973004B00000058000030DB0004A0E1267DC377#1302788780703#com.sap.sl.ut##com.sap.sl.ut####n/a##91d09720669d11e0a03a221c4ddda973#SAPEngine_System_Thread[impl:5]_89##0#0#Info#1#/System/Server#Plain###Successfully constructed!#

#1.5 #221C4DDDA973004B0000005A000030DB0004A0E126880E4E#1302788781378#com.sap.sldserv.comm.BridgeCommunicationHTTP##com.sap.sldserv.comm.BridgeCommunicationHTTP####n/a##91d09720669d11e0a03a221c4ddda973#SAPEngine_System_Thread[impl:5]_89##0#0#Error#1#/System/Server/SLDService#Plain###Error while sending HTTP data. Status: 503. Message: Service Unavailable. Please check if the target SLD system is available and the SLD bridge is started there.#

#1.5 #221C4DDDA973004C00000000000030DB0004A0E4B43596DD#1302804043239#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.handleRequest#J2EE_GUEST#0##n/a##1d98cf7066c111e0a58a221c4ddda973#SAPEngine_Application_Thread[impl:3]_7##0#0#Error##Plain###com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at rfcaccessejb_stateful, the whole lookup name is rfcaccessejb_stateful/SLDJAVA_ACCESSOR_REQUEST.#

#1.5 #221C4DDDA973004C00000001000030DB0004A0E4B435A0EF#1302804043242#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.handleRequest#J2EE_GUEST#0##n/a##1d98cf7066c111e0a58a221c4ddda973#SAPEngine_Application_Thread[impl:3]_7##0#0#Error##Plain###com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at rfcaccessejb_stateful, the whole lookup name is rfcaccessejb_stateful/SLDJAVA_ACCESSOR_REQUEST.

at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:261)

at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:624)

at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)

at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)

at javax.naming.InitialContext.lookup(InitialContext.java:347)

at javax.naming.InitialContext.lookup(InitialContext.java:347)

at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:129)

at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:254)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

#

#1.5 #221C4DDDA973004C00000003000030DB0004A0E4B435D454#1302804043255#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine#J2EE_GUEST#0##n/a##1d98cf7066c111e0a58a221c4ddda973#SAPEngine_Application_Thread[impl:3]_7##0#0#Error#1#/System/Server#Plain###Bean SLDJAVA_ACCESSOR_REQUESTnot found on host htlssolm, ProgId =SAPSLD_SM9: Path to object does not exist at rfcaccessejb_stateful, the whole lookup name is rfcaccessejb_stateful/SLDJAVA_ACCESSOR_REQUEST.registered entries for FuctionName=JNDIName : {}#

#1.5 #221C4DDDA973004C00000004000030DB0004A0E4B435D648#1302804043256#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.handleRequest#J2EE_GUEST#0##n/a##1d98cf7066c111e0a58a221c4ddda973#SAPEngine_Application_Thread[impl:3]_7##0#0#Error##Plain###java.lang.RuntimeException: Bean SLDJAVA_ACCESSOR_REQUESTnot found on host htlssolm, ProgId =SAPSLD_SM9: Path to object does not exist at rfcaccessejb_stateful, the whole lookup name is rfcaccessejb_stateful/SLDJAVA_ACCESSOR_REQUEST.#

#1.5 #221C4DDDA973004C00000005000030DB0004A0E4B435D706#1302804043256#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.handleRequest#J2EE_GUEST#0##n/a##1d98cf7066c111e0a58a221c4ddda973#SAPEngine_Application_Thread[impl:3]_7##0#0#Error##Plain###java.lang.RuntimeException: Bean SLDJAVA_ACCESSOR_REQUESTnot found on host htlssolm, ProgId =SAPSLD_SM9: Path to object does not exist at rfcaccessejb_stateful, the whole lookup name is rfcaccessejb_stateful/SLDJAVA_ACCESSOR_REQUEST.

at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:138)

at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:254)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

#

#1.5 #221C4DDDA973004D00000003000030DB0004A0E4B4368EF4#1302804043303#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine#J2EE_GUEST#0##n/a##1da21e4066c111e0be3b221c4ddda973#SAPEngine_Application_Thread[impl:3]_12##0#0#Error#1#/System/Server#Plain###Bean SLDJAVA_ACCESSOR_REQUESTnot found on host htlssolm, ProgId =SAPSLD_SM9: Path to object does not exist at rfcaccessejb_stateful, the whole lookup name is rfcaccessejb_stateful/SLDJAVA_ACCESSOR_REQUEST.registered entries for FuctionName=JNDIName : {}#

#1.5 #221C4DDDA973004D00000004000030DB0004A0E4B4369034#1302804043303#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.handleRequest#J2EE_GUEST#0##n/a##1da21e4066c111e0be3b221c4ddda973#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain###java.lang.RuntimeException: Bean SLDJAVA_ACCESSOR_REQUESTnot found on host htlssolm, ProgId =SAPSLD_SM9: Path to object does not exist at rfcaccessejb_stateful, the whole lookup name is rfcaccessejb_stateful/SLDJAVA_ACCESSOR_REQUEST.#

#1.5 #221C4DDDA973004D00000005000030DB0004A0E4B4369107#1302804043304#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.handleRequest#J2EE_GUEST#0##n/a##1da21e4066c111e0be3b221c4ddda973#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain###java.lang.RuntimeException: Bean SLDJAVA_ACCESSOR_REQUESTnot found on host htlssolm, ProgId =SAPSLD_SM9: Path to object does not exist at rfcaccessejb_stateful, the whole lookup name is rfcaccessejb_stateful/SLDJAVA_ACCESSOR_REQUEST.

at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:138)

at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:254)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

#

#1.5 #221C4DDDA973004E00000001000030DB0004A0EB3553F849#1302831979295#com.sap.sl.ut##com.sap.sl.ut####n/a##28c5c4c0670211e09335221c4ddda973#SAPEngine_System_Thread[impl:5]_22##0#0#Info#1#/System/Server#Plain###Establishing db connection...#

#1.5 #221C4DDDA973004E00000003000030DB0004A0EB355464D4#1302831979323#com.sap.sl.ut##com.sap.sl.ut####n/a##28c5c4c0670211e09335221c4ddda973#SAPEngine_System_Thread[impl:5]_22##0#0#Info#1#/System/Server#Plain###Successfully established!#

#1.5 #221C4DDDA973004E00000005000030DB0004A0EB355465E7#1302831979323#com.sap.sl.ut##com.sap.sl.ut####n/a##28c5c4c0670211e09335221c4ddda973#SAPEngine_System_Thread[impl:5]_22##0#0#Info#1#/System/Server#Plain###Constructing System Info...#

#1.5 #221C4DDDA973004E00000007000030DB0004A0EB35546A51#1302831979325#com.sap.sl.ut##com.sap.sl.ut####n/a##28c5c4c0670211e09335221c4ddda973#SAPEngine_System_Thread[impl:5]_22##0#0#Info#1#/System/Server#Plain###fillProducts(): Filling products array ...#

#1.5 #221C4DDDA973004E00000009000030DB0004A0EB3554775B#1302831979328#com.sap.sl.ut##com.sap.sl.ut####n/a##28c5c4c0670211e09335221c4ddda973#SAPEngine_System_Thread[impl:5]_22##0#0#Info#1#/System/Server#Plain###fillProducts(): Adding product ...#

#1.5 #221C4DDDA973004E0000000B000030DB0004A0EB35547CD3#1302831979329#com.sap.sl.ut##com.sap.sl.ut####n/a##28c5c4c0670211e09335221c4ddda973#SAPEngine_System_Thread[impl:5]_22##0#0#Info#1#/System/Server#Plain###fillPartsForProduct: Adding part to product -NetWeaver ...#

#1.5 #221C4DDDA973004E0000000D000030DB0004A0EB35548833#1302831979332#com.sap.sl.ut##com.sap.sl.ut####n/a##28c5c4c0670211e09335221c4ddda973#SAPEngine_System_Thread[impl:5]_22##0#0#Info#1#/System/Server#Plain###fillPartsForProduct: Adding part - AS - to product -NetWeaver ...#

#1.5 #221C4DDDA973004E0000000F000030DB0004A0EB35548943#1302831979332#com.sap.sl.ut##com.sap.sl.ut####n/a##28c5c4c0670211e09335221c4ddda973#SAPEngine_System_Thread[impl:5]_22##0#0#Info#1#/System/Server#Plain###fillPartsForProduct: Adding part to product -NetWeaver ...#

.#

#1.5 #221C4DDDA97300500000004E000030DB0004A0EE774A0EC3#1302845970844#com.sap.engine.core.thread.impl5.ThreadManagerImpl##com.sap.engine.core.thread.impl5.ThreadManagerImpl#J2EE_GUEST#0#####Thread[Thread-46,5,main]##0#0#Error##Plain###Unexpected thread activity after interrupt() is executed in shutdown of SAPEngine_System_Thread[impl:5]_ThreadManager:

Thread[SAPEngine_System_Thread[impl:5]_97]

Task: com.sap.engine.core.thread.impl5.ActionObject - Processing Task [classname: com.sap.engine.services.log_configurator.archive.ArchivingThread | toString: com.sap.engine.services.log_configurator.archive.ArchivingThread@13c32369] with classloader [com.sap.engine.core.service630.container.ComponentClassLoader@641a034d@service:log_configurator]#

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

There is no relevant error in the log. Could you please give a restart to the system again and paste dev_server0 and sted_server0 logs here ?

Thanks

Sunny

Former Member
0 Kudos

Thanks Sunny, the issue is resolved. We had changed the J2EE_ADMIN password in secure store but somehow either it was not saved properly or someone got it locked by incorrect logins.

Resolved by resetting it.

Regards,

Sabita