Skip to main content
Announcements
NEW: Seamless Public Data Sharing with Qlik's New Anonymous Access Capability: TELL ME MORE!
cancel
Showing results for 
Search instead for 
Did you mean: 
ronbosley
Contributor II
Contributor II

User Account used for Folder type Data connections

All my scheduled QLIK tasks suddenly failing with access denied.  The data connection type is FOLDER.  The User ID and Password are blank when editing the connection.

If a User ID is blank, what is the AD account the applications uses to access network shares?  Is there a way in the log files to see what user name it is using?

 

Labels (1)
2 Solutions

Accepted Solutions
Chip_Matejowsky
Support
Support

Hi @ronbosley,

If issue occurred suddenly and was working previously, then issue is likely environmental. What has changed within the environment or domain?
What is the full build version of QlikView you're running (e.g. 12.60.20200)?

Can you share the task log of any of the failed tasks? By default, the task logs are stored in %ProgramData%\QlikTech\DistributionService\1\Log\DateOfTask\NameOfTask. If you have configured the QDS Application Data Folder in a different folder, you can check the location by looking in the QMC > System > Setup > Distribution Services > QDS@ > General tab.  

If the task log displays error The source document was NOT reloaded successfully, then you'll need to check the document log of the QVW file associated with the failed task.

The QlikView service account runs scheduled tasks through the QlikView Distribution Service (QDS) / Publisher. So check to see if this account has the correct permissions to the source.

 

Best Regards

 

Principal Technical Support Engineer with Qlik Support
Help users find answers! Don't forget to mark a solution that worked for you!

View solution in original post

Ray_Strother
Support
Support

Hello ,

It seem like you are using the Qlik Sense product.

1. If no account is specified , Qlik Sense will use the service account to connect to the data source.
2. Confirm if the service account has permissions to the folder and data files.
3. If not update the data connection with appropriate account.

View solution in original post

4 Replies
Lucas_Gatling
Support
Support

@ronbosley  Can you provide a screenshot of your folder distribution configuration in the QMC?

If the issue is solved please mark the answer with Accept as Solution.
Chip_Matejowsky
Support
Support

Hi @ronbosley,

If issue occurred suddenly and was working previously, then issue is likely environmental. What has changed within the environment or domain?
What is the full build version of QlikView you're running (e.g. 12.60.20200)?

Can you share the task log of any of the failed tasks? By default, the task logs are stored in %ProgramData%\QlikTech\DistributionService\1\Log\DateOfTask\NameOfTask. If you have configured the QDS Application Data Folder in a different folder, you can check the location by looking in the QMC > System > Setup > Distribution Services > QDS@ > General tab.  

If the task log displays error The source document was NOT reloaded successfully, then you'll need to check the document log of the QVW file associated with the failed task.

The QlikView service account runs scheduled tasks through the QlikView Distribution Service (QDS) / Publisher. So check to see if this account has the correct permissions to the source.

 

Best Regards

 

Principal Technical Support Engineer with Qlik Support
Help users find answers! Don't forget to mark a solution that worked for you!
Ray_Strother
Support
Support

Hello ,

It seem like you are using the Qlik Sense product.

1. If no account is specified , Qlik Sense will use the service account to connect to the data source.
2. Confirm if the service account has permissions to the folder and data files.
3. If not update the data connection with appropriate account.
ronbosley
Contributor II
Contributor II
Author

Thank you for your replys.   The issue was that the QLIK service account was removed from access to the file shares.  To address we had to re-apply access, then restart QLIK services.