49.38.0d

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • CopyTech03
    Technician

    50+ Posts
    • Jul 2020
    • 54

    #1

    [Error Code] 49.38.0d

    HP m605 with an error 49.38.0d. The printer will come to Ready, once it prints out a print job or internal print (Configuration Page) it will give this code. Starting happening after a power surge. Tried updating the firmware and doing a Cold Reset. Does anyone have any other ideas?
  • DRichard
    Trusted Tech

    250+ Posts
    • May 2008
    • 482

    #2
    Re: 49.38.0d

    Originally posted by CopyTech03
    HP m605 with an error 49.38.0d. The printer will come to Ready, once it prints out a print job or internal print (Configuration Page) it will give this code. Starting happening after a power surge. Tried updating the firmware and doing a Cold Reset. Does anyone have any other ideas?
    From the manual... "A firmware error occurred. Corrupted print jobs, software application issues, non-product specific print drivers, poor quality USB or network cables, bad network connections or incorrect configurations, invalid firmware operations, or unsupported accessories can cause this error." In short, it appears to be a catch-all code for when the printer has lost its shit.
    "Enjoy every sandwich."

    -- Warren Zevon

    Comment

    • DRichard
      Trusted Tech

      250+ Posts
      • May 2008
      • 482

      #3
      Re: 49.38.0d

      Originally posted by CopyTech03
      HP m605 with an error 49.38.0d. The printer will come to Ready, once it prints out a print job or internal print (Configuration Page) it will give this code. Starting happening after a power surge. Tried updating the firmware and doing a Cold Reset. Does anyone have any other ideas?
      Recommended action for call-center agents and onsite technicians (NOTE:LaserJet formatter PCAs are rarely the root cause of 49 service errors. Please do not replace the formatter unless troubleshooting has identified the formatter as the root cause.)1.
      Turn the printer off, and then on.
      2.
      If the error persists, check the following:

      The error might be caused by a network connectivity problem, such as a bad interface cable, a bad USB port, or an invalid network configuration setting.

      The error might be caused by the print job, due to an invalid print driver, a problem with the software application, or a problem with the file being printed.

      Upgrading the printer firmware might help resolve the error.
      "Enjoy every sandwich."

      -- Warren Zevon

      Comment

      • blackcat4866
        Master Of The Obvious

        Site Contributor
        10,000+ Posts
        • Jul 2007
        • 22960

        #4
        Re: 49.38.0d

        I'd start by taking it off the network, booting up, then testing while off the network. If the error does not re-occur off the network, you may have a corrupt print job, wrong print driver, or non-print data hitting the printers IP address. =^..^=
        If you'd like a serious answer to your request:
        1) demonstrate that you've read the manual
        2) demonstrate that you made some attempt to fix it.
        3) if you're going to ask about jams include the jam code.
        4) if you're going to ask about an error code include the error code.
        5) You are the person onsite. Only you can make observations.

        blackcat: Master Of The Obvious =^..^=

        Comment

        • CopyTech03
          Technician

          50+ Posts
          • Jul 2020
          • 54

          #5
          Re: 49.38.0d

          Originally posted by blackcat4866
          I'd start by taking it off the network, booting up, then testing while off the network. If the error does not re-occur off the network, you may have a corrupt print job, wrong print driver, or non-print data hitting the printers IP address. =^..^=
          Have it off the network, but still getting same code when printing out internal prints

          Comment

          • blackcat4866
            Master Of The Obvious

            Site Contributor
            10,000+ Posts
            • Jul 2007
            • 22960

            #6
            Re: 49.38.0d

            That's not good.

            Try firmware, if it will take. =^..^=
            If you'd like a serious answer to your request:
            1) demonstrate that you've read the manual
            2) demonstrate that you made some attempt to fix it.
            3) if you're going to ask about jams include the jam code.
            4) if you're going to ask about an error code include the error code.
            5) You are the person onsite. Only you can make observations.

            blackcat: Master Of The Obvious =^..^=

            Comment

            Working...