RFC Error with SAP .NET Connector 2.0

[Former Member]

I'm attempting to access SAP using the .NET Connector 2.0. I previously used the 1.0.3 connector successfully with the same code. Now that I am using the 2.0 connector, I keep getting "Unhandled Exception" errors from the SAP Proxy Object. The RFC Log file has the following entry...

• ERROR file opened at 20041014 105258 Pacific Dayligh, SAP-REL 620,0,1658 RFC-VER 3 689290 MT-SL

T:3416 *> RfcInstallStructure2 : wrong API call : entries == 0 is not allowed

Any ideas?

[Former Member]

Hello,

did you re-generate the proxy with 2.0 or just rebuild the existing code generated with 1.0.3?

You had better open a SAP OSS message under component BC-OP-NET-NCO and attach the generated C# files.

Regards,

Guangwei

[Former Member]

Yes, I regenerated the Proxy in 2.0 because I'm developing in VB, and 2.0 is more tightly integrated with VB. Thus, the proxy generated files are VB files. I had opened an OSS Note on this subject and was told that this was not a technical problem...that I was to refer to this forum.

The OSS Message number is 0120050410 0000307544 2004

[Former Member]

Hello,

Please either re-open the message 0120050410 0000307544 2004 or create a new one and attach the VB code.

Regards,

Guangwei

[Former Member]

Thank you for your input. I posted a new message and attached the VB code per your suggestion. The message number is 3526872.

[Former Member]

Greg,

Were you able to resolve this issue? I'm getting exactly the same exception using the Java connector in Netweaver Dev Studio.

Cheers,

Nick

[Former Member]

Did anoyone find a solution to this problem?

I'm experiencing the same problems using the .Net Connector 2.0 in Visual Studio.Net 2003.

The error message is as follows (in dev_rfc.trc):

RfcInstallStructure2 : wrong API call : entries == 0 is not allowed.

I'm successfully calling the BAPI: BAPI_VENDOR_FIND. When I'm trying to call the BAPI: BAPI_VENDOR_GETDETAIL I'm receiving the error above.

BAPI's like BAPI_COMPANYCODE_GETDETAIL and BAPI_DOCUMENT_GETDETAIL2 is working perfectly.

Please respond someone.

Cheers,

Erling

[Former Member]

Hi,

The error seems to be caused by a bug in version 2.0.0 related to the built-in type BAPIRET1. This structure is used by BAPI_VENDOR_GETDETAIL but not by those BAPIs that succeeded.

Please apply version 2.0.1 that fixes this and other known bugs.

Guangwei Li