cancel
Showing results for 
Search instead for 
Did you mean: 

SLDCHECK not working

ayan_chaudhuri
Participant
0 Kudos

Hi experts,

When we are running SLDCHECK from ISU to check SLD connectivity to PI , we are getting the following errors.

ERROR:Calling function LCR_LIST_BUSINESS_SYSTEMS

Retrieving data from the SLD server

Function call returned exception code 3

ERROR: Calling function EXCHANGE_PROFILE_GET_PARAMETER

Retrieving data from XI Profile...

Function call returned exception code 2

Access to the XI Profile is currently disrupted

Other RFCs like (LCRSAPRFC,SAPSLDAPI) are working properly

Any input pls

Thanks Ayan

Accepted Solutions (1)

Accepted Solutions (1)

marksmyth
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello

Check the link [Configuration of Business Systems with an Integration Engine|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/c9/7a1041ebf0f06fe10000000a1550b0/frameset.htm]

There are several configuration steps required and these are documented in the sub-links i.e.

-> Configuring the Role of the Business System

-> Connecting to the Integration Server

-> ..... etc

Regards

Mark

ayan_chaudhuri
Participant
0 Kudos

Hi Mark,

The problem is still not resolved....

When the SLDCHECK is running from remote ECC system, it is throwing the following errors

ERROR:Calling function LCR_LIST_BUSINESS_SYSTEMS

Retrieving data from the SLD server

Function call returned exception code 3

ERROR: Calling function EXCHANGE_PROFILE_GET_PARAMETER

Retrieving data from XI Profile...

Function call returned exception code 2

Access to the XI Profile is currently disrupted

RFCs LCRSAPRFC and SAPSLDAPI are working properly.........

But the SLDCHECK is working fine when it is running from PI.

May I add, the SPROXY transaction in ECC system is working properly.......But when we are trigerring the Proxy from ECC to send the data to PI the below error is coming.

GET_BUSINESS_SYSTEM_ERROR An error occurred when determining the business system (COMMUNICATION_ERROR)...

After that we run SLDCHECK from ECC and the error is coming as mentioned above..

Thanks

Ayan

RKothari
Contributor
0 Kudos

Hello,

Please check in your ECC system, the connection type H in SM59, which connects to Integration server of PI system is working fine.

Also, verify if the RFC destination provided in T-code sxmb_adm --> Integration engine is correct.

-Rahul

Former Member
0 Kudos

Hi,

You should create a business system in XI system.

sldapicust user should have the role to access XI sld.

sm59 h type connection user should have the piappluser role.

Thanks and Regards,

Prakasu.M

ayan_chaudhuri
Participant
0 Kudos

HI Rahul

1)Please check in your ECC system, the connection type H in SM59, which connects to Integration server of PI system is working fine------ The connection of Type H is working properly

2)Also, verify if the RFC destination provided in T-code sxmb_adm --> Integration engine is correct----In Integration Engine configuration on checking the Global Configuration data , it is giving the following error

No Access to system landscape at present

Thanks

Ayan

Answers (4)

Answers (4)

marksmyth
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello

In ECC,

- are the LCRSAPRFC and SAPSLDAPI destinations using the same configurations as on the PI system i.e. the same Host and Gateway parameters.

- what user is maintained in trx SLDAPICUST? Is this user available on the PI system? Is the user locked?

- in trx sxmb_admin -> Integration Engine Configuration, what is the Role of Business System?

- in trx sxmb_admin -> Integration Engine Configuration, what is the value maintained for Corresponding Integration server? It should be in the form of dest://<SM59 destination pointing to PI Integration Server>. What user is maintained in this SM59 destination? Is it locked?

Regards

Mark

Former Member
0 Kudos

ERROR:Calling function LCR_LIST_BUSINESS_SYSTEMS

Retrieving data from the SLD server

Function call returned exception code 3

ERROR: Calling function EXCHANGE_PROFILE_GET_PARAMETER

Retrieving data from XI Profile...

Function call returned exception code 2

Access to the XI Profile is currently disrupted

1. Check on SDAPICUST , Check for user name / password / Locking

2. Check SLD , is up and Reachable and working .

3. On exchange profile , on right side , there will be a botton ( Connection) - check for username / password / Unlocked

Regards

Prabhat Sharma.

RKothari
Contributor
0 Kudos

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

-Rahul

Former Member
0 Kudos

Hi Ayan,

Check the below llinks:

Issue 1:

/people/vikas.jain12/blog/2009/01/13/sld-self-registration-problems-and-troubleshooting

http://help.sap.com/saphelp_nw04/helpdata/en/78/20244134a56532e10000000a1550b0/frameset.htm

Issue 2:

Please logon in XI. use tcode SXMB_IFR

Then go to administration tab.

Right side exchange profile tab will come. Login in exchange profile and check all SLD settings.

OR access exchange profile by this-

http://<host:port>/exchangeProfile

In this HTTP address, host and port are the host name and connection port of your Integration Server.

and chk whether these parameters are present in Connections for the XI server to which u wish to connect from SAP System

com.sap.aii.connect.repository.name

SAPXI3

com.sap.aii.connect.repository.httpport

50000(At SICF http service must be active)

com.sap.aii.connect.repository.contextRoot

rep

com.sap.aii.connect.integrationbuilder.startpage.url

rep/start/index.jsp

If these parameters are not present then add them.

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

Thanks,