Skip to content

x Want to ask a question or reply? Click here to join the group.
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 14 subscribers
  • Views 802 views
  • Users 0 members are here
Browse Forums
Announcements
309
topics
40
replies
General Discussion
533
topics
1k
replies
More Content

Financial Reporter (FR) does not print for 1 company (database)

Dami O.
Solved
Posted By

On web screens, the financial reporter does not run for a single database (it runs for other databases without issues). When I click Generate Statement it shows the processing screen for a few seconds then hangs on the "grey" screen. there is no error message and there is no customization of the FR templates.
I have dumped and loaded the database into other working databases and even loaded into another server entirely but no difference. Data Integrity check shows nothing.
Sage 300 2024 update 5 is installed on an Azure cloud server (VM).

Any idea is appreciated.

  • 0
    Suggested

    Hey  

    Thanks for using the Sage Community Hub  ,we appreciate you reaching out here first.

    Please see the suggested answer and click "Verify Answer" if the answer helps.

    That's a tricky one! You've already done some great detective work, moving the database around and running Data Integrity checks, showing you're serious about finding the cause.

    Since the Financial Reporter runs smoothly for your other databases but keeps hanging on this specific one (even after being moved to different servers), there's likely something unique in this database's setup that needs expert eyes on it.

    Let's get our technical team involved:

    Reach out to us at 086 123 7243 or log a support query at LogRequest - Sage Portal Be sure to share all the troubleshooting you've already done – it'll speed things up.

  • +1 in reply to Nteboheleng William M.
    Verified Answer

    Hi William. 
    Many thanks you for your suggestion. Sorry, I found a solution and forgot to check back here.

    The issue, for some reason I can't explain, was an optional field we set up on GL, AP and AR transactions. I had to change the Optional field code on GLOFD table to something else (i.e. I changed the code in the field OPTFIELD from SALESREP to REP) and that fixed the issue.

*Community Hub is the new name for Sage City