Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Session Lost when opening document (AJAX SR12)

Hello Community!

Recently we've been experiencing problems when attempting to open certain Looped&Reduced documents via Access Point. The document stays in a status of loading for about a minute, then an error message appears stating 'Session Lost'. To clarify, there are no problems encountered while loading the same distributed qvw via Desktop Client.

The distributed documents aren't that large in size (between 5 and 500MB), but do have a few macros triggered OnOpen. Has anyone who has experienced similar problems provide some insight as to the possible causes here?

Thanks,

James

1 Solution

Accepted Solutions
quwok
Creator III
Creator III

It could also be that the document is taking too long to open and the web server has timed out.

Try setting the <QvsTimeout> in the config.xml under your QlikView Web Server folder (C:\Documents and Settings\All Users\Application Data\QlikTech\QvWebServer\config.xml) to something larger.

View solution in original post

5 Replies
awhitfield
Partner - Champion
Partner - Champion

Hi James,

OnOpen triggers aren't supported when using AJX, from the reference manual:

OnOpen

Select this event to assign an action to be executed each time the QlikView

document is opened. This event is not supported when running in the AJAX

client.

HTH Andy

Not applicable
Author


Hi Andrew,

Regardless of whether or not they are supported, they do work in AJAX client. We've been using them successfully in our documents for several years. I think the solution is more complex than this I'm afraid.

Thanks,

James

quwok
Creator III
Creator III

It could also be that the document is taking too long to open and the web server has timed out.

Try setting the <QvsTimeout> in the config.xml under your QlikView Web Server folder (C:\Documents and Settings\All Users\Application Data\QlikTech\QvWebServer\config.xml) to something larger.

Not applicable
Author

We upped the timeout from 60 seconds to 600 seconds and this solved the issue - thanks very much!

enderl
Partner - Contributor III
Partner - Contributor III

Hi,

will this setting work, when we use an IIS?

Regards,

Dirk