Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

AD Group show proper access to QVW, but access is denied in Access Point

We have a QVW which we have created a task for.  In the task we are distributing based on Named users and add our Active Directory group Qlikview_QDash.  We are running QlikView server in NTFS mode just as note.  When we run the task, I can check out the properties of the file and see that our group was added, with full control.  When I open up access point though, and open the QVW I get the message that access is denied.

So we changed it around a little bit, where we created a local group and then added the AD group into it.  We switched the task to now use the local group instead of the AD group.  What happens now is that users can access the app, but then come back later and not have access.  Seems to be very hit and miss on when a user can access the app.  We have verified that we have enough user cals and session cals, so that isn't the issue.

The real question here is, why would an AD group that has access to the app, still be denied access?

Any help would be beneficial.

Running on server 2008 R2 with Qlikview 11.2

Thanks

4 Replies
jpapador
Partner - Specialist
Partner - Specialist

is the user assigned a CAL (either a named or a document CAL)?  I know you said you have enough, but are they assigned to those users?

Not applicable
Author

The server is using Dynamic cal assignments, so from what I remember I should just get assigned a cal when I try to access the file.

jpapador
Partner - Specialist
Partner - Specialist

That is true, have you looked in Management console to actually confirm they were assigned a CAL dynamically?

gopalopsharma
Creator
Creator

Hello Jeremy,

We faced the similar issue few days back that the report was opening on application but not on Access point. It was throwing "Failed to Open" error.

Uncheck the "Strict exclusion" option in Document properties.

Give it a shot, it worked for us.