cancel
Showing results for 
Search instead for 
Did you mean: 

Error in deploying first Webdynpro at SDM

Former Member
0 Kudos

Hi,

I have received the following error messages,after deploying the code(first webdynpro application) downloaded from SDN website.Similar error i got when i developed first webdynpro application using the help provided...

===========

An exception occured while deploying:

com.tssap.j2ee.ui.core.deploy.DeploymentException

Problems during deployment !

Deploy on SDM

==> Host is : localhost

==> Port is : 50018u00A0u00A0u00A0--> Created deploy item 0 for file:/C:/Documents and

Settings/Somnath/Desktop/Welcome/Welcome.earu00A0u00A0u00A0--> Deployment of item 0

executed but aborted: Execution of deployment Welcome aborted.

Error: Caught

exception during application deployment from SAP J2EE Engine's deploy

API:

com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot

connect to Host: [localhost] with UserName: [Administrator]u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0Check your

Login Info.u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0Exception is:

com.sap.engine.services.jndi.persistent.exceptions.NamingException:

Exception during getInitialContext operation. No server is running(Wrapped

by

com.sap.sdm.serverext.servertype.inqmy.icw.DeployManagerException)

Contents

of the log file of the target system:

03/10/27 21:25:01 -u00A0u00A0

***********************************************************

03/10/27

21:25:03 -u00A0u00A0Start updating EAR file...

03/10/27 21:25:03 -u00A0u00A0EAR file updated

successfully for 551s.

03/10/27 21:25:03 -u00A0u00A0Start deploying ...

03/10/27

21:25:10 -u00A0u00A0ERROR : com.sap.engine.deploy.manager.DeployManagerException:

ERROR: Cannot connect to Host: [localhost] with UserName: [Administrator]

u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0Check your Login Info.

u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0Exception is:

com.sap.engine.services.jndi.persistent.exceptions.NamingException:

Exception during getInitialContext operation. No server is running

u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0at

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

u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0at

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

u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0at

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

u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0at

com.sap.engine.deploy.manager.DeployManagerImpl.deploy(DeployManagerImpl.java:469)

u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0at java.lang.reflect.Method.invoke(Native Method)

u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0at

com.sap.sdm.serverext.servertype.inqmy.icw.IcwAbstractClassWrapper.icwInvokeInstanceMethod(IcwAbstractClassWrapper.java:303)

u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0at

com.sap.sdm.serverext.servertype.inqmy.icw.IcwAbstractClassWrapper.icwInvokeInstanceMethod(IcwAbstractClassWrapper.java:278)

u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0at

com.sap.sdm.serverext.servertype.inqmy.icw.IcwInstanceWrapperDeployManager.deploy(IcwInstanceWrapperDeployManager.java:292)

u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0at

com.sap.sdm.serverext.servertype.inqmy.EngineApplOnlineDeployer.performAction(EngineApplOnlineDeployer.java:198)

u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0at

com.sap.sdm.serverext.servertype.inqmy.EngineDeployer.act(EngineDeployer.java:68)

u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0at

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

u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0at

com.sap.sdm.flow.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:62)

u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0at

com.sap.sdm.flow.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:234)

u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0at

com.sap.sdm.flow.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:50)

u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0at

com.sap.sdm.inststate.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:82)

u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0at

com.sap.sdm.inststate.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:63)

u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0at

com.sap.sdm.inststate.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:80)

u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0at

com.sap.sdm.inststate.InstContext.processEventServerSide(InstContext.java:116)

u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0at

com.sap.sdm.inststate.InstContext.processEvent(InstContext.java:72)

u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0at

com.sap.sdm.flow.controllers.impl.DeployerImpl.deploy(DeployerImpl.java:440)

u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0at

com.sap.sdm.apiimpl.local.DeployProcessorImpl.deploy(DeployProcessorImpl.java:57)

u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0at java.lang.reflect.Method.invoke(Native Method)

u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0at

com.sap.sdm.client_server.guiandapiserver.impl.GuiServer.requestRemoteCall(GuiServer.java:1140)

u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0at

