In this webinar, our experts showcase a variety of demo use cases of how different components of the...
Once again we have been battling Microsoft CRM 4.0 and high CPU usage on the asynchronous process. This time it appear to have risen out of nowhere. Our quad core server went from 5% CPU usage all of the sudden to 100% CPU usage and workflows began taking 20 mins, then 30 mins, then not executing at all.
After a lot of debugging and many more gray hairs, we have found the cause....or in this case a bug caused by poorly designed workflows.
The issue is related to workflows that fire on deletion of a record AND try to check an attribute on the record. For example, this simple, yet poorly written workflow can cause havok.
Running this bad workflow on on lets say 3 contacts can cause a server to go from this:
Into this:
Run this bad workflow on 3 more contacts and we have this:
You can now image what happens if we were to delete 20 or 30 contacts thus causing this workflow to run 20 or 30 times. Havok and unhappy customers.
This is a bug and Microsoft is working on a hotfix. However, when researching this we did not find any info on newsgroups or blogs.
Let us know your thoughts.
Hi,
I think I have a solution for this if it's still is a problem.
/Anders
Hi Anders,
Yep - actually, microsoft is working on a fix. We are testing and it works good. The KB when published will be KB970016
It is possible that you write incorrectly de KB Number???
Hi Carlos,
That's the KB microsoft mentioned, but I don't think they have made the KB public yet.
I'll send you an email with the patches. We have patched our dev and qa environments, but not production yet. Testing it a big longer.
I am experiencing this same issue, I have been tracking it down for 2 days now. Please when will this be released?
Actually we have the same issue. Please can you tell me what I have to install to solve this issue?
Thank you.
The hotfix apparently has not been made public, but Microsoft will give it to anyone that request. Request KB970016 directly from Microsoft and it should solve the issue.
thx,
By any chance do you have the file for KB970016
?
You can get this hotfix from:
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=970016&kbln=en-us
Has Microsoft made this hotfix public for testing.Can it be applied in Prod enviornment.
http://support.microsoft.com/kb/970016
The Hotfix is now available to the public.