Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
NZFei
Partner - Specialist
Partner - Specialist

Discussion about the issue that users cannot open saved file with Personal Edition

Hello everyone,

I open this discussion because I have seen many people have published this issue but it is not fixed. The reasons that a user created a qv file, save it and cannot re-open it using persional edition are:

1) Change PC;

2) Change IP;

3) More than 4 times license changes (including recover or open files that are created by others 4 times).

4) Have installed QV before and did not uninstall completely.

Below is from QlikTech:

Please read carefully: Technically, every document is now saved with a user key -- information that ties that file to the file's creator. In Personal Edition, users can only open files that they have created.

We recognize that it may be necessary to install QlikView on a different computer (i.e. computer upgrade, replacement, etc.). In order to open documents created using the previous installation of QlikView, you will need to "recover" the files. Recovering files simply means that you are assigning an updated user key (old machine -> new machine) to these documents. When you recover a file, you are telling QlikView that you are moving this file to your new installation, and you will no longer be using it on your previous installation.

IMPORTANT: QlikView Personal Edition is limited to four recoveries per installation. When you recover a QlikView file created with a previous installation, it will apply your new user key to ALL documents created using the previous installation, not just that particular file.

DO NOT attempt to open QlikView files that you did not create (from the forums, created by a colleague, etc.) Doing so will use one of your remaining recovery attempts, and once you have exhausted all 4 of the attempts, you will no longer be able to access documents that you have created and, from that point on, you will only be able to create new documents using your current QlikView installation.

Now is the story that just happened today to my boss. He went to visit a prospect and demonstrated QV to them. They were very excited and interesting. Then my boss downloaded and installed the latest version of QV PE to their computer, connected to their database, took about 15 minutes to build a application for them, reloaded, saved and closed, and could not open it any more.

I know it could work if he uninstalls completely QV and reinstalls it again but there was not time to do that in a one-hour meeting. He had to quickly re-create a new application and left it open.

I want to know the reason why this happened. (this is at least the third time that has happened to him.) The PC and network are clearly not changed. He just tried to open a file that was created and saved by him 3 seconds ago. Why couldn't he re-open it?

As we cannot re-create the issue, we cannot report it. Anyone has any clue about it? Or how would you handle it when it happens to you on prospect's site? From memory it has happened to both 32 bit and 64 bit system. Can you provide any more information if you have met same problem?

If there is anyone from QlikTech, could you tell us how to report it without being able to re-create it?

Thank you very much!

Fei

2 Replies
luciancotea
Specialist
Specialist

As you noticed, this is a common problem. The answer is that the algorithm used to generate the key is unstable. Sadly, the free edition is not a priority.

NZFei
Partner - Specialist
Partner - Specialist
Author

I have opened a new case for this issue. QlikTech has confirmed "this is a bug #63607 which only happens on those PCs that have never applied any QlikView license.This bug is currently fixed but the fixed version is not released yet. Since this issue was reported on V11.2SR2(Build 11922), in the meantime, we suggest using V11SR2(build 11440) instead of V11.2SR2 for your future demonstration to your prospects."

This is a good news. Will ask my colleague to test it in next meeting. I am happly that this issue can be solved.

Thanks.