I installed WAS 6.40 on unix and now I am upgrading to Stack 04 which is the J2EE 7 patch.
I started the upgrade via sapinst and everything going fine until the online deploy near the end of the install, when it shows SDM not running. The server and dispatcher is running fine, and checked out via jcmon.
The Online deploy fails and SAPINST stops. I only has two more steps and it is done with the upgrade.
Has anyone seen an issue with SDM not performing online deploy...because SDM is not running?
I do not think there is any issue with going from sp03 that is installed up to sp7 right? (which is Stack 04)
I can deploy via SDM standalone but when running the instance the server and dispatcher are running but not the SDM.
Thanks
John
2 Answers
-
Former MemberPosted on Dec 26, 2004 at 05:45 PMHi
I have come across this problem quite a few times. Mostly if the case repeats then it is not a genuine error and a fake alarm. If it is possible for u, i would suggest stopping the j2ee system and restarting it, and then continue with the patch. and to the suprise it may go past the phase if all other parameters are ok.
Cheers,
Chetan
Add a comment
-
Former MemberPosted on Dec 29, 2004 at 10:20 PM
The SDM log looks like this:
Dec 29, 2004 5:08:20 PM Error: Aborted: development component 'tc/workflowmodel
er'/'sap.com'/'SAP AG'/'6.3007.00.0000.20040609164604.0000':
CPO data could not be get.
com.sap.sdm.apiint.serverext.servertype.deployment.DeploymentActionException: Er
ror: Caught the following error or exception: "com.sap.sdm.apiint.serverext.serv
ertype.deployment.DeploymentActionException"
Additional error message is:
Caught exception from deploy service of SAP J2EE Engine. Caught exception while
checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE E
ngine is up and running.
com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to H
ost: [mako] with user name: [J2EE_ADMIN]
Check your login information.
Exception is:
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception wh
ile trying to get InitialContext. [Root exception is com.sap.engine.services.sec
urity.exceptions.BaseLoginException: Cannot create new RemoteLoginContext instan
ce.]
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineD
eployerImpl.checkLoginCredentials.DMEXC)
Additional error message is:
com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to H
ost: [mako] with user name: [J2EE_ADMIN]
Check your login information.
Exception is:
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception wh
ile trying to get InitialContext. [Root exception is com.sap.engine.services.sec
urity.exceptions.BaseLoginException: Cannot create new RemoteLoginContext instan
ce.]
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineD
eployerImpl.performAction(DeploymentActionTypes).NO_CPO)
Dec 29, 2004 5:08:21 PM Info: J2EE Engine is in same state (online/offline) as
it has been before this deployment process.
Dec 29, 2004 5:08:21 PM Info: -
Deployment was successful -
-
Dec 29, 2004 5:08:21 PM Info: Summarizing the deployment results:
Dec 29, 2004 5:08:21 PM Error: Admitted: /usr/sap/trans/J2EE_PATCH/J2EE-RUNT-CD
/J2EE-ENG/ONLINE/SAPJTECHS07_0.SCA
Dec 29, 2004 5:08:21 PM Error: Processing error. Return code: 4
I read through note 756084 and can log in wioth J2EE_ADMIN id just fine. The note references the exact problem and error message. per the note I change authentication as specified in the note and restart instance and still have this issue popup during the final stages of sapinst.
Anyone help?
thanks
John
Add a comment
Add a comment