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: 
stabben23
Partner - Master
Partner - Master

Files get corrupt when save to disc

Hi,

This problem has bother me for over 1 year now. We having problem when files is distribute to the fileserver. The files gets corrupt almost every day, not all just one or two. Its not the same files, but most frequent is the big sized files. Whats happens is that the file dont save the whole file to the disc, around 50-95% of the filesize is saved and then the file is corrupt and cant be opened.

I'll think this is some network issue and not a qlikview problem. Because the Publisher server and the fileserver is not on the same machine.

Here is the last part of the logfile:

(2015-04-23 10:24:57) Information: Reload finished successfully

(2015-04-23 10:24:57) Information: Start saving document

(2015-04-23 10:25:12) Information: Check in document: \\servername\Qlikview\QVData\Private\Production\Public_PROD.qvw

(2015-04-23 10:25:12) Information: Closing the document.

(2015-04-23 10:25:13) Information: Closed the QlikView Engine successfully. ProcessID=30256

(2015-04-23 10:25:13) Information: Start document distribution.

(2015-04-23 10:25:13) Information: Opening source document

(2015-04-23 10:25:13) Information: Opening document: "Public_PROD.qvw"

(2015-04-23 10:25:13) Information: Allocating new QlikView Engine. Current usage count=5 of 8 (of type non-reader).

(2015-04-23 10:25:13) Information: Max retries:5

(2015-04-23 10:25:13) Information: Attempt:01

(2015-04-23 10:25:13) Information: Opened the QlikView Engine successfully. ProcessID=38424

(2015-04-23 10:25:13) Information: Allocated QlikView Engine successfully. Current usage count=6 of 8 (of type non-reader). Ticket number=478.

(2015-04-23 10:25:13) Information: Loading document "\\servername\Qlikview\QVData\Private\Production\Public_PROD.qvw" (37.88 Mb)

(2015-04-23 10:25:14) Information: Loading. LoadTime=00:00:01.0000512

(2015-04-23 10:25:16) Information: Loading. LoadTime=00:00:03.0001536

(2015-04-23 10:25:17) Error: Document open call failed. The document might require username and password.

(2015-04-23 10:25:17) Information: Attempted to load the document with data.

(2015-04-23 10:25:17) Error: The document failed to open.

(2015-04-23 10:25:18) Information: Closed the QlikView Engine successfully. ProcessID=38424

(2015-04-23 10:25:18) Error: Document could not be opened

(2015-04-23 10:25:18) Information: Closed the QlikView Engine successfully. ProcessID=38424

(2015-04-23 10:25:18) Information: Document distribution done.

(2015-04-23 10:25:18) Error: The task "Reload and Distribute of Public_PROD.qvw" failed. Exception:

(2015-04-23 10:25:18) Error: QDSMain.Exceptions.DistributionFailedException: Distribute failed with errors to follow. ---> QDSMain.Exceptions.FailedDocumentCheckoutException: Failed to open document: \\servername\Qlikview\QVData\Private\Production\Public_PROD.qvw

(2015-04-23 10:25:18) Error:    at QDSMain.DistributeTask.OpenDocument(TaskResult taskResult, String fileName)

(2015-04-23 10:25:18) Error:    at QDSMain.DistributeTask.Distribution(String fileName, DistributionRequest distributionRequest, TaskResult taskResult, String repeatVariableName, String currentRepeatVariableValue)

(2015-04-23 10:25:18) Error:    at QDSMain.DistributeTask.Execute(TaskResult currentTaskResult)

(2015-04-23 10:25:18) Error:    --- End of inner exception stack trace ---

(2015-04-23 10:25:18) Error:    at QDSMain.DistributeTask.Execute(TaskResult currentTaskResult)

(2015-04-23 10:25:18) Error:    at QDSMain.Task.AbstractTask.TaskExecution(ILogBucket logBucket, TaskResult taskResult)

(2015-04-23 10:25:18) Information: Task Execute Duration=00:05:13.7973156

1 Solution

Accepted Solutions
Bill_Britt
Former Employee
Former Employee

Hi,

The post about the NAS is correct in that it isn't supported. However, to see if that is the issue, move your root folder back to the local machine and see if your still have the issue.

Bill

Bill - Principal Technical Support Engineer at Qlik
To help users find verified answers, please don't forget to use the "Accept as Solution" button on any posts that helped you resolve your problem or question.

View solution in original post

15 Replies
stabben23
Partner - Master
Partner - Master
Author

Hi,

we have our fileshare on a Windows based NAS, could this be the problem? The QVS and Publisher is on separated servers.

marcus_sommer

It sounds that the network or the file-system caused these errors. I think you will need to look into the log-files from qv server/publisher and from the windows OS. Maybe there isn't enough cpu/ram-ressources at any time and/or some services like windows shadow copy or firewall/anti-virus are involved. Another reason could be corrupted hardware by ram or disk.

- Marcus

Anonymous
Not applicable

I have a feeling that QlikView does not formally support NAS.

stabben23
Partner - Master
Partner - Master
Author

Yes, Thats what I have read here on the community, but the "experts" does not agree with each other in this question.

Peter_Cammaert
Partner - Champion III
Partner - Champion III

What happens when you manually copy a very big file from the Publisher machine to the (NAS) File Server? Does the network experience hickups?

Peter_Cammaert
Partner - Champion III
Partner - Champion III

Is it just me, or does the log file you posted in reality document a reload failure due to a missing service account from the Section Access table?

Anonymous
Not applicable

I have too often seen NAS set up badly and causing problems.  Not have having a TOE (TCP/IP offload Engine) enabled NIC can have bad consequences.

stabben23
Partner - Master
Partner - Master
Author

Hi Peter, that is the test we have done, unfortunately is this test ok, we have only test a few times.

stabben23
Partner - Master
Partner - Master
Author

There is no Section Access on the document. I can see Section Access in almost all logfiles when somethings goes wrong.