We are using the QlikView Web Server which sits on Windows Server 2008. At the time of the crash there was 15 users on the Server. I don't believe it is a capacity issue as the server has 40 cores and 512 GBs of RAM. The document that fails can be reloaded successfully when executed manually or when the server has recovered.
Please let me know if you need any other information. Thanks again.
Very odd considering the environment. Was the user getting a No Connection error anything by chance? You can check your timeout settings in your config.xml file. We had some issues with things timing out and locking up the server requiring a reboot. This was more on the client side and less on the distribution side thought. I think the timeout is set to 60 seconds by default. We increased ours to 180 seconds. Again don't know if this is the issue or not. May need to put in a support ticket.
We believe that we may have found the issue with regard to this
The problem lies in our QlikView Application. I believe
that when a QlikView application passes a certain volume of data, the
application does not behave as it should.
In this instance, our application’s data structure is made up of
multiple tables. (please see below)
When a user selects dimensions that represent different
granularities of data, for example selecting BIR Flag in the Bet
Table, Event in the Selection Table, Affiliate Name in the Customer
Table and a Date Time dimension, the issue described
below occurs. The solution to this is to try and amalgamate the majority of these data
tables (Customer, Selection and Bet) in to 1 fact table.
If you have any queries I would be more than happy to help.
Thanks very much.