INTERNAL.SLD_NO_OWN_BS Error while reading ID of own business system from the SLD

[Former Member]

Hello experts,

We are facing some issues while executing tcode SLDCHECK on our ECC system. The log is:

Calling function LCR_LIST_BUSINESS_SYSTEMS
Retrieving data from the SLD server...
Function call returned exception code     4
=> Check whether the SLD is running!

Summary: Connection to SLD does not work
=> Check SLD function and configurations

When we checked in SLDAPICUST, we found the user was locked, so we unlocked it and ran tcode sldcheck again, it worked, also SLDAPICUST test was successful. But, when we went to test our proxy in sproxy tcode, we received following error:

INTERNAL.SLD_NO_OWN_BS Error while reading ID of own business system from the SLD for system 'SID' and client 001.

Again, the user got locked, and our SLDCHECK failed too. So, the issue is even after unlocking the user, it is getting locked all the time and our scenario is not working. This is happening in pre-prod system. In quality, everything is fine. While, in development system, all SLDCHECK, SLDAPICUST are running fine, rfc and HTTP connections are working, but still in SPROXY, similar error is thrown.

Please let us know what can be the possible reason behind such system behaviour.

Thanks,

Monika

[MichalKrawczyk · Accepted solution]

Hi,

if the user is being locked several times than it means that the password is not maintained correctly is some place

do you have the same pass for service user in the whole SLD landscape ? can you check passwords in exchange profile ?

BTW

one more strange thing:

INTERNAL.SLD_NO_OWN_BS 001

you're not using system client 001 anywhere right ? 001 should not be used for normal systems - just to confirm

Regards,

Michal Krawczyk

[Former Member · Accepted solution]

Thanks Michael. The Basis guys had messed up. The issue is resolved now.

And, yes client 001 is being used from dev to prod, please let me know why it is not recommended, I can then notify the basis team.

[MichalKrawczyk · Accepted solution]

hi,

read about 001 here (it's the same for all ABAP stacks based systems):

it's similar to 000 and should never be used for PRDD landscapes (I've never seen anyone using 001 in any landscape)

http://help.sap.com/saphelp_46c/helpdata/en/2e/d9530294f911d283d40000e829fbbd/content.htm

http://scn.sap.com/thread/1059993

http://help.sap.com/saphelp_46c/helpdata/en/7e/c8189452c511d182c50000e829fbfe/content.htm

Regards,

Michal Krawczyk

[Former Member · Accepted solution]

Thanks!!