2026-11-15

Sage 300 Financial Reporter: Error Code 9 — Index Was Outside the Bounds of the Array

Sage 300 Financial Reporter runs a report once, then fails on the second run with error code 9 — index was outside the bounds of the array. The report is not broken. Something it runs on is.

On the Sage Community Hub, a Sage 300 user in Financials Suite ran a Financial Reporter report in FR View. The first run worked. The second run — in the same session, without quitting Financial Reporter — stopped with error code:9, index was outside the bounds of the array. Reopening FR made it work again. Once.

Sage 300 Error Code 9: A Pattern, Not a Broken Report

The details rule out the obvious suspects. This was Sage 300 ERP 2024 PU3, running the generic Balsum01 report from the Sage GL folder — built to run on any database. Across two company databases, one ran it repeatedly with no error; the other failed on every second run. A corrupt report or bad GL data does not behave that selectively.

Why the New GL Year Looks Guilty — and Is Not

The error appeared right after a new year for 2026 was created in GL for both databases — created successfully, with no error. That timing sends most teams into fiscal setup and data checks. In the verified Hub thread, none of that was the cause: the trigger and the fault sat in two different places.

Where the Sage 300 Financial Reporter Fix Actually Sits

The verified answer traced the failure outside Sage 300 itself: to the 64-bit Excel install Financial Reporter was running against. Responders had seen the same second-run behaviour on 64-bit Excel, cleared by reverting to 32-bit. The poster confirmed it: reverting to 32-bit solved the problem. Whether that switch is right for your workstations is the real decision here.

Frequently Asked Questions

What causes Sage 300 Financial Reporter error code 9? In the verified case, the report and GL data were sound. The failure appeared only on the second run in the same FR session and was traced to the 64-bit Excel environment.

Why does the first run work and the second fail? That first-works, second-fails, works-again-after-restart pattern points away from report design and toward the session environment — not the numbers in the report.

What a Stalled Financial Reporter Costs

Financial Reporter is how month-end statements get out. A tool that must be restarted between runs turns reporting into a stop-start chore — and invites trusting the first run and skipping the re-run that would have caught a changed number.

Get Financial Reporter Running Again

Our free Sage health check reviews your Sage 300 reporting setup — versions, workstations, and the Office environment Financial Reporter depends on — together. Every Digit Masters consultant is a licensed U.S. CPA, and our Sage support plans keep small faults from becoming close delays. If Financial Reporter fails on the second run, contact us before month-end finds it again.

Related Services

This topic connects directly to our core service areas: Sage 300 Consulting, Sage 300 Support, and our Sage support plans. Related reading: our post on the Sage 300 day-end cstp xifo iloc mismatch error and our post on Sage 300 user access and missing options. If you're working through a similar challenge, contact us for a free consultation.

Written by the Digit Masters Consulting Team

Our CPA-led consultants have over 35 years of combined experience implementing, supporting, and migrating Sage 100 and Sage 300 for manufacturers and wholesale distributors across Southern California and nationwide.

Ready to Optimize Your Sage ERP?

Speak with a CPA-led Sage consultant. Free initial consultation — English or Chinese.

Get a Free Consultation