We had an interesting scenario the other day. A CRM 4.0 system that has been running fine for many months all of the sudden began to run slow on a specific workstation. The workstation had all the latest and greatest patches, tons of memory, IE 8, and windows 7.0. This was not a system wide or server issue, but clearly an issue with the specific workstations.
The Symptoms
Internet Explorer was running very sluggish when accessing the Dynamics CRM web site. Clicking from item to item sometimes took 3-10 seconds. All browser settings were correct and we had tried all the usually debugging methods: clearing the cache, rebooting, url is in trusted sites, etc, etc.
The Cause
After trying many things and getting close to just FDISK the workstation, we decided to try to turn off the AVG antivirus. This still did not help. However, in addition to disabling AVG also disabling its two Internet Explorer plugging did the trick.
Why is this strange?
This is very odd as we have other folks using the same version of AVG antivirus and accessing the same CRM system with no issues at all.
What to do now?
After doing a bit more research we are now recommending that if an antivirus has a url scanner, script scanner, (or some method of scanning web sites), the crm url should be added to a white list or bypass list.
This definitely appears to be the case McAfee and CRM 4.0
http://www.tekoppele.com/Blog/post/2009/05/20/McAfee-ScriptScan-Solution-for-Dynamics-CRM.aspx#comment
And now sporadically with AVG and CRM 4.0
I had the same issue with McAffe Total Protection AV. If I clicked on an Account the screen would display right away but the fields inside the account could take 5-10 seconds to display. I had to adjust the policies for Virus and Spyware protection. Under advanced setting there is a check box for “Enable script scanning” Once that was turned off CRM was zippy again.
A theme that is occurring on some but not all client(s). CPU outlook is high with crm 4.0. Have cleaned up emails; clear cache, etc. Could someone advise what are the “best practices” of what to expect with CPU for outlook with this application. In addition, what we may do to alleviate the pain…user(s) are frustrated…Thank you.