Section Access Connectivity Issue

[#1]

Hi Community,

I have been facing a small problem on Section Access Connectivity.

I have applied Sheet level section access on a dashboard. The relevant users only see their relevant sheets on that dashboard with a login ID and password.

Whenever any user connects to the dashboard using his credentials, the dashboard disconnects after some time, the user has to reconnect by inputting the credentials again and same scenario happens after few minutes again.

Is there any proposed solution to this?

Thank you,

Usama Anwar

[henrikalmen]

It is probably a problem in your network, not in QlikView itself.

[markodonovan]

Hi Usama,

Is the problem is only happening with this one document ?

If so can you check the timeouts in the Settings - Document Properties - Server tab.?

Has the problem only recently started happening ?

Mark

http://techstuffybooks.com

[Peter_Cammaert]

You're sure that Windows User accounts and licenses are not being used at two different locations? Sessions disconnect immediately if someone else connects to a document in the AP using the same credentials.

Peter

[markodonovan]

Hi Usama,

Have a look at your latest events log in

\\YOURSERVER\c$\ProgramData\QlikTech\QlikViewServer

you should have an message about what is happening.

Also check out this post:

Client Side Error Logging: QlikView IE-Plugin

Thanks

Mark

http://techstuffybooks.com

[#6]

Hi,

Thank you for all the responses. I don't face this connectivity issue in any other Dashboard because other dashboard do not have section access enabled. It could not be a network issue since other dashboards are working fine and those documents do not disconnect.

In this specific Dashboard, each user who has a separate User ID and pass, so they do not use a single ID to log in and access different sheets.

Even if when I use my ADMIN credentials, it disconnects.

[henrikalmen]

What type of secction access authorization are you using? Is it username and password, or are you using NTNAME? I was assuming that you use NTNAME and that the problem has to do with QV server communicating with AD server, and that when the connection is broken the user has to login again and again to authorize themselves.

[#8]

I am using the one with username and password. I have increase the number of timeout seconds and concurrent sessions and testing it now.