Service | Customer Service, Contact Center, Fie...

SQL Server timeout expired. {1}{0}

(3) Share

Report

Posted on by JFCDL

Hello,

I am getting sql server timeout expired error from Microsoft Dynamic CRM online (Dataverse), every day, 4 or 6 times, and the application stop working, i wait a few seconds or minutes, and the app start working again, i see more frequently in appointments table, when i am creating or updating a record, but it happen too when i ma trying to chek info in a view. The app not have any plug in or work flow that can crash, just happen. If someone had some info about this issue, i will appreciate your help.

Categories:

Dynamics 365 Field Service

I have the same question (0)

All responses (3)

Answers (0)

Holly Huffman 6,530 Super User 2025 Season 2 on at

Like (0)

Report
Morning! Happy Friday :)

Apologies if you've already tried these. Here are some troubleshooting thoughts:

The error might be caused by long-running queries. Use the SQL Server Profiler to identify any queries that are taking too long to execute. Once identified, you can optimize these queries to improve performance.

You can increase the timeout settings in Dynamics 365. This can be done by modifying the OLEDBTimeout and ExtendedTimeout settings in the system registry. Be cautious when making changes to the registry and ensure you have a backup.

Ensure that your database is optimized. This includes regular maintenance tasks such as indexing, updating statistics, and checking for fragmentation. A well-maintained database can significantly improve performance and reduce timeout errors.

Keep an eye on the resource usage of your SQL Server. High CPU or memory usage can lead to performance issues and timeout errors. Use tools like SQL Server Management Studio (SSMS) to monitor and manage resource usage.

Network latency can also cause timeout errors. Ensure that there are no network issues affecting the connection between your Dynamics 365 instance and the SQL Server.

Although you mentioned there are no plugins or workflows, it's still a good idea to review any custom code or scripts that might be running. Inefficient code can lead to performance issues and timeout errors.

Hope this helps!

Was this reply helpful? Yes No
JFCDL 8 on at

Like (0)

Report

i forgot to mention, i m working with a model driven app.

Was this reply helpful? Yes No
Suggested answer

Community Member 33 on at

Like (1)

Report
There are some reasons for these as follows:

Check if any concurrent system jobs running in your system at the same time (Go to Advanced Settings -> System jobs)

The SQL Server instance is experiencing high load due to other operations or a large number of concurrent users, impacting the performance of Dynamics 365 queries.

Insufficient CPU, memory, or disk I/O on the SQL Server can lead to slow query execution.

Ongoing database maintenance tasks (e.g., backups, index rebuilds) can temporarily impact performance.

Delays or interruptions in the network connection between the Dynamics 365 application server and the SQL Server can cause timeouts.

Insufficient Timeout Values: The timeout settings configured within Dynamics 365 or related applications (e.g., Power BI, custom integrations) might be too low for the operations being performed.

Was this reply helpful? Yes No

Join the conversation

Community site session details

SQL Server timeout expired. {1}{0}

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > Service | Customer Service, Contact Center, Field Service, Guides

Featured topics

Product updates

Community site session details

SQL Server timeout expired. {1}{0}

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Service | Customer Service, Contact Center, Field Service, Guides

Featured topics

Product updates