cancel
Showing results for 
Search instead for 
Did you mean: 

JSPM : Deployment Stopped in between

Former Member
0 Kudos

Hi experts,

Today I was updating Enterprise Support Portal from SP11 to SP21

(SAP Netweaver7.0 )

Half of the component Deployed successfully. But Rest of the component ended in error

I checked J2ee instance are runnig fine (server0,Dispatcher and SDM). But http://<hostname>:5000 [engine] is not up

i.e 503 service not available

Error in JSPM Tool :

/usr/sap/<SID>/JC00/SDM/program/log

-


more sdmcl20110810092246.log

<!LOGHEADER[START]/>

<!HELP[Manual modification of the header may cause parsing problem!]/>

<!LOGGINGVERSION[1.5.3.7185 - 630]/>

<!NAME[/usr/sap/<SID>/JC00/SDM/program/log/sdmcl20110810092246.log]/>

<!PATTERN[sdmcl20110810092246.log]/>

<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>

<!ENCODING[UTF8]/>

<!LOGHEADER[END]/>

Aug 10, 2011 5:22:46 PM Info: -


Starting validation -


Aug 10, 2011 5:22:46 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorSkipDepending

Aug 10, 2011 5:22:46 PM Info: Update strategy: UpdateLowerOrChangedVersions

Aug 10, 2011 5:22:46 PM Info: Starting deployment prerequisites:

Aug 10, 2011 5:22:49 PM Info: Loading selected archives...

Aug 10, 2011 5:22:49 PM Info: Loading archive '/usr/sap/trans/EPS/in/UMEADMIN21_0-10003471.SCA'

Aug 10, 2011 5:22:52 PM Info: Selected archives successfully loaded.

Aug 10, 2011 5:22:52 PM Info: Actions per selected component:

Aug 10, 2011 5:22:52 PM Info: Update: Selected development component 'tc/sec/ume/wd/kit'/'sap.com'/'MAIN_APL70P21_C'/'6993713

Aug 10, 2011 5:22:52 PM Info: Update: Selected development component 'tc/sec/ume/wd/uimodel'/'sap.com'/'MAIN_APL70P21_C'/'699

3607'/'0' updates currently deployed development component 'tc/sec/ume/wd/uimodel'/'sap.com'/'MAIN_APL70VAL_C'/'1077443'/'0'.

Aug 10, 2011 5:22:52 PM Info: Update: Selected development component 'tc/sec/ume/wd/waplugin'/'sap.com'/'MAIN_APL70P21_C'/'69

93957'/'0' updates currently deployed development component 'tc/sec/ume/wd/waplugin'/'sap.com'/'MAIN_APL70VAL_C'/'964690'/'0'.

Aug 10, 2011 5:22:52 PM Info: Update: Selected software component 'UMEADMIN'/'sap.com'/'MAIN_APL70P21_C'/'1000.7.00.21.0.2010

0106085247''/'0' updates currently deployed software component 'UMEADMIN'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.11.0.20070202

080641''/'0'.

Aug 10, 2011 5:22:52 PM Info: Update: Selected development component 'tc/sec/ume/wd/umeadmin'/'sap.com'/'MAIN_APL70P21_C'/'69

93786'/'0' updates currently deployed development component 'tc/sec/ume/wd/umeadmin'/'sap.com'/'MAIN_APL70VAL_C'/'1077807'/'0'

.

Aug 10, 2011 5:22:52 PM Info: Update: Selected development component 'tc/sec/ume/wd/enduser'/'sap.com'/'MAIN_APL70P21_C'/'699

3785'/'0' updates currently deployed development component 'tc/sec/ume/wd/enduser'/'sap.com'/'MAIN_APL70VAL_C'/'1077805'/'0'.

Aug 10, 2011 5:22:52 PM Info: Update: Selected development component 'tc/sec/ume/wd/batch'/'sap.com'/'MAIN_APL70P21_C'/'69937

11'/'0' updates currently deployed development component 'tc/sec/ume/wd/batch'/'sap.com'/'MAIN_APL70VAL_C'/'964645'/'0'.

Aug 10, 2011 5:22:52 PM Info: Update: Selected development component 'tc/sec/ume/wd/config'/'sap.com'/'MAIN_APL70P21_C'/'6993

712'/'0' updates currently deployed development component 'tc/sec/ume/wd/config'/'sap.com'/'MAIN_APL70VAL_C'/'1077666'/'0'.

Aug 10, 2011 5:22:52 PM Info: Ending deployment prerequisites. All items are correct.

Aug 10, 2011 5:22:53 PM Info: -


Ending validation -


Aug 10, 2011 5:22:53 PM Info: -


Starting deployment -


Aug 10, 2011 5:22:53 PM Info: Error handling strategy: OnErrorStop

Aug 10, 2011 5:22:53 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorSkipDepending

