Hi Collin, 

We are having a client that just moved to Sage 2017 and now are having this same issue. Did you ever get it resolved or find out any further information? 

Hi Rene,

No, never found a solution for it, despite the updates Sage issued. It seemed to work when it chooses, so I simply left it alone. Looked back it ever so often, but no solution.

The solution I have so far and its not perfect, is run Sage 300 as administrator (tick the box under properties) and also run outlook as administrator. So go to the folder where the outlook exe is on your local drive make a shortcut of it and tick the box "run as administrator". You can the also use this shortcut to Pin on the taskbar.

Problem is...

What is running as administrator is not allowed.

Can Sage 300 developers please look into this because this is very annoying. 

We are having the same issue and it only happen after this particular workstation perform recent Windows Update. It work after both Sage 300 & Outlook Run as Administrator but it's not the final solution.

The rest of 10 workstations with the same windows & Ms. Office version have no issue. 

Does anyone found the issue and solution for this type of case?

Sorry to bring this back from the dead but has anyone found a solution to this?  I'm seeing it on Sage 300 2019 with Outlook 2016.  It's intermittent, we will be fine for days and then it will happen again.  We have another identical system that was set up at the same time that doesn't have this error.  I have removed Office and put it back.  I have removed Adobe and put it back. There is only one email profile. It happens on a variety of emails but never consistently so it's not incorrect characters. It does look like if I run the Microsoft .NET Framework Repair Tool after things stop working, they will start again, but I can't guarantee that's the fix and not a weird coincidence at this point.  I see that some people have had luck with running Sage and Outlook as Administrators so I'm going to try that and see.

I am having this issue with Sage 300 2020. It launches outlook on one but not on the other. 

Same issue here. Love to hear if anyone has solved this.

We totally solved it for our use case. Here is what happened. The Lenovo workstations with the failure had office 365 stub loaded. So, you could launch it and download it and license it. But the client didn't want to handle office that way, instead, they bought office 2019 and licensed it per workstation. (The old school way). So, there were actually 2 outlooks installed according to the registry. Sage 300 launched the stub version of outlook which failed, not having been fully installed, instead of the "real" version. Fully uninstalling the stub version fixed the problem. Many PC mfr's will preload windows with this bloatware, and Lenovo is one of them. I can't tell you how irritated we all were when we figured it out. 

Thanks Peter. Our issue is with a workstation in France. It seemed to have two versions of office 365 on there. Removing one did not make a difference unfortunately. We have also worked out, that as long as Outlook is closed when exporting to Microsoft mail it will work properly and open an outlook email message (which wont send until Outlook is actually opened).  

However if the user already has Outlook open it doesn't work and we get some older looking accpac send mail box.

We set up another user on the same PC and everything works fine. Next step is to kill and recreate the users desktop profile, which will hopefully reset all MAPI registry settings for that user, but i have to wait until they awake and give me permission.

And if any of this doesn't make sense, my apologies, I am only the finance guy, not the IT guy!

6 months has gone past and we had another user come up with this problem. Given we didn't solve it for the first one, we had to look at it again.

The root of the problem is that we have to set our users to run Sage as administrator (due to a customization that only works if this is the case).  

As we now understand given Sage is running as administrator, Outlook sees it as a different user and therefore does not allow the email to be created (unless Outlook was already closed in which case it opens as administrator).

So the workaround is to set Outlook to also run as administrator and then it seems to all be ok.

However this is only a work around. The true problem is the Sage 300 customization that requires Sage to be run as administrator. We will look to solve that by getting rid of that customization!, and come up with a different one that doesn't require Sage to run as administrator.

We found a different workaround for custom screens and Ops Inquiry.

• Export/backup [HKEY_CURRENT_USER\Software\ACCPAC INTERNATIONAL, INC.\ACCPAC]
• Verify this backup looks correct (in Notepad)
• Delete that registry key
• Export [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ACCPAC International, Inc.\ACCPAC] to a different file
• Search and replace HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ACCPAC International, Inc.\ACCPAC with HKEY_CURRENT_USER\Software\ACCPAC INTERNATIONAL, INC.\ACCPAC and save it as HKCU-New.reg (or something like that)
• Import this new key
• Test

Please note: Follow these steps at your own risk. If you don't feel comfortable with any part of the above, please contact your business partner or IT professional to assist.

Nice catch on the user discrepancy between Outlook and Sage user.
Note that if the Sage user is given adequate permission to the Sage share AND the Sage 300 branch of the registry, running Sage 300 as administrator should not be required - it should serve more a a diagnostic approach to confirm that user security is set as required.
1. Ensure user has full permissions to the Sage shared data folder and at least read permission for the programs
2. Ensure the user has full permissions to the following registry trunk;
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ACCPAC International, Inc.\ACCPAC