Error: First RFC call failed, config not loaded. Check the System landscape

[alexander_stettler]

Hi Experts!

After an Upgrade to 7.3 we have some issues when we try to open a report in our SAP Portal.

Two examples:

- We've tried to open a BEx Query out of the BEx Query Designer.

- We've tried to open a Dashboard used a BICS Connection.

In both cases, we run on an error after we've signed on the SAP NW Portal.

After the input of the logon information (username and password) the following error message appears:

Error: First RFC call failed, config not loaded. Check the System landscape

We checked the BW connection in our system landscape. Unfortunately we couldn't find any wrong entries - But it is not excluded that we are wrong in our assumption. After the creation of a new object in the system landscape the connection test is possible, but when we run the connection test in the landscape overview it's not possible to run the connection test successfully.

Have anybody of you an idea how we can solve this issue?

Thanks in advance!

Best Regards, Alex

[kundangandhi]

Hello Everybody,

I had also faced same issue.

Resolution -

update latest patch for below compo.

BI-BASE-B

BI-BASE-E

BI-BASE-S

BI-WEBAPP

BI-IBC

Ref.

1789842 - Patch Level 0 for BI Java Installation

1899396 - Patch Level 0 for BI Java Installation - Detailed Information

1906520 - Deploying BI Java patches using Telnet

1974464 - Information on SCA Dependency Analysis for Java download objects

2041071 - How to download latest Java patches using System Recommendation

note - Make sure for BI-JAVA never keep on patch 0, Always apply latest patch.

Regards,

Kundan .

[Former Member]

Dear's,

Any one is having solution for above mentioned issue, we are also facing same issue.

we checked all the settings and we did not find any issue on portal system and we are not getting RFC error but we are getting " system configuration not loaded. ".

[former_member331531]

Hello,

Just in case you have same issue with some of your users, check if the users are locked in BW.

In my case, I had same issue with 2 users, and they were locked. You can see this in SUIM t-code or USR02 table.

Thanks, Federico

[navin_mittal]

Check if the user is not locked and validity has not expired in BW system. We faced the similar issue and the reason was this,

[AK31]

Hi,

I had the same problem. The error message said "check your system landscape". I went into the portal -> system administration -> system landscape and executed "test connection". An exception was thrown stating "ERROR       service 'sapmsSID' unknown". I added it to the windows services file and restarted the portal. The "test connection" was successful now and the Bex started.

Regards

Andreas

[draschke]

yes, we refreshed the metadata of the users and it worked  finally.

I mean we created the user only again. that was all!

Message was edited by: Dirk Raschke

[draschke]

Hi,

are there any other solutions?

We have the same problem with only one user (by 1000 users)!

We have proved all his permissions, everything seems to be fine.

And we have not a clue where this problem comes from.

Regards

Dirk

[Former Member]

Hi Dirk,

Unfortunately, we have the same issue like you had/have in one of our subsidiaries now. Actually all of our users are able to access our WAD reports but a few (up to now 3 of 500) users are struggling with the mentioned error "First RFC call failed (...)".

Could you find a solution for your issue?

Best Regards,

Alex

[nicholas_steffens]

I battled with this for a long time before finding out the problem was a missing entry in the services file for the ABAP message server.

In Linux / Unix I added an entry like this for the ABAP message server:

sapmsBIT 3620/tcp # SAP Message Server Port

Hope this helps.

Regards,

Nick

[Former Member]

Hi Alex,

We are facing the same problem. Did you solve your problem? If yes, could you tell me how?

Thanks and best regards.

Marcos Alexandre Bertaci

[alexander_stettler]

Hi Marcos,

Yes, we could solve our issue...

We changed the default key size of the logon certificate from 2048 to 1024...

Regards, Alex

[former_member225306]

Hi,

Please check the note 1566979. Please redeploy listed components and restart the server.

All in all your Java system should have (from BI-side) following 5 SCAs

on the same SP and patch level:

BI-BASE-E

BI-BASE-B

BI-BASE-S

BIWEBAPP

BI-IBC

It should resolved your issue.

Thanks,

Venkat

[former_member188080]

Hi,

Check the connection parameters in SM59.

Carry out connection test and authorisation tests.

Check for BWREMOTE and ALEREMOTE user authorisation and whether password is expired.

Thanks and regards

Kiran

[alexander_stettler]

@ Venkateswarlu Nandimandalam:

Thanks for this information. We've already seen this link - Unfortunately it wasn't the solution we've searched for.

@ Kiran Vasant Kere:

We've checked the all the existing RFC connection - All connection and authorization tests are OK. Thus, there must be an other issue...

Regards, Alex

[Former Member]

Hi Alexander,

I don't any idea about the issues, but the below article which has discussed on same issue may helps you

http://wiki.sdn.sap.com/wiki/display/BOBJ/PermissionsandauthorizationsrequirementsforBExWebintoBI+4.x

Regards,

Venkatesh