Qlikview Server Reload Failes

[#1]

The Qlikview Server has been running a reload successfully for months, however, it has now suddenly stopped working, it is supposed to run every 30 minutes, it will run successfully maybe once a day.

I can run the reload manually and this works without fail.

Does anyone know what the issue is from the log below?

(2016-01-12 07:26:31) Information: Starting task 'AccessPoint/Lima Fleet Database.qvw'. Id:66028217-05df-4a9b-9092-93d9cd5ab2f0. Triggered by 'ManualStartTrigger'. Id:00000001-0002-0003-0405-0607080a0b0c

(2016-01-12 07:26:31) Information: Entering Task Execution.

(2016-01-12 07:26:31) Information: ClusterID=1

(2016-01-12 07:26:31) Information: QDSID=cfc67562-6e77-9033-a9eb-424d0d9dea30

(2016-01-12 07:26:31) Information: TaskID=66028217-05df-4a9b-9092-93d9cd5ab2f0

(2016-01-12 07:26:31) Information: MaxRunTime=06:00:00

(2016-01-12 07:26:31) Information: MachineName=LIMAQV1

(2016-01-12 07:26:31) Information: Max attempts:1

(2016-01-12 07:26:31) Information: Current Attempt=0

(2016-01-12 07:26:31) Information: Task Dependencies are OK

(2016-01-12 07:26:31) Information: Document is marked to be Reloaded with fresh data. Initializing Reload for Distribution.

(2016-01-12 07:26:31) Information: Opening "E:\QlikViewDocuments\Accesspoint\Lima Fleet Database.qvw"

(2016-01-12 07:26:31) Information: Allocating new QlikView Engine. Current usage count=0 of 2 (of type non-reader).

(2016-01-12 07:26:31) Information: Max retries:5

(2016-01-12 07:26:31) Information: Attempt:01

(2016-01-12 07:26:32) Information: Opened the QlikView Engine successfully. ProcessID=2840

(2016-01-12 07:26:32) Information: Allocated QlikView Engine successfully. Current usage count=1 of 2 (of type non-reader). Ticket number=1.

(2016-01-12 07:26:32) Information: Loading document "E:\QlikViewDocuments\Accesspoint\Lima Fleet Database.qvw" (1.36 Mb)

(2016-01-12 07:26:33) Information: Loading. LoadTime=00:00:00.9997709

(2016-01-12 07:26:35) Information: Loading. LoadTime=00:00:02.9993149

(2016-01-12 07:26:39) Information: Loading. LoadTime=00:00:06.9984035

(2016-01-12 07:26:40) Information: Physical FileSize=1.36 Mb. Memory Allocation Delta for this file=22.57 Mb. Available Physical Memory Before Open=14758.91 Mb. Available Physical Memory After Open=14723.12 Mb. Total Physical Memory=16338.53 Mb.

(2016-01-12 07:26:40) Information: Attempted to load the document without data.

(2016-01-12 07:26:40) Information: The document was loaded successfully.

(2016-01-12 07:26:40) Information: Document was opened successfully

(2016-01-12 07:26:40) Information: Starting reload

(2016-01-12 07:26:40) Information: QlikView->Settings->Document Peferences->Generate Logfile in document is set. Enabling Log Copier.

(2016-01-12 07:26:40) Information: Waiting for the document log "E:\QlikViewDocuments\Accesspoint\Lima Fleet Database.qvw" to become available.. Check until 12/01/2016 07:27:10

(2016-01-12 07:26:40) Information: The Source Document is being reloaded. DocumentPath=E:\QlikViewDocuments\Accesspoint\Lima Fleet Database.qvw

(2016-01-12 07:26:40) Information: Found a document log. FileName=E:\QlikViewDocuments\Accesspoint\Lima Fleet Database.qvw.log

(2016-01-12 07:26:40) Information: Writing documentLog to C:\ProgramData\QlikTech\DistributionService\1\Log\20160112\072628 - AccessPoint_Lima Fleet Database.qvw\DocumentLog.txt

(2016-01-12 07:26:41) Information: Reloading.

(2016-01-12 07:26:42) Information: Reloading..

(2016-01-12 07:26:43) Information: Reloading...

(2016-01-12 07:26:44) Information: Reloading....

(2016-01-12 07:26:45) Information: Reloading.....

(2016-01-12 07:26:46) Information: Reloading......

(2016-01-12 07:26:47) Information: Reloading.......

(2016-01-12 07:26:48) Information: Reloading........

(2016-01-12 07:26:49) Information: Reloading.........

(2016-01-12 07:26:50) Information: Reloading..........

(2016-01-12 07:26:51) Information: Slow down logging. Log every <2> seconds.

(2016-01-12 07:26:51) Information: Reloading

(2016-01-12 07:26:53) Information: Reloading.

(2016-01-12 07:26:55) Information: Reloading..

(2016-01-12 07:26:57) Information: Reloading...

(2016-01-12 07:26:59) Information: Reloading....

(2016-01-12 07:27:00) Information: The Source Document reload complete. DocumentPath=E:\QlikViewDocuments\Accesspoint\Lima Fleet Database.qvw

(2016-01-12 07:27:00) Information: Memory Allocation Delta for this file=7.97 Mb. Available Physical Memory Before Reload=14723.21 Mb. Available Physical Memory After Reload=14739.29 Mb. Total Physical Memory=14739.29 Mb.

(2016-01-12 07:27:01) Error: The Source Document was NOT reloaded successfully. DocumentPath=E:\QlikViewDocuments\Accesspoint\Lima Fleet Database.qvw.

(2016-01-12 07:27:01) Information: Closing the document.

(2016-01-12 07:27:01) Information: Closed the QlikView Engine successfully. ProcessID=2840

(2016-01-12 07:27:02) Error: The task "AccessPoint/Lima Fleet Database.qvw" failed. Exception: || QDSMain.Exceptions.TaskFailedException: Task execution failed with errors to follow. ---> QDSMain.Exceptions.ReloadFailedException: Reload failed ---> QDSMain.Exceptions.LogBucketErrorException: The Source Document was NOT reloaded successfully. DocumentPath=E:\QlikViewDocuments\Accesspoint\Lima Fleet Database.qvw. || at QDSMain.ReloadTask.VerifyConditions(TaskResult taskResult) || at QDSMain.ReloadTask.Reload(String fileName, TaskResult taskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage) || --- End of inner exception stack trace --- || at QDSMain.ReloadTask.Reload(String fileName, TaskResult taskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage) || 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-12 07:27:02) Information: Task Execute Duration=00:00:30.5867753

