topic QVW-File cannot be opened after Reload in QlikView

QVW-File cannot be opened after Reload

fneumann — Tue, 17 Mar 2020 16:50:02 GMT

Hello, everybody,

i have a QVW file that after reloading, whether in the QMC or locally, cannot be opened after it has been saved. Me and my colleagues have never had such a problem before.

We have already restored the file from an older backup when everything was still working, but that's where the problem also occurs. The reload of the file always works without problems. I have already recreated the file from scratch, but the problem still exists. Somehow the reload seems to destroy the file in a way that it can't be opened after saving.

There are two simple error messages when trying to open the document: 1. Error opening the document "filename" 2. Failed to open document.
I and my colleagues are running out of ideas what the problem could be. Maybe someone can help here? Thanks in advance!

Re: QVW-File cannot be opened after Reload

m_woolf — Tue, 17 Mar 2020 17:39:52 GMT

You might try recreating the app from a project folder.

https://community.qlik.com/t5/QlikView-Integration/How-to-re-create-an-application-from-the-prj-folder/m-p/741783

You might also try:

https://community.qlik.com/t5/QlikView-App-Development/Failed-to-open-document/td-p/523546

https://support.qlik.com/articles/000002664

Re: QVW-File cannot be opened after Reload

fneumann — Wed, 18 Mar 2020 08:45:42 GMT

For some reason it worked again this morning without us changing anything. Maybe the daily reboot of servers solved it.

Thanks anyway!

Re: QVW-File cannot be opened after Reload

pwagner — Thu, 28 Jan 2021 12:49:46 GMT

Hello @fneumann
I am facing the same issue like you. In my case, for some time it's working and then out of a suddon this problem occurs again.

How is it at your qlikview site? Have you faced this problem again?

Thank you.

Best regards, Patrick

Re: QVW-File cannot be opened after Reload

fneumann — Thu, 28 Jan 2021 14:35:49 GMT

Hi @pwagner ! We have not faced that issue again since I wrote my last post on this. I still do not know what has caused the problem. Sorry!