Skip to Content
avatar image
Former Member

SLDCHECK not working!!!

hi all,

my sldcheck is not working and is giving me the following error:

*******************************************************************

Calling function LCR_LIST_BUSINESS_SYSTEMS

Retrieving data from the SLD server...

Function call returned exception code 4

*******************************************************************

in sxmb_moni i am getting the error:

**********************************************************************************

<SAP:Code area="INTERNAL">SLD_NO_OWN_BS</SAP:Code>

**********************************************************************************

i went through all the forums in sdn and checked the following:

ℹ️ sm59- lcrsaprfc and sapsldapi connections are working

(ii) sldapicust configurations are correct

(ii) sxmb_adm configuration is correct- rfc destination also connecting, user is not locked!

(iv) sld is opening but throwing the first error

(v) in se37 i tried to execute function module LCR_LIST_BUSINESS_SYSTEMS but my business system is not getting listed

can anyone suggest as to what i am missing and offer any solution to this problem.

thanks a lot in advance!

ridhima

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • Best Answer
    Dec 01, 2010 at 11:44 AM

    Hello,

    Check one of notes below according to your system version:

    #1143810 - Troubleshooting SLDCHECK - Releases 71X

    #768452 - Troubleshooting SLDCHECK - Releases 640, 70X

    And also take into account note #764176 if you find any inconsistences in your SLD.

    Regards,

    Caio Cagnani

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      maintain RFC destinations LCRSAPRFC & SAPSLDAPI of type T in ECC system as well

      Give proper SAP GATEWAY AND SAP HOST in above RFC destinations

      Check the technical system association with business system

      regards

      Ninad

  • avatar image
    Former Member
    Dec 01, 2010 at 12:04 PM

    Hi

    Check the below mentioned points:

    1. Check that the user maintained in transaction SLDAPICUST is not locked.

    2. The exchange profile RFC connection LCRSAPRFC is probably pointing to the wrong hostname, eventually the central SLD hostname. It must always point to the hostname of the system on which the PI system is running.

    SAP Note 768452 - Troubleshooting SLDCHECK

    Troubleshooting

    http://help.sap.com/saphelp_nw04/helpdata/en/3b/6f5c3c3806af06e10000000a11402f/content.htm

    http://help.sap.com/saphelp_nw04/helpdata/en/14/555f3c482a7331e10000000a114084/content.htm

    Thnx

    Pothana

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 01, 2010 at 11:42 AM

    Hi Explorer,

    Please check whether you have the business systems set for your proxy system in your PI server.

    If so, please check whether the Proxy system has the role as Application system and for that the integration server has properly linked in.

    Thanks!

    Regards,

    Dhayanandh. S

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 01, 2010 at 12:35 PM

    Hi Ridhima,

    Check the below SAP notes:

    1. OSS Note 764176 - Error in XI due to inconsistent SLD contents

    2. OSS Note 1117249 - Incomplete Registration of PI components in SLD

    Thanks,

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 01, 2010 at 12:43 PM

    Hi,

    ask basis to see if some service user pwd is changed.....if it is, then there is a SAP Note for changing system user pwds and follow the complete note to change it.....moreover in SLDAPICUST see the user used PISLDUSER is not locked.....

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hello Ridhima,

      Request you to please provide the solution. How did you solve it? It will help others like me in such situations.

      Thanks & Regards,

      Anand Patil