MJ1100 CRM Outlook Plug-in encountered a problem during the operation, when trying to file emails from Outlook to Sage CRM 2020 with Office 365

SUGGESTED

MJ1100 CRM Outlook Plug-in encountered a problem during the operation.

My client keeps randomly receiving the above error when trying to file emails from Office 365 to Sage CRM 2020 R2. They are using both Outlook and Sage CRM from a Terminal server. Sage CRM is installed on their Application and Database server. The Terminal Server is Server 2019 Standard with 64GB of RAM. We just recently upgraded them and they moved to a hosted environment. Please see below if you need the exact version of Microsoft Outlook. 

I tried looking for error in knowledgebase and it does not specify MJ1100 and the posts are over 6 years old.

Thank you very much for your help!

Parents
  • 0

    I forgot to add that it will file the email in CRM but the Filed in CRM box does not appear on the email.

  • 0 in reply to suegeek

    Try adding the crm url to the Trusted Sites in Internet Explorer settings - I have had this resolve issues with the Outlook plugin in the past.
    Note if using a Terminal Server you'll need to do this for each user unless the setting is pushed to all users via group policy or similar.

    Mike

  • 0 in reply to mikeflannery

    Hi Mike, Thank for taking the time to reply. I will give this a try and let you know whether or not it works. Take care,

  • 0 in reply to mikeflannery

    I would always suggest this anyway due to when wanting to file the email against Opportunities / Cases the window that pops up is an IE window and not your default browser. I always 

    - In IE, in Compatibility View Settings deselect 'Display Intranet Sites in Compatibility View'
    - In IE, In Internet Options, add the CRM URL to Trusted Sites and then lower the security level for trusted sites (make sure you have trust sites selected) to it's lowest level. 

    This seems to resolve several issues around filing emails to opportunities / cases and might help here. (For those with Sage 200 integration this also helps with the Form Launching with Task Launcher as well) 

  • 0 in reply to suegeek

    Hi Mike, 

    The CRM URL was already added to the trusted sites. When you add the URL it just adds the hppt:\\servername not the rest of the URL.

  • 0 in reply to Matthew Shaw

    HI Matthew,

    Thank you for taking the time to reply. I had already did the above items and I am still receiving the error.

  • 0 in reply to suegeek

    Hi,

    Yes that's fine - once the base url is there it's good. One thing to note though if you are using standard port 80 to access CRM and configure the plugin the url to add would be http://servername

    If using https on port 443 for CRM and the plugin then the url to add would be https://servername

    You could just add both versions of the url to be sure.

    Only other thing I can think of is that IE is trying to install/activate one of the activex components it uses but can't - this could happen if the user does not have admin rights.

    Usually if I am installing the Outlook plugin on a terminal server I will do these steps.

    1. Make the user a local admin of the terminal server.

    2. Log on as that user to the server

    3. Install the plugin

    4. Do a test file of an email and make sure all is ok.

    5. If the test file is OK remove the admin rights.

    6. Log off the server and back on again as that user

    6. Do another test file to make sure all is still ok.

    Can you throw up a screenshot of that error as I've never seen it before.

Reply
  • 0 in reply to suegeek

    Hi,

    Yes that's fine - once the base url is there it's good. One thing to note though if you are using standard port 80 to access CRM and configure the plugin the url to add would be http://servername

    If using https on port 443 for CRM and the plugin then the url to add would be https://servername

    You could just add both versions of the url to be sure.

    Only other thing I can think of is that IE is trying to install/activate one of the activex components it uses but can't - this could happen if the user does not have admin rights.

    Usually if I am installing the Outlook plugin on a terminal server I will do these steps.

    1. Make the user a local admin of the terminal server.

    2. Log on as that user to the server

    3. Install the plugin

    4. Do a test file of an email and make sure all is ok.

    5. If the test file is OK remove the admin rights.

    6. Log off the server and back on again as that user

    6. Do another test file to make sure all is still ok.

    Can you throw up a screenshot of that error as I've never seen it before.

Children