Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
We have server and publisher installed on 2 of our servers. One is QA the other is production. The Production one is fine, however on the QA one when I goto the Documents > Source Documents and expand the tree, the system does not show me folders & files within.
I had a "space" in the folder name. Removing the space resolved it.
I have a similar scenario, except Publisher is only on the QA server, and I see a similar issue.
Are distributing the documents to a central storage area?
If you have a publisher controlling centrally stored documents, I think the second server acknowledges the presence on the first and relinquishes control.
B
I'm not sure that two Publisher servers are aware of each other or their Source Documents locations unless they're set up in a cluster.
In order for QMS to be able to display the Source Documents tree from QEMC, it has to be able to reach the folder location. If it's a local drive, there should be no issue. If it's a UNC path to a shared folder, there could be network configuration or security issues between the Publisher server and the UNC path. For example, Source Documents is on another server and the service account that Publisher runs under does not have authorization to read from the UNC share.
Our source documents folder is on a SAN storage. We do not have any clustered setup, its a simple 1:1 setup. The same setup on Prod works fine.
The server services are run using a n/w service account. This account has full access to all the qlikview folders & files. The user documents are stored on the same SAN and the server reads it successfully without any issue.
I had a "space" in the folder name. Removing the space resolved it.
We have the same problem using network share from a NAS. When using the direct adress instead of the mounted volume letter we can sometimes see the files and sometimes not. It is very random. So we think the server has the permission to access the NAS. Could this be a bug or is there some solution to our problem of using a NAS for the "SourceDocuments" ?