Aug 10, 2011 5:22:53 PM Info: Update strategy: UpdateLowerOrChangedVersions

Aug 10, 2011 5:22:53 PM Info: Starting deployment prerequisites:

Aug 10, 2011 5:22:54 PM Info: Loading selected archives...

Aug 10, 2011 5:22:54 PM Info: Loading archive '/usr/sap/trans/EPS/in/UMEADMIN21_0-10003471.SCA'

Aug 10, 2011 5:22:55 PM Info: Selected archives successfully loaded.

Aug 10, 2011 5:22:55 PM Info: Actions per selected component:

Aug 10, 2011 5:22:55 PM Info: Update: Selected development component 'tc/sec/ume/wd/kit'/'sap.com'/'MAIN_APL70P21_C'/'6993713

'/'0' updates currently deployed development component 'tc/sec/ume/wd/kit'/'sap.com'/'MAIN_APL70VAL_C'/'1077668'/'0'.

Aug 10, 2011 5:22:55 PM Info: Update: Selected development component 'tc/sec/ume/wd/approval'/'sap.com'/'MAIN_APL70P21_C'/'69

93608'/'0' updates currently deployed development component 'tc/sec/ume/wd/approval'/'sap.com'/'MAIN_APL70VAL_C'/'963550'/'0'.

Aug 10, 2011 5:22:55 PM Info: Update: Selected development component 'tc/sec/ume/wd/concheck'/'sap.com'/'MAIN_APL70P21_C'/'69

93714'/'0' updates currently deployed development component 'tc/sec/ume/wd/concheck'/'sap.com'/'MAIN_APL70VAL_C'/'1077670'/'0'

.

Aug 10, 2011 5:22:55 PM Info: Update: Selected development component 'tc/sec/ume/wd/uimodel'/'sap.com'/'MAIN_APL70P21_C'/'699

3607'/'0' updates currently deployed development component 'tc/sec/ume/wd/uimodel'/'sap.com'/'MAIN_APL70VAL_C'/'1077443'/'0'.

Aug 10, 2011 5:22:55 PM Info: Update: Selected development component 'tc/sec/ume/wd/waplugin'/'sap.com'/'MAIN_APL70P21_C'/'69

93957'/'0' updates currently deployed development component 'tc/sec/ume/wd/waplugin'/'sap.com'/'MAIN_APL70VAL_C'/'964690'/'0'.

Aug 10, 2011 5:22:55 PM Info: Update: Selected development component 'tc/sec/ume/wd/umeadmin'/'sap.com'/'MAIN_APL70P21_C'/'69

93786'/'0' updates currently deployed development component 'tc/sec/ume/wd/umeadmin'/'sap.com'/'MAIN_APL70VAL_C'/'1077807'/'0'

.

Aug 10, 2011 5:22:55 PM Info: Update: Selected software component 'UMEADMIN'/'sap.com'/'MAIN_APL70P21_C'/'1000.7.00.21.0.2010

0106085247''/'0' updates currently deployed software component 'UMEADMIN'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.11.0.20070202

080641''/'0'.

3550'/'0'.

Aug 10, 2011 5:22:56 PM Info: SDA to be deployed: /usr/sap/<SID>/JC00/SDM/root/origin/sap.com/tc/sec/ume/wd/approval/MAIN_APL70

P21_C/0/6993608/tcsecumewdapproval.sda

Aug 10, 2011 5:22:56 PM Info: Software type of SDA: J2EE

Aug 10, 2011 5:22:56 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****

Aug 10, 2011 5:22:58 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****

Aug 10, 2011 5:22:58 PM Error: Aborted: development component 'tc/sec/ume/wd/approval'/'sap.com'/'MAIN_APL70P21_C'/'6993608'/

'0', grouped by software component 'UMEADMIN'/'sap.com'/'MAIN_APL70P21_C'/'1000.7.00.21.0.20100106085247''/'0':

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 Host: [<hostname>] with user name: [Administrator

]

Check your login information.

Exception is:

com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is

running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteL

oginContext instance.]

at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:494)

at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:363)

at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)

at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)

at javax.naming.InitialContext.init(InitialContext.java:219)

at javax.naming.InitialContext.<init>(InitialContext.java:195)

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

at com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthMethodInvoker.invokeCheckCredentialsInternal(DeployM

anagerAuthMethodInvoker.java:51)

at com.sap.sdm.serverext.servertype.inqmy.extern.ExternalMethodInvoker.invokeCheckCredentials(ExternalMethodInvoker.ja

va:45)

at com.sap.sdm.serverext.servertype.inqmy.extern.ExternalMethodInvoker.invokeCheckCredentials(ExternalMethodInvoker.ja

va:32)

at com.sap.sdm.serverext.servertype.inqmy.extern.EngineOnlineDeployerImpl.checkLoginCredentials(EngineOnlineDeployerIm

pl.java:173)

at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeploy

