Qlik Community

QlikView Documents

Documents for QlikView related information.

Power Tools 1.2 for QlikView

Employee
Employee

Power Tools 1.2 for QlikView

Power Tools for QlikView

Version: 1.2

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.

Attachments
Comments
ebapt_cegid
New Contributor II

Hi Stefan,

I'm using "Server Object Handler" from 1.1 on a server, it's works fine.

The new version 1.2 show me an empty list for "Select document" with the same host name.

Not only the host name is needed ?

Thanx

Emmanuel@

QVS version : 11.20.11922

johnh
Contributor

Hi Stefan,

Thanks for the new release.

Is there a way that I can tell the QV-User-manager on which server to add a CAL. I manage multiple QlikView Servers from 1 QMC and if I use QV-User-Manager to add a CAL it adds it to all servers.

Thanks

Employee
Employee

John,

That sounds like a bug to me, actually. Just to be clear; you have several (non clustered) QVS services added in one QMC, and when you add CALs they are added to all of the servers? You don't get to select a target QVS?

Employee
Employee

Emmanuel BAPT,

I would like to see it more closely, but I need to test your server version first. I'll get back to you.

johnh
Contributor

Hi Stefan,

That is correct. When I list the CALs there is a server field returned.

Maybe the server name can be added to the add CAL but it is not in the Documentation / help.

Cheers

Not applicable

I have QV Services 11.20.12235.0 installed on my laptop. QVEMC indicates all services are running just fine.

I run PT 1.2 QMSAPIClient and I get a flash disclaimer window and then no GUI window. Just a icon on the task bar, an app and a process in the task manager that consumes no cpu, has 6 threads.

I have tried rebooting .. no GUI.

What am I doing wrong?

vgutkovsky
Honored Contributor II

Really useful stuff, thanks! Quick question: do you know why the User Manager is not letting me remove Named User CALs. For example, I create a CSV with a single user named "testuser". I then execute the following command:

qv-user-manager --add cal < Roster.csv

The user is added as a named user (which is correct). I never actually use this CAL, but immediately create a 2nd CSV with that same user and execute the following command:

qv-user-manager --remove cal < OldUsers.csv

The CAL does not get removed. What am I doing wrong?

Thanks,

Vlad

Employee
Employee

Daniel, this is unfortunately a known bug that is related to the position of the main windows form of the tool. If you are on Windows 7 the workaround is to start the tool and then use the command Win+Up (or Win+Left or Win+Right) to move the window into the view. Another workaround is to find the registry settings for QMS Client and remove the X and Y pos settings, and then restart the tool. We hope to publish a fix for this soon, when I have the time to fix it.

Sorry for any inconvenience.

Employee
Employee

Vlad,

I'm not sure what's wrong here, but I will try and find out. I'll test this as soon as I can. Keep an eye out for a fix.

pablolabbe
Valued Contributor II

Hi Stefan,

  Good to see improvements on QvSharedFileViewer utilty.

  My customer reported an error on QMC Server when selecting a QVW inside Documents Panel. The error is:

QMCDocumentSelectionErrorMessage.JPG.jpg

  Server version is Qlikview v10 SR4.

  So, I suspect the cause could be the shared file.

  I used QvSharedFileViewer  utility to open the shared file (132 MB size). The QvSharedFileViewer process took 7 GB of RAM of my server and it shows  9418 objects.

I can do some filters without problem, but when using the menu option View>Sheet Objects, select a user and click on a specific sheet, I receive an error inside the Exception Window.  The error also appear to several users on different sheets. Does the shared file is corrupted ?

  See the error stack below:

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************

System.NullReferenceException: Object reference not set to an instance of an object.

   at QlikTech.BlobDbUtil.SheetObjects.AddObjectToList(String id, TocEntry obj, objectType objType)

   at QlikTech.BlobDbUtil.SheetObjects.PopulateObjectList()

   at System.Windows.Forms.TabControl.OnSelectedIndexChanged(EventArgs e)

   at System.Windows.Forms.TabControl.WmSelChange()

   at System.Windows.Forms.TabControl.WndProc(Message& m)

   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************

mscorlib

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.296 (RTMGDR.030319-2900)

    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll

----------------------------------------

QvSharedFileViewer

    Assembly Version: 1.5.3.0

    Win32 Version: 1.5.3.0

    CodeBase: file:///C:/Qlikview/util/PowerTools%201.2/SharedFileViewer/QvSharedFileViewer.exe

----------------------------------------

System.Windows.Forms

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.1002 built by: RTMGDR

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

----------------------------------------

System.Drawing

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.1001 built by: RTMGDR

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

----------------------------------------

System

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.1001 built by: RTMGDR

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

BlobDbLibrary

    Assembly Version: 1.0.0.0

    Win32 Version: 1.0.0.0

    CodeBase: file:///C:/Qlikview/util/PowerTools%201.2/SharedFileViewer/BlobDbLibrary.DLL

----------------------------------------

QdlLibrary

    Assembly Version: 1.0.0.0

    Win32 Version: 1.0.0.0

    CodeBase: file:///C:/Qlikview/util/PowerTools%201.2/SharedFileViewer/QdlLibrary.DLL

----------------------------------------

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

For example:

<configuration>

    <system.windows.forms jitDebugging="true" />

</configuration>

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

Best Regards,

Pablo

Version history
Revision #:
1 of 1
Last update:
‎02-20-2014 04:41 PM
Updated by:
Employee