locked
SQL server time-out expired for MSCRM 2011 advanced find searches exceeding 2 min RRS feed

  • Question

  • Hi,

    My users have been getting SQL server time-out or 502 errors for advanced find searches exceeding 2 min.  The search criteria is only on Activity Description 'contains' operator.  Indexing on description field is not allowed and so the search time can be very long.

    We've increased all these time-out settings already but the issue still persists:

    - OLEDBTIMEOUT

    - NORMALTIMEOUT

    - EXTENDEDTIMEOUT

    - SANDBOXCLIENTOPERATIONTIMEOUTINSEC

    - SANDBOXHOSTOPERATIONTIMEOUTINSEC

    - SANDBOXWORKEROPERATIONTIMEOUTINSEC

    - KEEPALIVE

    - IIS EXECUTION TIMEOUT

    - SQLCommandTimeout in MSCRM_CONFIG database properties

    Are there any other timeout that is defaulted as 2 min and can it be overwritten?

    Thanks.
    Friday, August 8, 2014 3:25 AM

All replies

  • Hi Karen,

    To answer your question, no. we should not over ride the timeout to that extent & searching on activity table will always be slow since it has more number of records. that too on a description field if search is enabled and made then system is going to end up in performance issues due to index fragment cause of search & frequent DB maintenance and minimizing the sharing can help you to make the search faster. 


    If my response answered your question, please "mark the response as an answer" and also "vote as helpful". Regards, Hari. www.crm2011byhari.blogspot.com

    Tuesday, August 12, 2014 8:55 AM