Qlik Community

QlikView Publisher

Discussion Board for collaboration on QlikView Publisher.

Announcements

Breathe easy -- you now have more time to plan your next steps with Qlik!
QlikView 11.2 Extended Support is now valid through December 31, 2020. Click here for more information.

ianscott
Not applicable

A user no longer to access document, qlikview server

Hi,

On Qlikview server we published a document to a specific user. It was working fine until yesterday but now whenever they try to open that document they get an error message:

"Failed to open document. You don't have access to this document."

As far as we can see this user has the same access level as the other users but the rest are having no issues with that document.

When the problem first arose the document was being published to selected users, after this we tried to publish is to all users to see if that would

solve the issue but it hasn't.

We are using QlikView 11 SR8, QlikView server and publisher. We are not using section access.


Any ideas of what might be happening would be much appreciated,


Ian



1 Solution

Accepted Solutions
ianscott
Not applicable

Re: A user no longer to access document, qlikview server

This was solved using the following method

1. Go to Document properties>Opening

2. tick - 'Initial Data Reduction Based on Section Access' to allow next step

3. untick - Strict Exclusion

4. untick - 'Initial Data Reduction Based on Section Access' that you ticked in step 2.

5. Reload and save.

We had tried step 1-4 but just saved it and then reloaded using the management console task and it didn't work so be sure to reload in the document.

1 Reply
ianscott
Not applicable

Re: A user no longer to access document, qlikview server

This was solved using the following method

1. Go to Document properties>Opening

2. tick - 'Initial Data Reduction Based on Section Access' to allow next step

3. untick - Strict Exclusion

4. untick - 'Initial Data Reduction Based on Section Access' that you ticked in step 2.

5. Reload and save.

We had tried step 1-4 but just saved it and then reloaded using the management console task and it didn't work so be sure to reload in the document.