Error 2004 ("Not enough memory") when producing a report.

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Petrol
    Contributor
    • Oct 2016
    • 306

    #1

    Error 2004 ("Not enough memory") when producing a report.

    For the last week I am unable to produce any report from my in-production Access 365 database. Any attempt results in Error 2004, "There isn't enough memory to perform this operation".
    ChatGPT informs me that Microsoft introduced the bug on September 16 in Version 2609 — Build 16.0.20430.2003 2, and that it has been reported by multiple users. Does anyone know whether this is true, and if so when they are going to fix it?? It has cause my entire application to become unusable.
  • cactusdata
    Recognized Expert New Member
    • Aug 2007
    • 224

    #2
    The Access team has identified the issue and expects a fix to be published soon, but when is not known yet.

    Comment

    • Petrol
      Contributor
      • Oct 2016
      • 306

      #3
      Thank you. Since the bug makes it impossible to produce reports, I assume it doesn't affect all Access users, or they would have fixed it by now!

      Comment

      • providetangible
        New Member
        • Oct 2026
        • 2

        #4
        I know how frustrating Error 2004 can be—it's especially annoying when you're in the middle of making a report. I found it helpful to see if my computer had enough memory for Access or to close any other programs that were taking up too much space. That can sometimes make all the difference by freeing up memory! I'd like to know if anyone has any other ideas for how to deal with this mistake better! What has helped you the most so far? This is
        Last edited by NeoPa; 3 weeks ago. Reason: Removed some paste residue.

        Comment

        • Petrol
          Contributor
          • Oct 2016
          • 306

          #5
          Thanks for your comments, posttangible. My understanding is that the problem is not really a shortage of memory, despite the error message. It's actually the result of a bug in Access. Since nobody on this forum has offered any solution, and it's been in existence for over a month now, I can only assume that it affects only a small percentage of users - Microsoft would never get away with ignoring it for a month if every Access report in the world was failing! Nevertheless it is a serious problem for some: Since an Office update released on the Current Channel (Preview) on September 15th, every single report in every database strikes the error.
          I have backed out the Office Update and paused updates, but how long can i go on with Office updates suspended? Does anyone have any idea about the current status?

          Comment

          Working...