Publisher publishes old version of qvw

[Anonymous]

Hi

For our QV Publisher and Server, both 11.2 SR3, we have folders:

• Source
• User

We also use QV Source Control with SubVersion.

This method of Publisher does not work:

• Change a qvw in DEV
  • Save
  • Check In Pending Changes into Source Control
  • Close the qvw
• Open the qvw in the Source Folder
  • Get Latest Changes from Source Control
  • [One can see that any changes appear in the Dashboard / Script]
  • Close the qvw
• In QMC run the task set up to reload & distribute the task
  • The date / time of the qvw in the User Folder gets updated
  • But the changes do not appear in the qvw in the User Folder
    • This is the crux of the problem

But it does work doing the same but adding one extra step :

• Change a qvw in DEV
  • Save
  • Check in Pending Change into Source Control
  • Close the qvw
• Open the qvw in the Source Folder with QV Desktop
  • Get Latest Changes from Source Control
  • [On see that any changes appear in the Dashboard / Script]
  • Reload the qvw manually in QV Desktop, save changes and close
  • Close the qvw
• In QMC run the task set up to reload & distribute the task
  • The date / time of the qvw in the User Folder gets updated
  • Now  the changes do not appear in the qvw in the User Folder

Can anybody shed any light in this ?

I found it hard to describe the symptoms, so please do ask for me to clarify anything if required.

Best Regards,     Bill

[Colin-Albert]

What is the path to your source folder, root folder, and users folder?

Are there other mounted folders?

The source and user folders MUST be different.

The reload task will reload the qvw from the source folder and write the updated file back to the source folder.

The distribute task distributes (copies) the file from source to user folders (as well as doing other actions such as reduce).

Colin

[Colin-Albert]

Have you tried restarting the QDS or QVS services? I have fixed strange reload behaviour by restarting QDS.

[Anonymous]

Colin

Many thanks for the prompt reply.

Source Folder Path is

• \\emea.menzies.net\BI\Data\QV.Prod\Apps.Source\STWT-2

The User Folder is

• \\emea.menzies.net\BI\Data\QV.Prod\Apps.User\STWT-2
• Mounted as Prod STWT-2

I.e The Source and User folders are different.

In total we have 17 Mounted User Folders, each with a corresponding Source Folder.

This issue happens across all folders.

Best Regards,     Bill

[Anonymous]

Colin

Yup, I have closed all the QV Services, inc. QDS & QVS,  and done full Windows level server reboot before restarting the QV Services. and the issue remained the same.

Best Regards,     Bill

[Colin-Albert]

Hi Bill

OK, so that rules out the bleeding obvious

Is it just the displayed timestamp on the Access Point thumbnail that is out-of date?

Does you app have a reload time visible and if so is this showing the old or new time when you open a the app after the reload runs?

Regards

Colin

[Anonymous]

Colin

No worries about the BLOB's [the Bleeding Obvious], they have to be gone through for due process.

To answer your questions :

• The timestamp on the AccessPoint is correct, as it shows the time that Publisher reload & distribute task finished.
• The qvw when viewed via the AccessPoint does not show the updates that have been made
• The qvw in the User Folder does not show the updates that have been made
• The qvw in the Source Folder does show the updates that have been made

But :

• If the qvw in the Source Folder is reloaded manually with QV Desktop
• Then the Publisher reload & distribute task is re-run
• All is ok, as in the qvw's in both the Source & User Folders they both show the updates that have been made

Best Regards,     Bill

[jerrysvensson]

Publisher or qvb.exe doesn't open the qv file. It hasn't any gui.

For changes to be applied you have to open and save your file either manually or via a script.

[Anonymous]

Jerry

The changes I have made and set Live via Source Control are saved ok in the qvw in the Source Folder, this I have double checked. 

But when the Publisher reload & distribute task is re-run, the changes are not reflected in the qvw in the User Folder / Access Point.

Best Regards,     Bill

[jerrysvensson]

Hi Bill.

The Publisher work exe file is qvb.exe. It has not a GUI.

What we have found is that changes made in the prj catalogue is not read if you don't reload or open using Developer (qv.exe). We suspect that the update from the prj changes is triggered by a windows event. Therefore qvb.exe which is windowless doesn't run the update.

I guess QlikTech are the only ones that can verify this.

We have a working solution using GIT where we open and close the qvw files using a script to get the latest changes.

Not a very good solution but it works.