cancel
Showing results for 
Search instead for 
Did you mean: 

Diagnostic Agents disconnected after SolMan SPS update

garethreeceuk
Explorer
0 Kudos

Hi,

I have just updated a SolMan 7.2 system from SPS06 to SPS18.  I now see that all the Diagnostic Agents are offline and cannot re-connect.  They are all on a pretty old version:

7.20.6.0.20171013033619

I have gone through the steps in Note 3316788 to set up user credentials that are now required, and I have run smdsetup to try and reconnect but nothing has worked so far.  I'm now getting this message in the SMD Agent log:

A HTTP request to the message server returned response code different from "200 OK": HTTP/1.1 404 Not Found
No P4 access points will be returned

Is my only option to re-install the agents with the latest version?

Accepted Solutions (1)

Accepted Solutions (1)

mamartins
Active Contributor

Please look into SAP note 2253383 - Diagnostics Agent - SWPM Archive-Based Installation. There is a list of all dependencies between JVM, kernel and SOLMAN versions.

Look also to the notes referenced by this note.

garethreeceuk
Explorer
0 Kudos
Thanks, I've seen that Note too. Looks like updating the kernel / JVM won't be enough and a full uninstall / reinstall with the latest versions will be needed.
garethreeceuk
Explorer
0 Kudos
Update - I decided not to waste any more time, and did the uninstall and re-install of the DAA using the latest recommended archives via SWPM. Worked first time. Thanks guys!

Answers (3)

Answers (3)

vera_jiang1
Product and Topic Expert
Product and Topic Expert

Dear Customer,

The "404 Not Found No P4 access points will be returned" error indicates that the message server http port used in the connect command doesn't work to return a working P4 port. Please test the following URL in the browser and does it return the P4 port? 
http://<solmanJAVAhost>:<MSG_SERVER_HTTP_PORT>/msgserver/text/logon

Please make sure the Solman JAVA Message Server is working. Please note the correct Message Server HTTP port and P4 port, try a sample agent and connect it as KBA  2385361 - How to connect Diagnostics Agent to Solution Manager 7.2 system in the section "For an existing Diagnostics Agent, you may perform steps below:".

Best regards,
Vera Jiang 

mamartins
Active Contributor

Please check SAP notes 2385361 - How to connect Diagnostics Agent to SAP Solution Manager 7.2 system and 2785611 - Compatible Diagnostics Agent version for Solution Manager 7.2 (Upgrade)

Updating the Diagnostics Agent is always (almost 😀) the right choice, because some security vulnerabilities have been discovered lately on it.

garethreeceuk
Explorer
0 Kudos

Update:  I discovered I was using the wrong port for the MS HTTP port in the smdsetup command.  After issuing the correct command, the agent now finds the P4 port and connects, but I'm getting this error relating to the SecStore:

"software version 7.00.000.001 is incompatible with file version 7.50.000.005"

This is covered in Note 3372657 - Error "software version 7.00.000.001 is incompatible with file version 7.50.000.005" occur... where it is suggested to delete the secstore files and allow smdsetup to recreate them.  I have done so but the error persists.

Could this be caused by incompatible kernel/JVM version of the Agent since the SolMan Java stack is now running on NW 7.5 / JVM 8.1?  Will updating the kernel of the Agent help?