We have report that is quite large and causes timeouts for one of our offices not surprisingly the one with the most transactions.
So I started looking for the timeout configuration values and I must say Reporting Services has quite a collection of timeout values :-)
We do a nightly generation of PDF files through the means of the RS webservice and it was the call to the webservice that timed out. The behavior wasn't influences by any of the configuration values of Reporting Services. So I started digging deeper and came across the following solution.
Add base.Timeout = 3600 (in milliseconds) to the constructor of the ReportingServiceProxy class.