Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
evan_kurowski
Specialist
Specialist

Scripts generate a Failure to Reload error, even when script emptied

Greetings All,

I'm having an issue with some of the documents I'm working with where reloading fails and generates the 'Execution of Script Failed. Reload Old Data?' message pop-up.

The strange thing is, I have emptied the script out or exited it after one or two lines in which I am certain there is nothing syntaxually incorrect.

It seems something is corrupting the .QVW files and not allowing me to proceed with them, does anyone know if there's some inhibitor setting or exploit that is being acted on?  Any assistance with this unwanted behavior would be appreciated.

~Evan

1 Solution

Accepted Solutions
Anonymous
Not applicable

Hello Qlik Community Members- this discussion has was posted previously but accidentally deleted we are recreating the thread. If you have any helpful answers please feel free to respond.

Jerry Svensson Oct 26, 2011 9:57 AM (in response to EvanKurowski)

Do you have logging activated? If so delete the logfile.

-------------------------

EvanKurowski Oct 27, 2011 9:21 AM (in response to Jerry Svensson)

Jerry, logging was not activated so that is not it.

Are you suggesting though that sometimes that error can be caused by the log file becoming "locked"?  ~E

View solution in original post

1 Reply
Anonymous
Not applicable

Hello Qlik Community Members- this discussion has was posted previously but accidentally deleted we are recreating the thread. If you have any helpful answers please feel free to respond.

Jerry Svensson Oct 26, 2011 9:57 AM (in response to EvanKurowski)

Do you have logging activated? If so delete the logfile.

-------------------------

EvanKurowski Oct 27, 2011 9:21 AM (in response to Jerry Svensson)

Jerry, logging was not activated so that is not it.

Are you suggesting though that sometimes that error can be caused by the log file becoming "locked"?  ~E