com.sap.sdm.client_server.guiandapiserver.impl.GuiServer.serve(GuiServer.java:202)

u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0at com.sap.bc.cts.tp.net.Worker.run(Worker.java:44)

u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0u00A0at java.lang.Thread.run(Thread.java:479)

03/10/27

21:25:10 -u00A0u00A0***********************************************************

(error ID:

com.sap.sdm.serverext.servertype.inqmy.EngineApplOnlineDeployer.performAction(int).DMEXC)

Please make sure that the J2EE and SDM server settings are correct and both

servers have been started.

===================================================================

I have tested the SDM individually i got the following messages

-


Trying to call SDM

==> Host is : localhost

==> Port is : 50018

==> Remote session succesfully created !

==> Client succesfully retrieved from session !

==> SDM configuration succesfully retrieved from client !

==> server types of SDM configuration !

u00A0u00A0u00A0u00A0-> Java-FS (Server for Filesystem-Deployment)

u00A0u00A0u00A0u00A0-> SAP J2EE Engine (Server for J2EE Software)

u00A0u00A0u00A0u00A0-> DATABASE (Server for Database Schema and Content)

==> target systems of SDM configuration !

u00A0u00A0u00A0u00A0-> FileSystem (null)

u00A0u00A0u00A0u00A0u00A0u00A0u00A0Java-FS (Server for Filesystem-Deployment)

u00A0u00A0u00A0u00A0-> SapJ2EEEngine (null)

u00A0u00A0u00A0u00A0u00A0u00A0u00A0SAP J2EE Engine (Server for J2EE Software)

u00A0u00A0u00A0u00A0-> CONFIG_DB (null)

u00A0u00A0u00A0u00A0u00A0u00A0u00A0DATABASE (Server for Database Schema and Content)

==> substitution variables of SDM configuration !

u00A0u00A0u00A0u00A0-> com.sap.engine.installdir (STRING) = C:\usr\sap/C11/JC00/j2ee

u00A0u00A0u00A0u00A0-> com.sap.systemdir (STRING) = C:\usr\sap\C11\SYS\global

u00A0u00A0u00A0u00A0-> com.sap.instancedir (STRING) = C:\usr\sap/C11/JC00

u00A0u00A0u00A0u00A0-> com.sap.SID (STRING) = C11

u00A0u00A0u00A0u00A0-> com.sap.InstanceNumber (STRING) = 00

u00A0u00A0u00A0u00A0-> com.sap.datasource.default (STRING) = SAPC11DB

==> Session was closed !

-


Your help is highly appreciated

Thanks

Senthil

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello Senthil,

testing the SDN connection may return a positive result and the J2EE engine still be down since these are two different processes. Please check in the SAP Management Console if the J2EE engine is up and running and restart it if necessary.

If your installation of the Sneak Preview edition is older than 90 days the server is shut down automatically without notification. This may be a potential reason why the server process could be down.

Cheers

Ivo

Former Member
0 Kudos

Hi Ivo,

J2EE engine is running fine and SAP WAS sneak preview we recently installed, it is not older than 90 days.I have tried with the SAP WAS CD from SAP i am facing the same problem, i downloaded from SDN and tested again, i am getting the same error.

Expecting your thoughts, so that i can proceed further with SAP WAS, i am not able to do any further work on Webdynpro.

Thanks

Senthil

Former Member
0 Kudos

Hello Senthil,

please check out two things:

a) Is the server really running? Please start the SAP Management Console and check if all the icons are green.

b) Can you please try to deploy the project coming with "Create your first J2EE application" on SDN? It is not bound to Web Dynpro and would give us information if the problem is related to Web Dynpro or more general.

Many greetings

Ivo

Former Member
0 Kudos

Hi Ivo,

i have excatly the same problem with the "Create your first J2EE application".

What shall i do?

Greeting,

Diedrich

Former Member
0 Kudos

Hello Diedrich,

we will issue a new version of the Sneak Preview edition  (with many, many bugs fixed) for download on SDN in the second week of February. My recommendation is to try this new version -the error will hopefully not appear anymore.

Many greetings

Ivo