topic Re: majority of users are not able to log into Access point in QlikView

majority of users are not able to log into Access point

MuizNaseem — Mon, 26 Jan 2026 18:19:17 GMT

Hi There,

I would like to know if QlikView requires any specific right or permission on Windows 2016 operating system. We are facing any issue where the user is NOT able to access the application through Access Point.

Regards

Muiz

Re: majority of users are not able to log into Access point

Albert_Candelario — Thu, 11 Jul 2019 13:09:29 GMT

Hi Muiz,
Are the users able to open the access point? or is the issue that the access point is empty for them?
Are you using DMS or NTFS ?
Cheers!

Re: majority of users are not able to log into Access point

abdul_qadir — Fri, 12 Jul 2019 04:59:30 GMT

Hi Albert,

The users are able to access from the open server but NOT from the access point and we are using NTFS ...

Looking for help because this is production level issue

Re: majority of users are not able to log into Access point

Albert_Candelario — Fri, 12 Jul 2019 08:24:43 GMT

Hi,

Has this ever worked? Did you provide Windows access to the mounted folder to the users?

See:

Authorization (What are you allowed to see?

What are you allowed to do?)

Once a user has been authenticated (i.e. the system knows who they are), the first step in

assigning their security privileges has been completed. The second step is to understand

what authority or rights they have to applications, data or both. This step is called

Authorization. At a fundamental level, an administrator will populate an Access Control

List (ACL) with a list of users and/or groups and what they should have access to. When

the time comes for a user to request access, the system looks up the user’s authenticated

identity in the ACL and verifies if the administrator has granted the user enough privileges

to do that.

Direct access to the QlikView Document using QlikView Desktop is always governed by

Windows NTFS File Security. Access to the web-based QlikView Enterprise Management

Console is restricted to Windows Users who are a member of a particular local Windows

Group.

DOCUMENT-LEVEL AUTHORIZATION

Once a user has been authenticated, the QVS typically handles authorization on its own. The

QVS offers the choice between storing the ACL information as Windows NTFS privileges

(applicable only when the user authenticated using a Windows user identity) or by storing

the ACL information in QlikView’s own internal repository (called DMS or Document

Metadata Service). The choice of NTFS or DMS affects access to all documents on the

QVS.

NTFS VS DMS

The QVS can use the Windows file system’s own NTFS privileges to store authorization

information. When in NTFS authorization mode, the QVS controls access to a given QlikView

document by determining if the authenticated user has NTFS privileges to the underlying

QlikView Document file (.QVW file). This is based on the operating system privileges and

Windows NTFS is used for the ACL. The privileges of the authenticated user are configured

by a server admin using standard Windows Explorer functionality via directory properties

options.

As an alternative to Windows NTFS, QlikView can use its own ACL called the Document

Metadata Service (DMS). Unlike NTFS, this allows non-windows users and groups to be

authorized to access applications and data. DMS integrates fully with the existing Directory

Service Provider (e.g. Active Directory, other LDAP) where Group Membership has been

recorded, this is a mechanism by which the QVS can re-use existing enterprise account and

group structures. The permitted Users or Groups are recorded in a meta file that resides

beside the QlikView Document, and is managed using the QlikView Enterprise Management

Console.

NTFS is the default document authorisation model, and suitable when all users and groups

are identified in Active Directory or locally on the QVS host. The NTFS permissions may be

inherited from the directory that the QlikView documents are in, or may be assigned using

QlikView Publisher distribution tasks.

DMS is required if the authenticated user identity is not a Windows User Account. The DMS

permissions are explicitly assigned using the QlikView Enterprise Management Console, or

may be assigned using QlikView Publisher distribution tasks.

https://community.qlik.com/t5/New-to-QlikView/WHat-is-NTFS-and-DMS-Difference/td-p/650839

Cheers!

Re: majority of users are not able to log into Access point

MuizNaseem — Fri, 12 Jul 2019 09:25:29 GMT

Hi Albert,

Thanks for the reply but the issue is that users who are initialized in the Licenses tab cannot log in to the Access point, they can access the page. However they are able to lease licenses. I have looked into the Qlik Logs and they seem to return this error for every user which is initialized in the License tab. In addition the active directory is also working fine because it's searching the user which are available.

warning system : meta service - has access : Empty user has found

I hope you understand that we haven't reached the document level authentication yet for the access point.

Regards

Muiz

Re: majority of users are not able to log into Access point

Albert_Candelario — Fri, 12 Jul 2019 14:48:11 GMT

Hi,

