cancel
Showing results for 
Search instead for 
Did you mean: 

SDM Ping(STMS TP Check) is not Working from Solution Manager to JAVA System

Former Member
0 Kudos

Hi Experts,

We are in the way of configuring the CTS in Solution Manager.

In Our Solution Managersystem SDM Ping(STMS TP Check) is not Working for JAVA System and attached the screenshots.

1) This is the screen shot from Solution Manager for JAVA System

2) We have check the port for java system from solution manager after Java System Completly Stopped and when Java System running.

Thanks

Kiran.GVL

Accepted Solutions (0)

Answers (10)

Answers (10)

0 Kudos

Kiran,

is your issue fixed? i have the same issue in our EP environment and just wondering if the issue is fixed or not

Thanks

Jags

Former Member
0 Kudos

we observed some connection related error messages in dev_icm trace file in PDJ which were related to P4 port. We added HOST entry in below parameter and restarted PDJ.

icm/server_port_3 = PROT=P4, PORT=51004, HOST=XXXXXXX.org

However this HOST entry is not there in PQJ.

Former Member
0 Kudos

HI Kunal,

SDM Ping is working for Quality Java System but not for Prodution Java System

Production Java System Log

Solution Manager Log

Thanks

Kiran.GVL

Manas_Vincit
Active Participant
0 Kudos

HI Kiran,


Can you check what is status of J2EE_GUEST user status ? is it locked or password mentioned in wrong .

Thanks

Manas Behra

Former Member
0 Kudos

Hi Experts,

It's Working for JAVA Quality System but not fo Production Java and Please find the QAS Screenshot.

Thanks

Kiran.GVL

Former Member
0 Kudos

Hi Kiran,

             Please check the below logs and post it for review.

User authentication failed

The cause of the problem could be:

  • Invalid password/user name
  • User has been locked
Step 1

Look in the file: …\server0\log\system\security.log to find the initial exception, for example "Invalid password for user Administrator".

Step 2

Verify if the user name and password specified by the connection parameters are correct.
If there is a log message in ...cluster\server0\log similar to:
"Invalid password for user TEST_USER. User 'TEST_USER' locked after 6 unsuccessful attempts to login."
then you cannot log on to J2EE Engine using the Visual Administrator because the user has been locked due to numerous unsuccessful logon attempts. In this case, make sure that an Administrator user can log on to J2EE Engine and unlock the user you need. For this aim:

Thanks and Regards,

Kunal Gahlot

Reagan
Advisor
Advisor
0 Kudos

Hello

A similar issue is mentioned here and resolved with this SAP KBA:

1688705  - CTS+ configuration changes required as of release 7.10 with respect to the change from SDM to the Deploy Controller (DC)

Check whether this helps you

http://scn.sap.com/thread/3264082

Regards

RB

Manas_Vincit
Active Participant
0 Kudos

Hi Kiran ,

Do not give CTS_ADMIN in SDM user ID and Password, it would not have propoer autorization .

Try to give Administrator/J2EE_ADMIN user in SDM user ID . You can update in TMS itself that user .

Check if this helps .

Thanks

Manas Behra

Former Member
0 Kudos

Hi Kiran,

Hi Kiran,

             Specifically check below post.

Problem

If you see the following message in the SDM logs or in the SDM Remote GUI Client deployment result panel:

Caught exception while checking the login credentials from SAP J2EE

Engine's deploy API:

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

connect to Host: [HOST_NAME] with UserName: [USER_NAME]Check your Login Info.        Exception is:

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

Exception while trying to get InitialContext. [Root exception is

  1. com.sap.engine.services.security.exceptions.BaseLoginException: User not
  2. authorized.]

(message ID:

  1. com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnl
  2. ineDeployerImpl.checkLoginCredentials.DMEXC)

the most likely reason is that you have CreateTicketLoginModule in the service.namingauthentication stack.

Solution

A solution suggested by Security Team is to:

       1.      Go to Visual Admin __MCE_ITEM__ Security Provider __MCE_ITEM__service.naming.

       2.      Select NO for the authentication template.

       3.      Remove the CreateTicketLoginModule. (This login module can be used only by Web applications.)

Thanks and Regards,

Kunal Gahlot


Former Member
0 Kudos

I am able to login into SDM

karthikeyan_natarajan4
Active Contributor
0 Kudos

Hi Kiran,

check the password of CTS_ADMIN in user secure store and also check the user id and password in TMS as well.

regards

karthik

Former Member
0 Kudos

Can you give me the steps

Former Member
0 Kudos

Hi Kiran,

             Can you please try to login to SDM using CTS_ADMIN . might be possible that the password has changed or the user is locked.

           Also look at the below post for troubleshooting SDM issues.

          http://help.sap.com/saphelp_nw04/helpdata/en/76/fb72ec091f4bf8a2d8ba321bb7e8d9/content.htm

Thanks and Regards,

Kunal Gahlot

Former Member
0 Kudos

Hi Kiran,

             Specifically check below post.

Problem

If you see the following message in the SDM logs or in the SDM Remote GUI Client deployment result panel:

Caught exception while checking the login credentials from SAP J2EE

Engine's deploy API:

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

connect to Host: [HOST_NAME] with UserName: [USER_NAME]

Check your Login Info.        Exception is:

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

Exception while trying to get InitialContext. [Root exception is

  1. com.sap.engine.services.security.exceptions.BaseLoginException: User not
  2. authorized.]

(message ID:

  1. com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnl
  2. ineDeployerImpl.checkLoginCredentials.DMEXC)

the most likely reason is that you have CreateTicketLoginModule in the service.naming authentication stack.

Solution

A solution suggested by Security Team is to:

       1.      Go to Visual Admin __MCE_ITEM__ Security Provider __MCE_ITEM__ service.naming.

       2.      Select NO for the authentication template.

       3.      Remove the CreateTicketLoginModule. (This login module can be used only by Web applications.)

Thanks and Regards,

Kunal Gahlot

Nibu
Contributor
0 Kudos

Hi Kiran,

Did you check the user CTS_ADMIN , can be logged into SDM without any issues ? Seems login issues with the user .