After upgrade to SR5, I've seen two customers where server reload/dist tasks never complete. The tasks hang loading the document, usually after the reload is complete and then loading again for distribution. If you look at the document log, you'll see an "Execution Complete" message. Look in the TaskLog.txt and you'll see the repeating message:
Loading. LoadTime=00:05:04.1817478
with the time incrementing. This will go on forever until the qvb.exe or the Distribution Service is killed.
Has anyone else seen this problem? Been sucessful in getting it accepted as a bug?
I've seen this before: In QV10 SR4 and SR5 there is a bug that makes a memory leak while reading a qvd and using any type of function in the load. So an optimized load fixes it with and then apply the functions via a preceding resident load. This is fixed in SR6.
The server and client both behave the same.
It really made my head scratch until i figured it had to be a bug.
According to the bug report I read, Its not a consistent as I describe. If you can observe a peak in memory use in the qvb.exe processes this would also fit the error.
In response to Michael's bug, it sounds exactly like the bug I’ve seen where the task logs confirm the reload has completed, but the QMC does not update the task status.
This is a known bug 46252 and is resolved in the current patch 11318 available from QT support.
Bug 46252 : Publisher in QV 11 Sr1 - Tasks status on QMC stay on running but they succeeded in the logs
(This bug effect both publisher and non publisher installations)