(2016-01-12 07:27:02) Information: TaskResult.status=Finished

(2016-01-12 07:27:02) Information: Notifying all triggers of new state:FinishedWithErrors

(2016-01-12 07:27:02) Information: Notifying all triggers of new state:FinishedWithErrors - completed

(2016-01-12 07:27:02) Information: Saving Task Result

[manojkulkarni · Accepted solution]

This issue might be coming from network or database connectivity. if you could find log details in eventlogger, then you will be in better position to assess the issue.

[#3]

Thank you! There is an ODBC Read fail there, strange why it does it on the Server reload and not my reload though

[manojkulkarni]

Great.. If you don't find exact issue with QV log, always try to look at EventViewer. This will give more information

[#5]

Do you know why it would run successfully when I run but fail when server runs the script?

This is the eventlogger -

12/01/2016 10:00:06: 0200  from pty_party

12/01/2016 10:00:08:       30 fields found: pty_id, pty_pty_id_parent, pty_name, pty_desc, pty_address_1, pty_address_2, pty_address_3, pty_town_city, pty_region, pty_postal_code, pty_cty_iso2, pty_telephone_primary, pty_telephone_secondary, pty_telephone_tertiary, pty_email, pty_web_access, pty_webid, pty_email_valid, pty_last_login, pty_notes, pty_fca_ref, pty_third_party_ref, pty_vat_no, pty_signiture, pty_initials, pty_created, pty_created_by, pty_modified, pty_modified_by, pty_ts,

12/01/2016 10:00:08:       QVX_UNEXPECTED_END_OF_DATA: SQL##f - SqlState: S1000, ErrorCode: 0, ErrorMsg: [Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream

12/01/2016 10:00:08:       Error: ODBC read failed

12/01/2016 10:00:08:       General Script Error

12/01/2016 10:00:08:       Execution Failed

12/01/2016 10:00:08:      Execution finished.

[manojkulkarni]

Do you run it manually in Server or is it from your Desktop ?

[#7]

If I run from desktop is works, if I click the play button from the Reload Engine or it hits the scheduled time to run, it fails.