C# Console Application - RunReport - CWS - Timeout

alan_otani@hna.honda.com

I am encountering a timeout error in a C# Console Application calling the RunReport method.

(Message: The request channel timed out while waiting for a reply after 00:01:00. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.)

I have increased the sendTimeout value in app.config, but still encounter the issue. Is there a different configuration item that needs to be addressed? If so, where does it reside and what modification is needed?

Find more posts tagged with

Comments

AKropp

Hi Alan,

Did a little poking around and found some similar posts over on StackExchange where setting it in app.config was not getting picked up. Sounds like for those folks setting it programmatically did the trick.

Some sample code from MS here:

https://docs.microsoft.com/en-us/dotnet/framework/wcf/feature-details/configuring-timeout-values-on-a-binding

So something like this may do it:

DocumentManagementClient docManClient = new DocumentManagementClient();

docManClient.InnerChannel.OperationTimeout = new TimeSpan(0, 30, 0); //30 minute timeout – adjust as you like

From: eLink Entry: Content Web Services Forum [mailto:otdncontentwebservices971forum@elinkkc.opentext.com]
Sent: Monday, January 15, 2018 12:06 PM
To: eLink Recipient <devnull@elinkkc.opentext.com>
Subject: C# Console Application - RunReport - CWS - Timeout

C# Console Application - RunReport - CWS - Timeout

Posted byalan_otani@hna.honda.com (Otani, Alan) On 01/15/2018 11:59 AM

I am encountering a timeout error in a C# Console Application calling the RunReport method.

[To post a comment, use the normal reply function]
Forum:	Content Web Services Forum
Content Server:	My Support

Nizar Ghazal

Hi Alan,

Make sure your web.config and app.config are setup, appropriately.

If you're using Visual Studio, you should see that you have an App.config file, under the Solution Explorer.

Open that up, and check to see what sort of sendTimeout, you may have configured.

For the ContentService, in the CWS sample code, we do provide an example on setting timeouts, in the following:

<binding name="BasicHttpBinding_ContentService" closeTimeout="00:01:00"
openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:10:00" .......

Since you're using RunReport, part of DocMan, and by our default, it doesn't configure anything else, in addition to just the default binding:

You could try to add a sendTimeout of 10 minutes.

Then, it'll look something like this:

Once that is set on the client-side portion, check to make sure you have an appropriate setting on the server's web.config (OTHOME\webservices\dotnet\Web.config):

In there, you could also add something like sendTimeout="00:10:00", to the above.

Take a backup of your web.config if you ever modify it, in-case you need to revert your development environment's bindings. You may also need to bounce IIS, to have it take effect.

Otherwise, give Alex's recommendation a try, and see if that works out as a cleaner solution.

Thanks.