2013.2 StiWebDesigner 'timed out' error on all reports

[RossAFaneuf]

We are getting a 'Timeout response from the server' error when the report designer comes up; this happens for all reports, so the error does not appear to depend on the report itself.
- We had no problems with 2013.1, or pre-release versions of 2013.2 through 2013.08.05
- We have just installed 2013.2.
- There are no error details
- 'Loading Designer.fx' appears and reaches 100%
- The OnLoadReport event handler is called and completes successfully
- The server timeout is set to 10:00 minutes
- The 'Exit' operation does not work. It is impossible to close the designer.
- SteReportViewer seems to have no errors and works as before

Please suggest what to look at, as we cannot deploy 2013.2 in this state.

[RossAFaneuf]

Why is the Designer.fx progress indicator appearing? We are not using the FX component as far as I know.

[Vladimir]

Hello,

We could not reproduce the error on the new 2013.2 version. In the attached archive is test sample project. Please, make the corrections (options, properties) to reproduce this error.

LoadSaveDemo.zip

(296.88 KiB) Downloaded 216 times

Thank you.

[RossAFaneuf]

Your simple test report application works, but so far I have not been able to reproduce the error our main application generates.

I know it happens immediately after the 'Loading Configuration' progress box flashes up, but before it completes. The progress bar is only about 20% done. Does this suggest anything about where I should look?

Thank you

[RossAFaneuf]

I have been able to reproduce the error in your test case by adding this line:

Stimulsoft.Report.Web.StiWebDesignerOptions.Connection.ClientRequestTimeout = 3000000;

In our application code we were using an incorrect configuration setting with a very large number. The following does not cause an error, and fixes our problem:

Stimulsoft.Report.Web.StiWebDesignerOptions.Connection.ClientRequestTimeout = 300;

I assume the large value is truncated or something to 0

[Vladimir]

Hello,

No need to set such large values because in case of an error response will be expected to 3000000 seconds or about 34 days.
Rather, in the data transmission system classes, there is a limit on the maximum timeout value.

Thank you.