Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi all
We have a development server using a QlikView test license.
I have created a mounted folder on the test Management Console (it is browsable) and setup the appropriate AD permissions on this folder.
When I move a .qvw in to this mounted folder it appears on the test AccessPoint and all users can see it. However, some users get the following error when they try to open the .qvw
This .qvw has section access and is reloaded in the live environment before being moved to the mounted folder on the test server.
The affected users do not get this error in the live environment.
Has anyone seen this before? Also, what is "QlikOcx"?
Thanks
The login you are using do not have the access to view the doc. Check managemnt console
We all have seen this message multiple times. It is displayed when one or more of the following conditions are true:
If you have a Publisher, there may be additional conditions or variations of the previous ones that deny access.
Peter
Hi Peter
I have narrowed it down to the third point in your list. More specifically 'Strict Exclusion' is checked in the problem .qvw
I have a workaround, which is to reload the document on the test server, but this adds time to the development process.
To reiterate, the affected users can access the report in the live environment, but it looks like there is a problem with section access when simply moving the .qvw to the test environment.
Does anyone know what is causing this and how to fix it?
Thanks
Good thing that you are using "strict exclusion" to secure your documents.
Whenever you push a document from development or production to your test server, do you cross domains? Section Access can cause trouble when it hasn't been refreshed on the machine where it is going to reside for end-users to be opened. I often have this problem when visiting customers where I put a finished document from my machine onto theirs without reloading.
Peter
Hi Peter
The Development and Production environments are on separate physical machines but they are in the same domain.
Thanks for the info, I will have to readjust my development process.
James