Known Issues - SAP .NET Connector Version 3.0.23 and previous Versions - Qlik Connector for use with SAP NetWeaver(R)

[Rakesh_HB]

1. An implementation of ISessionProvider is complaining about a thread being already blocked by a session when a session shall be activated.
2. Communication does not work at all showing error messages referring to NI.
3. An exception occurs that is similar to: SAP.Middleware.Connector.RfcInvalidParameterException: Element ABC of container metadata XYZ unknown
   

   at SAP.Middleware.Connector.RfcContainerMetadata.NameToIndex(String elementName)
   at SAP.Middleware.Connector.RfcXRfcParser.ProcessBeginTag()
   at SAP.Middleware.Connector.RfcXRfcParser.parse()​

4. An exception occurs that is similar to: SAP.Middleware.Connector.RfcInvalidStateException: index 30 out of range
5. A parameter of type BYTE is truncated.
   An exception occurs that is similar to: System.ArgumentNullException: Value cannot be null. Parameter name: args
   

   at String.Format(IFormatProvider provider, String format, Object[] args)
   at TextWriter.WriteLine(String format, Object[] arg)
   at RfcTrace.set_TracePerThread(Boolean perThread)​

 

Other Terms

RFC_METADA_GET, EX_FUNCTIONS

 

Reason and Prerequisites

The problems above have been caused by the following issues in NCo 3.0.23:

1. The session was created within an NCo Server. A critical error situation occurred, which caused the connection to be closed. As RFC sessions are associated with the connection, the session implicitly ended, but the registered ISessionProvider was not notified about this.
2. NI is the socket layer used by NCo. Under certain circumstances, it could happen that the initialization routine is not invoked before using the sockets.
3. The function module invoked returns a table or a nested structure in an exporting parameter, which is not defined in the metadata used for that function module. When trying to process the received data, the unknown parameter should be accessed, which led to the exception.
4. The function module invoked returns a table or a nested structure in an exporting parameter and the data amount is huge. In some border cases, the mentioned exception could occur.
5. The metadata retrieved for that function parameter was interpreted incorrectly so that the data was truncated at half the size.
6. Tracing policy is switched after traces were already written.

Resolution

Upgrade to at least NCo 3.0.24, which is available on the download page under SAP Connector for Microsoft .NET, or download

"Qlik Connector for use with SAP NetWeaver(R) v8.0.1" which contains 3.0.24 from the Qlik Downloads site.

Please note that this is a patch level exclusively for the .NET 4.0 binaries, specifically for the .NET runtime 4.0, 4.5, 4.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, or 4.8. For the .NET 2.0 binaries support ended on July 31, 2018.

1. Also in case of exceptions, the ISessionProvider is notified about a destroyed session.
2. NCo ensures that the initialization happens very early.
3. Unknown parameters are now always ignored.
4. The border cases are now treated correctly.
5. Metadata interpretation has been corrected for BYTE parameters.
6. Tracing policy switch was corrected.

In addition, the following enhancements have been added:

1. Improved tracing of the invocations for the methods of the registered ISessionProvider of RfcSessionManager.
2. Suppressing dev_nco_rfc.log when changing trace directory unless log has already been written to it.

Environment

Qlik SAP Connectors