Assign Diagnostics Agent

[Former Member]

Dear SCN Members,

I'm trying to complete the Managed Systems Configuration for several systems.

Within step 3 (Assign Diagnostics Agent) i receive following error message:

Error       SLD server could not be reached : HTTP status: 503 Service Unavailable

Please be informed that SLD connection is working (for JAVA part for Solution Manager)

The error appears for every system not only Solution Manager JAVA part.

I can't see any Agent connected to SLD...i run also the script "smdsetup managingconf" with OK no error...

Please advice

Thank you!

[Former Member · Accepted solution]

Hi Andy,

1. In SolMan -> System Prep -> 6.1 ... is the status of the connection to the SLD green?

2. If #1 is green, is this the SLD you are registering your Agents against?

3. In Agent Admin, offline agents ... can you see your diag agent?

4. Have you checked the Diag Agent Logs (e.g. SMDAgentApplication.log, SMDSystem.log, etc) for any indication where the issue might be?

Regards,

JnJ

[Former Member · Accepted solution]

Hello,After refreshing the status in System Prep-> SLD config was red....I have entered the SLD hostname with FQN and voila is working:-)

Thanks everyone!

[former_member182657]

Hi Andy,

Error  SLD server could not be reached : HTTP status: 503 Service Unavailable 

Have a look with SAP Notes  1822831 - Web Service Soap Errors in solman_setup

&   1752309 - Web service invocation problem caused by Unsupported xstream found ("HTTP Code 404 : Not ...

Hope this will help you.

Regards,

[Matt_Fraser]

Hi Andy,

Have you confirmed that your SLD is actually running? What happens if you try to logon to the SLD administration page with your browser from your workstation? The URL will be something like http://<solmanhost>:50000/sld

Cheers,

Matt

[Former Member]

Yes SLD up and running!

[Matt_Fraser]

And on the Administration page of the SLD it has a green light? Sorry to be so basic, just making sure we're covering everything to get to the root of the problem.

Assuming all that is good, have you gone through all of the SLD configuration steps, and, furthermore, have you checked that you've configured REGINFO.DAT to allow remote gateway connections? For more information about this, see .

In your ABAP systems, do you have SAP_SLD_DATA_COLLECT scheduled and running in SM37? Are there any errors in the spool output of this job?

[manumohandas82]

Hi  ,

Please execute the transaction SLDCHECK and post the screenshot  [ Also the solution manager version ]

Also check in the following link

http://<solution manager host>:<port>/webdynpro/dispatcher/sap.com/tc~smd~server~agent~admin/SMDAgentAdminApplication?sap-language=EN

Thanks ,

Manu

[Former Member]

Hello,

I have checked the URL

http://<solution manager host>:<port>/webdynpro/dispatcher/sap.com/tc~smd~server~agent~admin/SMDAgentAdminApplication?sap-language=EN

and the agent is not there.

Please be informed that the AGENT is present in SLD.....Content Maintenance->Diagnostic Agents.

Please advice.

Thanks!

[prakhar_saxena]

Hi Andy,

Have you entered the correct port for SLD which you have used for connecting agent with SLD.

Please check below link and verify again.

http://wiki.scn.sap.com/wiki/display/SMSETUP/Diagnostics+Agents#DiagnosticsAgents-SLDRegistration-Re...

Kindly re run commands and make sure user is also not locked which you have provided like SMD_AGT etc in solman system

Thanks

Prakhar

[Former Member]

Hello,

I have runt with the script the SLD registration with ok also the conection to Solution Manager...

Thanks!