Skip to Content
avatar image
Former Member

sneak preview WAS 6.4 installation -- second last step

May 02, 2004 at 04:10 PM | 5 Views

The second last installation step fails on my system

with the following log message in the file

callSdmViaSapinst.log:

May 2, 2004 11:08:05 AM Info: Start logging to console

May 2, 2004 11:08:05 AM Info:

May 2, 2004 11:08:05 AM Info: ============================================

May 2, 2004 11:08:05 AM Info: = Starting to execute command 'deploy' =

May 2, 2004 11:08:05 AM Info: ============================================

May 2, 2004 11:08:05 AM Info: Starting SDM - Software Deployment Manager...

May 2, 2004 11:08:06 AM Info: tc/SL/SDM/SDM/sap.com/SAP AG/6.3004.00.0000.20040204183620.0000

May 2, 2004 11:08:07 AM Info: SDM operation mode successfully set to: Standalone

May 2, 2004 11:08:08 AM Info: Initializing Network Manager (50017)

May 2, 2004 11:08:08 AM Info: Checking if another SDM is running on port 50018

May 2, 2004 11:08:08 AM Info: -

Starting deployment -

May 2, 2004 11:08:08 AM Info: Loading selected archives...

May 2, 2004 11:08:08 AM Info: Loading archive 'C:\SAP\SAPinst_WAS\J2EE-CD\J2EE-ENG\ONLINE\SAPJTECHS04_0.SCA'

May 2, 2004 11:08:18 AM Info: Selected archives successfully loaded.

May 2, 2004 11:08:19 AM Info: Actions per selected component:

May 2, 2004 11:08:19 AM Info: development component 'com.sap.security.core.admin'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040203163559.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'com.sap.aii.ibtranslationclient'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040120173557.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'com.sap.aii.proxy.framework'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040120173557.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'com.sap.rprof.jddschema'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040203163504.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'tc/SL/UTIL_JDD'/'sap.com'/'SAP AG'/'6.3004.00.0000.20031022133109.0000': useexisting

May 2, 2004 11:08:19 AM Info: software component 'SAP_JTECHS'/'sap.com'/'SAP AG'/'1000.6.30.4.0.20040212152521': deploy

May 2, 2004 11:08:19 AM Info: development component 'com.sap.engine.docs.examples'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040205154547.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'com.sap.engine.class.download'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040205154547.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'com.sap.lcr.jddschema'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040204183559.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'com.sap.lcr.saprfc'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040204183559.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'tc/uddi'/'sap.com'/'SAP AG'/'6.3004.00.0000.20031118214805.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'tc/wd/pdfsvrchal'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040204185252.0000': deploy

May 2, 2004 11:08:19 AM Info: development component 'com.sap.jdo'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040203164404.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'com.sap.aii.util.rb'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040120173557.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'com.sap.util.monitor.grmg'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040203162838.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'com.sap.mobile.clientinfo'/'sap.com'/'SAP AG'/'6.3004.00.0000.20031008103221.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'tc/SL/CMS/IDEClient'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040128131819.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'SQLTrace'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040204181929.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'com.sap.lcr.namealloc'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040204183559.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'com.sap.lcr'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040204183559.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'com.sap.aii.ibtransportclient'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040120173557.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'com.sap.rprof.remoteProfile'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040203163504.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'tc/SL/UTIL'/'sap.com'/'SAP AG'/'6.3004.00.0000.20031022133109.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'com.sapmarkets.mesyncjco'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040203163438.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'com.sap.ip.me.webconsole'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040120173114.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'tc/wd/pdfobject'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040205111447.0000': deploy

May 2, 2004 11:08:19 AM Info: development component 'tc/uddi/dbschema'/'sap.com'/'SAP AG'/'6.3004.00.0000.20031118214805.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'com.sap.lcrabapapi'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040114175434.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'tc/sec/app'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040203162810.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'tc/sec/wssec/app'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040203162810.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'com.sap.util.monitor.jarm.j2ee'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040114180217.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'com.sapportals.htmlb.ear'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040114175417.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'tc/wd/tools'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040204185252.0000': deploy

May 2, 2004 11:08:19 AM Info: development component 'com.sap.aii.util.xml'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040120173557.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'tc/wd/dispwda'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040205111447.0000': deploy

May 2, 2004 11:08:19 AM Info: development component 'tc/wd/corecomp'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040204185252.0000': deploy

May 2, 2004 11:08:19 AM Info: development component 'com.sapportals.htmlb'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040114175417.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'synclog'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040204181929.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'com.sap.rprof.dbprofiles'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040203163504.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'com.sap.engine.services.webservices.tool'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040205154547.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'com.sap.aii.util.misc'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040120173557.0000': useexisting

May 2, 2004 11:08:19 AM Info: development component 'tc/sld/data'/'sap.com'/'SAP AG'/'6.3004.00.0000.20040204183559.0000': useexisting

May 2, 2004 11:08:20 AM Info: SDM configuration: Do not automatically start/stop J2EE Engine. Do not save current state of J2EE Engine now.

May 2, 2004 11:08:20 AM Info: Error handling strategy: OnErrorStop

