QV Publishers reloads some documents but not others after 12.5 upgrade
We just upgraded to 12.5. We have many documents that the publisher processes nightly. Some of the documents reload just fine while others do not. We think there might be something with the documents themselves because the same documents do not reload. I just cannot figure out what needs changed in the document.
For the documents that the publisher does not reload, when I open them in the client and reload the data, it works just fine. The same credentials are used to connect to the source DB by the Publisher and the client.
Here is a sample of the Task Log from the publisher:
(12/4/2020 7:47:21 AM) Information: Physical FileSize=0.14 Mb. Memory Allocation Delta for this file=3.14 Mb. Available Physical Memory Before Open=60247.42 Mb. Available Physical Memory After Open=60243.92 Mb. Total Physical Memory=65535.55 Mb.
(12/4/2020 7:47:21 AM) Information: Attempted to load the document without data.
(12/4/2020 7:47:21 AM) Information: The document was loaded successfully.
(12/4/2020 7:47:21 AM) Information: Document was opened successfully
Hi @austin_james, you can enable document log openeing the document with Qv desktop, in document properties -> General, chek the box to generate log.
The repeated reloading message can have diffrent causes, maybe some data type is beign readed as a different sata type and causing duplicated records, it can be hanging trying to read/write some file that is locked, database can fail to return data or error.... in any case the document log can help to debug, also try manual relaod with a 12.5 desktop using the same user that executes the reload task to confirm it has enough permissions to do all the tasks
@austin_james can you attach the full task log/document log to this thread for review? From the snippet you posted, we can see Information: MaxRunTime=00:10:00. So is the task exceeding this configured max runtime? Also, does this task fail each time it is run.
Sr. Technical Support Engineer with Qlik Support Help users find answers! Don't forget to mark a solution that worked for you!