Hi John

We upgraded to version 28 on Monday evening and since then we can no longer email reports from Sage.  We also get the same error.  I was told to change report settings to MAPI but after trying that it doesn't seem to work on some of them - I still get the same error.

I'm not an email expert so this is really time consuming to try and sort out a solution.  

What is the full error message you are getting in the Windows Event Log? Also is it a 64bit or 32bit version of Outlook you are using?

Hi Darren

It's 32 bit Outlook (2016 edition) and the windows event log message is:

Error sending email using Outlook  : System.NullReferenceException: Object reference not set to an instance of an object.

   at Sage.Email.RedemptionLoader.NewRedemptionObject(Guid guid)

   at Sage.Email.RedemptionLoader.new_SafeMailItem()

   at Sage.Email.Outlook.OutlookMailer.SendMailInternal(Email email, SendMailOption whenToSend)

   at Sage.Email.Outlook.OutlookMailer.SendMail(Email email, SendMailOption whenToSend)

I have a case raised with support, but they've not found a solution yet.

I've investigated the problem and have identified an issue in the code that will be causing the problem, and it is the interaction with the 3rd party component we use as per my other post. Fixing it will require changes to the code and a new version. I can't provide any ETA on when this might happen at the moment (I'll post back as soon as I hear more on this).

In the meantime there is a mechanism available to disable our use of the 3rd party component and go directly to Outlook. I've tested this and it works well, resolving the error that you are seeing. To apply this simply copy this file 1drv.ms/.../s!ArHsmj4Ox6v-hGVDpMCWZgcOimiM to your v28 Accounts install folder (by default this will be C:\Program Files (x86)\Sage\Accounts). You will need to close/reopen Accounts for the setting to take effect but afterwards things should just work as they did previously with no special action.

Hope that helps.

Hi Darron

Thanks for the file, that seems to have worked for us which is a massive help.  Good to know it should be addressed on a future version update.

Thanks for your help with this issue.

A brief update on this - it is looking like the code changes will be included in the v28.1 release due out in the new year. In the meantime if anyone else encounters this error the above file should sort the issue out.

A brief update on this - it is looking like the code changes will be included in the v28.1 release due out in the new year. In the meantime if anyone else encounters this error the above file should sort the issue out.

We just upgraded from v27 (which was working perfectly) to v28. We are now experiencing the above issue. 

The above config file and instructions should work to resolve the issue for now. The v28.1 release with the proper fix in it and you will not need the config file for that (although it will do no harm if you leave it there after installing v28.1). Don't have an exact date for the release of v28.1 yet but I believe it is around the April timeframe.