Script execution reaches end, but doesn't conclude, and no error messages

[stevelord]

Hi, I've pressed reload on a dashboard, and it spent a few minutes running through the script.  The Script Execution Progress window shows it has reached what I know is the last table and appears to have completely loaded it, but the dialogue window is not closing itself even though I have that checkbox selected.  It is also not letting me close it with the end here button, and I've had to close qlikview with task manager a couple times now.

Can someone provide me possible scenarios and solutions for this phenomenon?  The dashboard is on qlikview server and is live, I was just sneaking in a couple more fields and reloading it.  There are no errors in the script that I can see, and the Task Manager shows CPU Usage at ~25% and Physical Memory hanging at 80%.  (I've pushed the first past 80% and the second to 99% without crashing anything, so pretty sure those aren't the issue.)

[arthur_dom]

Maybe there is some problem with Read/write file. Copy the App and try again. If have store commands check the files of store, they could be the problem.

[hic · Accepted solution]

This is the stage in the script where QlikView establishes the data model and creates the synthetic keys. If you have many synthetic keys, the script will hang at this stage.

I would suggest you load just a small amount of data - either by using "First 10" before each load statement, or by making a "Limited Load" in the script debugger - so you will be able to analyze the data model.

HIC

[stevelord]

I had added a resident load in script to do some more formulas for additional fields, and neglected to drop the previous table, so a massive Synthetic key ensued.  Adding the drop table after the latest resident load cleared the synthetic key and let the dashboard refresh.  Thanks!

PS> I have had issues in the past where someone or something was accessing a file the same time the dashboard was trying to access it, causing the dashboard to error, so gave the other response a helpful answer mark for that.  (I did run around and make sure that wasn't the issue before I saw this correct answer response here.)

[Karim_Khan]

Hi HIC,

    Even after applying 10 limited rows debugging its not working again facing the same issue.

Regards,

Karim Khan

[stevelord]

Hi Karim, In the document, open settings-> Document Properties.  And on the General tab, check the box for Generate Logfile in the upper right, then check Timestamp in Logfile Name.

Then go into your qvw and try the debug again.  Maybe right before you go to lunch and check on it during/after lunch.  (Safest if you can run it on your local desktop.)

The logfile is written as the script runs, so at worst you should see where it's hung even if the reload doesn't finish.  Then you can comment out that piece of script and the piece after it.  If the script runs okay after that, then you know the issue is something in that piece of script you commented out.

Other thing to do is be sure you're QV is update to 11.2 SR 12 - Doing that fixed a few random other issues I had with other things in the past too.  Lastly if it's just not reloading from QV Management Console, you might try rebooting the server to give the QV services and console a clean start.

Edit: Server reboot is a last resort during business hours, but easy to get away with outside business hours (unless it's a 24/7 customer-facing dashboard, then you might stick with 5am EST or something appropriate for your business.)

A couple more thoughts: In all likelihood the issue will be something with synthetic keys - if you have very many tables even 10 records might be a lot.  If you have many tables with a mix of the same fields, you might think about letting only one table bring in certain fields and all tables have one common key.  If your key needs to be multiple fields, you might concatenate those fields into a single key field like: field1&field2 as KeyField then relabel or comment out the component fields to keep them unique between the tables.

Or if nearly all the fields are the same, but not quite all, you might just concatenate load the second table onto the first or left join onto a key field etc.  (Do a bit of trial and error to be sure result is a correct data model.)  Generally best to spell everything out and not let Qlikview try to figure out the intention.

[Karim_Khan]

HI Steve, 

    Thanks for your reply I will work on above mention things.I am little confused about last part because I have developer version only.I don't know how and where to clear the QV services and console clearance.

Once again thanks will check your solution hope it will work

Regards,

Karim Khan

[stevelord]

Yeah, by all means skip the qlikview server/management console suggestions if you don't have those.  Going to help-qlikview update is a good place to start, then the more arduous troubleshooting after that.

[Karim_Khan]

Its a single table only

[stevelord]

Are you able to share the script?  Not sure how one table could get stuck.  Maybe if the database table you're querying is locked by someone else's query (they forget to write (nolock) or with nolock into the end of their query).  Or an interesting syntax error in the script itself though I can't think of what that would be.