Skip to main content
Announcements
Customer Spotlight: Discover what’s possible with embedded analytics Oct. 16 at 10:00 AM ET: REGISTER NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Slow opening when trying to open the Qlikview Desktop Script Editor

Hi team,

When trying to open the script editor from a document, the opening of the script editor takes a long time (30 seconds).Anybody has aby idea regarding this issue?


Thanks in advance.


10 Replies
vardhancse
Specialist III
Specialist III

What is the size of your QVW?

RAM in your system?

Not applicable
Author

Hi,

Which version are you using /

in v12 it is happening ..

It is always depends upon ur

Size of the application

Ram Space

Consumption of ram while opening

Not applicable
Author

Hi,

I have updated V12.1  (SR1, SR2, SR3,SR4) From  V11.2. ( Windows7 SR2)

After installation i have found the same problem.

Is not a problem of size, ram etc.

It happens  also opening script on empty documents.

Ragards

Claudio

tamilarasu
Champion
Champion

Hi Nishant,

Below links might have answer for your question.

https://community.qlik.com/thread/161046#1102691

Slow opening when trying to open the Script Editor

Good luck

Not applicable
Author

Many thanks for your appreciate replay

I tried to do this:

- Deleted (from register) Qlikview\Toolbar 7

- Installed QV Desktop 12.10 SR4  version  .20200.0

- Updated the ODBC Driver (IBM iAccess)

- Deleted (from register ) all drivers (including Excel, Access, Sql Server  except Ibm iAccess drivers)

Now the time of opening is around 10 seconds

With 11.2 was 1 or 2 second.

Someone has a solution ???

Many thanks

Claudio

tamilarasu
Champion
Champion

Hi Claudio,

Sorry, I am not sure about this behavior. Maybe someone might have answer for this or from Qlik Support. If you find a solution, please let us know. Thanks.

Anonymous
Not applicable
Author

HI!

We have this issue in all QV12.* releases.

We have contacted Qlik Support and received the Bugid

QV-10133

Unfortunately we haven't got much priority behind fixing this, as Qlik Support tells us we are the only ones contacting Qlik Support about this topic.

So please open a case at Qlik & referencing the BugId above! May this helps to get if fixed soon.

Thx,

Roland

Anonymous
Not applicable
Author

Hi

Have a look: https://community.qlik.com/thread/259101

Hope it helps!!!

Not applicable
Author

Many Thanks

Claudio