Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
I have a range of documents with reload tasks set for various times at various intervals - some once a day and I have at least one which is every 2 minutes. As at 16:48 today the "Last Execution" showing in QMC is 10:47. All four of my services have a status "Running":
When I select QVS@pid-sql-cl01 on the QVS Statics tab I get a "Processing... Please wait." message and nothing else.
I presume I need to ask our IT dept to restart one of the Windows Services, can you let me know which one(s)?
I have QlikView 11.2 SR6 and I do not have Publisher.
Thank you
But before restarting the QlikView services, ask your IT dept to perform a quick in-site upgrade to either SR15 (if you don't like extended quarantaine periods) or SR17 (if you don't really care). For example, between SR6 and SR15 there were more than 720 bug fixes...
But before restarting the QlikView services, ask your IT dept to perform a quick in-site upgrade to either SR15 (if you don't like extended quarantaine periods) or SR17 (if you don't really care). For example, between SR6 and SR15 there were more than 720 bug fixes...
Thanks Peter,
So, in other words, they need to restart all of them? Last time we had this problem I asked IT to restart everything but I wondered if this was overkill, hence my post here.
At first, when they restarted everything it didn't work, they then tried restarting from the bottom up (whatever that means, I'm guessing they appear in a certain order on his screen) and that did work. Is there a specific order they should be restarted in?
Is the Distribution Service a part of Publisher as we don't have that or is it something that's not visible in QMC?
With regards to SR6, we're planning to get a new system and move from 32gb RAM to 256gb, we'll upgrade away from SR6 at that time.
Wow, many questions. It started simple...
BTW does your QlikView environment experience reload lockups often?
Best,
Peter
Sorry Peter, I thought it was a simple question at first too.
Thank you very much for your thorough answers though, it's much appreciated.
Yes, you're right, there is a task called ReloadEngine.
I wouldn't say we experience lockups often and I think that this one was caused by a colleague writing a bad script. I noticed a new document listed this morning and the history said that 4 out of the 5 reloads had taken 2 seconds and the 5th one had taken 6 hours and then failed. It was around that time that we then had the issue. After the first 4 he said his dataset wasn't complete and made a change. So, I'm blaming him.
My main question though was restarting those services, I have no idea what's involved or how long they take and didn't want to tie IT up with restarting services un-necessarily if the do take a while. So, thank you very much for answering that.