The request channel timed out while waiting for a reply RRS feed

  • Question

  • I have several scopes in my project. In the development stage, the amount of data to be synchronized is smaller; I have never received timeout error.

    After I installed this project in the production server, it works fine when I tested one scope. But it failed when I tested three scopes. Do I have to make the thread sleep a while among scopes? 3 minutes for sendtimeout/receivetimeout are not long enough?

    There are a few topics in the forum, but they do not solve my problem.

    Here is the error message:

    “The request channel timed out while waiting for a reply after 00:02:59.9969998. 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 set MemoryDataCacheSize = 2K

    Here is my binding setup


            <binding name="reliableSessionOverHttps" sendTimeout="00:03:00" receiveTimeout="00:03:00">


                <readerQuotas maxDepth="32"






              <reliableSession />

              <httpsTransport  maxReceivedMessageSize="10485760" />



    By the way, I call SqlSyncProviderProxy.Dispose() when finishing a scope.

    I appreciate any feedback from you!



    • Edited by jz2012 Monday, March 25, 2013 4:09 PM
    Monday, March 25, 2013 4:05 PM


  • it all depends on how much changes you're trying to push on the service.

    as the error has already suggested, you should increase the timeout since it looks like its not enough for the sync to finish.

    am not sure how a thread sleep will help in your case.

    • Marked as answer by jz2012 Wednesday, March 27, 2013 8:52 PM
    Wednesday, March 27, 2013 1:01 AM