Power Tools 1.2 for QlikView

[StefanBackstrand]

Power Tools for QlikView

Version: 1.2

Download here

https://www.dropbox.com/sh/8hac72aljgqlr7d/AAASkzbM2H1OoVcLE_wa0kWGa?dl=0

For the absolute latest version, please see Power Tools for QlikView - One-stop-shop

In this release:

• QlikView Server Agent *updated* - 1.6.2
• QlikView Server Super Agent *updated* - 1.7.2
• QMS API Client - 1.0
• Qvs Detector - 0.9
• Qv User Manager *updated* - 1.0.1
• Reload Schedule Migration - 1.0.4321
• Server Object Handler *updated* - 2.0 - Updated to 2.1 @ 2014-03-18 11:00
• Server Object Handler Batch *updated* - 2.0
• Shared File Viewer *updated* - 1.5.2 - Updated to 1.5.3 @ 2014-02-21 09:32
• Qv Server Object Connector *updated* - 1.5
• XML Db Viewer - 1.0.4321
• Shared File Repair *new* and *updated* - 1.1 - Updated to 1.2 @ 2014-06-30 21:29

Release notes here: Power Tools 1.2 for QlikView - Release Notes

Readme here: Power Tools 1.2 for QlikView - Readme

Patches

• Shared File Viewer: Fixed broken "Color on top" sort option, new version 1.5.3
• Server Object Handler: Fixed credentials being passed wrong, causing no documents to show in list, new version 2.1
• Shared File Repair: Fixed "The path is not of a legal form" error when selecting Qvs binary, added "Don't show this" option in startup notification, fixed fonts", new version 1.2

Want to collaborate?

Do you have questions, thoughts or suggestions? Maybe you want to report a defect in the Power Tools? Please post it in the Management forum on QlikCommunity: http://community.qlik.com/community/discussion-forums/management

Also check out our Twitter: @QvPowerTools

DISCLAIMER

Power Tools are a collection of software programs and tools used for troubleshooting purposes only. Power Tools are provided free of charge and are not supported. Power Tools are not official QlikView products and are provided without warranty. Use of Power Tools is entirely at the user's own risk.

[#2]

Excellent software. Help for any things.

[Anonymous]

Hi Stefan

Is there a way to remove Doc CALs not used since last 90 days?

I'm trying to achieve it by
1. exporting the usernames who haven't used document since last 90 days to "RemoveCals.txt" --- SUCCESS

2. qv-user-manager.exe --remove cal < RemoveCals.txt   --- DOESN'T WORK

[Anonymous]

Hi Guys

Can someone please help me, how to configure power tool to remove CALs if not used since last 90 days?

[#5]

Hi Stefan,

is the problem with remove CAL resolved?

[Anonymous]

Stefan, we recently implemented digital certificate security and now qv-user-manager fails to run. I think it's a problem with how the qv-user-manager.exe.config file is set up. We got QMSEDX working so I tried using the .config file from there, which does work, but it isn't working for qv-user-manager. Any suggestions?

[celindho]

Has anyone had any success in running the server super agent as a background task?

[nucleus]

Hi!

I'm wondering if it´s possible to run qlikview server super agent as a service?
We have tried but the service won´t start. What other options is there to have the agent run in service-like mode?

[barryharmsen]

Fredrik Bendixen You have to modify the source for that. A little too lazy to search at this moment, but it is posted somewhere on the community and/or Github.

[barryharmsen]

Christian Lindholm You could try running super agent as a scheduled task (in Windows Task Scheduler) and trigger it when the computer starts.

[barryharmsen]

Stefan Bäckstrand I am running into some strange behavior with qv-user-manager for QV11 (running against QV11 SR3). When removing named CALs for users that haven't been active in the last 30 days, qv-user-manager sometimes seems to add CALs and place them directly into quarantaine. Additionally, I also see the 'last used' date and time changing for all the users.

The way I've tested this is with a batch file that:

• Lists all CALs
• Deletes unused CALs
• Lists all CALs again

All these commands are executed immediately after one another.

When comparing the before and after results I see that the "last used" date and time are changed (sometimes made blank) and that "new" users appear, immediately quarantined. These new users aren't actually new, but already existed before the removal procedure. Somehow qv-user-manager doesn't list them in the "before" list.

Could this be a bug in qv-user-manager? Scanning through the source I don't really see anything out of the ordinary. Perhaps this is an idiosyncrasy in the API? (are these CAL lists cached?)

I've seen similar issues at another client some time ago (but didn't really dig into it back then).