SP5210DN frequent SC899 codes

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • KenB
    Geek Extraordinaire

    2,500+ Posts
    • Dec 2007
    • 3944

    #1

    SP5210DN frequent SC899 codes

    Howdy,

    We have a customer with quite a few SP5210DN printers, scattered all over the country.

    The bulk of them have either completely or near current firmware, although I'm quite sure a number of them are ancient.

    Not sure on the exact specifics, but we are getting frequent, random SC899 errors.

    Any suggestions?

    Thanks!
    “I think you should treat good friends like a fine wine. That’s why I keep mine locked up in the basement.” - Tim Hawkins
  • Zaxxon
    Senior Tech

    500+ Posts
    • Jan 2014
    • 608

    #2
    Re: SP5210DN frequent SC899 codes

    Update FW
    Please start you post with brand, model, problem.

    Comment

    • slimslob
      Retired

      Site Contributor
      25,000+ Posts
      • May 2013
      • 37353

      #3
      Re: SP5210DN frequent SC899 codes

      Latest PCL firmware is v1.05. v1.04 and 1.05 corrected for causes of SC 899.

      Comment

      • copier tech
        Field Supervisor

        5,000+ Posts
        • Jan 2014
        • 8132

        #4
        Re: SP5210DN frequent SC899 codes

        Yes keep FW bang up-to-date.

        Most causes of this are when they print webpages, its the adverts or scrolling banners etc that cause SC899.

        Advice the customer if it does happen to power off the machine, delete the last print job & reboot.
        Let us eat, drink, and be merry, because tomorrow we may die!

        For all your firmware & service manual needs please visit us at:

        www.copierfirmware.co.uk - www.printerfirmware.co.uk

        Comment

        • anothertech
          Service Manager

          Site Contributor
          1,000+ Posts
          • Nov 2007
          • 1760

          #5
          Re: SP5210DN frequent SC899 codes

          Why do we keep getting questions like this? Shouldn't techs update the firmware when they have problems, before asking others for help?

          Comment

          • slimslob
            Retired

            Site Contributor
            25,000+ Posts
            • May 2013
            • 37353

            #6
            Re: SP5210DN frequent SC899 codes

            Originally posted by anothertech
            Why do we keep getting questions like this? Shouldn't techs update the firmware when they have problems, before asking others for help?
            Because not all techs have access directly to firmware.

            Comment

            • omorales
              Technician

              50+ Posts
              • Mar 2015
              • 86

              #7
              Re: SP5210DN frequent SC899 codes

              My question is,
              where I can get FW, for ricoh.

              Comment

              • KenB
                Geek Extraordinaire

                2,500+ Posts
                • Dec 2007
                • 3944

                #8
                Re: SP5210DN frequent SC899 codes

                Originally posted by slimslob
                Latest PCL firmware is v1.05. v1.04 and 1.05 corrected for causes of SC 899.
                Thanks, Slimslob.

                I had seen that in the firmware history, but I have also been told that many of these 5210s were current, and still having the issue.

                We will need to investigate just what versions they are actually at, and not just takes someone's word for it.

                Unfortunately, SC899 is pretty much a "catch-all" code, which can be caused by various problems.
                “I think you should treat good friends like a fine wine. That’s why I keep mine locked up in the basement.” - Tim Hawkins

                Comment

                • slimslob
                  Retired

                  Site Contributor
                  25,000+ Posts
                  • May 2013
                  • 37353

                  #9
                  Re: SP5210DN frequent SC899 codes

                  Originally posted by KenB
                  Thanks, Slimslob.

                  I had seen that in the firmware history, but I have also been told that many of these 5210s were current, and still having the issue.

                  We will need to investigate just what versions they are actually at, and not just takes someone's word for it.

                  Unfortunately, SC899 is pretty much a "catch-all" code, which can be caused by various problems.
                  Apparently there are still some printing issues that Ricoh has not yet identified. I have 4 MP C3503 at the Hyundai-Kia Western Proving grounds. Three work fine. One throws a SC899 at least once a week.

                  One thing that I have been told will help when printing form the internet is to preview and then print from the preview screen. This will flatten the image and should remove the offending code. The hard part is to get all users to do so.

                  Comment

                  • Voodou

                    #10
                    Re: SP5210DN frequent SC899 codes

                    We had a bank with numerous machines that would throw an 899 every Wednesday, turn out it was some security software that ran every Tues night/ Wed. morning that was causing it. The client made some changes to the software and problem went away.

                    Comment

                    • zed255
                      How'd ya manage that?

                      1,000+ Posts
                      • Dec 2009
                      • 1024

                      #11
                      Re: SP5210DN frequent SC899 codes

                      If Java is present but not being used try removing it. I had one behaving badly with SC899's in the mornings and removing Java seems to have solved it.

                      Comment

                      • KenB
                        Geek Extraordinaire

                        2,500+ Posts
                        • Dec 2007
                        • 3944

                        #12
                        Re: SP5210DN frequent SC899 codes

                        I was able to remote into an offending machine today.

                        All the firmware was current, and it still throws the dreaded code.

                        I did notice that Java was at 7.20.

                        The most current version is 7.23, so I installed that.

                        It's not running any Java apps, but I'm not sure that matters.

                        Just a tip: The most current RXOP version on TSRC is 7.22, but if you log onto RFG-eSource, and search for "CVM", you can download a rather large (820 mb) file that has a ton of Java firmware. You can then extract the RXOP version of 7.23. careful, though....there is a 7.24, but it's not for the 5210dn. (You have to read the .doc that's in the download.). The CVM packs came about with the advent of SLNX.

                        Good tip on the weekly security push. We will try to get logs to see if it happens at any set time.

                        I that SP 7403 will allow me to see what area of the machine the SC came from, and I will look into that for any hints. If I'm not mistaken, it will show "SDK" if it's Java related.

                        Sadly, the machine I'm testing is about 1200 miles away, and I don't think I can get that info remotely. (My arms don't quite reach that far...almost, but not quite...).

                        Thanks for replying!
                        Last edited by KenB; 09-03-2016, 01:48 AM.
                        “I think you should treat good friends like a fine wine. That’s why I keep mine locked up in the basement.” - Tim Hawkins

                        Comment

                        • KenB
                          Geek Extraordinaire

                          2,500+ Posts
                          • Dec 2007
                          • 3944

                          #13
                          Re: SP5210DN frequent SC899 codes

                          Originally posted by zed255
                          If Java is present but not being used try removing it. I had one behaving badly with SC899's in the mornings and removing Java seems to have solved it.
                          Thanks, Zed,

                          I've considered that as a test.

                          Definitely a good way to narrow it down. We can try that, then go back to Engineering for escalation if need be.

                          Removing the cards permanently would be a nightmare, for both financial and political reasons. It's also possible there will soon be a Java app added, but I'm not sure.

                          This is a HUGE account; all the numbers are staggering.
                          Last edited by KenB; 09-03-2016, 02:31 AM.
                          “I think you should treat good friends like a fine wine. That’s why I keep mine locked up in the basement.” - Tim Hawkins

                          Comment

                          • anothertech
                            Service Manager

                            Site Contributor
                            1,000+ Posts
                            • Nov 2007
                            • 1760

                            #14
                            Re: SP5210DN frequent SC899 codes

                            Ricoh has a tool called RLogtool that I've heard can be used to collect device logs over the network.

                            I have not used it myself, but it might be worth a try.

                            Comment

                            • KenB
                              Geek Extraordinaire

                              2,500+ Posts
                              • Dec 2007
                              • 3944

                              #15
                              Re: SP5210DN frequent SC899 codes

                              Originally posted by anothertech
                              Ricoh has a tool called RLogtool that I've heard can be used to collect device logs over the network.

                              I have not used it myself, but it might be worth a try.
                              Yep, I have used it before, although just once about a year ago.

                              Once you capture the logs, you send them into Support to be analyzed, as there will not likely be much a mere human can get out of it.

                              Definitely on the list of possibilities, but I would need to predict when the error may happen, as to catch it in the proverbial act, and not build a humongous file waiting for something that may or may not ever occur.
                              “I think you should treat good friends like a fine wine. That’s why I keep mine locked up in the basement.” - Tim Hawkins

                              Comment

                              Working...