Error: QVX_UNEXPECTED_END_OF_DATA:

[AliceB]

Hi all.

We are extracting data from a Date Base using an OLE DB connection for SQL server in Qlik Sense Enterprise.

At the beginning it was working well without any error, until we've started to experience this error:

Error: QVX_UNEXPECTED_END_OF_DATA:

Execution Failed

Execution finished.

The error pops up randomly when the code is reading any table, most of the time reading one of the biggest tables.

We thought it was because of the copies the client is making to the BD but even if we've asked to stop copies in a window of time of 1 hour and half, the error persists.

Any idea what is happening and how to fix it?

Thanks in advance.

Alice 

[Anonymous]

Hello @AliceB , many thanks for sharing your case and following it up; I believe the case is really well described; I would be happy to help you but - from my point of view - I belive more logs and informations are requiered here.

What version of SQL SERVER are you using? What version of QLIK are you using? What version of OLE  DB driver are you using?

When the above error appears on the client side, can you check for server-side logs, if any?

From a server-side perspective, do you have any logs related to your error when it appears on client-side?

Do you have more detailed logs from a client-side perspective?

Regards,

[chriscammers]

Here is what I would suggest 

1. Query the table directly do not use a view
2. simplify your code, remove joins, subqueries anything other than select...from where...
3. apply any where clause to the sql part of your load statement
4. Reduce the fields retrieved to only the ones you are using, do this in a methodical fashion so you can determine if any individual fields are causing the issue.
5. Reduce the number of rows retrieved in a single query, partition by some meaningful field to split large tables into more manageable segments
6. test your network latency and take steps to reduce
   • In the cloud - gateways and QDTU servers need to have close proximity to the database server.
   • Client Managed servers - reload nodes should also be proximal to the source data

[AliceB]

Hi all.

There are some news.

• We've created a new extraction APP using a Microsfot SQL server connector (we've been using the OLEDB SQL Server Connector until now) and the error is this one: Error: ERROR [08S01] TDSConnectionFailed.
• We experiment the error at 3.30 AM when the copies of replica DB are stopping and supposely there are no other DB processes or QMC reloads, but it works after a couple of intents at 7.30 AM.

Just to answer to @chriscammers :

1. We are trying to extract from the orginal DB and from its replica too. Both give us same errors.
2. No joins or subqueries, just extraction of whole tables.
3. We use where in a few tables when it's required to limit the rows by date or type.
4. We are selecting all the fields as we make in the other client (the error doesn't occur in the same tables, but most of the time extracting the biggest ones).
5. We have divided the code in more sections where we connect to the DB, exctract and save tables in QVDs, finally disconnect and reconnect another time.
6. We are not using QS Cloud but QS Enterprise, and we just have one node.

Don't know how to manage it this error of TDSConnectionFailed.

Thanks in advance to all,

Alice B.

[kismoflans]

@AliceB I have another suggestion. Create a folder on the server where Qliksense can read files from. Download QDT and Qlikview. Create your odbc ole connections on Qlikview. Paste your sql script on the load editor and store the table to QVD to the folder that Qliksense can access files from. Use QDT to schedule times for the Qlikiew to run extraction.