Environment: Windows 2012R2 Server, IIS 8.5
I have a classic .asp script which uses "wscrip.shell" to call an external .exe to create LARGE .zip files on the fly and send them to the client browser. While this process is running, other requests to the server are blocked (well they stay in the queue) but this is not acceptable for minutes. I already increased the maximum number of worker processes in the advanced settings of the application pool associated with the site. But like this, I loose my sessions, because they are tied to the worker process. A following page request could be processed by any of the worker processes and session state seems not to be shared amongst the worker processes. Thefore the user possibly looses it's session variables with each page request. Re-Designing the application without sessions would be possible but taking to long in actual emergency.
ANY BETTER SOLUTIONS?