Skip to main content
Announcements
Qlik Connect 2025: 3 days of full immersion in data, analytics, and AI. May 13-15 | Orlando, FL: Learn More
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Server Reload : Data Protection option is not working !

Dear All,

I'm facing to a strange issue with our QlikView Server : 11.20.11922.0

A windows admin changed the service account of all QlikView services to a new one  ! Wonderful , because we used "section access" security 😉

=> so all our reloads failed !!

I changed the reload data options in the "Documents" tab of the QlikView management console; I checked the option "Section Acess" and added  my  domain user !

But this feature is not working, I have the following error

(2013-07-19 14:48:49) Error: The document failed to open. Bad Username and password is the most likely cause of this problem.

(2013-07-19 14:48:50) Information: Closed the QlikView Engine successfully. ProcessID=3756

(2013-07-19 14:48:50) Error: Document could not be opened

(2013-07-19 14:48:50) Information: Closed the QlikView Engine successfully. ProcessID=3756

(2013-07-19 14:48:50) Information: Failed to check in document: C:\QlikView Storage\Public Data\AccessPoint Documents\Billable\Unpublished Application\QVD_Billable.qvw

(2013-07-19 14:48:50) Error: The task "Billable/Unpublished Application/QVD_Billable.qvw" failed. Exception:

(2013-07-19 14:48:50) Error: QDSMain.Exceptions.DistributionFailedException: Distribute failed with errors to follow. ---> QDSMain.Exceptions.ReloadFailedException: Reload failed ---> QDSMain.Exceptions.FailedDocumentCheckoutException: Failed to check out document with path: C:\QlikView Storage\Public Data\AccessPoint Documents\Billable\Unpublished Application\QVD_Billable.qvw

(2013-07-19 14:48:50) Error:    at QDSMain.ReloadTask.Reload(String fileName, TaskResult taskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage)

(2013-07-19 14:48:50) Error:    --- End of inner exception stack trace ---

(2013-07-19 14:48:50) Error:    at QDSMain.ReloadTask.Reload(String fileName, TaskResult taskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage)

(2013-07-19 14:48:50) Error:    at QDSMain.DistributeTask.Execute(TaskResult currentTaskResult)

(2013-07-19 14:48:50) Error:    --- End of inner exception stack trace ---

(2013-07-19 14:48:50) Error:    at QDSMain.DistributeTask.Execute(TaskResult currentTaskResult)

(2013-07-19 14:48:50) Error:    at QDSMain.Task.AbstractTask.TaskExecution(ILogBucket logBucket, TaskResult taskResult)

rd.

Furthermore, I did not have any document logs, the option Generate Logfile was activated "QlikView->Settings->Document Peferences->Generate Logfile"

So to fix this issue, I open my QlivView application and add the new service account to my section acess and reload manualy the application.

I go back to the server and launch the reload task successfully with a document log file !!

So 2 questions :

    -> Why section access is not working : we can not overlap the QVS service account ?

    -> Why when I have an error ine QVS I do not have a document log, is it normale ?

thanks in advance for your help !

regards

Benoît

2 Replies
Bill_Britt
Former Employee
Former Employee

Hi,

If the document can't be open, then a log can't be generated. Until the document is open QV can't get the document properties.

I don't understand you quest "Why section access is not working : we can not overlap the QVS service account"

You said once you rename the service account in section access it was working.

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.
Not applicable
Author

Hi Bill

     thanks a lot for your quick reply !

     Ok about the document log : it's a normal behavior of the application.

     Effectively, I omit to say that after adding my new service account in my section access ine the QlikView application I looked the document log generated by QVS and I found that the reload was executed by the service account not by the one defined in the "Reload" tab option in the  QlikView management console :

19/07/2013 17:39:21:  ScriptWantsDbWrite        false
19/07/2013 17:39:21:  ScriptWantsExe            false
19/07/2013 17:39:21:  LogFile CodePage Used:    1200
19/07/2013 17:39:21:   Reload Executed By mydomain\newserviceaccount
19/07/2013 17:39:21:   Process Executing: QVB
19/07/2013 17:39:21:   Process ID: 4628

Normally I expect to find the user defined in "data options : section access"

But maybe I do a mistake!!

Regards

Benoît