No suggestions, just info:
I have QV Server 9 on Windows Server 2003, and it works fine. Small documents opens in a sec. There is a large one, it takes 10 sec to open first time, and momentarily next time, as expected. I suspect that youe issue is Windows 2008 specific.
Did you try preload feature?
Turning off the local firewall fixes the performance problem, but the "page not found" problem on first opening is still there. I can't get away anymore by saying to my colleagues the QlikView server is still sleeping in the morning and that you need to awake it first..
"Page not found" problem:
When you try to open a document the first time after you turned on your local system, a page not found error is shown, after refresh (of the page in IE) or a second try the document is normally opened. Some colleagues were even mentioning that is occurs multiple times a day, but I can't confirm that myself. It happens for sure the first time you open a QV document through the plugin in the morning, and on every local system. (so not only the first one that tries) Opening the Accesspoint page does not have this problem.
Does anybody know what causes the "page not found" problem and how it can be fixed?
Configuration: Windows 2008 Server x64 and QlikView Server 9 x86 (not x64 because lack of support of certain ODBC drivers)
Just a suggestion, instead of turning the firewall off completely just allow the following in the inbound rules as suggested by our network administrator.
I think that you would only really need to allow the qvwebserver.exe for the IE plugin to work quicker but by allowing these it has worked for us.
Support came back on the ie Plug in Issue which explains the Delay as Follows:
The communication between the Plugin client and the QlikView Server is transmitted over a protocol called qvp, which uses port 4747.
However, if this port is not open, the plugin will instead try to tunnel via port 80. This seems to be what is happening in your case, as you can access the documents fine, but with a delay.
If you would be using the AJAX client instead, all traffic will be sent via port 80.
Hope this sheds some more light on how things work!