Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

RFC Connection not working between ECC5 to ECC6 system

Former Member
0 Likes
1,020

Hi all,

I have created RFC connection ( connection type is ABAP) in SM59 to connect my ECC 5 to ECC6 system for transfer data using ALE, i have given all the details in RCF connection and connection test is also working fine from ECC5 to ECC6 but when i distribute the model in BD64 it is showing me error "Model can not be distributed communication error, user name or password in not correct*" then i checked connection in SM59 and test the connection for authorization test here i am getting the same error but with same user id and password i can login into the ECC6 system.

here ECC 5 is my sending system and ECC 6 is receiving system, and connection is not working from ECC5 to ECC6 where as from ECC6 to ECC5 connevtion is fine

Please help in this Regard.

Thanks & Regards

Madhu

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
960

Sounds like a problem of downward incompatibility of passwords caused by lower- and UPPER-case characters.

This means that the higher release is expecting a case-sensitive password, but the lower one (and components in between) are converting the password to UPPER-CASE.

If the user is only used in this connection... set a password with all characters in UPPER-CASE in the ECC 6.0 system and test again.

Alternately take a look at the RZ11 profile login/password_downwards_compatibility. You can instruct the higher system to evaluate a password sent by a lower release system, if the new hashing mechanism fails. So it uses both until all connecting systems are compatible.

I prefer a mimic of the old mechanism (entering the password in UPPER-CASE) than using downward compatibility (both mechanisms).

Cheers,

Julius

Hi all,

I have created RFC connection ( connection type is ABAP) in SM59 to connect my ECC 5 to ECC6 system for transfer data using ALE, i have given all the details in RCF connection and connection test is also working fine from ECC5 to ECC6 but when i distribute the model in BD64 it is showing me error "Model can not be distributed communication error, user name or password in not correct*" then i checked connection in SM59 and test the connection for authorization test here i am getting the same error but with same user id and password i can login into the ECC6 system.

here ECC 5 is my sending system and ECC 6 is receiving system, and connection is not working from ECC5 to ECC6 where as from ECC6 to ECC5 connevtion is fine

Please help in this Regard.

Thanks & Regards

Madhu

6 REPLIES 6
Read only

abdul_hakim
Active Contributor
0 Likes
960

Hi

The user might not have been registered as RFC User. Check with the BASIS regarding this issue.

Regards,

Hakim

Read only

0 Likes
960

Hi,

Try to change user type to SYSTEM or Communication if it Dialog or for test purpose create a user of type System user and test whether model gets distributed.

KR Jaideep,

Read only

Former Member
0 Likes
960

Hi,

In ECC 5 , can the user able to LOGIN ?(dialog user)

Secondly , Check the Target Host, gateway service ( ECC 5).

Regards,

KC

Read only

Former Member
0 Likes
961

Sounds like a problem of downward incompatibility of passwords caused by lower- and UPPER-case characters.

This means that the higher release is expecting a case-sensitive password, but the lower one (and components in between) are converting the password to UPPER-CASE.

If the user is only used in this connection... set a password with all characters in UPPER-CASE in the ECC 6.0 system and test again.

Alternately take a look at the RZ11 profile login/password_downwards_compatibility. You can instruct the higher system to evaluate a password sent by a lower release system, if the new hashing mechanism fails. So it uses both until all connecting systems are compatible.

I prefer a mimic of the old mechanism (entering the password in UPPER-CASE) than using downward compatibility (both mechanisms).

Cheers,

Julius

Read only

Former Member
0 Likes
960

Hi,

Provide the right password and check with authorization test. It should work. Alternatively, check if the user exists in SU01D transaction and is extended to the system ECC6.

~ Bineah.

Read only

Former Member
0 Likes
960

Answered..