Skip to Content
author's profile photo Former Member
Former Member

Install SP10 WAS 6.40 fails at phase 17 Deploy via SDM

Running on UNIX and during J2EE SP 10 upgrade everything is fine until Phase 17.

I tried restart the J2EE engine, but it seems the dispatcher and server comes up fine but the SDM does start....

During the SDM deploy the install fails with the following excerpt sapinst log:

Jan 14, 2005 10:35:57... Info: Software type of SDA: J2EE

Jan 14, 2005 10:35:57... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE A

pplication) *****

Jan 14, 2005 10:35:59... Info: ***** End of SAP J2EE Engine Deployment (J2EE App

lication) *****

Jan 14, 2005 10:35:59... Error: Aborted: development component 'tc/webadministra

tor/dsalias'/'sap.com'/'SAP AG'/'6.4010.00.0000.20041202145645.0000':

Caught exception while checking the login credentials for SAP J2EE Engine. Check

whether the SAP J2EE Engine 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.EngineApplOnlineDepl

oyerImpl.checkLoginCredentials.DMEXC)

Jan 14, 2005 10:35:59... Info: J2EE Engine is in same state (online/offline) as

it has been before this deployment process.

Jan 14, 2005 10:35:59... Info: -


Deployment was successful -


-


Jan 14, 2005 10:35:59... Info: Summarizing the deployment results:

Jan 14, 2005 10:35:59... Error: Admitted: /usr/sap/J2EE_PATCH10/J2EE-RUNT-

CD/J2EE-ENG/ONLINE/SAPJTECHS10_0.SCA

Jan 14, 2005 10:35:59... Error: Admitted: /usr/sap/J2EE_PATCH10/J2EE-RUNT-

CD/J2EE-ENG/ONLINE/LMSERVICE10_0.SCA

Jan 14, 2005 10:35:59... Error: Processing error. Return code: 4

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jan 14, 2005 at 04:56 PM

    Hi John

    i have the same error message when i upgrade from WAS Java SP9 to WAS Java SP10 but the WAS is running on Windows.

    Anybody an idea ?

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 17, 2005 at 09:41 PM

    Sorry if this is too obvious, but did you make sure you have the right password for J2EE_ADMIN?

    com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to H

    ost: [mako] with user name: [J2EE_ADMIN]

    Check your login information.

    You can check your security log to see if the J2EE_ADMIN login fails by the installer.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Feb 02, 2005 at 10:32 AM

    I am also trying to upgrade Portal cluster in Windows platform from stack9 to stack10. During the upgrade of the Web AS, I have got processing error with return code 4 during the deploy online step (Deploy via SDM/J2EE) phase 18/22. Below is the log showing the error:

    Feb 2, 2005 10:35:11 AM Info: Software type of SDA: J2EE

    Feb 2, 2005 10:35:11 AM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****

    Feb 2, 2005 10:35:14 AM Info: Begin of log messages of the target system:

    05/02/02 10:35:12 - ***********************************************************

    05/02/02 10:35:13 - Start updating EAR file...

    05/02/02 10:35:13 - start-up mode is lazy

    05/02/02 10:35:13 - EAR file updated successfully for 156ms.

    05/02/02 10:35:13 - Start deploying ...

    05/02/02 10:35:13 - EAR file uploaded to server for 94ms.

    05/02/02 10:35:14 - ERROR: Not deployed. Deploy Service returned ERROR:

    java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/tc_webadministrator_abapsyssetup.ear.

    Reason: None of the available containers recognized the components of application sap.com/tcwebadministratorabapsyssetup; it is not possible to make deploy.

    at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:480)

    at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)

    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:291)

    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)

    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)

    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)

    at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)

    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:94)

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

    For detailed information see the log file of the Deploy Service.

    05/02/02 10:35:14 - ***********************************************************

    Feb 2, 2005 10:35:14 AM Info: End of log messages of the target system.

    Feb 2, 2005 10:35:14 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****

    Feb 2, 2005 10:35:14 AM Error: Aborted: development component 'tc/webadministrator/abapsyssetup'/'sap.com'/'SAP AG'/'6.4010.00.0000.20041202145645.0000':

    Caught exception during application deployment from SAP J2EE Engine's deploy service:

    java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/tc_webadministrator_abapsyssetup.ear.

    Reason: None of the available containers recognized the components of application sap.com/tcwebadministratorabapsyssetup; it is not possible to make deploy.

    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)

    Feb 2, 2005 10:35:14 AM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.

    Feb 2, 2005 10:35:14 AM Info: -


    Deployment was successful -


    Feb 2, 2005 10:35:14 AM Info: Summarizing the deployment results:

    Feb 2, 2005 10:35:14 AM Error: Admitted: F:\EP 6.0\NW04\Stack10\WebAS SP10\J2EE-RUNT-CD\J2EE-ENG\ONLINE\SAPJTECHS10_0.SCA

    Feb 2, 2005 10:35:14 AM Error: Admitted: F:\EP 6.0\NW04\Stack10\WebAS SP10\J2EE-RUNT-CD\J2EE-ENG\ONLINE\LMSERVICE10_0.SCA

    Feb 2, 2005 10:35:14 AM Error: Processing error. Return code: 4

    Any idea will be greatly appreciated!!

    Ahmed.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Vladimir Pavlov

      hello Ahmed,

      i recently installed sp10 on windows and ran into a very simlilar error, if not identical, during sdm online deploy phase. it was also complaining about some ear file related to webadministrator.

      since i didn't care about any abap component or this new webadministrator application, what i ended up doing was to remove LMSERVICE10_0.SCA from the deploy.list, which is located at:

      <your sp10 direcytory>\J2EE-RUNT-CD\J2EE-ENG\ONLINE\.

      in the DEPLOY.LST file you will find two .SCA entries. i believe the first one, SAPJTECHS10_0.SCA, is the core of the patch. the second one, LMSERVICE10_0.SCA, contains some new administrative utilities and tools.

      if you don't care about the utils and really want to complete the patch for now, edit deploy.lst and continue with the installation of sp10. i got this tip from searching sap notes and reading a not-too-related note, not even for net weaver.

      also try the trick of manually stopping and starting the instance via sap mmc, in case the installation script has trouble restarting the instance. after a few tries, i was able to get the sp10 installed. everything works fine. but i did notice that in visual admin tool, deploy service, many of the webadministration app components are not in the running status.

      there are definitely bugs in sp10 install script. it would be good if eventually we get perform clean installations without errors and modifications.

      hope the above helps and good luck.

  • author's profile photo Former Member
    Former Member
    Posted on Feb 03, 2005 at 10:26 AM

    Thanks to you both Vladimir and Wentao for the suggestions, I will give it a try then will let you know if I have a success.

    Best regards,

    Ahmed.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.