May 2, 2004 11:08:20 AM Info: Update strategy: UpdateLowerVersions

May 2, 2004 11:08:20 AM Info: Starting to execute deployment action (deploy) for "tc/wd/dispwda".

May 2, 2004 11:08:20 AM Info: SDA to be deployed: C:\usr\sap\J2E\JC00\SDM\root\origin\sap.com\tc\wd\dispwda\SAP AG\6.3004.00.0000.20040205111447.0000\WebDynproDispWda.sda

May 2, 2004 11:08:20 AM Info: Software type of SDA: J2EE

May 2, 2004 11:08:24 AM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****

May 2, 2004 11:08:53 AM Info: Begin of log messages of the target system:

04/05/02 11:08:25 - ***********************************************************

04/05/02 11:08:27 - Start updating EAR file...

04/05/02 11:08:29 - EAR file updated successfully for 1625ms.

04/05/02 11:08:29 - Start deploying ...

04/05/02 11:08:52 - ERROR : com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [jordan] with UserName: [Administrator]

Check your Login Info.

Exception is:

com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot create new RemoteLoginContext instance.]

at com.sap.engine.deploy.manager.DeployManagerImpl.setBroker(DeployManagerImpl.java:3516)

at com.sap.engine.deploy.manager.DeployManagerImpl.makeNewConnection(DeployManagerImpl.java:3483)

at com.sap.engine.deploy.manager.DeployManagerImpl.deployUpdateAction(DeployManagerImpl.java:589)

at com.sap.engine.deploy.manager.DeployManagerImpl.deploy(DeployManagerImpl.java:506)

at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:167)

at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:97)

at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:216)

at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:63)

at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:181)

at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:51)

at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)

at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)

at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:72)

at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:85)

at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:71)

at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:122)

at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:91)

at com.sap.sdm.control.command.cmds.Deploy.execute(Deploy.java:168)

at com.sap.sdm.control.command.decorator.AssureStandaloneMode.execute(AssureStandaloneMode.java:53)

at com.sap.sdm.control.command.decorator.AssureOneRunningSDMOnly.execute(AssureOneRunningSDMOnly.java:61)

at com.sap.sdm.control.command.decorator.SDMInitializer.execute(SDMInitializer.java:52)

at com.sap.sdm.control.command.decorator.GlobalParamEvaluator.execute(GlobalParamEvaluator.java:60)

at com.sap.sdm.control.command.decorator.AbstractLibDirSetter.execute(AbstractLibDirSetter.java:46)

at com.sap.sdm.control.command.decorator.ExitPostProcessor.execute(ExitPostProcessor.java:48)

at com.sap.sdm.control.command.decorator.CommandNameLogger.execute(CommandNameLogger.java:49)

at com.sap.sdm.control.command.decorator.AdditionalLogFileSetter.execute(AdditionalLogFileSetter.java:65)

at com.sap.sdm.control.command.decorator.AbstractLogDirSetter.execute(AbstractLogDirSetter.java:54)

at com.sap.sdm.control.command.Command.exec(Command.java:42)

at SDM.main(SDM.java:21)

04/05/02 11:08:52 - ***********************************************************

May 2, 2004 11:08:53 AM Info: End of log messages of the target system.

May 2, 2004 11:08:53 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****

May 2, 2004 11:08:53 AM Error: Execution of deployment action for "tc/wd/dispwda" aborted:

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

com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [jordan] with UserName: [Administrator]

Check your Login Info.

Exception is:

com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot create new RemoteLoginContext instance.]

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

May 2, 2004 11:08:53 AM Error: Deployment NOT successful for tc/wd/dispwda

May 2, 2004 11:08:53 AM Info: SDM configuration: Do not automatically start/stop J2EE Engine. Do not restore state of J2EE Engine now.

May 2, 2004 11:08:53 AM Info: -

Deployment was successful -

May 2, 2004 11:08:53 AM Info: Summarizing the deployment results:

May 2, 2004 11:08:53 AM Error: Admitted: C:\SAP\SAPinst_WAS\J2EE-CD\J2EE-ENG\ONLINE\SAPJTECHS04_0.SCA

May 2, 2004 11:08:53 AM Error: Processing error. Return code: 4

Any help aapreciated.

Matthias

SAP NetWeaver Application Server
Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • avatar image
    Benny Schaich-Lebek
    May 03, 2004 at 08:27 AM

    Could it be, that you stopped installation and continued it later? Could it be you changed something in you passwords then?

    Regards,

    Benny

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member
      May 03, 2004 at 12:32 PM

      Yes and no 😊

      Yes: during installation, my home system rebooted.

      I assume because of RAM problems (but am not really

      sure, actually. I tried to install with 256 MB only

      over the week-end.) I don't remember when the reboot

      occured, but it was near the end of the installation

      procedure and before the second last step.

      So it might be that due to the reboot soemthing didn't get

      installed properly, and that might be the reason for the

      failure later on. It must be something the installation

      procedure doesn't check though.

      No: I didn't change any passwords.

      On a different note, I was successful today on a 1GB RAM

      system.

      Matthias