Strange issue with a huge SSRS 2008 report (supposed to return 3 million records)

Question

Hi,
NOTE: The strange part (as mentioned in title) will come in the end.
I am running a SSRS 2008 report which fetches 3 million records from a remote server. After around 1 hour the report processing stops and I see an error icon on the lft bottom of the browser window. When I click on that to see the error details it shows
some PageRequestManagerSQLErrorException with an unknown error message with code 12029 (sometimes 12002).
When I see the reportserver logs there is an error message logged in it which says "Microsoft.ReportingServices.Library.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the
database is required for all requests and processing. ---> Microsoft.ReportingServices.Library.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for
all requests and processing. ---> System.InvalidOperationException: Timeout expired.  The timeout period elapsed prior to obtaining a connection from the pool.  This may have occurred because all pooled connections were in use and max pool size
was reached."
The <DatabaseQueryTimeOut> value in the report server configuration file is already having a value set to 7200 seconds(2 hours).
NOW, the strange part is, when I open the ExecutionLog2 table in ReportServer database, there is an entry for the same report with the status as "success" !!!
My head is spinning over this issue, somebody please rescue.
Regards.

Answer 1

Not sure if this will help but you might give it a try :
1. Open the Registry Editor.
2. Navigate to the registry path below.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\
3. Create a DWORD value MaxUserPort.
Value name
MaxUserPort
Value data (in Decimal)
10000
4. Restart the server.
5. Check and confirm that the registry key ‘MaxUserPort’ is added.
Do the same process as above for TCPTimedWaitDelay and reduce the value to 60.  The above steps are to increase the maxuserports and reduce the time_wait in order to free up resources on the server.