on 09-07-2021 6:27 PM
Hi, we have some problem with data synchronization between managed system (S4HANA) and SLD (SM7.2).
SLD, section "Application Servers" does not contain information about ASCS:
Diagnostic agent from managed system connected to the solman succesfully, also hostagent upgraded to latest.
In SMDagent admin console diagnostic agent and hostagent status is green.
Also we have BW and Solman (itself) connected to SLD, those data about ASCS is stored in SLD normally.
This problem only with two S/4HANA sattelite systems (2020FPS2).
I have read sapnote 1419603 - Missing ABAP SAP Central Services (ASCS) instance in SLD/LMDB and already tried steps from that sapnote (using sldreg tool), but there is no result.
Can you help us?
Thanks in advance.
Hi olzhas.omarov,
When you perform the actions from point 4 above, namely the command "sldreg -configure slddest.cfg -usekeyfile", is the result successful? Try to execute the command sldreg again and restart thesapstartsrv ("sapcontrol -nr <NR> -function RestartService") according to the note, then look in the SLD -> Technical Systems, check the time of update in the column "Last update". If the system is not updated please check connectivity, and input parameters for sldreg again. It may take a couple of minutes to update data in SLD. Also check the following notes:
2178912 - Central application server not found in SLD for ABAP system
2171661 - Central Application Server Check in RZ70
2719664 - Support for "Standalone Enqueue Server 2" in RZ70
3030085 - Obsolete ENQ parameters in SAP Basis 755
Some more questions, what is the version of SM7.2 you have? Is ASCS on the same server as PAS or separate?
Also for troubleshooting check:
Regards,
Abay
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
olzhas.omarov,
Check this note as well:
3030085 - Obsolete ENQ parameters in SAP Basis 755
--Abay
Thanks compatriot, sapnote 3030085 is solved my issue!
I don’t understand why I didn’t find it before via Google & SMP, thanks!
Hi olzhas.omarov,
Here some points to check:
1. How do you push data suppliers' data from S4H to SM, in RZ70 via HTTP or RFC?
2. Can you check also profile parameters data in RZ10 if ASCS instance correctly defined there?
3. Before push of data have you updated CIM model and CR data of the corresponding SLD?
4. Have you checked this note 2225446 - ABAPInstanceKernel or J2EEInstanceKernel Data Supplier is shown as incomplete in LMDB. Please make sure the SLD data is updated after you registered the specified data supplier as described in the note, don't forget to restart the service.
Please chek the points and revert.
Regards,
Abay
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Abay,
thanks for response,
1. Data pushed via http (not httpS)
2. I checked profiles, all is good (compared with working BW4)
3. Yes, data is updated.
4. I tried mannual steps from that note (sldreg -configure slddest.cfg -usekeyfile). But it doesn't solved problem.
I found some interest behavior when using sldreg -configure slddest.cfg -usekeyfile command, after run that command generates file sapstartsrv_sld.xml. I read this file, and find some parameters looking wrong:
I tried to change parameter sync to true, but after restart service it's automatically changed to "false".
Hi dammerto,
LMDB shows the same as SLD - the absence ASCS, AppServer and Message server information stored normally.
As I know LMDB synchronize data from SLD. In SLD no information about ASCS.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.