4002i warning low memory

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • nathicana
    Trusted Tech

    Site Contributor
    250+ Posts
    • Aug 2008
    • 322

    4002i warning low memory

    I was setting up this brand new 4002i and noticed a blinking memory light that would not go out. After continuing to run copies for a while the message came up "Warning low memory cannot start the job try again later."

    Turning the machine off and on made it work again but I'm concerned the problem may come back.

    So far I have updated the firmware to 4.0

    Has anyone experienced this?
    Attached Files
  • Phil B.
    Field Supervisor

    10,000+ Posts
    • Jul 2016
    • 22808

    #2
    Re: 4002i warning low memory

    Originally posted by nathicana
    I was setting up this brand new 4002i and noticed a blinking memory light that would not go out. After continuing to run copies for a while the message came up "Warning low memory cannot start the job try again later."

    Turning the machine off and on made it work again but I'm concerned the problem may come back.

    So far I have updated the firmware to 4.0

    Has anyone experienced this?
    your memory is getting filled... find out what jobs are being stored and delete them.

    Comment

    • bsm2
      IT Manager

      25,000+ Posts
      • Feb 2008
      • 27442

      #3
      Re: 4002i warning low memory

      Run a hhd format

      Comment

      • ntbann
        Senior Tech

        500+ Posts
        • Jan 2012
        • 612

        #4
        Re: 4002i warning low memory

        We just had one with the flashing memory light. It turned out to be an old TA3050 driver being directed to the new printer. Changed to correct driver and all is good.

        Comment

        • nathicana
          Trusted Tech

          Site Contributor
          250+ Posts
          • Aug 2008
          • 322

          #5
          Re: 4002i warning low memory

          I kept the machine in the shop for a few days and the problem went away. There were no jobs in progress while the problem was happening.

          Prior to having the problem the machine took a really long time to register the remote services settings. Maybe that had something to do with it.

          Comment

          Working...