erImpl.java:168)

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

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

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

:60)

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

at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.jav

a:48)

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.j

ava:60)

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

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

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

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

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

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

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

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:127)

at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38)

at com.sap.sdm.apiimpl.remote.server.ApiClientRoleCmdProcessor.process(ApiClientRoleCmdProcessor.java:84)

at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67)

at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76)

at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:286)

at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43)

at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39)

at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50)

at java.lang.Thread.run(Thread.java:534)

Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instan

ce.

at com.sap.engine.services.security.remote.login.RemoteLoginContextExt.<init>(RemoteLoginContextExt.java:34)

at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:81)

at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:355)

... 38 more

Caused by: com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.

Nested exception is:

java.io.EOFException: End of stream is reached unexpectedly during input from Socket[addr=/fe80:0:0:0:211:9ff:fe14:6a6

f,port=50004,localport=2259]

at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:737)

at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:712)

at com.sap.engine.services.security.remote.RemoteSecurity_Stub.getRemoteLoginContext(RemoteSecurity_Stub.java:674)

at com.sap.engine.services.security.remote.login.RemoteLoginContextExt.<init>(RemoteLoginContextExt.java:28)

... 40 more

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

Aug 10, 2011 5:22:58 PM Info: Starting to save the repository

Aug 10, 2011 5:22:58 PM Info: Finished saving the repository for 628 ms.

Aug 10, 2011 5:22:58 PM Info: Starting: Update: Selected software component 'UMEADMIN'/'sap.com'/'MAIN_APL70P21_C'/'1000.7.00

.21.0.20100106085247''/'0' updates currently deployed software component 'UMEADMIN'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.11.

0.20070202080641''/'0'.

Aug 10, 2011 5:22:58 PM Error: Aborted: software component 'UMEADMIN'/'sap.com'/'MAIN_APL70P21_C'/'1000.7.00.21.0.20100106085

247''/'0':

Failed deployment of SDAs:

development component 'tc/sec/ume/wd/approval'/'sap.com'/'MAIN_APL70P21_C'/'6993608'/'0' : aborted

Please, look at error logs above for more information!

Aug 10, 2011 5:22:58 PM Info: Starting to save the repository

Aug 10, 2011 5:22:59 PM Info: Finished saving the repository for 696 ms.

Aug 10, 2011 5:22:59 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.

Aug 10, 2011 5:22:59 PM Error: -


At least one of the Deployments failed -


-


Please help in resolving the issue

Regards,

Kamal

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

..

Former Member
0 Kudos

It is not able to pick your host name. There no problem with password. Check if your sdm server is up and you are able to log in and deploy stuff directly from there.

Former Member
0 Kudos

Hi Srikishan ,

Well , Thanks for your help

I was checking the log of dev_server0 . IT seems my J2ee engine is going out of memory . there is exception for end of stream.

Now I have raised a High priority

message and working with sap

I will paste the solution here as I will resolve the issue.

Regards,

Kamal

Former Member
0 Kudos

Issue has been resolved by bind host field

Former Member
0 Kudos

Hi,

ERROR: Cannot connect to Host: [] with user name: [Administrator ] Check your login information. Exception is: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteL oginContext instance.] at

Checn the login information for Administration user. If it is correct, make sure the same is maintained in the Config Tool secure store as well.

Regards,

Srikishan

Former Member
0 Kudos

Hi Srikishan

I was checking in the config tool . Then a pop came saying j2ee engine is started in safe mode. Then I turned off the safe mode and restarted the J2ee engine. It solved my problem of 503 service unavailable.

When I went to deploy rest of the component through JSPM. J2ee engine went into the safe mode and my deployment ended in error

How to come out from this situation ?

Regards,

Kamal

Former Member
0 Kudos

Hi Kamal,

The deployment usually makes the system to go into the safe mode so that the applications can be deployed without interference.

So once you switch off the safe mode - go into the Config Tool:

Choose Secure Store, right screen.

Choose Admin\Password\Systemid\ - here make sure you give the correct 'Administrator' password.

Set the Password value, choose add and save.

Restart Server.

Then retry the deployment. The root cause of incorrect password in Config Tool should be corrected I guess.

Regards,

Srikishan

Former Member
0 Kudos

Hi Srikishan

I followed your instructions but no luck again.

Changed password and restarted the server in no safe mode .

Deployment ended in error in the same fashion

Regards,

Kamal

Former Member
0 Kudos

Hi Kamal,

Looking a bit more closely at the logs:

ERROR: Cannot connect to Host: [] with user name: [Administrator ]

Here the hostname seems to be empty while JSPM tries to connect to the Java system.

Please check if the hostname is correctly defined in the 'hosts' file and upon pinging to the host - the correct IP is reached.

Check if the system is accessible(not necessarily useable) when the deployment starts.

Also check SAP Note 609603 if above all seems fine.

Regards,

Srikishan