locked
Outlookclient 2015 - Only items in the default Microsoft Outlook store can be promoted to Microsoft CRM RRS feed

  • Question

  • Hi,

    a colleague of mine has troubles with the outlook client and CRM 2015. The Following error keeps popping up each time he starts outlook.

    “Nur Elemente, die sich im Standardspeicher von Microsoft Outlook befinden, können zu Microsoft CRM heraufgestuft werden. Elementname=…“

    The corresponding error message in english should be:

    Only items in the default Microsoft Outlook store can be promoted to Microsoft CRM. Itemname=…”

    I did some google research…all the know issues are about multiple mailboxes and so on…

    We definitely don’t have multiple mailboxes configured and the issue didn’t occur directly after installation/setup. It went well without any problem over months. But since last week, my colleague has got multiple popups with the above message (and different Itemnames).

    I don’t know if it is possible, but my assumption is that the E-Mails are deleted form outlook, bevor the upload to CRM-Server has finished. If this is the cause it is really a big problem, because he lost all the deleted mails, which should be in CRM.

    Does anyone know what’s going wrong there? We already did a reinstallation of the outlook-client, but the error occurs again.

    Best regards

    Klemens


    Wednesday, July 29, 2015 6:43 AM

Answers

  • Hi,

    as wrote in my last post, I opened a Microsoft-Case. Luckily we have been able to fix the issue. It was a bit tricky, because there where especially old emails (from year 2012...) which actually where tracked in CRM but not marked as successfully synchronized in CRM.

    You can this in Outlook if you navigate to the developer-ribbon and open the emails draft-form. There usually you should have a tab called "All fields". The important field is the crmState, which can following values:

    • 0 - not synchronized
    • 1 - marked for sync
    • 2 - succefully syncronized

    In our case, all the corrupted mails were marked as 1 although they are already in the CRM. Every start-up of outlook the client tried to sync these items again, which throws an error because CRM already has the items.

    So we deleted all these items, and all works fine so far (instead you can set the crmState manually to 2, which will have the same effect)

    Due to the Microsoft-support-engineer, this is a known issue in previous versions of CRM. We don’t know why it happened in this version and why we didn’t observe this behaviour before.

    However know it works ;)

    Many thanks for your input and advises

    Kind regards

    Klemens

    • Marked as answer by k.duschlbauer Thursday, August 13, 2015 5:02 AM
    Thursday, August 13, 2015 5:02 AM

