We reload all data into QVDs. We then reload a separate qvw that only uses the qvds. When the job runs nightly new qvds are created with updated data but the new data in the qvds in not picked by the second qvw load. If I run the job manually through the publisher the new data shows up?
This has just started happening recently and it is only happening on one QVW which leads me to believe this is caused by a change I made to the qvw. I did recently add a macro could this have any impact?
Is the reload of the QVW file dependent or triggered to run after creating the QVDs? Is the reload run in parallel with others reloads? If the reload runs well when started manually from the publisher or from the developer it should run fine if scheduled. The macro shouldn't make a difference. If it is run with other documents it could run out of memory. Does the log tell you anything?
I would try playing with the schedule when it is run to make sure it runs alone and after the QVDs are reloaded.
The reload is dependent to run after the QVD creation. There may be other jobs running while this reload is running. I can't see anything in the log files. Both jobs complete successfully and run in almost the same exact amount of time. I will try to find a more isolate window well after the QVD reload is finished. I will report back.
I noticed you are reloading and then distributing to a QVS Server. Does the original source document update properly? Does both the original and user document not update properly? Is the original source doucment the same document as the user document?
Since it's failure and success are inconsistant, could some other process be using the file and prevent it from being distributed correctly?