cancel
Showing results for 
Search instead for 
Did you mean: 

Connection to SLD does not work from ECC

Former Member
0 Kudos

I'm trying to enable ABAP proxies on ECC , I'm not seeing any software components on ECC side., When I run SLDCHECK I'm getting this error Connection to SLD doesn not work at LCR_GET_BS_DETAILS

I enabled the ABAP proxies in diff client sites, never had any problem. Any help in my debugging greatly Appreciated.

Thanks

Ssk

Accepted Solutions (0)

Answers (8)

Answers (8)

0 Kudos

Hello!

Apply note:

#764176 - Error in XI due to inconsistent SLD contents

This will solve the inconsistences that you may have in you SLD.

Also, check the note below according to your system version:

#1143810 - Troubleshooting SLDCHECK - Releases 71X

#768452 - Troubleshooting SLDCHECK - Releases 640, 70X

Regards,

Caio Cagnani

Former Member
0 Kudos

Dear Folks

With regards to above thread I had similar issue and found the solution for SLD PI 711

We have requirement to configure PI 711 SLD and need to update all Current ABAP stacks in the Landscape to new PI 711 SLD but failed to communicate to SLD.

u2022 After analysis found the root cause that in PI SLD, Administration  Settings Section: Data Supplier  Gateway Service shows wrong service port details, it has taken the instance number by default where it has to update the Gateway service instance number which was allocated during installation.

I mean in my scenario main instance number is 00 and ASCS instance number is 01, in NW 711 Release SAP has provided Gateway Service along with ASCS instance i.e. here in my scenario Gateway service is sapgw01 but it has been updated with sapgw00, which is causing failure detection of SLD from source systems.

u2022 Updated Gateway service sapgw01 in SLD  Administration  Settings Section: Data Supplier  Gateway Service with value sapgw01 and restarted SLD, which has solved my issues.

Best Regards,

Venkata.

former_member368216
Participant
0 Kudos

Hi SSK,

Hopefully by now you have got the solution. I have similar problem, that reads service ' ' unknown. It is showing error on the Gateway service. RFC connection is to establish with PI 7.1. Lookig for some inputs. Please help, if you have some solution.

Thanks,

Ashok

Former Member
0 Kudos

Hi

In RZ70 transcation in data Collection programs check the SLDRFC and activate. that will solve your problem

Thanks

Former Member
0 Kudos

Hi,

I always use this blog to enable abap proxy on SAP ECC side:

/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies

So first of all check steps provided in this blog.

Second make sure that you ran transaction RZ70 (SLD administration) on SAP ECC side (and mentioned SAP PI server and gateway).

And third check in SLD that technical and business systems for SAP PI and SAP ECC are created if not, create business systems (technical system should be created automatically after running RZ70 transaction).

BR,

Dzmitry

Former Member
0 Kudos

Yes I folllowed the steps in the blog.

Technical system already existing in SLD. It was created manually ( Not through RZ70 ).

Now When I'm trying to execute RZ70 I'm getting following error.

0: sdaora1_DEV_00 : Execute program: SLDAPPL_SERV

0: sdaora1_DEV_00 : Execute program: SLDBCSYS

0: sdaora1_DEV_00 : Execute program: SLDCLIENT

0: sdaora1_DEV_00 : Execute program: SLDCOMPSYS

0: sdaora1_DEV_00 : Execute program: SLDDBSYS

0: sdaora1_DEV_00 : Execute program: SLDGWSRV

0: sdaora1_DEV_00 : Execute program: SLDINSTSC

0: sdaora1_DEV_00 : Execute program: SLDINSTSP

0: sdaora1_DEV_00 : Execute program: SLDIPSERV

0: sdaora1_DEV_00 : Execute program: SLDMSGSRV

0: sdaora1_DEV_00 : Execute program: SLDASSOC

0: sdaora1_DEV_00 : Collection of SLD data finished

0: sdaora1_DEV_00 : Data collected successfully

0: sdaora1_DEV_00 : RFC data prepared

0: sdaora1_DEV_00 : Used RFC destination: SLD_UC

0: sdaora1_DEV_00 : RFC call failed: JCO.Server could not find server function 'SET_SLD_DATA'

