on 08-01-2007 3:36 PM
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for that.
However we are using the test systems in SAP, we are not using our own systems. We have been given access to the ECC 6.0 system and this is the one we can't connect to. We can connect to the R/3 test system and we can connect to the ECC 6.0 test system with SAPGUI, but not with our application. As mentioned we are using excatly the same RFC connection method on both systems (except for the system specific parts).
Regards,
John.
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.