locked
Crm 3 addin problem.. cant promote to crm, no toolbar in new message RRS feed

  • Question

  • Hi there,

    When I click track in crm i get this: "An error occurred promoting this item to Microsoft CRM
    There is no toolbar for CRM showing in New messages
    In my event viewer i see this: Source: CRMAddin, eventid: 5971, Description: A problem occurred initializing Microsoft CRM COM interop.  Restart Microsoft CRM and try again. HR=0x80131509. Context=. Function=CAddin::PrepareInterop. Line=1599.

    I have searched the error message and found some things about rich text and clearing forms cache and temp files, this doesnt seem to apply to my problem and I have tried these resolutions unsuccessfullly.

    I am running outlook 2007, and have tried a clean install and with office sp2 and then sp3, I have reinstalled the outlook crm client. The user account I am trusting this with is set in CRM roles as System administrator and has no problem accessing crm via web site or in outlook tree view. The only issue seems to be the addin fails to work anymore. I have also tried this on a fresh installs of xp sp3.... 

    I have a few machines where it work fine but on all my new installations it is broken..  

    If anyone can shed some light on this I will be truly grateful!
    • Moved by ashawani_dubey Wednesday, March 31, 2010 2:52 AM user Forum Merge (Feladó:Microsoft Dynamics CRM)
    Tuesday, August 18, 2009 1:09 AM

Answers

  • Turns out it was my proxy server causing the issue!!    I had to add an exception to the auto config file..   Thanks for all your help though.
    • Marked as answer by k2k9000 Wednesday, October 21, 2009 6:13 AM
    Wednesday, October 21, 2009 6:13 AM

All replies

  • Hi there,


    Browsing your letter now it is clear - you have problem with MSCRM outlook client right?
    MS Office 2007 has no sp3 till this time - probably you thought outlook 2003 sp2, sp3 ? You might hurry...
    There could be several causes of this problem - beginning from a wrong isv.config - to unsupported customization and different outlook and crm languages.

    Please try the following:

    -  install latest rollup package on client machines as well

     - test the installation with office 2003 sp2 with the same crm, office and xp language. This problem sourced mostly because of different outlook/crm languages.

    - don't use ms word as a default word processing eidtor in ms outlook

    - reinstall msxml 4.0 sp2 on faulty client computers (restart needed)

    - export isv.config on the server and check that the first line is: <?xml version="1.0" encoding="Windows-1252"?>

    - crmaddin.dll disabled
    On the Help menu, click About Microsoft Office Outlook. 
    Click Disabled Items.
    In the list, click Addin: Microsoft CRM Outlook Addin (crmaddin.dll), and then click Enable.

    Good luck !
    SzT
    Tuesday, August 18, 2009 7:01 AM
  • Hi Thanks for your reply,  I ma using outlook 2007 i mean sp1 and sp2 , sorry about that...

    I have treid all of these suggestions with no joy, I did initally have an isse with default input langugae defaulting to Us english and the CRM server being Australian English but after a clean install I still have the same problems.
    Wednesday, August 19, 2009 2:47 AM
  • Hi,

    Please check the Crm server installation localization instead of server local settings.
    In terms of Crm 3.0 crm server program was localized - and there was no facility to install language packs. You should check crm server software language and localization.
    Please verify your client side office product against the correct language and localization.
    For example if your crm server installed with language EN-US, and your office by default is EN-AU or EN-NZ, etc. - you might have problems.

    IF your server installation is an EN-US crm server, use EN-US office without any language packs as your Office. You should use Windows XP EN-US as well as a client OS.

    Please check those client environments carefully where no problem raised.
    - What's the difference bw. working environment localization and non-functional clients?
    - what is the difference in cases msxml 4.0 sp2 version/build number on working and non-working computers/clients?
    - had the latest rollup been installed on server and clients as well?


    Regards,
    SzT
    Wednesday, August 19, 2009 12:57 PM
  • Turns out it was my proxy server causing the issue!!    I had to add an exception to the auto config file..   Thanks for all your help though.
    • Marked as answer by k2k9000 Wednesday, October 21, 2009 6:13 AM
    Wednesday, October 21, 2009 6:13 AM