my named cal not pulling down from qlikview server to local desktop

[stevelord]

Hi, it's been routine for me to pull my named license down from our qlikview server to my desktop, but it's not working this time around and we're not sure why.

-On Qlikview Management Console, System->Setup->security I have NTFS authorization (Windows controls file access) checked.

-My server desktop login id is also present on the list of of ids with named cals.

-I can also access all of the documents on the qlikview accesspoint web browser with my own named login, including ones I did not create.

-I am unable to open documents on my local desktop that I created, or any documents on the network drive that others created.

This happens every couple months or so, and the solution is usually simple:

-I open qlikview on my local desktop, go to file->open in server.

-Connect using Alternate Identity (my user id for the qlikview server environment differs from my user id on my local desktop environment, so I use this and enter my qlikview server credentials to connect to it from my local desktop.)

-pick any qlikview document on the list in the bottom window of the open in server box and open that qvw.

-close the qvw I opened in server.

At this point, my named cal would be recognized in my local qlikview again,and I could open whatever I want from my local desktop again.

But it's not.  It used to work fine, but it doesn't now.  My name is on the list of users with cals in qlikview management console.

Any idea what could cause this or what I should check into?  It seems to have occurred in the last two weeks since I can't open files that were made before then on my local desktop.  Engineering is unaware of any changes to the qlikview server environment, and I'm unaware of changes on my local machine, but maybe some external or inbetween something happened?  Maybe some little obscure associated file this stuff references?

[vgutkovsky]

Here's something to try that's helped some of my clients in the past:

1. Close all open QVWs and open a new instance of QV Desktop

2. Go to Settings >> User Preferences >> Locations

3. Click the entry named "QlikView Server AccessPoint (URL)" and press Modify

4. Type in the full URL of the AP and press OK twice to exit User Preferences.

5. Press Tools >> Open QlikView AccessPoint

6. When the AccessPoint opens and you've logged on, open any document.

7. After the document successfully loads, close QV Desktop. When you reopen it, it should have leased a license.

Regards,

Vlad

[stevelord]

Done, but didn't work.  Any other ideas?

(I'm about to remove and readd my named license on qvmc to see if that causes invisible stuff to repopulate, but at a loss otherwise. )

[vgutkovsky]

I believe QV Desktop license leasing info lives in the file C:\Users\username\AppData\Roaming\QlikTech\QlikView\Settings.ini. In that file, lines 9 - 11 are records that are necessary to have leasing work properly. Maybe something got corrupt. Try closing all instances of QV, renaming/moving this file, and then relaunching QV. That should cause a clean version of the file to appear. I believe it should even release the license automatically (not sure how it does that).

Give that a try. Otherwise, you may need to do a clean uninstall and reinstall of QlikView, deleting all the stuff in ProgramData\Qliktech and other QV directories (such as the one mentioned above).

Vlad

[stevelord]

I renamed the file temporarily and reopened qlikview.  It prompted me for language, I did english, opened doc in server, closed, and couldn't open other files on my desktop still.  I looked at the new setup.ini file and see nothing about licenses- those lines referenced a filepath of a file I opened or tried to open.

I looked back at the old setup.ini file, and maybe 30 lines down I see these:

LeasedLicenseExpiry=2014-06-19 20:08:31, 2014-06-25 20:32:35 //I left this as is.

LeasedLicenseCheck=afafafafafa123 //bunch of alphanumeric code I probably shouldn't disclose.

LeasedLicenseServer=qvp://me@123.45.678.910 //ip address I'm not disclosing here.

PInfoX=afafafafafa123 //bunch of alphanumeric code I probably shouldn't disclose.

PInfoY=afafafafafa123 //longer bunch of alphanumeric code I probably shouldn't disclose.

PInfoZ=afafafafafa123 //longest bunch of alphanumeric code I probably shouldn't disclose.

Then there's more stuff recognizable a layout settings, recent file list, and such.  Then this stuff at the end:

[Module Checksums System]

afafafaf123-afafafafa123-afafafafafafa123-afafafafaf123= //bunch of alphanumeric code I probably shouldn't disclose.

[Authentication]

LastLefUpdateAttemptDate=2014-06-25 afafafaf123-afafafafa123-afafafafafafa123-afafafafaf123 //bunch of alphanumeric code I probably shouldn't disclose.

Also, this edition of qlikview was installed May 2013.  My boss thought maybe I'd reinstalled it and caused the problem, but the May 2013 says I didn't.  I'm hesitant to do an uninstall and reinstall, but can give it a whirl as a last resort.  Is there another thing left to try?   I see Help->License Update has blank stuff and wonder if copy/pasting text from somewhere on the qlikview server down to that might do something...

Other phenomenon is I used the restore feature one time, and still have one time left, and it is letting me open many of my desktop documents again.  For some reason, there are still others where it won't let me open them and is suggesting/warning about restoring those.  I don't think I ever used the restore feature before, so not sure how it got down to 2 in the first place.  If I can get my named cal back down here though, maybe all that stuff will be moot again.  (I may take a step back at this point and see if our qlikview rep consultant guy can cleanup and restore whatever for me.)

[vgutkovsky · Accepted solution]

The LeasedLicenseExpiry value in the old file definitely indicates your lease is expired...but I have no idea why it's not refreshing it. If a clean uninstall and reinstall doesn't do the trick, I'd say open a support ticket with Qlik.

Regards,

Vlad

[stevelord]

Thanks Vlad, I've actually reached out to our qlikview consultant.  He charges more than super lawyers, but only for trainings and projects, not for one-off 'help me!' interactions like this.  If he says uninstall/reinstall, I'd be safe hiding behind his instruction if something goes southward (though I don't think it can be a bigger mess than it is right now.)   He might have a some cool copy/paste zappo solution too.  He's very familiar with the nuances of our company's setup, so should be easier for him to sort out if our setup is much different from the norm.

Ultimately, you put alot of good time in this and I did learn stuff, so points to you were earned.  Thanks again!

[stevelord]

(all the advice offered was helpful and should make a shorter call and less troubleshooting with the consultant.  upgraded to correct for decisive instruction to put in a ticket. )

[vgutkovsky]

Good forum etiquette, thanks! Let me know the final resolution, would be very interested.

Vlad

[stevelord]

Hey Vlad, the consultant says a named license can only be present on two machines (have two instances).

I have one on the desktop hosting the qlikview server.

There is a separate qa server (just a remote desktop with no qlikview serer, accesspoint, or source control- only a personal edition qlikview on it) that may be holding the second instance of my license, but that is not evident when looking at the license information in qlikview on that desktop.  Even so, the qlikview on the qa desktop is letting me open whatever I want.

There is clearly no instance of he license on my local destkop since I am having this issue on my local desktop.

Consultant recommended these steps:

remove myself from the named cal in qlikview management console at the end of day Friday,

let the quarantine pass and the cal become available again over the weekend (I think I might have to push another x or something to confirm removal after the 24 hour quarantine time passes)

restart qlikview services on Monday

re-add myself to the named cal

Then try to pull it down to my local desktop again.

This looks like it's half a step shy of the uninstall/reinstall of the whole program, by removing and re-adding just the affected named cal user, so uninstall/reinstall looks like it'd accomplish the same thing with similar effort in a less complex environment.  Pretty sure the only advantage the consultant had was more detailed knowledge of our layout.

I will check back with him with the result, and pop by here if it worked.  (And maybe we learned named cals only work on two desktops each, and maybe this qv on the qa remote desktop has one I can't see with my access level on that desktop.)