Retrieving operation Timeout error while updating user entity in CRM 4.0
-
Saturday, May 05, 2012 6:24 PM
Hi,
We often face operation time out errors while updating the users in crm 4.0. We have nearly 18,000 users in ms crm 4.0. We receive the updates for these user from another system and through our custom developed application we process these updates in the crm. while updating most of the times we receive operation time out error.Apart from the user we also udpate few other entity records like account, contact and .... We have configured our application to run every 3 hrs. Users in crm often browse the application all through the day.
To avoid these time out erros, what exactly we need to do. Any kind of suggestions are appreciated. Please help.
Thanks, Rajesh
- Edited by rajesh kumar Sunday, May 06, 2012 12:32 AM
All Replies
-
Sunday, May 06, 2012 7:27 AMAnswerer
Hi,
First we need to establish where the timeout is happening. 1. Inside your code (WCF or we reference). 2. Inside Crm when it calls SQL server. 3. A call to an external system.
Could you post the error message you get please.
Scott
Scott Durow
Read my blog: www.develop1.net/public
If this post answers your question, please click "Mark As Answer" on the post and "Mark as Helpful" -
Sunday, May 06, 2012 12:28 PM
Scott,
Thanks for the reply. Iam getting the time out error in my custom application while updating in CRM. Our application records all the data how many records got inserted and upated. Below is the error received in the log file
5/4/2012 12:00:22 PM - (INFO) GetAgent() - Inserts Started
5/4/2012 12:00:25 PM - (INFO) GetAgent() - Inserted VUE data into customdb
5/4/2012 12:00:25 PM - (INFO) GetAgent() - Get data from customdb and insert into CRM
5/4/2012 12:00:25 PM - (INFO) Records to be Updated :120
5/4/2012 12:10:50 PM - (ERROR) 5/4/2012 12:10:50 PM,SaveAgentInfo main Method:-The operation has timed outSaveAgentInfo,Line: 0,Column: 0,GetAgents
5/4/2012 12:10:50 PM - (FAILURE__) GetAgents()Agents Inserts FAILURE__SaveAgentInfo main Method:-The operation has timed out.Please suggest me.
Thanks, Rajesh
-
Sunday, May 06, 2012 8:55 PMAnswerer
Hi Rajesh,
This isn't the full exception- can you get the full exception details including the stack trace?
Scott
Scott Durow
Read my blog: www.develop1.net/public
If this post answers your question, please click "Mark As Answer" on the post and "Mark as Helpful" -
Sunday, May 06, 2012 9:49 PM
Scott,
Thanks for the reply. This is the full exception recorded in the log file. We didn't have more details other than this. When the process is upading the users in crm, and at the same time if users browsing the crm application, is there is a chance of time out and blocking exceptions. If both process run simultaneously.
Please help.
Thanks,
Rajesh
-
Sunday, May 06, 2012 10:05 PMAnswerer
Hi Rajesh,
It's hard to tell without the full exception.
The next thing to try is to look in the Event Logs on the CRM server to see if there is any more information. And if nothing, then you can turn on Tracing using the DiagTool : http://crmdiagtool2011.codeplex.com/
It could be a simple load issue where you are putting too much stress on your SQL Server and so it's timing out - also it could be a deadlocking issue with SQL transactions being co-dependant and so can't commit - and hence the timeout.
Scott
Scott Durow
Read my blog: www.develop1.net/public
If this post answers your question, please click "Mark As Answer" on the post and "Mark as Helpful" -
Sunday, May 06, 2012 10:10 PM
Scott,
Thanks for your time. I will try to look into the Event Logs on the CRM to find more information.
Thanks, Rajesh
-
Tuesday, May 08, 2012 2:45 AMModerator
Hello,
I have faced with this kind of issue. To make your update work without timeout exceptions you should increase your timeouts - http://support.microsoft.com/kb/918609 (I know that symptoms are not yours but the solution is the same).
Microsoft CRM Freelancer
My blog (english)
Мой блог (русскоязычный)
-
Tuesday, May 08, 2012 5:11 AMModerator
One possible issue is if the code is trying to update the user's business unit, their name or their emailaddress. If it does, then this incurs a significant number of SQL operations and a lot of locking.
If possible, the application should check which fields have changed, and only include the fields that have changed, rather than sending all fields. This could significantly reduce the amount of work CRM has to do, and hence avoid the timeouts
Microsoft CRM MVP - http://mscrmuk.blogspot.com http://www.excitation.co.uk
- Edited by DavidJennawayMVP, Moderator Tuesday, May 08, 2012 5:12 AM