Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in NYC Sept 4th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Script Execution Progress Box

Wondering if anyone has run into this issue.

Since upgrading from 8.5 to 9 we can no longer see the script execution details when reloading the data.

One developer can't see any information in this box when he is loading from a QVD. If he is loading from a database it's not a problem.

Another developer sees this issue on and off -sometimes she can see the details sometimes the screen is gray.

Any help would be appreciated.

Thanks.

1 Solution

Accepted Solutions
Not applicable
Author

Ended up that this was specific to version 9 sr1 for us. When we went to sr2 it worked as expected again.

View solution in original post

17 Replies
Not applicable
Author

I have the exact same problem. In 9.0 I have never seen any details running in the Script Execution Progress window. This is very annoying since it gives useful indication of how long the reload still takes, if there is a dead ODBC connection, or if anything else is going wrong.

In addition, Qlikview appears "not responding" while the script is running which indicates that the reload doesn't allegedly work.

Of course I can go the logfile that is generated but why bother if this screen should work?

Is it a setting or a bug?

Not applicable
Author

Ended up that this was specific to version 9 sr1 for us. When we went to sr2 it worked as expected again.

Not applicable
Author

Using SR2 (latest build) did not do the trick for us, unfortunately.

-TP

Not applicable
Author

UP...

Still having this problem in 9.0 SR2. Anyone else?

- TP

Colin-Albert
Partner - Champion
Partner - Champion

I see this problem intermittently on several sites running v9 SR3.

Sometimes the execution progress updates realtime, other times it displays nothing until the script has completed.

chriscammers
Partner Ambassador
Partner Ambassador

I am seeing this problem too in V9 SR3.

I'm not sure if it is a universal solution but I added a "status message" to my code and the execution dialog was unresponsive until it hit the "Trace" statement.

So if you add a very simple statement to the beginning of you code it may overcome the bug, or whatever the issue is.

chriscammers
Partner Ambassador
Partner Ambassador

Never mind, it only worked that one time

Not applicable
Author

I'm on SR3, and experience this issue on a seemingly random basis.

I've resorted to firing up task manager, going to the "Processes" tab and order by CPU. If QV is working it'll be at the top or very near the top of the list.

Not the best solution, I know.

Hopefully this will get fixed in the next release.

We can but hope!

chriscammers
Partner Ambassador
Partner Ambassador

I'm also seeing it on V9 SR4