QlikView throws the below error while testing the SapSQL Connection:
Connection failed
RfcCommunicationException: The only destination DefaultDestination available failed when retrieving metadata from ESS -- see log for details
Below error found in SAP SQL Connector logs files (C:\ProgramData\QlikTech\Custom Data\QvSAPSqlConnector\Log\)
SqlSapService.OpenConnection() - Using SocketBufferSize:32768
Connection to SAP verified, using sapnco version:3.0.18.0 with SocketBufferSize:32768
Mismatch Error in SapErpConnection.TransportsHaveCorrectVersion(): RfcCommunicationException:The only destination DefaultDestination available failed when retrieving metadata from ESS -- see log for details
Environment
Resolution
- You must be on the recent .NET Framework version.
- Upgrade to SAP Connector version to 8.0.1 as this is a known issue found in earlier versions of 3.0.24.
- SAP .NET connector version is 3.0.24 is included in 8.0.1 and be confirmed in details of "sapnco.dll" found in "C:\Program Files\Common Files\QlikTech\Custom Data\QvSAPSqlConnector\"
Cause
The problems above have been caused by the following issues in NCo 3.0.23:
- 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.
- 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.
- 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.
- 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.
- The metadata retrieved for that function parameter was interpreted incorrectly so that the data was truncated at half the size.
- Tracing policy is switched after traces were already written.
Note:
Microsoft provided the following information:
Install the most recent version of SAP Connector (NCo 3.0) for Microsoft.NET 3.0.25.0 compiled with.NET Framework 4.0 - Windows 64-bit (x64). Previous versions of SAP NCo may encounter the following issues:
The following exception message will be displayed in an older version: 'The only destination <some-GUID> available failed when retrieving metadata from <SAP-system-ID> - see log for details'.
Internal Investigation ID(s):
QB-17093
Related Content
Known Issues - SAP .NET Connector Version 3.0.23 and previous Versions - Qlik Connector for use with...