Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
eiconsulting
Partner - Creator
Partner - Creator

Data Upload fails on server

Dear Qlik support, 

I would have some support from you in relation to some qlikview modules which perfectly run on the pc and find several issues on the BI server. one of this , which i read from the log, is that the module was successfully upload but it fails the saving process. 

what can be the reason why it fails during the saving phase ? could it depend from the cloud environment in which the BI Server is installed ? what action can we do to fix the issue conseidering the 95% of the remaining module on the same server, so on the same environment, work correctly ?

if you have some idea it can be very appreciated. 

 

thanks in advance, Emanuele

 

 

 

Federico Sason | Emanuele Briscolini
Labels (1)
1 Solution

Accepted Solutions
Albert_Candelario

Hello @eiconsulting ,

This is very unfortunate, there is no option to recover the hidden script if you cannot recall the password that is has been added.

Cheers,

Albert 

Please, remember to mark the thread as solved once getting the correct answer

View solution in original post

6 Replies
Jill_Masinde
Support
Support

@eiconsulting 

We need the reload log of the document to get more info of what it's doing when trying to save.

When reloading from the Server (QMC) Service Account is used to launch the reload and it may not have write permissions in the folder.  It could also be that when the script tries to store a qvd; the qvd is in another read/write operation or it's hanged in another process.

Kindly attach the logfile in which you are reading from; The document and Tasklog will be useful.

eiconsulting
Partner - Creator
Partner - Creator
Author

Hello Jill, 

thanks for your comment. tonight it completed correctly the data upload but in general, in the previous run if failed with these messages, thanks in advance for your comments: 

(28/07/2022 12:55:36) Information: The Source Document reload complete. DocumentPath=C:\QVS\Work\Modelli\0 - Smart BI\Officina sintesi.qvw

(28/07/2022 12:55:36) Information: Memory Allocation Delta for this file=384.77 Mb. Available Physical Memory Before Reload=11680.59 Mb. Available Physical Memory After Reload=10905.77 Mb.

(28/07/2022 12:55:37) Information: The Source Document was reloaded successfully.

(28/07/2022 12:55:37) Information: QlikView->Settings->Document Peferences->Generate Logfile in document is not set.

(28/07/2022 12:55:37) Information: Reload finished successfully

(28/07/2022 12:55:37) Information: Start saving document

(28/07/2022 12:55:37) Error: File is not ok. Target file was not saved.

(28/07/2022 12:55:37) Information: Closing the document.

(28/07/2022 12:55:38) Information: Closed the QlikView Engine successfully. ProcessID=69056

(28/07/2022 12:55:38) Error: The task "0 - Smart BI/Officina sintesi.qvw" failed. Exception: || QDSMain.Exceptions.TaskFailedException: Task execution failed with errors to follow. ---> QDSMain.Exceptions.ReloadFailedException: Reload failed ---> QDSMain.Exceptions.LogBucketErrorException: File is not ok. Target file was not saved. || in QDSMain.AbstractReloadTask.Reload(String fileName, IExecutingTaskResult executingTaskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage) || --- Fine della traccia dello stack dell'eccezione interna --- || in QDSMain.AbstractReloadTask.Reload(String fileName, IExecutingTaskResult executingTaskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage) || in QDSMain.DistributeTask.PerformExecute(IExecutingTaskResult executingTaskResult) || --- Fine della traccia dello stack dell'eccezione interna --- || in QDSMain.DistributeTask.PerformExecute(IExecutingTaskResult executingTaskResult) || in QDSMain.Task.AbstractTask.TaskExecution(CurrentExecutionArgs args)

(28/07/2022 12:55:38) Information: Task Execute Duration=00:36:55.4455629

(28/07/2022 12:55:38) Information: TaskResult.status=Finished

(28/07/2022 12:55:38) Information: Notifying all triggers of new state: "FinishedWithErrors"...

(28/07/2022 12:55:38) Information: Notifying all triggers of new state: "FinishedWithErrors" - Completed

 

 

Federico Sason | Emanuele Briscolini
eiconsulting
Partner - Creator
Partner - Creator
Author

another topic. we storically put some credentials on an hiden part of the script of our modules.. unfortunately team members changed and now we don't remember the credential for the hidden script included into our back end. 

is there any possibility to enter in this hidden part of our modules for example with other credential provided by you, so from qliktech ? this can help us to solve some inconsistency on the data upload.. 

Emanuele

Federico Sason | Emanuele Briscolini
Albert_Candelario

Hello @eiconsulting ,

This is very unfortunate, there is no option to recover the hidden script if you cannot recall the password that is has been added.

Cheers,

Albert 

Please, remember to mark the thread as solved once getting the correct answer
Albert_Candelario

Hello @eiconsulting ,

Regarding the original issue posted.

Is always failing to save the same qvw file or is random?

Are all the antivirus exclusions in place?

Cheers,

Albert

Please, remember to mark the thread as solved once getting the correct answer
marcus_sommer

Just a try: Copy the not hidden script into a new qvw and reload it. Possible errors to missing fields/tables/variables - which might be ignored with ERRORMODE - and/or the later differences within the data-model or the data may give valuable hints what might be happens within the hidden script.

Another approach could be to look for any per include-variables loaded qvs-scripts. They might be contain the entire hidden script and could be therefore removed and/or adjusted. If they are only partly in use they might be extended to grab the already loaded tables/fields/records and storing them external as qvd or doing everything else.

With it you may be able to re-create it or to find another ways to get a valid and stable solution. 

- Marcus