This is a very long one, but please bear with me! I feel like I am about to cry right now because things have gone from bad to worse to catastrophe!
We have been running QlikView version 8.2 for far, far too long and I am in the process of user acceptance testing on version 10. In our original scope of the project, we had intended to have a vendor do most of the installation with major revamps for security access changes and general cleanup of loading scripts, but due to significant budget cuts (the drawback of working for a non-profit), we have shortened the project to simply making it work with what we have today and everything done by an internal I.T. employee (me).
Old (Currently production) 8.2 server:
An "expert" from QlikTek was brought in for initial setup and configuration. An Access section in our load scripts within our dashboard referencing an external excel spreadsheet data source that QlikView is sucking data out of that contains department code number (for security access filtering), UserID and password (only specified for the QV system application user - all others are asterisk, asterisk), Access, NT Name, and a handful of other fields that are for human benefit when reading or modifying the file. it also appears in version 8.2 that there is a separate section on the load scripts where you can specify "use this file for access control" (I'm paraphrasing) that was also marked.
New 10.0 server:
I had reloaded the dashboard successfully logged in as myself (there is no license for QV desktop for our QV system application user, so I wasn't able to test this out there). It reloaded fine. When I migrated the dashboard to server, testing users were able to open and view it through the interface, but there didn't appear to be any security access filtering. When I finally got all of the supporting tasks set up in Publisher and tried to reload the dashboard there, it wouldn't reload and gave me an error message saying "Document open call failed. The document might require username and password.", so I went in and removed the access section of the script. At some point in there, I also went in to the security settings section in Enterprise Management Console and tired to set up some security (I don't know if this is important or not) by creating some empty section access tables. Removing the access section allowed publisher to run, but now users (including myself) are getting prompted for a username and password when they try to open the dashboard through the server and no existing domain NT logins (including our system application account) with or without a domain name seem to work for anyone (nor does just putting ** in). I've tried adding the names in to the access tables I created, but that didn't change anything.