Skip to Content
avatar image
Former Member

SLDCHECK problem!!

Gurus,

I'm having an issue getting SLDCHECK to run successfully.

Here's the steps I've taken

1. Ensure SLD server is running.

2. Created and tested SAPSLDAPI RFC connection.

3. Enable the Unicode RFC settings.

4. Created primary destination in SLDAPICUST for SLD server.

5. Tested user entered in SLDAPICUST via interactive login - all passwords and authentication are OK.

6. Created JCO RFC entry in SLD Visual Admin for ABAP system. It is running and tested OK.

7. Ran SLDCHECK on Abap side and here's the output:

Exchange Infrastructure: SLD Connection Test

Properties of RFC destination SAPSLDAPI

RFC host: %%RFCSERVER%%

program id: SLDAPI_DV4

gateway host: sldqas

gateway service: sapgw02

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

RFC ping was successful

SLD server address settings:

host name: sldqas

port number: 50000

Use transaction SLDAPICUST if you wish to maintain the SLD server address

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

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

Testing the SLD API

A communication or system failure has occured

Description: System error: Server repository could not create function template for 'SLDJAVA_ACCESSOR_REQUE

SLD host: sldqas

SLD port: 50000

Clearing the local SLD cache

Calling function LCR_LIST_BUSINESS_SYSTEMS

Retrieving data from the SLD server...

Function call returned exception code 3

=> Check whether the SLD is running!

Summary: Connection to SLD does not work

=> Check SLD function and configurations

______________________________________________________________

I have gone through the troubleshooting document "Transaction SLDCHECK reports errors" and only find one discrepancy.

My JCO RFC entry in SLD Visual Admin does not have a "Unicode" option? This document says that you need this selected if you are connecting b/t Unicode systems?

I also noticed that it was complaining about LCR fuction. I found that LCRSAPRFC is an RFC connection typically setup for XI <--> SLD communcation. Since my system is not XI (just normal R/3), would I need this RFC entry?

Please advise as to what config is missing.

Many points for helpful answers!!!!!

Thanks,

Jeff Martens

Basis Admin

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Sep 30, 2008 at 05:27 AM

    Hi Jeff,

    You are on right track. Since your current system is not a XI/PI you do not need LCR fuctionality. I believe this is required to fetch Business systems defined in SLD, which is useful for XI.

    Just try to initiate data transfer through RZ70 (without scheduling, if u already have done it) and check the logs. If data is transferred and in SLD if you can see last updated date/time as same, job's done.

    regards, Sean.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Jeff,

      Before you go for maintaining two SLDs, did you try considering having a single SLD [highly recommended even by SAP]. Many times more than two SLDs have conflict possibly due to mismatch in CIM model release level.

      Only in case you have more than one application which critically relies upon SLD you may want to distribute load [as we already discussed you don't have XI] For your and future support team's ease, go for one SLD.

      Still if you want to keep current status read Note 935474. One way data transfer is simply possible by export/import. I do not know of automatic data transfer. Will try finding out. In case you do, update this thread.

      regards, Sean.

      PS: Thanks for points 😊

  • avatar image
    Former Member
    Sep 30, 2008 at 02:01 AM

    Hi,

    Yes, if your ABAP system is a UNICODE system you will have to maintain the UNICODE flag here. You can check whether your ABAP is UNICODE of not in System->Status.

    Moreover, I think your problem in the settings in JCo Provider in Visual Admin. Make sure this is started and working. Check the seetings for SAP Gateway paramaetsr and the SAP user is fine and woking. This should solve it.

    Regards, Dibya

    Add comment
    10|10000 characters needed characters exceeded