Googling the error seems to point to javascript or cookies, not sure what else it could be, to be honest.

Hi,

Apologies for the delay, we've received a handful of calls around this error in the past couple of weeks. The issue is being actively investigated but we don't as of yet have a robust solution.

We have however collated a number of potential solutions that other partners have contributed as follows:

• Check if Workspaces work for this user.
• Run through the steps of Ask Sage Article 31313 even if Workspaces are working correctly for this user
• Check for failed Windows updates
• Ensure IE is a supported version and check browser settings to ensure that they are present and correct, particularly around
trusted sites as per the deployment guide
• Ensure a clear local temp folder
• IISRESET
• Check if IE has not installed properly (Repair IE or for whatever supported browser tool you are using)
• Add the self-service URL to Trusted Sites.
• Add the sage server to trusted sites

• If emailing set the communication method to Outlook within Report Designer

The last one seems to be pertinent to your case, we have seen MAPI communication being changed to Outlook has alleviated the symptoms described in a number of cases.

Lastly, as we are still actively investigating this issue could you please provide a copy of the Self Service logs to us on the support help line (0845 111 7733).

Thanks

Hi,

It looks as if a recent Microsoft Office update has caused this, this update was also producing 'Sage has stopped working' errors when trying to email correspondence from Sage 50 and Sage 200 programs. We already had a hotfix available for the 'Sage has stopped working' error and it has been confirmed this hotfix will also resolve the Script error.

Ask Sage article 37044 provides the steps to resolve this on each affected machine: ask.sage.co.uk/.../std_adp.php

The hotfix updates Sage.Email.dll to version 1.4.2017.1. You can check this by looking in C:\Windows\Assembly. Please ensure you follow the step to amend the email setting to Outook if currently set to MAPI.

Regards

Stu Mcalister

Hi Stu,

Thanks for the replies, had a feeling it might have been office related.

The only problem is I am unable to set these layouts from MAPI to OUTLOOK because I recently had to change them from OUTLOOK to MAPI to get around another issue that has been popping up on a lot of sites the "GENERIC COM" error when sending emails.

But I will try the hotfix and see if that works,
Thanks
Paul

Hi Paul,

The Generic Com error was part of the original issue that necessitated the hotfix when emailing documentation from Sage:

Issue 7112: Batch emailing via Office 365 - 2016 variant doesn't work

Potentially this may kill two birds with one stone for you.

Stu Mcalister

Hi Stu,

Sorry for delay in reply, thanks for your help, that worked perfectly.

The hotfix itself does not fix the script error - its switching back to Outlook that fixes the script error
But in turn the hotfix solved the Generic Com error.

So install Hotfix and switch layouts back to Outlook resolved it.

Thanks,
Paul

Hi Stuart Mcalister - it might be worth adding what Paul said on to the article as thats what worked for us on a call today.

Hi, I've fedback on the article to see if we can include this.

Stu

Cheers Stu, I knew I could count on you! :)

I checked in with a colleague and the article already makes mention of ensuring your setting is set to Outlook. Unless the article has changed since we reviewed it a few moments ago could you have a peek at it and let me know if any part of it needs clarified please?

Thanks Stu, it must have been cached, a swift Ctrl f5 and now it shows fully.