Skip to Content
avatar image
Former Member

RfcOpenEx failing on ECC 6.0, works on R/3

Hi,

We have an application that uses RFC. It works happily on R/3 but when we try against ECC 6.0 with the application on Windows we get a fail from RfcOpenEx - 'Name or password is incorrect (repeat logon)'.

We are passing exactly the same connection string - service identification bits are different of course.

TYPE=3 CLIENT=<800> USER=<uname> PASSWD=<password> LANG=E DEST=<server> USESAPGUI=0

The rfc.ini entry looks like:

DEST=<server>

TYPE=A

ASHOST<route>

SYSNR=<number>

RFC_TRACE=1

ABAP_DEBUG=0

USE_SAPGUI=0

The trace shows:

*> RfcOpenEx

options->destination = <server>

options->mode = RFC_MODE_PARAMETER

options->connopt = <NULL>

options->client = 800

options->user = <user>

options->password = 😊 secret (-:

options->language = E

options->trace = 1

Send RFCHEADER: 01/LIT/IEEE/SPACE/1100

Send UNICODE-RFCHEADER: cp:1100/ce:REJECT/te:REJECT/cs:1/rc:0x00000023

...

Received RFCHEADER: 01/LIT/IEEE/SPACE/1100

Received UNICODE-RFCHEADER: cp:4103/ce:REJECT/te:IGNORE/cs:2/rc:0x00000023

======> Name or password is incorrect (repeat logon)

The trace for the RfcOpenEx parameters looks identical when accessing R/3.

What has changed as far as this call is concerned between R/3 ECC 6.0? I can find no documentation at all for it.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Aug 01, 2007 at 05:06 PM

    hi

    Follow this link

    Question on BDLS

    regards

    santosh

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      This turned out to be because ECC 6.0 passwords are case-sensitive and up to 32 characters but RFC always capitalises passwords and truncates them to 8 characters. Hence the password set for the RFC user must be uppercase and at most 8 characters.