Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
The latest QlikView I'm working on needs Section Access. Here it is:
section access;
load * inline
[ACCESS, NTNAME, USERID, PASSWORD, DEPT, XCOM
ADMIN, qserver01$, admin0, pw, Admin,
ADMIN, admin1, admin1, pw, Admin, 0
USER, user1, user1, pw, User, 1
USER, user2, user2, pw, User, 2
];
section application;
//Security_table:
load * inline
[ACCESS, USERID, PASSWORD, DEPT, XCOM
ADMIN, admin1, pw, Admin, 0
USER, user1, pw, User, 1
USER, user2, pw, User, 2
];
As per "QlikView Publisher 8.5 Tech Manual" and "Data protection and security in QlikView", I've added the NTNAME field and set a special account to the proper name, plus blanked out the value in the reduction field (XCOM).
All seems well, until we try to push it thru Publisher. then we get treated to wondrous errors like this:
4940515 2009-06-11 11:37:24 Normal Error The document failed to open.
4940529 2009-06-11 11:37:24 Normal Error Reload failed because the document could not be opened successfully. DocumentState=DocumentNotFound
Sooooooooooo, ?how do we open that document successfully in Publisher?
Is qserver01$ the user account that is currently running the QlikView Execution Service service?
/Karl
Yes, qserver01 is the name of the computer and the account name my manager told me to use.
Hi There,
The document not found message is completely misleading, and can appear for a number of reasons. I suspect the issue is that the QV document is expecting a user name and password, and publisher is not providing it. You need to set publisher to run with a specific user account, and use that account in the NTNAME for publisher.
This forum thread relates to this issue:
http://community.qlik.com/forums/t/15809.aspx
I also found that it is not entirely obvious how the security works with published documents, as the Admin account doesn't have access to all values when you leave the reduction field blank. That is discussed with examples in this forum thread:
http://community.qlik.com/forums/t/16717.aspx
I hope those posts provide you with all you need to get your document working.
Cheers,
Steve
Manager set up the server (I don't have admin rights, and have no way to run Execution Service from my remote session myself) and said that lettercase shouldn't matter. From that, I have to think that qserver01 in some incarnation is the name, and should be.
Thanks for the blog chains Steve. Good food for thought as we hack at this in the next couple of days.
Hi there,
Being able to see the server config will certainly be a help. I would expect that the name should have either a domain or machine name prefix, split with a backslash, eg. domainname\qserver01.
Cheers,
Steve