A corrupt QlikView document will output exceptions in the QlikView Server log files.
To identify the related Document and solve the issue walk through the steps in the Solution.
Example from Windows Application Log (Event Log Verbosity=High):
2012-03-31 12:36:20 2012-05-01 05:03:03 4 500 Information Debug: Opening file test.QVW on disk
2012-03-31 12:36:20 2012-05-01 05:03:05 4 500 Information Debug: File test.QVW opened OK
After that you will find something like this:
2012-03-31 12:36:20 2012-05-01 05:03:03 2 302 Warning Caught ... exception in: .\ChartFunctions.cpp at 2952
2012-03-31 12:36:20 2012-05-01 05:03:03 2 302 Warning Caught ... exception in: .\ChartFunctions.cpp at 3038
2012-03-31 12:36:20 2012-05-01 05:03:03 2 302 Warning Caught ... exception in: .\QPivotTableBox.cpp at 2314
As you see in this Example the Warning appears directly after the Call of the test.qvw so this is the Application that produces the Warning.
Environment:
QlikView
Resolution:
- Open the Event.log of QlikView Server: C:\ProgramData\QlikTech\QlikViewServer
- Search Debug: Opening file
In the Line where you find an entry with this, you may find the related Application which produces this message.
- Identify the Corrupt Object and recreating the Application:
- Open the Application in QlikView Desktop in this Example our file called "ab.qvw"
- Create a Folder "ab-prj" next to the Application
- Save the Application in QlikView Desktop - now the ab-prj folder will filled with xml files.
- Rename the Application ab.qvw to ab_qvw that you have a backup
- Create a new / blank Application with QlikView Desktop and Save As "abNew.qvw"
- Close QlikView
- Goto Windows Explorer and Rename the Application abNew.qvw to the old orginal name "ab.qvw"
- Open these Application "ab.qvw" and it will get all data from Project Folder and recreate the Application.
- Save the Application and Relaod it cause the data didn't stored in the Project Folder
