on 04-11-2014 5:14 PM
Hi Gurus,
Need help with this alert which i am getting from Solman 7.1 SP10.
ABAP Message Server Status | XXX-ABAP | 3 | 3 | 3 | No process found for: msg_server(.*) |
I have already checked following notes but no luck
1419603 - Missing ABAP SAP Central Services (ASCS) instance in SLD/LMDB
1916237 - ABAP Central Service not available alert in Technical Monitoring
Our managed system kernel is 720 P 401 as per-requisites for the sld registration.
Have tried few things here and there but no luck.
Please suggest is any has any suggestion or solution.
Dev
We had similar issue and was resolved by executing
sldreg -configure slddest.cfg -usekeyfile
and restarting sapstartsrv service. (make sure you restart the service) before checking the missing entries in SLD.
From note : 1717846 - sapstartsrv SLD registration
"If sldest.cfg is created after sapstartsrv startup sapstarstrv needs to be restarted to activate the SLD registration. This can be done while the instance remains running using SAP MMC / MC ("All Tasks->Restart Service" context menu) or "sapcontrol -nr <NR> -function RestartService" from the command line. When registering sapstartsrv executes sldreg (in combination with "slddest.cfg", "slddest.cfg.key") and sends the content of "sapstartsrv_sld.xml" to the SLD. The registration logfile is "dev_sldregs".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear all,
I also have this problem in the monitoring.
Using sap note 1419603 to register the ASCS was not helping.
I also found in this note that you can change the settings in the LMDB. That was helping me to solve the problem.
Once this is done you have to remove the monitoring from this system. Then reconfigure the monitoring. Be careful, first do a reset to original because otherwise the system remembers the old templates assigned and these are incorrect!.
For me the “ABAP CENTRAL SERVICES" template was assigned to the Managed Object: SID~ABAP~servername_SID_sysnr.
This can only be removed using the reset to original.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If all else fail, try adding the missing entries manually in SLD by following this SAP note.
1419603 - Missing ABAP SAP Central Services (ASCS) instance in SLD/LMDB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Donald,
I am having the same headache - I found this note by myself, but it is totally unclear what has to be done there !! I have opened SLD, but I did not find out how to "Create a new SAP_BCCentralServiceInstance (BC central service instance)."
Could you please describe what exactly have you done ?
Hi Dev,
Please check the following note first:
1853096 - Availability Metric: ABAP Message Server Status
The reason seems to be the following: you have assigned in "setup Monitoring" the template delivered from "SAP ABAP CENTRAL SERVICES" to the real Central Service Instance: DGW~ABAP~Central Service Instance
and additionally to the Managed Object: DGW~ABAP~vwmdasapgw_DGW_10
but this is not your central instance! (see attached screen)
Well, you have now to remove the template "SAP ABAP CENTRAL SERVICES" from DGW~ABAP~vwmdasapgw_DGW_10 and re-do the Setup for managed object.
To remove the template:
- Select Managed Object "XXX~ABAP~XXXXXXXXXXXXXXXXXXXXXX" and click on
"Restore Defaults" save it
Assign the correct Template to the managed object as per you choice.
Thanks
Vikram
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Devenda,
I guess you will need to create a "slddest.cfg" file where you specify
to which SLD the data should be sent and which credentials should be used for SLD logon.
The startup service (SAPSTARTSRV) included Kernel can register SAP
Kernel information and ASCS instance automatically in the SLD (as per SAP Notes 1717846 and
1018839).
To trigger the SAPSTARTSRV registration you need to restart the
service either via
-> SAP MMC/MC -> "All Tasks-> Restart Service" context menu
-OR-
-> command line -> "sapcontrol -nr <NR> -function RestartService"
Once the ASCS is registered in the SLD it will be synchronized to the
LMDB within approx.10 minutes and made available for monitoring.
After these steps have been executed successfully, please reconfigure
technical monitoring for the system again -> " Apply and Activate".
I hope this helps.
Kind regards,
Roland
Hi Roland,
I followed the note 1717846 and performed all the steps successfully.. But still no luck with ASCS in SLD.
Any ideas or suggestions .?
Attaching the logs for your reference:
Tue Apr 15 15:52:23 2014 Parsing XML document.
Tue Apr 15 15:52:23 2014 Supplier Name: BCControlInstance
Tue Apr 15 15:52:23 2014 Supplier Version: 1.0
Tue Apr 15 15:52:23 2014 Supplier Vendor:
Tue Apr 15 15:52:23 2014 CIM Model Version: 1.5.29
Tue Apr 15 15:52:23 2014 Using destination file '/usr/sap/XXX/SYS/global/slddest.cfg'.
Tue Apr 15 15:52:23 2014 Use binary key file '/usr/sap/XXX/SYS/global/slddest.cfg.key' for data decryption
Tue Apr 15 15:52:23 2014 Use encryted destination file '/usr/sap/XXX/SYS/global/slddest.cfg' as data source
Tue Apr 15 15:52:23 2014 HTTP trace: false
Tue Apr 15 15:52:23 2014 Data trace: false
Tue Apr 15 15:52:23 2014 Using destination file '/usr/sap/XXX/SYS/global/slddest.cfg'.
Tue Apr 15 15:52:23 2014 Use binary key file '/usr/sap/XXX/SYS/global/slddest.cfg.key' for data decryption
Tue Apr 15 15:52:23 2014 Use encryted destination file '/usr/sap/xXX/SYS/global/slddest.cfg' as data source
Tue Apr 15 15:52:23 2014 ******************************
Tue Apr 15 15:52:23 2014 *** Start SLD Registration ***
Tue Apr 15 15:52:23 2014 ******************************
Tue Apr 15 15:52:23 2014 HTTP open timeout = 420 sec
Tue Apr 15 15:52:23 2014 HTTP send timeout = 420 sec
Tue Apr 15 15:52:23 2014 HTTP response timeout = 420 sec
Tue Apr 15 15:52:23 2014 Used URL: http://sapr6bv:51600/sld/ds
Tue Apr 15 15:52:23 2014 HTTP open status: true - NI RC=1
Tue Apr 15 15:52:23 2014 HTTP send successful.
Tue Apr 15 15:52:23 2014 Return code: 200 --- Return message: (OK)
Tue Apr 15 15:52:23 2014 HTTP response: Success. HTTP status code: 200
Tue Apr 15 15:52:23 2014 ****************************
Tue Apr 15 15:52:23 2014 *** End SLD Registration ***
Tue Apr 15 15:52:23 2014 ****************************
User | Count |
---|---|
71 | |
26 | |
10 | |
9 | |
7 | |
6 | |
4 | |
4 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.