web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics SL (Archived) / FRx - multiple issues
Microsoft Dynamics SL (Archived)

FRx - multiple issues

(0) ShareShare
ReportReport
Posted on by Sherry Whitten 329

User successfully ran all reports in FRx first thing this morning.  Then she made one change (added a row to a row definition) and tried to save.  She gets Run-time error '-2147467259 (80004005)': Not enough space on temporary disk.

Following that, she is unable to open several of her row formats.  We don't get any kind of error; the screen just blinks very quickly, and it goes back to the main FRx dashboard screen.  

We went through all of this yesterday and finally ended up restoring a sysdata folder backup from Monday.  But the problems have recurred today.  We've been through compacting the system database and current spec set database.

I'm out of ideas, and I'm not finding much searching this error.  Any suggestions?  Thanks.

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Community Member Profile Picture
    Community Member on at

    This sounds like corruption in the FRx database files. Compacting will typically keep it from reoccurring after restoring from backup. When compacting the spec set database, it only compacts the one that is assigned to the company you are currently logged into. Check Company -> Information to see what spec sets are assigned to which companies. Then, check Company -> Specification Sets to confirm which F32 files each spec set points to. You want to log into enough companies so that each F32 file would be compacted. If you have already done that, you could try exporting/importing the reports into a new spec set and then assign that new spec set to the company. When creating the new spec set, be sure it points to a new F32 file name otherwise you will just be adding more reports to an already corrupt file.

  • Verified answer
    Community Member Profile Picture
    Community Member on at

    I suggest upgrading to MR as soon as you can.

  • Sherry Whitten Profile Picture
    Sherry Whitten 329 on at

    Thanks for your help.  I created a new spec set and exported everything from the old one and imported into the new one.  No issues since then.  Keeping our fingers crossed that we can limp on a little longer with this, pending upgrade.  Thanks.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the February Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics SL (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans