Qlik Community

QlikView App Development

Discussion Board for collaboration related to QlikView App Development.

bharatkishore
Contributor III

Page un-responsive in chrome

Hi All,

I have a qvw in access point and till yesterday it is fine.

But from today  while i am trying to open, i can open the qvw in access point but while i am trying to make any filters it is not happening.

Getting error as page un-responsive.

Can you please help me what could be the issue and how can i get it re-solved. Image for reference:

Thanks,

Bharat

7 Replies

Re: Page un-responsive in chrome

I think the first measure should be a re-start from server-services and/or the whole server-machine.

- Marcus

bharatkishore
Contributor III

Re: Page un-responsive in chrome

Thanks Marcus.

But this is just happening only for one specific qvw.

There are other qvw's as well. But it is not creating any impact for them.

Is there any specific reason?

Thanks,

Bharat

Re: Page un-responsive in chrome

What happens if you used another browser maybe firefox?

- Marcus

bharatkishore
Contributor III

Re: Page un-responsive in chrome

I am using IE and chrome and in both browsers i am facing this issue.

Re: Page un-responsive in chrome

Ok. It seems that the issue is anywhere within the datamodel - maybe there are now any synthetic keys, circular loops or broken associations (and loosen tables) or something like that through any changes on the load-steps before. Therefore I think you should open the application with the desktop client and find and fix the issue.

- Marcus

bharatkishore
Contributor III

Re: Page un-responsive in chrome

Thanks for your suggestion. Will look into that.

But till yesterday it is fine.

Only from today it is not working. It is the same app what is there yesterday.

Apart from data model anything else could be the reason.

Highlighted

Re: Page un-responsive in chrome

Another possible reason could be that there is an issue with server-objects which are stored within the shared-files. For checking you could just remove the shared-file (I would backup it before) and then test again. If then the application reacts normal you could try to restore an older version of them and/or to repair them with the Power Tools 1.2 for QlikView.

- Marcus

Community Browser