More Information in Error Cases

Trace Files

For better error analysis, the RFC library and the SAP system Release 3.0E onwards will write some more error information into the TRACE file:

• dev_rfc0, dev_rfc1,... within an SAP system or

• dev_rfc or RFCnnnnn.TRC (16-bit RFC library) in non-SAP systems

RFC Library 3.0C on Windows (16- and 32-bit)

When working with the saprfc.ini file on Windows (librfc16.dll and librfc32.dll), you cannot connect to an SAP system Release 3.0D onwards with dialog user, because of a security error (system log with error code 152!).

In this case, use the RFC library version 3.0D onwards or CPIC user.

Stack Overflow while Working with librfc16.dll in 3.0D onwards

Because of some extensions in the "network interface" (NI) layer, some RFC programs could be broken by Windows Operating System with the error STACK OVERFLOW in some RFC error cases while working with the 16-bit RFC library 3.0D onwards.

In this case, recompile your RFC program with at least 9000 bytes stack size. The default value in "cl.def" of the Microsoft Visual C++ 1.5x is 8096 bytes.

Getting Version of the RFC Library

Until now it has been possible to get the version of the RFC library and all SAP internal libraries, such as cpic, ni,..., by using the call RfcGetAllLibVersions, but this call does not return any information about the Release to which this RFC library belongs.

From Release 3.0E onwards, the RFC library will also return the release of the SAP system.

To get this information, you can start sapinfo -v from the command line.