You won't need the Excel file path, unless the server needs to reload your document.
How do you publish this document? Do you do a QDS reload before the document is shown in the AP? Which by the ways is always a good idea...
And highly useful: "they can't open..." doesn't mean much. I cannot open your document either, but that's probably because of the geography. Does the document appear in the Access Point? If so, what kind of message do they get when they click the thumbnail?
I don't know it it's the same, but in my first post I said that we use the Publish Server to deploy our applications, but instead we use the "QlikView Management Console" (QMS). Is it the same thing?
The publish procedure is as follow:
- In the QMS we specified what are the folders to load QVW files;
- Non of these QVW files are schedule or set to reload;
- In a specific time of month, production team reload all the QVWs files;
- Automatically the QMS publish the new version.
After the client logged in the portal, he can see all the correspondent applications. Then they open the application and try to access throw their second login (Section Access). Is in this step that the user can't open the document. There's no error message, only say that the user don't have access.
Thanks in advanced,
QlikView Server is composed of a number of services (always the same number). All of those services are managed and configured using the QlikView Management Console (QMC). The Management Console is a web page displayed by the Management Service (QMS). The Management Service stores whatever you do in the Management Console in configuration files for the Distribution Service (QDS aka the "Publisher"), the Directory Service (DSC), the Web Service (QVWS) and last-but-not-least the QlikView Service (QVS).
To answer your question: the Publisher or Distribution Service is a program acting like a black box (ie no user interface). The only way you can tell the Publisher to do something is through the QMC (or via the Manegement API).
Publishers exist in editions too. If you do not have a Publisher license, then you are running the Publisher in a very simple way: the QMC becomes very clean: only a Reload tab is added to your documents. If you do have a Publisher license, then the QMC has Source and User Documents tabs and allows you to configure very complex tasks and publication mechanisms. I understand that you do have a Publisher license.
Anyway, I do not think this is the cause of your problems. A hunch tells me that you may have trouble with your Section Access fields and conflicts between the different authentication mechanisms. Just to make sure: does your Section Access data contain values for both NTNAME (AD authentication) and USERID/PASSWORD (Ad-hoc document security) in every row? Or do these fields on occasion contain * characters?
Can you post a sample of the content of your Section Access source data?
The content of the Excel file that is load via Excel file is:
ACCESS NTNAME USERID PASSWORD LEVEL1_SA LEVEL2_SA LEVEL3_SA
ADMIN * user1 pass1 * * *
USER * user2 pass2 * * *
ADMIN Domain\companyName * * *
In the meanwhile, I've a hunch that might resolve my issue. Instead of reload the QVW file in my local PC and then copy it to the Publisher Server, I'll reload the QVW file in the Publish Server and place it on the correct folder. Do you think this might solve my problem?
Thanks in advanced,
Of course that's a good idea (see my first post, 2nd sentence). Although NTNAME values are stored as plain text, and AFAIK problems only arise with reloads with AD accounts in your SA table outside of the QlikView Server domain, I am convinced that QlikView often runs into trouble when SA tables are reloaded somewhere else.
If the publisher is allowed to reload all your document data, you can be sure that the contents is consistent with the environment and the implicit domain connections. So go ahead and try it - at least once.
Remember that in order to reload your document, the Publisher must have access to your document. So you may have to provide a document in which Section Access instructions are present but not active yet.