All replies

  • Hi Klemens,

    first trace both server and client same time and provide more details about your deployment.

    Is the clients Outlook using exchange? Maybe cached-mode off?

    Did you recreated the PST/OST (outlook datafile) ? Also create a new mail profile.

    Also correct if the mail was deleted before uploading then logical to tell that CRM cant upload if the mail is not present.


    gruss Daniel Ovadia MBSS - Microsoft Dynamics CRM MCNPS

    Wednesday, July 29, 2015 7:37 AM
  • Hi Daniel,

    I did some tests: changed chached-mode, recreated datafile, reconfigure CRM-Client,.... but nothing changed.

    But I think I will open an microsoft-Support-case.

    a snippet of the Client trace is as follows:

    >crm id :'', Error:Das ausgewählte Element kann nicht in Microsoft Dynamics CRM nachverfolgt werden.
    [2015-07-24 08:52:12.036] Process:OUTLOOK |Organization:4efa07ef-eaee-498c-96c3-9b4c35cb74ba |Thread:   34 |Category: Application.Outlook |User: 00000000-0000-0000-0000-000000000000 |Level: Warning |ReqId: 00000000-0000-0000-0000-000000000000 |   ilOffset = 0xFFFFFFFF
    > Exception: System.Runtime.InteropServices.COMException (0x80040203): Resource not found(-2147221067).
       bei Microsoft.Crm.Application.SMWrappers.ResourceForOutlook.Microsoft.Crm.Application.SMWrappers.IResourceForOutlook.GetString(Int32 id)
    [2015-07-24 08:52:12.036] Process:OUTLOOK |Organization:4efa07ef-eaee-498c-96c3-9b4c35cb74ba |Thread:   34 |Category: Application.Outlook |User: 00000000-0000-0000-0000-000000000000 |Level: Error |ReqId: 00000000-0000-0000-0000-000000000000 | ProgressDialogForOutlook.Microsoft.Crm.Application.SMWrappers.IProgressDialogForOutlook.SetDetailedErrorMessage  ilOffset = 0x19
    	at ProgressDialogForOutlook.Microsoft.Crm.Application.SMWrappers.IProgressDialogForOutlook.SetDetailedErrorMessage(String entityType, String entityName, Boolean warning, String errorMessage, String entryId, String storeId, String crmId, Int32 entityObjectTypeCode, Boolean showDialog)  ilOffset = 0x19
    >crm id :'', Error:Das ausgewählte Element kann nicht in Microsoft Dynamics CRM nachverfolgt werden.
    [2015-07-24 08:52:12.036] Process:OUTLOOK |Organization:4efa07ef-eaee-498c-96c3-9b4c35cb74ba |Thread:   34 |Category: Application.Outlook |User: 00000000-0000-0000-0000-000000000000 |Level: Warning |ReqId: 00000000-0000-0000-0000-000000000000 |   ilOffset = 0xFFFFFFFF
    > Exception: System.Runtime.InteropServices.COMException (0x80040203): Resource not found(-2147221067).
       bei Microsoft.Crm.Application.SMWrappers.ResourceForOutlook.Microsoft.Crm.Application.SMWrappers.IResourceForOutlook.GetString(Int32 id)
    [2015-07-24 08:52:12.052] Process:OUTLOOK |Organization:4efa07ef-eaee-498c-96c3-9b4c35cb74ba |Thread:   34 |Category: Application.Outlook |User: 00000000-0000-0000-0000-000000000000 |Level: Error |ReqId: 00000000-0000-0000-0000-000000000000 | ProgressDialogForOutlook.Microsoft.Crm.Application.SMWrappers.IProgressDialogForOutlook.SetDetailedErrorMessage  ilOffset = 0x19
    	at ProgressDialogForOutlook.Microsoft.Crm.Application.SMWrappers.IProgressDialogForOutlook.SetDetailedErrorMessage(String entityType, String entityName, Boolean warning, String errorMessage, String entryId, String storeId, String crmId, Int32 entityObjectTypeCode, Boolean showDialog)  ilOffset = 0x19
    >crm id :'', Error:Das ausgewählte Element kann nicht in Microsoft Dynamics CRM nachverfolgt werden.
    [2015-07-24 08:52:12.052] Process:OUTLOOK |Organization:4efa07ef-eaee-498c-96c3-9b4c35cb74ba |Thread:   34 |Category: Application.Outlook |User: 00000000-0000-0000-0000-000000000000 |Level: Warning |ReqId: 00000000-0000-0000-0000-000000000000 |   ilOffset = 0xFFFFFFFF
    > Exception: System.Runtime.InteropServices.COMException (0x80040203): Resource not found(-2147221067).
       bei Microsoft.Crm.Application.SMWrappers.ResourceForOutlook.Microsoft.Crm.Application.SMWrappers.IResourceForOutlook.GetString(Int32 id)
    [2015-07-24 08:52:12.052] Process:OUTLOOK |Organization:4efa07ef-eaee-498c-96c3-9b4c35cb74ba |Thread:   34 |Category: Application.Outlook |User: 00000000-0000-0000-0000-000000000000 |Level: Error |ReqId: 00000000-0000-0000-0000-000000000000 | ProgressDialogForOutlook.Microsoft.Crm.Application.SMWrappers.IProgressDialogForOutlook.SetDetailedErrorMessage  ilOffset = 0x19
    	at ProgressDialogForOutlook.Microsoft.Crm.Application.SMWrappers.IProgressDialogForOutlook.SetDetailedErrorMessage(String entityType, String entityName, Boolean warning, String errorMessage, String entryId, String storeId, String crmId, Int32 entityObjectTypeCode, Boolean showDialog)  ilOffset = 0x19
    >crm id :'', Error:Das ausgewählte Element kann nicht in Microsoft Dynamics CRM nachverfolgt werden.
    [2015-07-24 08:52:12.068] Process:OUTLOOK |Organization:4efa07ef-eaee-498c-96c3-9b4c35cb74ba |Thread:   34 |Category: Application.Outlook |User: 00000000-0000-0000-0000-000000000000 |Level: Warning |ReqId: 00000000-0000-0000-0000-000000000000 |   ilOffset = 0xFFFFFFFF
    > Exception: System.Runtime.InteropServices.COMException (0x80040203): Resource not found(-2147221067).
       bei Microsoft.Crm.Application.SMWrappers.ResourceForOutlook.Microsoft.Crm.Application.SMWrappers.IResourceForOutlook.GetString(Int32 id)
    [2015-07-24 08:52:12.068] Process:OUTLOOK |Organization:4efa07ef-eaee-498c-96c3-9b4c35cb74ba |Thread:   34 |Category: Application.Outlook |User: 00000000-0000-0000-0000-000000000000 |Level: Error |ReqId: 00000000-0000-0000-0000-000000000000 | ProgressDialogForOutlook.Microsoft.Crm.Application.SMWrappers.IProgressDialogForOutlook.SetDetailedErrorMessage  ilOffset = 0x19
    	at ProgressDialogForOutlook.Microsoft.Crm.Application.SMWrappers.IProgressDialogForOutlook.SetDetailedErrorMessage(String entityType, String entityName, Boolean warning, String errorMessage, String entryId, String storeId, String crmId, Int32 entityObjectTypeCode, Boolean showDialog)  ilOffset = 0x19
    >crm id :'', Error:Das ausgewählte Element kann nicht in Microsoft Dynamics CRM nachverfolgt werden.

    Friday, July 31, 2015 6:17 AM
  • you may try to create a second datafile for outlook and reconfigure the client. also an office repair or upgrade to another version often helps. 

    A case for just one computer and a local issue? Is this error on other machines present also?


    gruss Daniel Ovadia MBSS - Microsoft Dynamics CRM MCNPS

    Friday, July 31, 2015 7:12 AM
  • Hi,

    as wrote in my last post, I opened a Microsoft-Case. Luckily we have been able to fix the issue. It was a bit tricky, because there where especially old emails (from year 2012...) which actually where tracked in CRM but not marked as successfully synchronized in CRM.

    You can this in Outlook if you navigate to the developer-ribbon and open the emails draft-form. There usually you should have a tab called "All fields". The important field is the crmState, which can following values:

    • 0 - not synchronized
    • 1 - marked for sync
    • 2 - succefully syncronized

    In our case, all the corrupted mails were marked as 1 although they are already in the CRM. Every start-up of outlook the client tried to sync these items again, which throws an error because CRM already has the items.

    So we deleted all these items, and all works fine so far (instead you can set the crmState manually to 2, which will have the same effect)

    Due to the Microsoft-support-engineer, this is a known issue in previous versions of CRM. We don’t know why it happened in this version and why we didn’t observe this behaviour before.

    However know it works ;)

    Many thanks for your input and advises

    Kind regards

    Klemens

    • Marked as answer by k.duschlbauer Thursday, August 13, 2015 5:02 AM
    Thursday, August 13, 2015 5:02 AM