We have a 3 Node NLB Windows 2003 IIS6. There is this report which craps out. It runs fine on a stand alone Windows 2003 IIS Server.
Our developers think its the NLB causing this report to break though all other reports are fine. These are small reports which run just fine but this issue with the report we are having is the biggest report and runs for long time. Developers say the default app pool recyling kicks in when the report is running and knocks it flat.
> Developers say the default app pool recyling kicks in when the report is running and knocks it flat.
Even if that were true, what's the relation with NLB? On a single host you would have the same problem. On top of that, an app pool cycle does not reset the TCP session, so the client cannot switch to another host anyway.
Maybe something else is going on, like a TCP session timing out?
Make it as simple as you can, but not simpler -- Albert Einstein