topic Re: Access Issues in QlikView

Access Issues

kevbrown — Wed, 25 Nov 2020 16:16:04 GMT

Hi,

I'm trying to deploy an app to a number of users but they're reciving the following error and can't access it -

"qlikview you do have permission to view this directory or page"

Why are my users receiving this and how can I stop it?

Thanks

Kev

Re: Access Issues

srchagas — Tue, 31 Oct 2017 09:50:48 GMT

there a 2 options:

1- You application have a Session acess? it's possible a Session Acess problem u must check if the name of the people in session it's correct try put corporate\Login_for_AD in session acess

2- They don't have acess by AD to see the aplication.

Re: Access Issues

kevbrown — Tue, 31 Oct 2017 09:51:52 GMT

Section access is being used.

AD?

Re: Access Issues

srchagas — Tue, 31 Oct 2017 09:54:40 GMT

Probably is session acess

Try put Withoutcaps lock in Session acess

Example: COMPANY_NAME\User_Active_diretory_Name

OBS: AD ( Active Directory)

Re: Access Issues

madhumitha — Tue, 31 Oct 2017 10:14:15 GMT

Hi Kevin,

Since the error message is about the Directory or Page, there is a high chance that the users dose not have access to the Active directory. Please check.

If the error msg reads "You do not have access to this document" then you can check the section access or the Document user access.

Thanks!

Re: Access Issues

stevedark — Tue, 31 Oct 2017 10:17:30 GMT

Hi Kevin,

Try putting an app without any section access in the same folder to ensure that the users can open that one successfully.

In this app add a text box to the main sheet with the code =OSUser() , this will show you the user name you need to have in section access. It may differ from what you expect.

Section access can be picky about the case of values it is matching and field names. Fields that you have in your section access table should all be upper case, this means the fields that match in the rest of the data-model must be also.

Be careful with * when matching in section access, this only matches other records explicitly referenced in the section access table, and not all values in the rest of the data.

Hope that helps.

Steve

Re: Access Issues

kevbrown — Tue, 31 Oct 2017 10:19:41 GMT

Thanks for your replies. I'm currently refreshing the document, it then has to be deployed by IT and hopefully then the User's will have access. I have noticed that when developing OSUSER() is in lower case but when deployed on the server it's UPPER CASE, not frustrating at all!! Would a "/" cause any problems?

Re: Access Issues

Miguel_Angel_Baeyens — Tue, 31 Oct 2017 10:21:39 GMT

Yes, "/" is not a valid character for accounts, and the separator between directory and username must be "\", unless the OSUser() function would return otherwise.

Re: Access Issues

kevbrown — Tue, 31 Oct 2017 10:22:55 GMT

Sorry I meant "\", my bad!

Re: Access Issues

stevedark — Tue, 31 Oct 2017 10:41:33 GMT

The \ is essential when giving AD names.

I've had strangeness around building a Section Access table within the section access part of the script. What I have found works consistently is building the table in a temporary table, doing a resident load into the section access and then dropping the temporary table.

I don't know how complex the load of your section access table is?

Re: Access Issues

Miguel_Angel_Baeyens — Tue, 31 Oct 2017 10:43:51 GMT

The username must be in uppercase as any other field name or field value in the section access table. If you are loading the section access table using an INLINE load you should not need to do it.