0: sdaora1_DEV_00 : Existing periodic jobs removed. Number: 1

0: sdaora1_DEV_00 : Program scheduled: 20100111 203822

1: sdaora1_DEV_00 : Event-controlled job already exists; scheduling not necessary

In SLD check I'm getting an error saying not able to connect to SLD.

Calling function LCR_GET_BS_DETAILS

Retrieving data from the SLD server...

Function call returned exception code 5

=> Check whether the SLD is running!

Summary: Connection to SLD does not work

=> Check SLD function and configurations

Thanks

SSk

VijayKonam
Active Contributor
0 Kudos

Did you maintain the right address and userid password in SLDAPICUST?

VJ

VijayKonam
Active Contributor
0 Kudos

Check if PIAPPLEUSER is able to log on to SLD. If not ask your security team to look at the error while trying to log on and assign the required roles to this user id. The problem should get solved..!!

VJ

Former Member
0 Kudos

I gave all trails on SAPSLDCUST, still same error.

Not able to access SLD.

SLDCHECK erroring @

Calling function LCR_GET_BS_DETAILS

Retrieving data from the SLD server...

Function call returned exception code 5

=> Check whether the SLD is running!

Summary: Connection to SLD does not work

=> Check SLD function and configurations

Thanks

Ssk

Former Member
0 Kudos

I gave all trails on SAPSLDCUST, still same error.

Not able to access SLD.

SLDCHECK erroring @

Calling function LCR_GET_BS_DETAILS

Retrieving data from the SLD server...

Function call returned exception code 5

=> Check whether the SLD is running!

Summary: Connection to SLD does not work

=> Check SLD function and configurations

Thanks

Ssk

Former Member
0 Kudos

Check the hostname in SLDAPICUST. The error indicates that it's not able to reach the system, thereby the SLD as well.

VijayKonam
Active Contributor
0 Kudos

Did you mention the complete qualified name of the SLD server? like servername.domain.com ??

VJ

Former Member
0 Kudos

Hi,

Just make sure that the user(in PI side) you are using in SLDAPICUST has role "SAP_SLD_GUEST"

Also check whether the user is locked in PI.

Try logging in with the userid in PI and see whether u can get in.

Mostly this happens due to the above reasons.

Thanks,

Gerard

Former Member
0 Kudos

Hi SSK,

Have you created HTTP RFC Connection for proxy to connect SAP R/3 to SAP XI??...if created then test it..

Then 1. Goto Transaction SXMB_ADM

2. Choose Edit --> Change Global Configuration Data.

3. Select Role of Business System: Application system

4. Corresponding Integration server: dest://<HTTPDESTINATION>.

5. Under Specific Configuration Data you can specify additional configuration data

1.Select the relevant category under Specific Configuration Data.

2.Choose Change Specific Configuration Data.

For ABAP Proxies, Add the following configuration:

1.Category RUNTIME

2.Parameters: IS_URL

3.Current Value: dest://<host>:<port>/sap/xi/engine?type=entry

Also create RFC destination (TCP/IP) LCRSAPRFC and SAPSLDAPI for the SLD connection.

Finaly,1. Goto J2EE Engine

2. Choose Cluster --> Server --> Services. JCo RFC provider

3. Under RFC destination specify the following:

Program ID: LCRSAPRFC

Gateway Host: <Integration Server host>

Gateway Service: <Integration Server gateway service>

Number of process: 3

4. Under Repository specify the following:

Application Server: <Integration Server host>

5. Choose Set.

Also check in SLD whether business system for your ECC exists or not...

Hope this will help you...

Regds,

Pinangshuk.

agasthuri_doss
Active Contributor
0 Kudos

SSK,

Checks to see if the rfc destinations exist and a connection between the both system & make sure SAP ECC are mentioned in SLD as WebAS ABAP/Java.

Check the below link

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

Cheers

Agasthuri

abhijitbolakhe
Advisor
Advisor
0 Kudos

Hi

Have you maintained the tcp/ip RFC's in sm59 LCRSAPRFC & SAPSLDAPI for the SLD connection in R/3 ?

Also test the RFC's Http type H..

Regards

Abhijit