cancel
Showing results for 
Search instead for 
Did you mean: 

UD Connect based Source System connection issues

Former Member
0 Kudos

We are using few UD connect based connections. Until recently (we upgraded from BW 7.1 to BW 7.31 SP5)  they were working fine. We are getting extraction error " Communication error: Cannot authenticate the user" in production for the loads with process chain but it goes through with multiple attempts directly from IP or DTP.

But in our Development system all UD based Source System show broken. RSA1 check for S.S gives below error. I have tried troubleshooting it from all possible aspects with Basis, AD and portal resource nothing seems to come out but SM59 RFC connection test goes fine. I will appreciate to get any insight from someone with similar experience .

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Source System check errors:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Diagnosis

    You tried to logon to check connection CSABID_RIG to the source system.

    This was not successful.

System Response

    Cannot authenticate the user.

Procedure

    Check the destination of the BW system in the source system.

    Particularly with SAP connections, make sure that you have entered the

    correct password.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Diagnosis

    BI Java connector 'SDK_JAVA ' is entered for source system CEDBPM . This

    is not correct.

System Response

Procedure

    Enter the correct BI Java connector in table RSLOGSYSUDC.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Sorry for the late update.We finally narrowed down and the issue was due to the difference in the clock setting between Portal and BW servers and got corrected after sync'g up server clocks.

Answers (1)

Answers (1)

RamanKorrapati
Active Contributor
0 Kudos

Hi,

Ask your basis team to recheck partner profiles are in active or not in bw server Tx - We20/21.

Basis or source system consultant may need to have authorization to establish the broken connection.

Error also clearly saying as your logical mapping table RSLOGSYSUDC have wrong entries.

Check that table and maintain proper source and target system technical details.

Thanks

Former Member
0 Kudos

Hi Raman,

Thanks for your reply. We checked partner profile which shows active and entries in RSLOGSYSUDC are correct, it shows Source System and name of the SDK correctly. Any other idea to look at?