Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello Everyone,
I get error message "Failed to open document, You don't have access to this document" when i try to load the AJAX pages via IIS.
scenario:
I'm using QV9 on Windows2003 server, 32bit
Running as Admin directly on the server
I want to access my project via AJAX, using a nice short URL such as http:\\server\MYproject
I have used the Objects Client Page Generator to create the AJAX pages
Target folder is c:\myweb
Document URL points to qvp://localhost/MYproject.qvw
In IIS i have created a new website 'MYProject'
Selected the folder c:\myweb (note the ajax pages are within another folder called MYproject_ajax)
Left permissions as Read.
Done.
When i test the website by rightclick, browse, i get the error message.
Also when i navigate to http:\\localhost\MYproject i get the same error.
Does anyone have any suggestions as to what to try?
Thanks,
Peter.
Well, thanks for all help, but I can't get anonymous access to ajax zfx working no matter how I try, right now.
I was able to get it up and running, when I switched to
and followed the instructions in iPhone document access
So finally I see the ajax interface at least
Oh, I didn't realize you were using DMS before. It's still possible with DMS mode, but you need to make sure you add the anonymous account to the document's authorization tab. But I'm glad it's working for you if NTFS mode is acceptable!
Regards,
We're running into a similar type of issue with our QlikView 9.0 SR3 test upgrade. We have a pair of clustered QVS's running under DMS Authorization. The only way we can get the document to be served up is to set the Authorization on the User Document to <Anonymous>. If we enter a real DMS user name in the User Document Authorization Recipients list we get a 404 error when we try to pull the document up. Our URL looks like this pseudo-URL:
http://SERVERNAME/QvAJAXZfc/AccessPoint.aspx?open=&id=QVCluster%7CMOUNTEDFOLDERNAME/DOCNAME.qvw&client=Ajax&userid=AAABBBCCC111222333
If we add <Anonymous> back to the User Document's Authorization Recipients list, we are able to access the document again.
In case this is important, the DMS Users we are adding are not available to the Directory Service. They are local Windows accounts on a remote (non-QV) web server. Right now we are manually adding the user name to the document's DMS security via the QEMC. Eventually we'll convert the code we use in our 8.5 environment to populate this through the API.
Anybody run into an issue like this or have any ideas on what we might look at?
Thanks in advance.
Jim