Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Publisher fails with direct discovery

Hi all,

I have an intermittent problem publishing an application using direct discovery. I have a scheduled reload&publish once a day and it goes fine and sometimes the manual reload&publish goes fine as well but once it fails I've come up short on solutions. Very frustrating since I can't test my changes.

The reload goes fine but when publishing the application it fails. See publisher log excerpt below.

Has anybody else had this issue and found a remedy/workaround?

(2016-01-15 09:10:23) Information: <Error />

(2016-01-15 09:10:23) Error: The QlikView Server returned a error

(2016-01-15 09:10:23) Information: Performance data (CopyFile): Connecting to QVS. (0), DMSAccessRules=7 (0), Uploading file: Dashboard.qvw (0), Write complete. (438784 bytes processed) (47)

(2016-01-15 09:10:23) Error: QVS Distribution failed to distribute to QVS

(2016-01-15 09:10:23) Error: Distribution to resources failed with errors. Warnings: 1, Errors: 2

(2016-01-15 09:10:23) Information: Deleting temporary files.

(2016-01-15 09:10:23) Information: Closing the document.

(2016-01-15 09:10:24) Information: Closed the QlikView Engine successfully. ProcessID=118912

(2016-01-15 09:10:24) Error: The task "Reload and Distribute of Documents\Dashboard.qvw" failed. Exception: || QDSMain.Exceptions.TaskFailedException: Task execution failed with errors to follow. ---> QDSMain.Exceptions.LogBucketErrorException: Distribution to resources failed with errors. Warnings: 1, Errors: 2 || at QDSMain.DistributeTask.RevertOneAndAlwaysOne(Document qvbDocument) || at QDSMain.DistributeTask.ReleaseQvb(Document qvbDocument) || at QDSMain.DistributeTask.Distribution(String fileName, DistributionRequest distributionRequest, TaskResult taskResult, String repeatVariableName, String currentRepeatVariableValue) || at QDSMain.DistributeTask.Execute(TaskResult currentTaskResult) || --- End of inner exception stack trace --- || at QDSMain.DistributeTask.Execute(TaskResult currentTaskResult) || at QDSMain.Task.AbstractTask.TaskExecution(ILogBucket logBucket, TaskResult taskResult)

(2016-01-15 09:10:24) Information: Task Execute Duration=00:00:47.0034026

(2016-01-15 09:10:24) Information: TaskResult.status=Finished

(2016-01-15 09:10:24) Information: Notifying all triggers of new state:FinishedWithErrors

(2016-01-15 09:10:24) Information: Notifying all triggers of new state:FinishedWithErrors - completed

(2016-01-15 09:10:24) Information: Saving Task Result

1 Solution

Accepted Solutions
Anonymous
Not applicable
Author

This behaviour is a confirmed bug. It is the connect/reload-process (QVConnect64.exe in my case)  that locks the qwv-file on the publisher.

There is a patch for SR12 ( (11.20\SR12-1\12929(29))) but according to Qlik no plans, as of yet, to include it in a SR.

View solution in original post

9 Replies
oknotsen
Master III
Master III

What version and service release is your server?

May you live in interesting times!
Anonymous
Not applicable
Author

Ahh, sorry about that: 11.20.12904.0

oknotsen
Master III
Master III

Sorry, I do not recognize the service patch in that. That's just because I do not know the individual build numbers.

Reason I asked is because Direct Discovery did not work pre SP5. Start SP5 we have seen various improvements in the functionality. If the developer uses a higher SP to develop the app than your server, it might give errors because your server does not recognize the new functionality.

So, check if both have the same SP (or your server is on a higher SP).

May you live in interesting times!
Anonymous
Not applicable
Author

It appears the server is on SR12 and I'm developing on SR9. I'll upgrade mine to SR12 as well and see what happens.

qv_versions.JPG

jerrysvensson
Partner - Specialist II
Partner - Specialist II

11.2 SR13 has a bug fix

"69944 Direct Discovery: Reload task failure after selections been made"

Could it be what is causing your issue?

Anonymous
Not applicable
Author

That is interesting. I upgraded my qv desktop to SR12 (same as server) but the problem remains*.

Is there somewhere one can read the the full issue description/report? It is not the reload task per se, but the distribution.

*I managed to publish it once but I realised that I had disabled the reload so maybe I still have the file built on the older version published. It failed to reload and publish again. Also when clearing all selections. There is still a slight glimmer of hope that once I have managed to reload AND published the file built on the SR12 it will work.

Not applicable
Author

If you are using Patch version, please contact Qlik support on this issue. More or less its happening issue some reload tasks in the schedule. I believe its issue with your version.

jerrysvensson
Partner - Specialist II
Partner - Specialist II

I don't think upgrading Desktop will make any difference.

Your problem is related to Publisher/server. If you have a test Environment, I would try SR13 on that.

Anonymous
Not applicable
Author

This behaviour is a confirmed bug. It is the connect/reload-process (QVConnect64.exe in my case)  that locks the qwv-file on the publisher.

There is a patch for SR12 ( (11.20\SR12-1\12929(29))) but according to Qlik no plans, as of yet, to include it in a SR.