Report timeout after 60 minutes

I'm running a long report from Reporting Services web site. When I run
the stored procedure by itself, it executes with no problem, taking
about 3 hours to complete. When I execute the report itself, it runs
for exactly 60 minutes and after that I get "The page can not be
displayed" message. I played around with session timeouts and report
execution timeout setting both of these to 5 hours, however that didn't
give any positive results. I'm beginning to think that it maybe some
IIS issue. I also increased the connection timeout in IIS to 5 hours.
Does anyone have any clues?
I'm running this on Windows 2000, IIS 5.
Thank you.
-IKI solved the problem myself. Looks like IE version 5.x and higher,
have 60 minute time-out limit.
A quick registry setting and a restart fixes the problem.
1. Add a ReceiveTimeout DWORD value with a data value of (<number of
seconds>)*1000 in the following registry key:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet
Settings
For example, if you want the timeout duration to be 8 minutes, set the
ReceiveTimeout data value to 480000 (<480>*1000).
2. Restart your computer.
You can find more info at:
http://support.microsoft.com/kb/q181050/
-IK|||hi IK,
one clarification.
need to set this on the server or on the client.
i am adjusting this setting on a comp connecting to the server and checking
this out.
would be quite a relief to get round this one.
thanks for your note,
SamK
"IK" wrote:
> I solved the problem myself. Looks like IE version 5.x and higher,
> have 60 minute time-out limit.
> A quick registry setting and a restart fixes the problem.
> 1. Add a ReceiveTimeout DWORD value with a data value of (<number of
> seconds>)*1000 in the following registry key:
> HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet
> Settings
> For example, if you want the timeout duration to be 8 minutes, set the
> ReceiveTimeout data value to 480000 (<480>*1000).
> 2. Restart your computer.
>
> You can find more info at:
> http://support.microsoft.com/kb/q181050/
> -IK
>sql