sql server reporting services: I'm having a deployment timeout failure on one report. (after about 2
minutes) Other reports on the same project succeed, so I know I have URL and
security logins correct.

This report does have more components than most (13 tables and that many
data sets), so it probably is bigger than most.

Can you tell me where to increase the deployment timeout?

You can specify time-out values to set limits on how system resources are
used. Report server supports two time-out values:

a.. A query time-out value is the number of seconds that the report server
waits for a response from the database. This value is defined in a report.


b.. A report execution time-out value is the maximum number of seconds
that report processing can continue before it is stopped. This value is
defined at the system level. You can vary this setting for individual
reports.


Most time-out errors occur during query processing. If you are encountering
time-out errors, try increasing the query time-out value. Make sure to
adjust the report execution time-out value so that it is larger than the
query time-out. The time period should be sufficient to complete both query
and report processing.


--
Andy Potter
blog : http://sqlreportingservices.spaces.live.com
info@(NOSPAM)lakeclaireenterprises.com
[quoted text, click to view]

I dont think there is something like deployment timeout. I think something is
going wrong that's why it is not gettting deployed.

Is this report builds without any problem. check for any errors. Basically
deploying is nothing but encrypts and puts it in the target server database.
So check for any access issue and the server is running.

change the targetURL and deploy it in some other server and see whether it
works.

Amarnath

[quoted text, click to view]