Qlik Community

QlikView Publisher

Discussion Board for collaboration on QlikView Publisher.

Announcements
QlikView Fans! We’d love to hear from you.
Share your QlikView feedback with the product team… Click here to participate in our 5-minute survey.
Rules, plus terms and conditions, can be found here.
Not applicable

Publisher mount folder

Hi,

I have a QlikView Cluster environment with 2 Qvs and 1 Qvd (Publisher)..

I have configured a Sharepoint folders and stored there the SourceDocumens and the Documents folder for the cluster.

The root folder for the Qvs is Documents while the data folder for the Publisher is SourceDocuments.

I have several tasks with the distribution task but the problem is that some task the document is correctly published in the Documents folder while for other task documents are published is a sub folder, called "Root folder", under the main Documents folder configured.

The Publisher automatically create the •Root folder" if it does not exist.

What I have ti check to correc this behavior?

I have manually modified all the XML files in the Publisher folders (the tasks folder) to set the "mount point" as empty.

In fact for some XML files it was set to "Root folder".

Initially everything works fine but after one day it began again to Publisher under the "root folder", and in fact I have that the XML files were modified again.

What i have ti check?

The Qlik version is 11 SR2

Thanks

8 Replies
Not applicable

Re: Publisher mount folder

Please test with re-naming your folder to something else then Root.

Not applicable

Re: Publisher mount folder

Hi,

also, I would check if QlikView cluster is properly configured. It seems that Publisher 'sees' two separate QlikView Servers instead of cluster.

regards

Re: Publisher mount folder

I ran acrosss this problem recently after making some manual changes to the QVPR. Never did figure out what my editing error was, but corrected the problem like this. For those tasks that were going to "Root Folder", in the task Distribute pane, the Mount dropdown showed an old incorrect mount name. I changed the dropdown to Root Folder and that corrected the problem.

-Rob

Not applicable

Re: Publisher mount folder

Hi,

the cluster is correctly setted. I have a cluster license and I have enabled two different QVS from the QEMC.

Not applicable

Re: Publisher mount folder

Hi,

in the QEMC I have setted the QVS Root Folder to a share like this "\\myserver\Document$".

Bith QVS work fine.

On the Distribution Service I have setted the path "\\myserver\SourceDocument$".

Distribution Service tasks are simply going to reload and publish their own document on the "Root Folder", which I expect matches the one I have defined as a Root Folder for the QVS ("\\myserver\Document$").

I have checked all task on the QEMC and each one have the "Root Folder" correctly specified as the mount.

But when I execute the task some go correctly on  "\\myserver\Document$" while other go to " "\\myserver\Document$\Root folder".

The Distribution Service automatically creates the "Root folder" if it doesn't exist ( I have even try to delete it, nothing has changed).

So I have check the XML file configuration in "Tasks" folder under the Distribution Service path on the file system.

I have verified that some files has setted "Root Folder" as mount, while other has setted "" as mount.

I changed everything to "" and for some hours everythig works fine, but the next day everything was changed again.

All tasks coming from a migration from QlikView 10 SR4, and now I'm working with the last update of QlikView 11 (not 11.2).

What I have to check again ?

It sounds really strange!

Thanks a lot

Re: Publisher mount folder

This is real similar to the problem I had -- I migrated from QV10Sr5 to QV11. For the distributions that are having problems, try deleting the distribution spec and then re-add it.

-Rob

Not applicable

Re: Publisher mount folder

Hi,

do you mean to recreate the distrubtion task from scratch ?

Re: Publisher mount folder

No. On the Distribution pane for the task, just delete the existing Server Distribution and then re-add it.

-Rob

Community Browser