Occasional crashes when connecting via librfc32.dll

[Former Member]

I'm maintaing a home-brewn (c++) connector to SAP which connects via librfc32.dll to an SAP system.

We get occasional crashes (Access violations) during calls to SapRfcCall and SapRfcReceive (more frequently in SapRfcReceive). The crashes are the real problem, but the errors in the tracefile described below are also symptoms that something is quite broken.

The output in dev_rfc.trc looks like this, every access to the Sap system results in these entries in the tracefile:

• ERROR file opened at 20100324 203546 Westeuropäisch, SAP-REL 640,0,76 RFC-VER 3 755776 MT-SL

T:2244 *>RfcInstallStrucure2: field 11 (ROW, t:8, l:4) offset 502 too small

(at least 504 expected)

The calculated offset of 502 which is used to construct the structure which is installed using RfcInstallStructure2 is

correct (the sum of the lenghts of all preceding fields).

Along with the above entries, sometimes occasional errors like this one are strewn in:

• ERROR file opened at 20100326 102646 Westeuropäisch, SAP-REL 640,0,76 RFC-VER 3 755776 MT-SL

T:3252 *>RfcInstallStrucure2: field 11 (ROW, t:8, l:4) offset 502 too small

(at least 504 expected)

>TS> Fri Mar 26 10:28:44 2010

T:3252 *>RfcInstallStrucure2: field 11 (ROW, t:8, l:4) offset 502 too small

(at least 504 expected)

T:3252 Invalid ParameterT:3252 detected

T:3252 parameter[4].name =

T:3252 parameter[4].type = 8

T:3252 parameter[4].leng = 0 expected 4

T:3252 -> -

-

---

<-

T:3252 <* RfcReceive : returns 19:RFC_INVALID_PARAMETER

For these Error messages, the parameter name is sometimes empty, sometimes scrambled garbage. Also, the error occurs for

different parameters.

Changing the offset to 504 in the descriptor makes the errors go away, but does not fix the crashes. (it is obvious that such a brute-force measure did not work)

When the RFC_TRACE=1 in the saprfc.ini file is set, an additional trace file is produced, but then the crashes occur at virtually every access to the sap system.

Any help on the problem would be apreciated, thanks in advance.

[Sandra_Rossi]

you should contact sap support