5/30/2023 0 Comments Import checkmark payroll to myobSo to know that it can be set up to sync to Outlook 2013 is helpful, but now to have to uninstall and reinstall to accomplish the task is a bit daunting to me (again I am a bookkeeper, bought Simply then Sage to do bookkeeping) and not a programmer or a computer guru. So I set it as my default email client, hoping this would rectify the MAPI problem and emulate the good old XP Outlook Express days, but low and behold it didn't. After having so many clients opt to electronic invoicing, decided it was time to set Outlook 2013 as my default mail client to see if this would rectify the double entry issue of sending electronic invoices via Sage 50. Months ago I though the issue was relative to Windows Live as my email client, so bought and installed Outlook 2013, set it up, but never set it as my default email client. When I said I was using Outlook 2013, the answer to that is yes and no. But last week having an extremely large number of clients opting to move to electronic invoicing and statements, found myself angry having to duplicate the work, especially when in the good old XP days, I could send electronic invoices to clients in my Simply client journal whether they were in my Outlook Express address book or not. Being of modest technical ability but with a desk full of work ALL OF THE TIME, decided to muddle through adding addresses to the Windows Live Mail address book as I added clients to my Sage Client Journal. Upgraded to Windows 7, obviously Outlook Express was no longer bundled, had to find a similar email client, so downloaded Windows Live Mail (with all of its issues) and immediately ran into the MAPI issue. To give some history, I have been using Simply for years on an XP machine with Outlook Express as my default mail as it was a simple component of XP. Thanks Keith, and Richard for also joining the thread (you are not taking it over, but asking some very important questions that have helped me understand the resolution of the issue). HKEY_LOCAL_MACHINE\Software\Microsoft\Office\15.0\Common\InstallRoot\Virtual\VirtualOutlookĬheck the Microsoft web link for additional information:.In order to verify the outlook 2013 32bit is using click- to-run edition which is Sage 50 not supported, please check the registry: If you see “OUTLOOK.EXE*32”, then it’s a 32-bit Outlook. Sage 50 works with Outlook 2013 32bit (not 64 bit or any click-to-run edition)Īn easy method to find the version of Outlook is to check the Task Manager – Processes. More information can be found in this article.Įmail MAPI error - An error occurred in resolving name If Live Mail is used, you will need to add the contact manually. There is no Sage 50 add-on toolbar to Windows Live Mail. However, if you have error regarding resolving name, syncing the customer list in Sage 50 with Outlook contact list can be used to troubleshoot the issue, so you do not need to enter the email manually to Outlook contact list one by one. You should not need to do that if you are using Outlook. I am running into this frustrating problem using both Windows Live Mail and Outlook2013. Now I know the guru's at Sage are going to say it is as a result of mail handling changes in Windows 7 and Windows Live Mail, but the end reality is that everyone is migrating to later o/s systems and it is time that Sage took the initiative and corrected this compatibility issue so THEIR SOFTWARE functions correctly. Very often we are sending a one off invoice and to have to create a record for the client in Sage including email address and then have to duplicate the email address in our email client contact list is really a pain in the butt and if I remember correctly was not required in an earlier version when we were running Windows XP with Outlook Express. It is so frustrating and unproductive that to be able to send an invoice, statement, etc via email, that first you have to add the designated receipient to your contact list in your email client otherwise receive a MAPI error message. does Sage 50 not work as its own outgoing email client.
0 Comments
Leave a Reply. |