cancel
Showing results for 
Search instead for 
Did you mean: 

Access to the XI Profile is currently disrupted.

Former Member
0 Kudos

Experts

I am getting similar error in sld check

Exchange Infrastructure: Test LCR Connection

Properties of RFC destination SAPSLDAPI

RFC host:

%%RFCSERVER%%

program id: SAPSLDAPI_PP4

gateway host:

HOSTEST

gateway service: sapgw00

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

RFC ping was successful

SLD server access settings:

host name: HOSTEST

port number: 50000

user : j2ee_admin

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!

Calling function LCR_LIST_BUSINESS_SYSTEMS

Retrieving data from the SLD server...

Function call terminated sucessfully

No business systems maintained in the SLD

=> Check data integrity within the SLD!

Summary: Connection to SLD works technically, but the SLD content may need maintenance

=> Check and maintain the SLD data content

Now checking access to the XI Profile

Properties of RFC destination LCRSAPRFC

RFC host:

%%RFCSERVER%%

program id: LCRSAPRFC_PP4

gateway host:

HOSTEST

gateway service: sapgw00

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 returned exception code 3

Access to the XI Profile is currently disrupted.

=> Check whether you can access the XI Profile using a web browser!

all my rfc are working fine.

sldapicust is also working ok.

but my exchnage profile link is not working.

when ever i open URL exchange profile URL my PISUPER user gets locked.

Dont know why

and when i unlock it and open my URL again it gets locked.

I have cleared all caches and deleted old values but still i hve the error.

even whn i try sxmb_ifr t code i get the error;

3: Error while reading configuration for secure communication

Message no. SAI_GLOBAL030

Can you help on this plz.

Regards

Pooja

Accepted Solutions (0)

Answers (1)

Answers (1)

sunny_pahuja2
Active Contributor
0 Kudos

Dear Pooja,

If I am checking your logs then first thing which I observed is:

1) You have not defined your XI system in SLD in Business systems.

2) Why not you try to change your XI profile from different user instead of PISUPER user ?

Thanks

Sunny

Former Member
0 Kudos

Resolved this error by re checking the exchange profile entries.

All the rfcs and program ID both at ABAP and J2EE level.

Doing the xi readiness checks again.

Thanks for your answer.

Regards

Pooja

Former Member
0 Kudos

Hello PPooja¡¡¡

I've the same problem. I'm trying to configure SLD in my SOLUTION MANAGER 7.0 EHP1. The Solution Mananger Is not a XI system and then i have this question. Is this checking necesary for my system?

The error is:

Calling function EXCHANGE_PROFILE_GET_PARAMETER

Retrieving data from the XI Profile...

Function call returned exception code 3

Access to the XI Profile is currently disrupted.

=> Check whether you can access the XI Profile using a web browser!

Best regards,

Javier Mora

Former Member
0 Kudos

Hi Javier

Request you to perform all the Readiness checks for your PI system.

Then if you are diverting your SLD to that system then follow the notes for SLD diversion.

Also use the user wth apppropriate priviledges and authorizations.

Let m know if u still have the issue.

Regards

Pooja

Former Member
0 Kudos

Hello Pooja,

Thanks for your rapdly answer...

I've executed all these cheks in the PI system, there is no problem in this point. I have the problem with the Solution Mananger. When i execute SLDCHECK in the Solution Manager (NO XI system) I get this error. I understan the access to the XI Profile in PI is necesary and the access to the XI profile in Solution Mananger si not necesary, It's this true?

best regards,

Former Member
0 Kudos

is ur solman acting as central sld system.

Have u directed both of ur abap and j2ee sld of PI system to solman system

Follow the notes for sucessful sld diversion.

The user used for communication in both sysytem should be the same.

defined in sldapicust.

Regards

Pooja

Former Member
0 Kudos

Hi Javier,

You are correct. The Exchange profile is not needed in Sol Man. If you run SLDCHEK In Sol Man, you will get the 'Access to the XI Profile is currently disrupted'. I don't think Sol Man needs it.

WL