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.