Hi John, I haven't been on this forum before. I am joining in a last gasp to see if I can get anywhere. I am using Sage 50 Cloud accounts and since updating from Version 24 to Version 27 it freezes within a minute of trying to do anything. I have wasted hours forcing shutdowns and on several live chats with Sage people - just can't work like this. It has jus frozen again after 1 recorded transaction - sorry I can't help but It is nearinmg month end and I'm running out of options

Hi Again John, I am bneginning to wonder if it is worth deleting Version 27 and reloding Version 24. Version 24 at least worked?

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.

This has got to be related to the fact that Sage (for some odd reason) is still running it's software at 32bit when the rest of the world has moved on to 64bit. 

We are having issues sending emails now. We have the 32bit version of Outlook 2013 but have been advised not to install 32bit of 365. If we install the 64bit then it won't work with Sage.

Honestly, Sage should be prioritising moving over to 64bit.

It's nothing to do with 32bit Vs 64bit in this case. From my initial research it looks to be related to a 3rd party component we are using to interact with Outlook. this was introduced to avoid the poor user experience created through the heavy-handed security changes that that Microsoft added to Outlook several years ago. I'm still investigating an exact root cause but can confirm it's not a 'bitness issue'.

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.