x Want to participate? Join the group to interact
  • State Not Answered
  • Replies 20 replies
  • Subscribers 119 subscribers
  • Views 1216 views
  • Users 0 members are here
Browse Forums
Announcements
268
topics
260
replies
Databases and Operating Systems
758
topics
2k
replies
Financials Suite
1k
topics
3k
replies
General Discussion
2k
topics
10k
replies
Operational Suite
851
topics
2k
replies
Reporting and Analytics
1k
topics
3k
replies
Reports, Macros, and Customizations
876
topics
3k
replies
Sage CRM for Sage 300
182
topics
410
replies
laushandy

Sage 300 2024 Encountered Error Code: 5 during FR Financial Statements Printing

Posted By

Hi,

Did anyone encountered the same error code when print Financial Statements in Sage 300 2024? 

After clicked OK button, the report still works fine. Why is there an error code shown after click Preview button?

Client is using Microsoft Excel 2016 64bit. All workstation PCs at client's site are encountering the same error msg. However, the same FR report is working fine at our office.

Kindly advise what could be the cause of this error?

Thanks in advanced.

Regards,
Shandy

Top Replies

Parents
  • 0

    Hi  we have found a workaround but its not ideal - uninstalling Microsoft 365 64-bit from workstations and Office Access Database 64-bit (v2016) components then re-installing Microsoft 365 32-bit instead resolves the error.  I know its not ideal to have to switch back to 32-bit Office and some sites are particularly against it (as I've experienced in the past) but it is a workaround I've confirmed works and have informed Sage support.  The issue somehow appears to be server side in 2024 PU1 so hopefully the Dev or Support teams at Sage will come up with a permanent solution soon.

Reply
  • 0

    Hi  we have found a workaround but its not ideal - uninstalling Microsoft 365 64-bit from workstations and Office Access Database 64-bit (v2016) components then re-installing Microsoft 365 32-bit instead resolves the error.  I know its not ideal to have to switch back to 32-bit Office and some sites are particularly against it (as I've experienced in the past) but it is a workaround I've confirmed works and have informed Sage support.  The issue somehow appears to be server side in 2024 PU1 so hopefully the Dev or Support teams at Sage will come up with a permanent solution soon.

Children
No Data

*Community Hub is the new name for Sage City