SLDCheck is giving error

[Former Member]

Hi All,

Yesterday our XI system was upgraded from SP14 to SP19. On SP14 everything was fine.

Now on SP19, we are having the issue that SLDCHECK transaction is not working fine........The output of SLDCHECK is following:

Exchange Infrastructure: Test LCR Connection

Properties of RFC destination SAPSLDAPI

RFC host: %%XXX%%

program id: XXX

gateway host: XXX

gateway service: XXX

Testing the RFC connection to the SLD java client...

RFC ping was successful

SLD server access settings:

host name: XXX

port number: XXX

user : xiappluser

Use transaction SLDAPICUST if you wish to maintain the SLD server access data

Launching the SLD GUI in a separate browser window...

=> Verify in the browser GUI that the SLD is in a healthy running state!

<b>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</b>

Now checking access to the XI Profile

Properties of RFC destination LCRSAPRFC

RFC host: %%XXX%%

program id: XXX

gateway host: XXX

gateway service: XXX

Testing the RFC connection to the SLD java client...

RFC ping was successful

Calling function EXCHANGE_PROFILE_GET_PARAMETER

Retrieving data from the XI Profile...

Function call terminated sucessfully

Retrieved value of

section = Connections

parameter = XXX

-> value =

Summary: Connection to the XI Profile works correctly

I have replaced our XI server data with XXX in above output........

I have seen below things:

1. The RFC destinations SAPSLDAPI and LCRSAPRFC are working fine.

2. The data in SLDAPICUST transaction is maintained properly - hostname, userid, password, port etc.

3. i have seen the below link:

http://help.sap.com/saphelp_nw04/helpdata/de/78/20244134a56532e10000000a1550b0/content.htm

I am seeing one strange thing about XIAPPLUSER that it is getting locked everytime now.......why is XIAPPLUSER getting locked everytime now?

<b>How to resolve this SLDCHECK issue - is XIAPPLUSER getting locked the reason of SLDCHECK error.....if so, then how to make sure that XIAPPLUSER is not getting locked everytime.........</b>

Thanks,

Rajeev Gupta

[Former Member]

Hi,

Password for XIAPPLUSER in tcode SLDAPICUST must be consistent throughout the system landscape. Check if this user is maintained in RFC destinations or SLDAPICUST transaction of other SAP systems that use this SLD. On other SAP system SLDAPIUSER is generally used.

Please use the SAP note #936093 XI 7.0: Change passwords of XI service users, to check that the password is maintained in the correct locations throughout the system and that the passwords are consistent in these locations.

When you have made the changes please retry trx SLDCHECK (at least 3 times)

Hope this helps.

Regards,

Riyaz

[henrique_pinto]

probably a wrong password for xiappluser at one of the systems maintained in SLD and/or some application calling XI. check sldapicust tx code at all systems and sender adapters that log onto xi.

However, as a matter of fact, you should use SLDDSUSER and not XIAPPLUSER for sld connections, as a best practice (and to avoid problems like that).

Regards,

Henrique.

[Former Member]

Hi,

To solve this issue

1. Ask your Basis guy to enable user trace for this user.

2. Check SM59 if you have maintained any self pointing RFC destination

meanwhile you can use workaround to unlock user automatically: use BAPI_USER_UNLOCK to write wrapper and run it on every two three hrs and it will solve your problem.

Regards,

Gourav

---

<i>Reward points if it helps you</i>

[Former Member]

Gourav,

>>meanwhile you can use workaround to unlock user automatically: use BAPI_USER_UNLOCK to write wrapper and run it on every two three hrs and it will solve your problem.

This will not solve the problem. The problem is not to unlock the userid. But the connection to SLD. Evenif the user id is unlocked every 2 or 3 hours by sceduling this report, the connection to SLD will not be established.

For solving the problem, RFC destinations have to be debugged.

Regards,

Jai Shankar

[Former Member]

Ofcourse...It is workaround and not the solution. Debugging connection will take time and not as easy as it seems.

Meanwhile service should not be interrupted so I prefer to use workaround until problem is solved.

Regards,

Gourav

[MichalKrawczyk]

hi,

>>>>XIAPPLUSER getting locked

if he's getting locked then it might mean

that XI uses this user with a wrong password from somewhere

check out XI FAQ to find how to change pass for service users

did you try debugging this function ? LCR_LIST_BUSINESS_SYSTEMS

Regards,

michal

-

---

<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>