cancel
Showing results for 
Search instead for 
Did you mean: 

CTS+ DEPLOYMENT error with SDM authentication problem

AaronLong
Advisor
Advisor
0 Kudos

Hi

I got authentication error when doing release for JAVA transport in CTS+.

why the user 'J2EE_ADMIN' is used  ? where it is defined ?

How can I fix it ?

my cts+ is running on Solman dual stack.  netweaver 7.01

while my SAP J2EE system are running on NETWEAVER 731

1TP199X######################################

1TP189 DEPLOYMENT

1TP101 transport order : "DEVK900002"

1TP102 system : "QAS"

1TP108 tp path : "tp"

1TP109 version and release : "380.10.20" "720"

1TP198

3PU689XCTS File Import Service - Version 1.00 - 08.09.2009

3PU615 Deploy Web service destination: "CTSDEPLOY"

3PU616 Directory: "/usr/sap/trans/data"

3PU617 "SDM" Deploy URL: "http://172.16.234.48:50004"

3PU617 "SLD" Deploy URL: " "

3PU617 "XI" Deploy URL: " "

3PU607 Non-ABAP system "QAS" (communication system "P10")

3PU655 Deploy proxy features: "DEPLOY" "IMPORT" "FILETRANSFER" "GENERICIMPORT"

1PU676XStart deployment of "NWDI"

1TW000 Deploy Webservice environment (2015-06-18 16:51:25.0888 +8:00)

2TW000 DeployProxy (vendor: 'sap.com', name: 'tc/cts/appl', scV: 'sap.com', scN: 'LM-TOOLS', location: 'MAIN_NW702P14_C', counter: '487080

2TW000 6', R: '7.02', SP: '14', PL: '0', change number: '224', appl-level:0) called.

2TW000 J2EE server is P10.

1TW000 Communication data provided (2015-06-18 16:51:25.0892 +8:00)

2TW000 connection:http://172.16.234.48:50004 user:J2EE_ADMIN password:filled properties:empty deployType:SDM/DEPLOY_CONTROLLER application

2TW000 Type:null

1TW000 Begin deployment (2015-06-18 16:51:25.0892 +8:00)

2TW000 Import Event (Id:B8CA3A69CF081ED585B2E66BB50D0C2A)

2TW000 properties:

2TW000 key:TARGETSYSTEMID value:QAS

2TW000 Transport Request (Id:DEVK900002 description:GENERATED REQUEST)

3TW000 properties:

3TW000 key:OWNER value:S_AARON

3TW000 key:DESCRIPTION value:GENERATED REQUEST

3TW000 key:TARGETSYSTEM value:QAS

3TW000 TransportEntity ( id:B8CA3A69CF081ED585AF371BB41CA95C content:/usr/sap/trans/data/DEVK900002/sap.com~MII_CUSTOM~CUST_MIICUST_C~2015

3TW000 0618051940.sca deployType:SDM/DEPLOY_CONTROLLER applicationType:null)

4TW000 properties:empty

2TW000 TransportEntity (Id:B8CA3A69CF081ED585AF371BB41CA95C) status set to 'PROCESSING'.

2WTW000 connection:http://172.16.234.48:50004 user:J2EE_ADMIN password:filled properties:empty deployType:SDM/DEPLOY_CONTROLLER application

2WTW000 Type:null

1ETW000 Error opening the deploy connection

1TW000 End deployment (2015-06-18 16:51:26.0501 +8:00)

2ETW000 com.sap.di.cts.deploy.api.exception.DeployToolCommunicationException: AuthenticationException: The user 'J2EE_ADMIN' could not be a

2ETW000 uthenticated for the specified host '172.16.234.48'and port '50004'.caused by:com.sap.sdm.apiimpl.remote.client.APIAuthenticationEx

2ETW000 ception: The user 'J2EE_ADMIN' could not be authenticated for the specified host '172.16.234.48'and port '50004'.caused by:com.sap.

2ETW000 engine.services.dc.api.AuthenticationException: [ERROR CODE DPL.DCAPI.1144] BaseLoginException.Cannot get initial context.

3WTP000 Reason:

2ETW000 Error during authentication. For more information see the remote server traces.caused by:com.sap.engine.services.security.exception

2ETW000 s.BaseLoginException: Error during authentication. For more information see the remote server traces.

3PU705 Error stack trace

2TW000 com.sap.di.cts.deploy.core.SDMConnectionImpl.openConnection(SDMConnectionImpl.java:131)

2TW000 com.sap.cts.deployer.NWDeployer.deploy(NWDeployer.java:126)

2TW000 com.sap.cts.core.GenImportManager.execImport(GenImportManager.java:121)

2TW000 com.sap.cts.ejb.DeployBean.execImportGen(DeployBean.java:93)

2TW000 com.sap.cts.ejb.DeployLocalLocalObjectImpl0_0.execImportGen(DeployLocalLocalObjectImpl0_0.java:103)

2TW000 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

2TW000 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

2TW000 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

2TW000 java.lang.reflect.Method.invoke(Method.java:331)

2TW000 com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)

