"Ghost" Documents and CALs

[#1]

Hello,

I have two issues, both equally as confusing. 

First, I have a document showing in Documents > User Documents which I can not find on the server.  I ran a search on my hard drive, and nothing showed up; furthermore, I have checked all mounted user document folders, and again, nothing.  Has anyone seen something similar?  I tried to restart the services, to no avail.

Second, when I go through all Documents in Documents > User Document, and add up the values for "Document CALs allocated to this Document", I come up with a number X.  However, when I go to Systems > Licenses, and look at the Number of Document CAL's assigned, it doesn't agree.  There are an extra 5 CALs being claimed somewhere, yet I can't find the document claiming these?

Note, it is not the mystery document reference in my first question, I confirmed this document is claiming 0 CALs.

Thanks,

Chris

[swuehl]

I have currently no idea about your first issue.

The second issue can arise when you delete a qvw with document CALs assigned.

Maybe one of these suggested solutions help you.

[jaimeaguilar]

Hi,

for your first issue, it sounds to me like the document actually existed sometime but it was deleted without deleting its references from management console. So even though the document doesn't exist anymore it still appears on the server. So it comes the second issue. It can be that the document had X number of document CALs assigned, but since it was deleted from server but not from management console, the reference continues to be there (including those "ghost" assigned CALS).

The workaround I can think of is creating a "dummy" file with the same filename and then deleting it first from Management Console and then deleting from Windows. It would be a good practice to do this everytime you need to delete a QlikView File,

regards

[#4 · Accepted solution]

Thank you!

This did the trick, on both issues!

[Anonymous]

Hi Chris,

Related to your first issue.

Is your Qlikview version is 11 and Release SR4,if yes this might be issue related to SR4