search

eapowertools-archive / qs-governance-dashboard

Unsupported - Collects metadata and parses script logs for Qlik Sense applications for use with Qlik Sense Governance
Other
38 stars 14 forks source link

Governance QVD Generator script failure #68

Open amibaron opened 6 years ago

amibaron commented 6 years ago

Description

Governance QVD Generator script failure

Steps to Reproduce

  1. Run QVD Generator app.

Expected behavior: Successful completion of script run.

Actual behavior: Script fails at several points:

  1. script tab 'LoopResouresAccessControl'
  2. script tab 'LoopAppObjectsAccessControl' for points 1 & 2 - I suspect the problem is due to the fact i'm using legacy mode, this seems to impact some of the syntax in the script (e.g. with regards to library path syntax used in load statements.
  3. script tab 'Audit and Usage'
  4. script tab 'Export Data' for points 3 &4 - i suspect that some changes have taken place in the log file structure in QS Server since the script was written - i've had to redirect the load statements to slightly different locations and comment out the looping through subfolders of log files to make it work. I'm not happy with this since i don't know enough about the logfile inner structure to be 100% sure that what i did is correct. it would be good if this could somehow be addressed (assuming i'm correct reg. log file strucutre changes).

Reproduces how often: 100%

Versions

-QlikSense 3.2 SR3 (qliksenseserver10.28.1) -QSense Server OS = Windows server 2008 R2 standard -qs-governance-collector v.2.1.1.0

Additional Information

Any additional information, configuration or data that might be necessary to reproduce the issue.

  1. QlikSense server setting changed to legacy mode.
  2. Log file location / folder structure / files is not inline with the script. Suspect some changes were made to the log files structure since the last script version of the qsgc QVD generator (just a thought, don't know enough to confirm this).
qlikperf commented 6 years ago

Hi Amibaron,

This might be related to issue #78; the root cause may be extraneous single quotes that don't parse as expected in Qlik Sense 3.2. Please see issue #78 for fix instructions.

Cheers,

J. R.