x Want to participate? Join the group to interact
  • State Suggested Answer
  • Replies 7 replies
  • Answers 3 answers
  • Subscribers 132 subscribers
  • Views 741 views
  • Users 0 members are here
Browse Forums
Announcements
271
topics
260
replies
Databases and Operating Systems
771
topics
2k
replies
Financials Suite
1k
topics
3k
replies
General Discussion
2k
topics
10k
replies
Operational Suite
854
topics
2k
replies
Reporting and Analytics
1k
topics
3k
replies
Reports, Macros, and Customizations
878
topics
3k
replies
Sage CRM for Sage 300
184
topics
415
replies
Michael Baldwin

Error on Opening the xla macro

SUGGESTED
Posted By

Hi,

We have encountered an issue whereby we are receiving the following error messages:

1. PrintReport: Error on opening the xla macro

2. Problem is found in running Financial Reporter Addin

We do not have application support in-house and have been unable to progress the issue so would be grateful for any assistance or recommendation for a support company in Sydney Australia that can assist.

Kind regards

Michael

Parents
  • 0
    SUGGESTED

    Hi Michael, this issue has occurred for our clients in several ways:

    1. Antivirus behaviour detection kills the RunDLL process that launches the Statement Designer.  Locate the error in the Event Viewer on the affected machine or check your Antivirus/AntiMalware logs for events and detections.  In particular I've had HitManPro (part of a Sophos suite) kill it at a couple of sites producing this error.  Whitelist your Sage 300 Programs folder to exclude it from scanning over the network in the central management area of your AntiVirus/AntiMalware.
    2. AppLocker kills the process - put an exclusion in AppLocker though this should show in the Event Viewer.
    3. Add your Sage 300 programs share to the Trusted Locations if you're blocking Macros from running outside the Share.
    4. How old is old for your Sage 300 version?  There is a limit to how far back you can go with the latest (even 32-bit) version of Excel 365 but I can't recall specifics.

    Definitely build that relationship with Anne, Sheena and the crew at Orchid Systems - they're exceptional!

Reply
  • 0
    SUGGESTED

    Hi Michael, this issue has occurred for our clients in several ways:

    1. Antivirus behaviour detection kills the RunDLL process that launches the Statement Designer.  Locate the error in the Event Viewer on the affected machine or check your Antivirus/AntiMalware logs for events and detections.  In particular I've had HitManPro (part of a Sophos suite) kill it at a couple of sites producing this error.  Whitelist your Sage 300 Programs folder to exclude it from scanning over the network in the central management area of your AntiVirus/AntiMalware.
    2. AppLocker kills the process - put an exclusion in AppLocker though this should show in the Event Viewer.
    3. Add your Sage 300 programs share to the Trusted Locations if you're blocking Macros from running outside the Share.
    4. How old is old for your Sage 300 version?  There is a limit to how far back you can go with the latest (even 32-bit) version of Excel 365 but I can't recall specifics.

    Definitely build that relationship with Anne, Sheena and the crew at Orchid Systems - they're exceptional!

Children

*Community Hub is the new name for Sage City