2TW000 com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:174)

2TW000 com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:81)

2TW000 com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:90)

2TW000 SoapServlet.doPost(SoapServlet.java:47)

2TW000 javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

2TW000 javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

2TW000 com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

2TW000 com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

2TW000 com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)

2TW000 com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)

2TW000 com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)

2TW000 com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

2TW000 com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

2TW000 com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

2TW000 com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.

2TW000 java:33)

2TW000 com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

2TW000 com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

2TW000 java.security.AccessController.doPrivileged(Native Method)

2TW000 com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)

2TW000 com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

1PU677XStop deployment of "NWDI"

3PU717XImport options:

4PU734 Ignore invalid component version

4PU730 Overtaker transport (leave in the queue for further imports)

3PU711XImport transport targets

4PU719 No more actions required for this transport

1APU619XHighest return code is "12"

1TP189 DEPLOYMENT

1TP110 end date and time : "20150618165126"

1ATP111 exit code : "12"

1TP199 ######################################

Accepted Solutions (1)

Accepted Solutions (1)

bxiv
Active Contributor
0 Kudos

J2EE_Admin would of been used in either your destination on the 731 system, ctsdeploy in stms, or the RFC connection.

Did you follow a guide to setup CTS?

Also was this working and it broke or are you trying to get things up and running?

AaronLong
Advisor
Advisor
0 Kudos

the user J2EE_ADMIN is not used in destination on my NW 731 or STMS system.

that's why I feel strange.

AaronLong
Advisor
Advisor
0 Kudos

I found the problem was due to wrong IP existing on my deployer (CTS system Java Stack).

>jump 0

You jumped on node 3141750.

>>add p4

>p4_profiles -list

..: P4 Profiles :..

0.      None:127.0.0.2:50004

1.      None:172.16.12.90:50004

2.      None:172.16.13.90:50004

3.      None:#fe80.0.0.0.baca.3aff.fe69.cf08:50004

4.      SAPRouter:127.0.0.2:50004

5.      SAPRouter:172.16.12.90:50004

6.      SAPRouter:172.16.13.90:50004

7.      SAPRouter:#fe80.0.0.0.baca.3aff.fe69.cf08:50004

8.      httptunneling:127.0.0.2:50005

9.      httptunneling:172.16.12.90:50005

10.     httptunneling:172.16.13.90:50005

11.     httptunneling:#fe80.0.0.0.baca.3aff.fe69.cf08:50005

12.     ssl:127.0.0.2:50006

13.     ssl:172.16.12.90:50006

14.     ssl:172.16.13.90:50006

15.     ssl:#fe80.0.0.0.baca.3aff.fe69.cf08:50006

However it is hard to found out where 127.0.0.2 is from

SAP released a fix for for skipping localhost addresses such as 127.0.0.2 on 7.02 SP15

SAPJEECOR15P patch #18

I am closing this.

Answers (0)