cancel
Showing results for 
Search instead for 
Did you mean: 

SolMan Diagnostic Agent connection issues

Former Member
0 Kudos

Hello

I reinstalled my Solution Manager 7.1 and upgraded to SP12. My landscape was connected to it via diagnostic agents without any problems. Now at the Solman setup Basic settings none of my systems are connecting to it. I can see every system but on 6.7 connect diagnostic agent page all of them, including Solman's DA is giving me Logon Denied error.

On agent management page, I did push credentials to every system but it didn't work.

I tried smdsetup.bat sldconf hostname:"FQDN" port:"50000" user:"SLDDSUSER" pwd:"user password" and smdsetup.bat managingconf hostname:"FQDN" port:"50004" user:"SMD_AGT" pwd:"user password".

Both users have necessary standard roles plus SAP_ALL and SAP_J2EE_ADMIN roles.

What else can I do? As last resort I am thinking reinstalling all agents but it will take too much time.

Best regards

Kaan

Accepted Solutions (1)

Accepted Solutions (1)

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Kaan,

1st stop agents on all system.

2nd any system and smdsetup manageconf script and register the agent using a copy SMD_AGT user.

3rd start agent

4th remove the entry of this agent from SLD.

5th Goto managed system configuration of this system and assign the agent.

If above works repeat the steps for others.

Regards

divyanshu_srivastava3
Active Contributor
0 Kudos

Also, can you quickly goto agent admin and check maintenance mode is off

Former Member
0 Kudos

I am still getting same error. smdsetup.bat is not giving any errors, my rc code is 0 but still getting logon denied error.

Also how can I remove a DA from my Solman?

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Kaan,

Did you check agent-admin for maintenance mode ?

Regards

divyanshu_srivastava3
Active Contributor
0 Kudos

To remove from SLD, pick any one agent from your landscape and refer below note:

1751977 - Obsolete agent listed in Agent Candidates Management

Former Member
0 Kudos

Yes, it is currently off.

Edited.

divyanshu_srivastava3
Active Contributor
0 Kudos

Did you check agent logs for any error message related to connection or anything.

If you are not getting anything, perhaps use smdsetup.exe supportlogs to get all relevant logs and upload it. That would help us to at least to look into which system - solman or managed system.

Also, in agent admin, can you see agents ? What is their status ? look for possible issues from agent admin and share here.

Former Member
0 Kudos

All of them are like as attached picture

Former Member
0 Kudos

I also uninstalled DA on Solman and then reinstalled but I received same error.

divyanshu_srivastava3
Active Contributor
0 Kudos

That should be simple

The user that you have used have a different password or is locked.. reset the password which was before and re-connect the agent.

Before that, Click on Details and paste the reason for denial.

Regards,

Divyanshu

Former Member
0 Kudos

It is like in the attached file.

SLDDSUSER and SMD_AGT are not locked.

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Kaan,

Refer this note to find the screen where you have to go and make changes

1878392 - Diagnostic Agents loose connection after solman offline backup


In Agent connectivity policy select  "Use Basic Authentication" and try again.

Answers (2)

Answers (2)

Former Member
0 Kudos

I switched authentication scheme from certificate to basic authentication and then pushed credentials to all servers again. All is working now, but I still couldn't find an answer for certificate authentication error.

Thanks anyway

divyanshu_srivastava3
Active Contributor
0 Kudos

I can give you the answer for this also.

You used certificate method initially. Here, in the SMDAgent secstore.properties a parameter like this is generated.

smd/agent/certificate/pass=am28KDshsdldh23jhanasd2Hx7NEJCQjA2M0EtMDYzOS00QTc5LUUxMDAtMDAw\r\nMDLKHsajkhdsHSl

And in the SMDAgent runtime properties this parameter is used

smdserver.connection.requiresAuthentication=certificate

And this was generated with you last installation, so certificates are not valid for new installation.

If your issue is resolved you can mark and close this thread.

P.S. Already 1 AM here need to sleep now

Cheers,

Divyanshu

Former Member
0 Kudos

How can I push new certs to other servers to prevent my problem?

You can go to sleep, it is no rush

Sriram2009
Active Contributor
0 Kudos