locked
Getting timeout error when creating more than 2 organizations at same time using c# RRS feed

  • Question

  • Hey guyz, we have a program which helps us create CRM organizations on ouor on premise CRM Server and it is very much useful for us. Now we do this creating crm organization asynchronously so that user will be notified about the status of creation.

    but recently when I am creating more than 2 organizations, one or two of them fails and i get the below exception.

    The request channel timed out while waiting for a reply after 00:01:59.9970669. 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.

    Does any one know what is wrong here??

    Friday, January 24, 2014 10:03 AM

All replies

  • Hi,

       Refer to following article to increase the time out valueL

    http://stackoverflow.com/questions/14760228/how-to-increase-the-sendtimout-value-on-the-binding

    http://blogs.msdn.com/b/hongmeig/archive/2010/03/06/timeouts-in-wcf-and-their-default-values.aspx

        There are a lot of reasons why you could be getting timeout errors. May be performance.


    Hope this helps.
     
    -----------------------------------------------------------------------
     Minal Dahiya
    blog : http://minaldahiya.blogspot.com.au/

     
    If this post answers your question, please click "Mark As Answer" on the post and "Vote as Helpful"

        

    Friday, January 24, 2014 10:54 AM
  • The error message says the timeout was less than 2 minutes.  It looks like someone may have already put an OLEDBTimeout and or ExtendedTimeout key(s) in place in the registry.  You definitely need to look in the registry and either increase the time or remove them.

    It is not recommended to keep the OLEDBTimeout and ExtendedTimeout keys in the registry.  They are only intended to get past a specific issue and nothing more.  Leaving the keys in place can cause issues down the road.  Presumably like you are seeing now.


    Jason Peterson

    Tuesday, January 28, 2014 12:25 PM
  • This error is a WCF (web service call) timeout, rather than a SQL one, so OLEDBTimeout won't help

    My suspicion is that the ultimate cause is some locking (probably SQL in MSCRM_Config, but maybe in the CrmDeploymentService code), with the creation of one organisation blocking the creation of the other. If that's the case, then you'd need to increase all timeouts (SQL and WCF) to a period longer than the typical time to create a new organisation.

    However, how important is it to be able to create multiple organisations in parallel ? It may be easier to either live with this, or to modify you application to create organisations in series


    Microsoft CRM MVP - http://mscrmuk.blogspot.com/ http://www.excitation.co.uk

    Wednesday, January 29, 2014 1:25 PM
    Moderator