Community
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
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

RFC Problems after BW Upgrade

Former Member

‎2007 Feb 13 8:53 PM

0 Likes
555

Folks,

We have upgraded a BW 3.5 System to BI 7.0. After the upgrade, the RFC connections are giving problems. When I click test connection, it works. But remote login is not working.

The RFC trace file gives the error "

*CLIENT > SREAD [EndWrite...StartRead] Time 0.000000

======> You are not authorized to logon to the target system.

ABAP Programm: RSRFCPIN (Transaction: SM59)

Called function module: RFCPING

User: xxxx (Client: xxx)

The BI is upgraded to 7.0. But R3 system is 4.0B. The hostname, instance number are correct. The source and destination users are dialog users and the RFC Connection is 3. Please help me in finding the problem. Points will be awarded for any kind of help.

Folks,

We have upgraded a BW 3.5 System to BI 7.0. After the upgrade, the RFC connections are giving problems. When I click test connection, it works. But remote login is not working.

The RFC trace file gives the error "

*CLIENT > SREAD [EndWrite...StartRead] Time 0.000000

======> You are not authorized to logon to the target system.

ABAP Programm: RSRFCPIN (Transaction: SM59)

Called function module: RFCPING

User: xxxx (Client: xxx)

The BI is upgraded to 7.0. But R3 system is 4.0B. The hostname, instance number are correct. The source and destination users are dialog users and the RFC Connection is 3. Please help me in finding the problem. Points will be awarded for any kind of help.

Reply
2 REPLIES 2
Read only

Former Member

‎2007 Feb 14 12:11 AM

0 Likes
489

I think it is a password issue. Please do the authorization test in SM59.

From 7.0 passwords are case sensitive, so if you are connecting to or from 7.0 system enter the password with proper case.

Since you are connecting to 40B system in BI 7.0-SM59 enter an upper case password in the 40B system definition.

Hopefully this should resolve your issue.

Chandhu

Read only

Former Member

‎2007 Feb 19 9:52 PM

0 Likes
489

Abdul,

I agree with Chandhu. In WAS700, many of the restrictions to password creation were lifted. WAS700 observes case sensitivity and greater password lengths. Remember that your 4.0B backend will not be able to interpret case sensitivity nor passwords greater than 8 characters in length.

If the password of the user in the 4.0B backend is PASSWORD, then make sure your cap locks is on when you enter the password in the RFC. WAS700 will store the PW in lowercase, and will also pass it over to the 4.0B system as such.

Good luck,

Tim