Deployment error: Exception during getInitialContext operation

[former_member188498]

Hello,

after portal upgrade to 7.0 SP 15 we have a problem with deployment through SDM and NWDS.

The login and passwords for deployment are correct.

Any ideas how to solve this?

Here is the message:

2008-06-27 10:16:42 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:

[003]Deployment aborted

Settings

SDM host : gruffi

SDM port : 50618

URL to deploy : file:/C:/DOCUME_{1/lado/LOCALS}1/Temp/temp62133PhoneComparator.ear

Result

=> deployment aborted : file:/C:/DOCUME_{1/lado/LOCALS}1/Temp/temp62133PhoneComparator.ear

Aborted: development component 'PhoneComparator'/'local'/'LOKAL'/'0.2008.06.27.10.16.21'/'0':Caught exception during application deployment from SAP J2EE Engine's deploy API:com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [gruffi] 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 RemoteLoginContext 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.setBroker(DeployManagerImpl.java:3527) at com.sap.engine.deploy.manager.DeployManagerImpl.makeNewConnection(DeployManagerImpl.java:3496) at com.sap.engine.deploy.manager.DeployManagerImpl.deployUpdateAction(DeployManagerImpl.java:596) at com.sap.engine.deploy.manager.DeployManagerImpl.update(DeployManagerImpl.java:518) at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:198) 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.java: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.java: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 instance. 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) ... 37 moreCaused by: java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: This call must be performed from a system thread. at com.sap.engine.services.security.login.SecuritySession.setExpirationPeriod(SecuritySession.java:479) at com.sap.engine.services.security.login.TicketGenerator.getSecuritySession(TicketGenerator.java:180) at com.sap.engine.services.security.login.SecurityContext.load(SecurityContext.java:299) at com.sap.engine.services.rmi_p4.Message.loadContextObject(Message.java:345) at com.sap.engine.services.rmi_p4.Message.parseMessage(Message.java:239) at com.sap.engine.services.rmi_p4.Message.getByteArrayInputStream(Message.java:314) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:212) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200) at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) 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:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) at com.sap.engine.services.security.exceptions.BaseSecurityException.writeReplace(BaseSecurityException.java:349) 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 java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:896) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1011) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278) at com.sap.engine.services.rmi_p4.DispatchImpl.throwException(DispatchImpl.java:146) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:360) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200) at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) 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:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).DMEXC)

Deployment exception : The deployment of at least one item aborted

Regards,

Ladislav

[former_member698570 · Accepted solution]

Hi,

did you change the Administrator Password lately?

I would try the following:

- Check if SDM is properly running (I guess you already did that)

- Start SDM RemoteGUI and login to SDM (does that work??)

If you have problems doing this change the SDM password from command line

> sdm.sh changepassword newpassword=<new password>

if you are on windows use sdm.bat accordingly

You could also try to change SDM mode (integrated,standalone). You should use the integrated mode

See this blog for useful information on SDM tasks:

If this all does not help you should update the Administrator password in secure store

Start the config tool and set the password in the secure store for user admin to you administrator password

I think the SDM deployment won't work correctly if the password is wrong here (You will always have to perform this step

after changing the Administrator password via UME UserAdministration etc.)

Hope this helps

Cheers

[former_member188498 · Accepted solution]

Hello,

the problem has been solved.

It was caused by difference on security session expiration time on the server nodes - the values were not the same on all

server nodes.

Regards,

Ladislav

[Former Member · Accepted solution]

Hi,

I had the same problem and i solved it through the steps below.

Go to Configtool

-> Click on the Server Nodes

-> Click on Services

-> Go to Security

-> change the local Properties

-> Set as Global Properties