topic Re: Recovery problem in QlikView

Recovery problem

Wed, 17 Apr 2013 07:54:57 GMT

Hello all,

I'm desperately hoping that someone can help with this because at the moment I am unable to use Qlikview and feel like I've been blinded in (at least) one eye as I use it daily for analysing data.

I have been using the Personal Edition for some years now; the last few months I've been on version 11, but for various reasons (changing laptop, IT changing domains, etc.) I have used up all my recovery attempts. I understand and accept completely the reasons for this limitation, so had resigned myself to having to recreate my dashboard from scratch after the last domain change had made the one I was using inaccessible.

However, I now have a problem whereby, even when I create a brand new file, save it, close, then try to re-open it, I *still* get the "recovery attempts exceeded" error and cannot open it again. Since this is a file created by the same user on the same machine--and indeed, I don't even have to close Qlikview to get this message--I can't understand why I am seeing this error.

Could anyone shed any light on it and if there is a possible solution. Sadly, it seems unlikely that I will be able to persuade my employers to shell out $1300 on a licence

Many thanks.

Re: Recovery problem

Gysbert_Wassenaar — Wed, 17 Apr 2013 19:01:21 GMT

Could be this problem.

Re: Recovery problem

Thu, 18 Apr 2013 06:50:48 GMT

Hi Gysbert,

Thanks for your reply. Sadly, that's not the problem. I *am* having that problem too, but after reading the thread about it, deleted the -prj folder. Unfortunately after having done so, I am still left unable to open the file just created because I have exceeded the allowed number of recoveries, even though this isn't actually a recovery.

Thanks for your help anyway.

Re: Recovery problem

Thu, 18 Apr 2013 06:51:06 GMT

Hi Gysbert,

Thanks for your help anyway.

Re: Recovery problem

coskunist — Mon, 22 Jul 2013 16:58:18 GMT

Hello simonking87, did you resolve the problem?

I have the same issue.

Thanks.