cancel
Showing results for 
Search instead for 
Did you mean: 

SDM deployment

Former Member
0 Kudos

i am trying to deploy some missing components and get the following error. I have checked the j2ee_admin in the abap stack for client 001 and the password is the same for visual administrator and in secure store. any ideas?

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

Deployment started Fri Feb 01 08:21:29 GMT 2008

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

Starting Deployment of com.sap.ip.bi.broadcasting

Deployment of com.sap.ip.bi.broadcasting finished successfully (Duration 4781 ms)

Starting Deployment of com.sap.ip.bi.broadcasting.kmmimes

Deployment of com.sap.ip.bi.broadcasting.kmmimes finished successfully (Duration 4828 ms)

Starting Deployment of com.sap.ip.bi.portalheartbeat

Deployment of com.sap.ip.bi.portalheartbeat finished successfully (Duration 4594 ms)

Starting Deployment of com.sap.ip.bi.portallogger

Deployment of com.sap.ip.bi.portallogger finished successfully (Duration 4531 ms)

Starting Deployment of com.sap.ip.bi.portalnavigation

Deployment of com.sap.ip.bi.portalnavigation finished successfully (Duration 4515 ms)

Starting Deployment of com.sap.ip.bi.portalrfc

Deployment of com.sap.ip.bi.portalrfc finished successfully (Duration 4516 ms)

Starting Deployment of com.sap.ip.bi.portalrfctest

Deployment of com.sap.ip.bi.portalrfctest finished successfully (Duration 4484 ms)

Starting Deployment of com.sap.ip.bi.biloggingconfig

Aborted: development component 'com.sap.ip.bi.biloggingconfig'/'sap.com'/'SAP AG'/'7.0007.20060316173253.0000', grouped by software component 'BI-IBC'/'sap.com'/'SAP AG'/'1000.7.00.7.0.20060319093500':

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: [OFCOMTOLS039] with user name: [J2EE_ADMIN] Check your login information. 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 authenticate the user.]

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

Deployment of com.sap.ip.bi.biloggingconfig finished with Error (Duration 6594 ms)

Starting Deployment of BI-IBC

Aborted: software component 'BI-IBC'/'sap.com'/'SAP AG'/'1000.7.00.7.0.20060319093500':

No further description found.

Deployment of BI-IBC finished with Error (Duration 3968 ms)

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hello Mike,

Your issue is described in note 997810:

If deployment fails with the error:

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: [sapmef1d] with user name: [Administrator] Check your login information.

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.checkLoginCredentials.DMEXC)

Either the connection details in Secure Store are incorrect, or the j2ee engine is not running at all. First check the admin/port/<SID>entry in Secure Store and make sure it corresponds to the p4 port on the dispatcher. If the j2ee engine is not running (no jlaunch processes on os level), check the std_<XXX> and dev_<XXX> files in the instance work folder, located on the same level as the j2ee one.

Regards,

Ventsi Tsachev

Technology Development Support (J2EE Engine)

SAP Labs, Palo Alto, Ca (USA)

suresh_krishnamoorthy
Active Contributor
0 Kudos

Hi Mike,

Are you sure that the Administrator's password in the database is the same as the one written in the secure store? It seems to be the problem described in note 701654.

Refer this link too:[Here|;

Hope above SAP Note will solve your problem

Regards, Suresh KB