Qlikview 8.5 failed to load because of no file access

[Anonymous]

Hello, maybe somebody can help us.

We work with an old version of Qlikview (8.5).

Some passwords are reset and now several guys cannot access their QV-documents anymore

And because our application manager left the company nobody knows how to manage this.

Tips are welcome.

Thx. in advance

[avkeep01]

Hi Gert,

Is this a section access issue? I mean are the passwords set in Qlikview itself?

If you aren't using section access you've multiple options which you can try:

- open without data (right mouse button on app in the recent files in qlikview)

- binary load of the application

- recovery, that is an hidden option which you can find under help > about qlikview and then qlik on the qlikview logo in the bottom. More information here;

Recovering Corrupt Document

with kind regards, Anton

[Anonymous]

Hello Anton, thx. for your fast reply.

The issue is not that the documents are not accessible.

Because some users still can access them and others not.

They all try to open the documents with 'Open in server' and then give in a server-name and use their NT-indentity.

Some users see the QV-documents and can open them

Some users see the QV-documents and cannot open them but the error comes failed to load etc...

THe issue is where can we authorise this?

Thx. in advance

[Gysbert_Wassenaar]

Did the same users have access to the documents before?

[avkeep01]

Hi Gert,

Did you check the access rights in the Qlikview Management console? Maybe the users who cannot open the application don't have a document cal or named user cal. Opening the application with "open in server" is the basically the same as opening the application via the accesspoint.

In the management console you need to go to

- for named users: System > Licenses > server > assigned cal's

- for document users:

- if small business server: Documents > select the document > document cal's

- if enterpise server: documents > user documents > select the document > document cal's

[Anonymous]

Yes, correct