Update - I got the fixed AESCrypto.DLL file from Sage Support (Thanks Tony!) and it fixed the issue.   Please contact Support for the updated file, or check the Announcement for a possible update that provides the new file.

I already created the Article for the Resolution of the Error 5.  Unfortunately, I can't attach the fix file on the Article.  Customers need to contact Support for us to provide the fix file.  

Thank you,

TonyD

I already created the Article for the Resolution of the Error 5.  Unfortunately, I can't attach the fix file on the Article.  Customers need to contact Support for us to provide the fix file.  

Thank you,

TonyD

Tony,

This should dictate a new build of the 1099 update.

Something to consider is that users shouldn't be forced to burn a support case and wait for resolution of a potentially critical problem. Many accounting departments don't even start compiling their 1099s until the last week of January and some have learned to test and run this on the weekend so they can restore a backup, if needed, and so that no operations are interrupted.

The fix and any instructions could potentially be uploaded here, if the file(s) are not too large but not to have the ability to resolve this type of problem quickly whenever it is encountered is a disservice to the customer base.