Link to home
Start Free TrialLog in
Avatar of Björn Maesen
Björn MaesenFlag for Netherlands

asked on

Dynamics CRM 4.0 plugin causes extremly many WER and high CPU

Hello,

I could not find anything in the database about my problem. The basics:

Software: Fresh installed Windows 7 Pro with SP1 and all updates, Office 2010, Dynamics CRM 4.0 Client with Rollup 19. Offcause there are many more programs like Acobat Pro 10, ELO, AccountView, etc.

Hardware: HP Workstation X400 with Vertex2 SSD, 6Gb RAM, ATI FirePro V4800

Symptoms: What happenes is that the desktop freezes from time to time. That's what's triggerd the user to call me.

Cause: Eventually I found out that the Dynamics CRM 4.0 plug causes this problem. Within minutes there are >150 WER processes running and an 8 core CPU (Xeon) has over 50% usage. Each second there are 70 WER entries added in the Application Log.

Workaround: Disable the CRM Dynamics Plugin in Outlook.

Done so far: Office Repair, Removed and re-installed latest Rollup 19.
Disabled all Synchronisation items in the options, Synchronisation tab
Removed and re-installed the Dynamics CRM 4.0 Client

Does anybody have any idea where to start? User generated image
Avatar of Björn Maesen
Björn Maesen
Flag of Netherlands image

ASKER

The fist Application Log Error:

Foutbucket 2103216970, type 5
Naam van gebeurtenis: CRMmanaged
Antwoord: Niet beschikbaar
Id van CAB-bestand: 0

Handtekening van probleem:
P1: 4.0.7333.3531
P2: OUTLOOK
P3: Microsoft.Crm
P4: Index (op nul gebaseerd) moet groter dan of gelijk aan nul zijn en kleiner zijn dan de argumentenlijst.;Hash='1814242234'
P5:
P6:
P7:
P8:
P9:
P10:

Bijgevoegde bestanden:
C:\Users\Secretariaat-1\AppData\Local\Temp\tmp766B.tmp

Deze bestanden zijn mogelijk hier beschikbaar:
C:\Users\Secretariaat-1\AppData\Local\Microsoft\Windows\WER\ReportArchive\NonCritical_4.0.7333.3531_88f2325b987e998b0764470b450da17512ad8c1_16b680c3

Analysesymbool:
Opnieuw zoeken naar oplossing: 0nRapport-id: aafe552b-f0ca-11e0-b4a1-643150444b24
Rapportstatus: 0
The second Application Log Error:

Foutbucket , type 0
Naam van gebeurtenis: CRMmanaged
Antwoord: Niet beschikbaar
Id van CAB-bestand: 0

Handtekening van probleem:
P1: 4.0.7333.3531
P2: OUTLOOK
P3: Microsoft.Crm
P4: Index (op nul gebaseerd) moet groter dan of gelijk aan nul zijn en kleiner zijn dan de argumentenlijst.;Hash='1814242234'
P5:
P6:
P7:
P8:
P9:
P10:

Bijgevoegde bestanden:
C:\Users\Secretariaat-1\AppData\Local\Temp\tmp7EF7.tmp

Deze bestanden zijn mogelijk hier beschikbaar:
C:\Users\Secretariaat-1\AppData\Local\Microsoft\Windows\WER\ReportQueue\NonCritical_4.0.7333.3531_88f2325b987e998b0764470b450da17512ad8c1_cab_0b6a7ec0

Analysesymbool:
Opnieuw zoeken naar oplossing: 0nRapport-id: ac495bd8-f0ca-11e0-b4a1-643150444b24
Rapportstatus: 4
Avatar of Chinmay Patel
Hi BGMServices,

Did you try to check the contents of the error log files
for example check what errors are mentioned in : Deze bestanden zijn mogelijk hier beschikbaar:
C:\Users\Secretariaat-1\AppData\Local\Microsoft\Windows\WER\ReportQueue\NonCritical_4.0.7333.3531_88f2325b987e998b0764470b450da17512ad8c1_cab_0b6a7ec0

Regards,
Chinmay.
The temp file says:
Exception generated at: 7-10-2011 12:37:50
Error Type: System.FormatException
Error Message: Index (op nul gebaseerd) moet groter dan of gelijk aan nul zijn en kleiner zijn dan de argumentenlijst.
Error Stack Trace: System.FormatException: Index (op nul gebaseerd) moet groter dan of gelijk aan nul zijn en kleiner zijn dan de argumentenlijst.
   bij System.Text.StringBuilder.AppendFormat(IFormatProvider provider, String format, Object[] args)
   bij System.String.Format(IFormatProvider provider, String format, Object[] args)
   bij Microsoft.Crm.Application.SMWrappers.CrmSqlCeDatabase.LookupValue(CrmSqlCeConnection connection, SqlCeTransaction transaction, String query, Object key)
   bij Microsoft.Crm.Application.SMWrappers.EmailIdMappingTable.AddEmailMapping(String messageId, String entryId, String crmId, String regardingId)

Stack Frame:

      at OutlookUtility.TraceReportException(String message, Exception exception)
      at EmailIdMappingTable.AddEmailMapping(String messageId, String entryId, String crmId, String regardingId)
      at ThreadProc.Invoke(IntPtr parameter)
      at ThreadsSupport.ExecuteThreadProc(ThreadProc threadProc, IntPtr parameter)

Does anyone have any clue? If not I suppose I have to test removing Office 2010 and install Office 2007 again.
Today I tried the following:

Removed Update Rollup 19 for Microsoft Dynamics CRM 4.0 (KB 2550097)
Removed Update Rollup 18 for Microsoft Dynamics CRM 4.0 (KB 2477777)
Removed Update Rollup 17 for Microsoft Dynamics CRM 4.0 (KB 2477746)
Removed Update Rollup 16 for Microsoft Dynamics CRM 4.0 (KB 2477743)
Removed Update Rollup 15 for Microsoft Dynamics CRM 4.0 (KB 2449283)
Removed Update Rollup 14 for Microsoft Dynamics CRM 4.0 (KB 2389019)
Removed Update Rollup 13 for Microsoft Dynamics CRM 4.0 (KB 2267499)
Removed Update Rollup 12 for Microsoft Dynamics CRM 4.0 (KB 2028381)
Removed Update Rollup 11 for Microsoft Dynamics CRM 4.0 (KB 981328)
Removed the Dynamics CRM 4.0 Client for Microsoft Outlook

Installed Microsoft Dynamics CRM 2011 for Microsoft Outlook client
Installed Update Rollup 5 for Microsoft Dynamics CRM 2011 (KB 2567454)

But.... while opening Outlook the CRM 2011 configuration screen pops up. After entering the server address http://crmsql-01-w2k8 an error pops up. The server address (URL) is invallid.

I guess the 2011 Client does not work with CRM 4.0 while the CRM 4.0 client does work with Dynamics 2011.

Removed Update Rollup 5 for Microsoft Dynamics CRM 2011 (KB 2567454)
Removed Microsoft Dynamics CRM 2011 for Microsoft Outlook client

Installed the Dynamics CRM 4.0 Client for Microsoft Outlook

to be continiued
ASKER CERTIFIED SOLUTION
Avatar of Björn Maesen
Björn Maesen
Flag of Netherlands image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Glad to hear that. Finally we are getting somewhere.
Still no high CPU and WERs reported after serveral months. Can't tell why, but after applying the Roll-updates it's still ok.