could you attach a screenshot of what the users are seeing in the access point? Is there shown any No Server message?

As I asked before, has this ever worked?

Thanks!

Re: majority of users are not able to log into Access point

MuizNaseem — Mon, 15 Jul 2019 06:40:52 GMT

Albert this is a fresh Installation so this issue is appearing for the first time, I have attached a screenshot of what is appearing on my access point screen, it doesn't gives me an error it just gives a blank screen after inputting the username & password Regards

Re: majority of users are not able to log into Access point

Albert_Candelario — Mon, 15 Jul 2019 11:44:26 GMT

Hi,

Thanks for the pictures, so I understand the users add the user and password and it becomes blank again. In this case, it could be an issue with the authentication. What kind of authentication are you using?

Did you also check the Windows logs, applications, security and system?

I hope we, the Community, can help to solve your issue 💪

Re: majority of users are not able to log into Access point

MuizNaseem — Tue, 16 Jul 2019 06:16:04 GMT

I also though of that but when i am leasing licenses to QlikView Desktop with this user its leasing it. Authentication type is NTFS. After checking the windows logs i found the error for the users stating. I have searched the internet for this particular issue but nothing that i could find. I hope so. Thanks for the continuous help

warning system : meta service - has access : Empty user has found

Re: majority of users are not able to log into Access point

Albert_Candelario — Tue, 16 Jul 2019 20:50:29 GMT

Hi,

I guess you mean you use for the authorization the NTFS and for the authentication the NTLM, right?

Are you using IIS or QVWS?

Are you seeing in the windows security logs any failure on the login?

Is the error just - warning system : meta service - has access : Empty user has found or is there something else at the end.

Thanks to you for sharing this with us!

Re: majority of users are not able to log into Access point

MuizNaseem — Wed, 17 Jul 2019 11:22:08 GMT

Hi Albert,

Firstly thank you for your continuous support

Yes for authentication i am using NTLM (screenshot is attached)

and using QVWS

20190715T073104.588+0100 Information Login: euro\sxhams failed.
20190715T073104.589+0100 Error Request failed: This operation cannot be performed after the response has been submitted.

this is the main error after this starts into normal information transfer such as this.

20190715T073104.590+0100 Information Request received [GET]: http://localhost/qlikview/FormLogin.htm
20190715T073104.593+0100 Information Request received [GET]: http://localhost/qlikview/global.css
20190715T073104.593+0100 Information Request received [GET]: http://localhost/qlikview/custom.css
20190715T073104.594+0100 Information Request received [GET]: http://localhost/qlikview/images/logo_main.png
20190715T073104.595+0100 Information Request received [GET]: http://localhost/qlikview/js/jquery.min.js
20190715T073104.595+0100 Information Request received [GET]: http://localhost/qlikview/js/login.js
20190715T073104.596+0100 Information Request received [GET]: http://localhost/qlikview/js/accessPoint.js
20190715T073104.621+0100 Information Request received [GET]: http://localhost/qlikview/images/bg_login.png
20190715T073104.621+0100 Information Request received [GET]: http://localhost/qlikview/images/bg_body.png
20190715T073104.628+0100 Information Request received [GET]: http://localhost/QvAjaxZfc/htc/Images/favicon.ico
20190715T073104.634+0100 Information Request received [GET]: http://localhost/qlikview/lang/en-US/accesspoint.json

Re: majority of users are not able to log into Access point

Albert_Candelario — Wed, 17 Jul 2019 15:11:57 GMT

Hi,

As the authentication is handled by Windows and not QlikView I would advise contacting your AD team too in order to check if they can help you on this.

Are you seeing any error like: "user has not been granted the requested logon type at this machine"?

Regards!

Re: majority of users are not able to log into Access point

Brett_Bleess — Tue, 06 Aug 2019 14:02:36 GMT

Muiz,

Were you able to get things resolved? If so, if you could leave a post with with what the issue was and what you did to address it, it might help others in the future, and once you post that, you can then click the Accept as Solution button on that post as well noting that it did solve the issue.

You never answered which web server you were using, IIS or the QV Web Server? I suspect IIS, and I expect you have something misconfigured there, as using Forms Login option, IIS security should be set to Anonymous, but the QlikView IIS Application Pool would definitely need to be set to run under the QlikView service account at that point to ensure things work properly, and the service account would need to be a Local Administrator as well.

Probably the best tool to get a better idea of what is happening would be web browser Developer Tools and network trace there, or potentially Fiddler HTTP trace tool, that should likely provide better information as to what is going on with the client/server communications and where things may be going wrong.

Regards,
Brett