Qlik SAP Connector: TIMEOUT_READ_MEMORY and Invalid LZ-compressed data block received, ignored

Invalid LZ-compressed. It’s from the SAP drivers for .NET. It does not affect the loading. The drivers will get a new data block to replace the one it ignored because of invalid compression. This should be just ignored.

TIMEOUT_READ_MEMORY and TIMEOUT_READ_DATA does not have to mean that something is wrong. If there is a heavy load on the SAP system, you can get them frequently.
 
TIMEOUT_READ_DATA means that the background batch job (fetching the data) has not started yet. This can happen if all available background processes in the system are occupied. Then our job starts as soon as there is a free process.
 
TIMEOUT_READ_MEMORY means that the Windows part of the connector does not receive data from the batch job. This can happen if it is a complex SQL statement. The connection string property TimeOutFetch decides how long to wait before it is considered to be an error.
 
TimeOutFetch

n (default = 1200 seconds)

The number of seconds spent trying to fetch from SAP without getting any records back.

This can be adjusted to suit the environment however, as mentioned it will all depend on the load from SAP.