I installed the Governance Dashboard on our Qlikview 11 Server.
But I always get a Script Error in the hidden part:
Table not found
1 as MaxID,
Max(LoadDate) as MaxLoadDt
Did somebody has the same issue?
I´m useing Amazon and get the same error.
Attached the file with my log configurations.
|Operating System Version||Win32_OperatingSystem=@ X64 (Microsoft Windows NT 6.1.7601 Service Pack 1)|
|CPU 0||Intel(R) Xeon(R) CPU E5645 @ 2.40GHz|
|CPU 1||Intel(R) Xeon(R) CPU E5645 @ 2.40GHz|
Same error, when I disable Has Log Server, the problem didn´t occur.
The problem only occur when the document read Logs is enabled.
I´ve Publisher and didn´t enable
Hello Ricardo - can you please verify all of the following listed in the following document and let me know if any of it has fixed the issue:
This issue (script error) has been reported and is being fixed, however if none of the items in the document fix the issue it might be related to the VM.
I assume you are getting the DateIsland Script error when running the scan of the QVGD?
I will have one of our team look at this too to get another set of eyes on it.
Can you also attach the following logs:
I get the same error. I have a physical server with Windows Server 2008 R2 64-bit.
I have several folders in my source document path. One folder is called "In Production" and another is called "Prod" and a third one is called "QVD Load".
When I add "In Production" to the list i get the DateIsland error and when I search the others it works just fine. I thought that the space in "In Production" might have been the cause but the folder "QVD Load" works so logically it has to be something else. What can I do?
Also, how do I change to western formatting of dates? And in some parts the letters "å ä ö" are either replaced with weird characters or just skipped. In other parts they are displayed correctly.
Hello Marcelo - can you send these logs - attach to the thread you respond with:
After your last message I wanted to run the program and give you the logs of both folders. The "In production" that returned an error and the "QVD Load" that worked. After your message I initiated a scan with the dashboard providing only the "In production" folder. I left it running and when I logged back in 5 hours later it was still running so i cancelled it and uninstalled the dashboard. All processes didn't end and I could not manually end them either. etool.exe *32 was running several instances. I performed a reboot today, removed all files and installed it again. I must have done something wrong because the same thing happened today but when performing a scan on the "QVD Load" folder that I know worked before and this time it kept running much longer than it should have so i cancelled it. I can't end the process etools.exe now so I have decided to put this on hold for now.
EDIT: For clarity, I uninstalled it properly and removed the files that were not deleted automatically.
Hello Marcelo - it seems like you may be experiencing a long run-time - however it seems you did not get the script error as originally stated:
Have you tried scanning a smaller directory? Just to see? Something that has a few QVW, QVD files just to test the behavior? If that DOES work then at least we know the dashboard is now working and you resolved your original issue.
Please note this write up on the slow run time:
Problem: Scans take a very long time, in some cases multiple hours.
Issued Id: GOV-121
Remedy: The QlikView Governance Dashboard metadata scanner obtains its QVW and QVD metadata
by scanning these files and extract out XML tag information that contains the metadata. In the case of
QVW files, these XML tags tend to be near the end of the file, after all the encoded data contents. In
the case of QVD files, the XML tags are at the top of the file.
For QVW files that have very large data volumes, identifying the start of the XML tag block can take
longer than for QVW files that have little or no data. If the QVWs to be scanned are deployed to the
Publisher’s SourceDocuments folder in a data cleaned state, the time to scan them will generally be
faster than if deployed with a large volume of existing data. Use the ‘File->Reduce Data->Remove All
Values’ function on these larger QVWs before deploying so that the scanner can identify the XML tag
blocks more quickly.
For QVD files that were generated from QVWs that loaded hundreds of data sources (either using a
looping construct or a LOAD * pattern), these target QVD files will contain as many <LineageInfo> tags
as there were different source files used in the QVWs that generated the target QVDs. We have
observed instances in which the generating QVW files we’re loading thousands of machine generated
log files resulting in thousands of <LineageInfo> elements (all with cryptic, machine-generated file
names which provided little additional lineage value). These QVDs can be eliminated from the
Governance Dashboard scan process by entering a pattern that matches unite parts of their file names
or parts of the names of the sub-directories to which they are written. Care must be exercised to make
sure your pattern does not inadvertently match the names of QVW or QVD files (or their directories)
that you do want included in the scan.
Please let me know how you do when you continue working with QlikView Governance Dashboard.