49 4c01 service error

49 4c01 service error

Code: 1300; Description: Defective during duplex-printing; Causes: Registration sensor detects paper feed condition at out of specified timing during. o/cjf6gtsr950sr0125idy65yiy%2Ff245e964-d756-4c01-98de-b6e5a9070588%2Fbottles1.jpg?alt=media&token=b381c976-da30-49d7-8e95-eb4ae8588354". Next IIS Manager Error: The process cannot access the file because it is being used by i have configured my server well and it runs asp pages correctly. 49 4c01 service error

Consider, that: 49 4c01 service error

Terrordrome v 2.7
49 4c01 service error
49 4c01 service error
Teamviewer waitforconnectfailed error
3ds max 9 registration-activation error

@greg-plamondon I spent a few hours working on this issue last night. I’m proud to report I can’t duplicate this error. That doesn’t really mean a hill of beans here. That just means my environment is a bit different than yours. My dev box only has a handful of clients and is on a pretty fast server. I do have a few ideas that I would like you guys to test. We do need php-fpm to work well to help improve web ui performance. The UI Developers are working on an optimized version of the new ui for 1.6.0 release, but that is a few months out yet.

What I would like both of you to do is:

  1. Rerun the fog installer to reset everything back to a known configuration (hopefully).
  2. Once the installer has completed I want both of you to modify the following file:
  3. Insert the following section:
  1. To make the file look like this:
  1. Save and exit the editor
  2. Issue the following command to restart apache:

This directive should tell apache to wait up to 5 minutes for php-fpm to complete its operations, 49 4c01 service error. (if it takes that long there is something else really wrong)

Now Greg, since you had a memory exhaustion issue I want you to do these additional setup.

  1. Edit this file
  2. Look for a line that reads:
  3. Uncomment that line and change the parameter to 2000 to make it look like this:
  4. Save and exit the editor.
  5. Restart php-fpm and apache.

I think we actually have 2 issues here, and they are both relevant, 49 4c01 service error. Both are hitting the timeout issue, while Greg is hitting the next issue too.

Thank you guys for helping to work this out. I’m pretty sure we can get a resolution, if not we can always make 2 changes to apache and be back to the way 1.5.1 and earlier worked using the built in apache php engine.

App crashed after deployed on 49 4c01 service error. But it's working in 49 4c01 service error local.

Anyone please help me .I am also getting the same error. i need an urgent help. I am using django and python 3.6.10 along with tensorflow =2.1 and keras

Microsoft Windows [Version 6.3.9600] © 2013 Microsoft Corporation. All rights reserved.

C:\windows\system32>heroku logs --tail » Error: Missing required flag: » -a, --app APP app to run command against » See more help with --help

C:\windows\system32>heroku logs --tail -a healtech 2021-01-11T15:02:05.933848+00:00 app[web.1]: [2021-01-11 15:02:05 +0000] [11] [I NFO] Worker exiting (pid: 11) 2021-01-11T15:02:05.933853+00:00 app[web.1]: [2021-01-11 15:02:05 +0000] [10] [E RROR] Exception in worker process 2021-01-11T15:02:05.933854+00:00 app[web.1]: Traceback (most recent call last): 2021-01-11T15:02:05.933855+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/site-packages/gunicorn/arbiter.py”, line 583, in spawn_worker 2021-01-11T15:02:05.933855+00:00 app[web.1]: worker.init_process() 2021-01-11T15:02:05.933855+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/site-packages/gunicorn/workers/base.py”, line 119, in init_process 2021-01-11T15:02:05.933856+00:00 app[web.1]: self.load_wsgi() 2021-01-11T15:02:05.933856+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/site-packages/gunicorn/workers/base.py”, 49 4c01 service error, line 144, in load_wsgi 2021-01-11T15:02:05.933856+00:00 app[web.1]: self.wsgi = self.app.wsgi() 2021-01-11T15:02:05.933857+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/site-packages/gunicorn/app/base.py”, line 67, in wsgi 2021-01-11T15:02:05.933857+00:00 app[web.1]: self.callable = self.load() 2021-01-11T15:02:05.933857+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/site-packages/gunicorn/app/wsgiapp.py”, line 49, in load 2021-01-11T15:02:05.933858+00:00 app[web.1]: return self.load_wsgiapp() 2021-01-11T15:02:05.933858+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/site-packages/gunicorn/app/wsgiapp.py”, line 39, in load_wsgiapp 2021-01-11T15:02:05.933859+00:00 app[web.1]: return util.import_app(self.app_uri ) 2021-01-11T15:02:05.933859+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/site-packages/gunicorn/util.py”, line 358, in import_app 2021-01-11T15:02:05.933859+00:00 app[web.1]: mod = importlib.import_module(modul e) 2021-01-11T15:02:05.933860+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/importlib/init.py”, line 126, in import_module 2021-01-11T15:02:05.933860+00:00 app[web.1]: return _bootstrap._gcd_import(name[ level:], package, level) 2021-01-11T15:02:05.933861+00:00 app[web.1]: File "

2021-01-11T15:02:06.408675+00:00 heroku[web.1]: State changed from crashed to st arting 2021-01-11T15:02:49.936312+00:00 heroku[web.1]: Starting process with command 2021-01-11T15:02:50.000000+00:00 app[api]: Build succeeded 2021-01-11T15:02:54.195478+00:00 app[web.1]: [2021-01-11 15:02:54 +0000] [4] [IN FO] Starting gunicorn 20.0.4 2021-01-11T15:02:54.196657+00:00 app[web.1]: [2021-01-11 15:02:54 +0000] [4] [IN FO] Listening at: http://0.0.0.0:36107 (4) 2021-01-11T15:02:54.201883+00:00 app[web.1]: [2021-01-11 15:02:54 +0000] [4] [IN FO] Using worker: sync 2021-01-11T15:02:54.217181+00:00 app[web.1]: [2021-01-11 15:02:54 +0000] [10] [I NFO] Booting worker with pid: 10 2021-01-11T15:02:54.234018+00:00 app[web.1]: [2021-01-11 15:02:54 +0000] [10] [E RROR] Exception in worker process 2021-01-11T15:02:54.234035+00:00 app[web.1]: Traceback (most recent call last): 2021-01-11T15:02:54.234040+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/site-packages/gunicorn/arbiter.py”, line 583, in spawn_worker 2021-01-11T15:02:54.234045+00:00 app[web.1]: worker.init_process() 2021-01-11T15:02:54.234045+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/site-packages/gunicorn/workers/base.py”, line 119, in init_process 2021-01-11T15:02:54.234046+00:00 app[web.1]: self.load_wsgi() 2021-01-11T15:02:54.234046+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/site-packages/gunicorn/workers/base.py”, line 144, in load_wsgi 2021-01-11T15:02:54.234046+00:00 app[web.1]: self.wsgi = self.app.wsgi() 2021-01-11T15:02:54.234051+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/site-packages/gunicorn/app/base.py”, line 67, in wsgi 2021-01-11T15:02:54.234051+00:00 app[web.1]: self.callable = self.load() 2021-01-11T15:02:54.234051+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/site-packages/gunicorn/app/wsgiapp.py”, line 49, in load 2021-01-11T15:02:54.234052+00:00 app[web.1]: return self.load_wsgiapp() 2021-01-11T15:02:54.234052+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/site-packages/gunicorn/app/wsgiapp.py”, line 39, in load_wsgiapp 2021-01-11T15:02:54.234052+00:00 app[web.1]: return util.import_app(self.app_uri ) 2021-01-11T15:02:54.234053+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/site-packages/gunicorn/util.py”, line 358, in import_app 2021-01-11T15:02:54.234053+00:00 app[web.1]: mod = importlib.import_module(modul e) 2021-01-11T15:02:54.234053+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/importlib/init.py”, line 126, in import_module 2021-01-11T15:02:54.234054+00:00 app[web.1]: return _bootstrap._gcd_import(name[ level:], 49 4c01 service error, package, level) 2021-01-11T15:02:54.234054+00:00 app[web.1]: File "

A way to reset server-side Firefox Sync data?

  • Multi-Account Containers Version: 6.2.1
  • Operating System + Version: MacOS Mojave 10.14.6
  • Firefox Version: 73.0.1
  • Other installed Add-ons + Version + Enabled/Disabled-Status:

Actual behavior

Something messed up in MAC with Sync, and it’s syncing back the erroneous data to my browser. Screen Shot 2020-02-25 at 10 20 48 AM

Expected behavior

The ability to wipe 49 4c01 service error data synced and start from scratch.

Steps to reproduce

  1. Create some containers
  2. Something I’m not aware of breaks
  3. Get an ever-growing list of duplicate containers populating and slowing down Firefox to a crawl.

Notes

about:sync-log

Try Lightrun to collect production stack traces without stopping your Java applications!

Brother DCP-T710W

  • Catalog

  • Sign In

  • Contacts

  • Forum

  • Eng

    Error Codes List page 1

    • Code: 1300
    • Description: Defective during duplex-printing
    • Causes: Registration sensor detects paper feed condition at out of specified timing during switchback.
    • Remedy: < User Check > - Check whether the recording paper being used is within the specification.
      1 Registration actuator caught on the surrounding parts Set the registration actuator into place.
      2 Registration sensor defective Replace the registration sensor PCB.
      3 Main PCB defective Replace the main PCB.
    • Code: 1500
    • Description: Paper jam during duplex ejecting
    • Causes: Recording paper is not able to be ejected since it is longer than 840 mm when ejecting the paper. (The registration sensor stays 49 4c01 service error the paper feeding condition during ejecting.)
    • Remedy: < User Check > - Remove the jammed paper. - Check whether the recording paper being used is within the specification.
      1 Foreign materials in the recording paper path Remove foreign materials.
      2 Registration actuator caught on the surrounding parts Set the registration actuator into place. 3 Main PCB defective Replace the main PCB.
    • Code: 49 4c01 service error Recording paper size error (duplex-printing/duplex-copying)
    • Causes: - The paper width detected by the paper width sensor or the paper length detected by the registration sensor was not suitable for duplex printing.
    • Remedy: < User Check > - Check 49 4c01 service error the recording paper being used is within the specification. - Check that dark recording paper is not used.
      1 CR encoder strip stained Clean the CR encoder strip.
      2 PF encoder disk stained Clean the PF encoder disk and flushing guide.
      3 Registration actuator caught on
      the surrounding parts
      Set the registration actuator into place.
      4 CR encoder strip defective Replace the CR encoder strip.
      5 PF encoder disk defective Replace the PF encoder disk.
      6 Registration 49 4c01 service error defective Replace the registration sensor PCB.
      7 Paper width sensor defective Replace the carriage PCB ASSY.
      8 Paper feed motor defective Replace the paper feed motor.
      9 Main PCB defective Replace the main PCB.
    • Code: 1800
    • Description: Paper jam during duplex-printing
    • Causes: Registration sensor does not detect paper feed within specified pulse numbers in the second side paper re-feed.
    • Remedy: < User Check > - Remove the jammed paper. - Check whether the recording paper being used is within the specification. - Check that recording paper are not curled, wrinkled or wet.
      1 Foreign materials in the duplex print paper path Remove foreign materials.
      2 Registration actuator caught on the surrounding parts Set the registration actuator into place.
      3 Registration sensor defective Replace the registration sensor PCB.
      4 Switchback roller defective Replace the switchback roller.
      5 Drive frame ASSY defective Replace the maintenance unit.
      6 Main PCB defective Replace the main PCB.
    • Code: 2000
    • Description: Cannot identify a black ink cartridge.
    • Causes: The ink cartridge detection sensor and the ink remaining sensor are detecting.
    • Remedy: < User Check > - Check if incompatible ink cartridge is loaded. - Reload the ink cartridge. - Replace the ink cartridge.
      1 Each ink cartridge sensor or ink cartridge IC chip PCB defective Replace the ink refill ASSY.
      2 Main PCB defective Replace the main PCB.
    • Code: 2001
    • Description: Cannot identify a yellow ink cartridge.
    • Causes: The ink cartridge detection sensor and the ink remaining sensor are detecting.
    • Remedy: < User Check > - Check if incompatible ink cartridge is loaded. - Reload the 49 4c01 service error cartridge. - Replace the ink cartridge.
      1 Each ink cartridge sensor or ink cartridge IC chip PCB defective Replace the ink refill ASSY.
      2 Main Error 57 pascal defective Replace the main PCB.

    PrintCopy .info service 2001 - 2022

    Error Code
    Parts Catalog
    Service Mode, Troubleshooting
    Compatibility
    Home

    IIS EXECUTING ASP CLASS PAGES

    <div class="body">

    Hello and thank you for any support you can provide.

    I am runnig IIS 7.5 error code = 0x3f5 a decicated Windws 2008 R2 Server. When I bring up Internet Information Service Manager and display the Application Pools all three of the application pools listed show a status fo Unknown and the icon appears with a red cycle and X.

    When attempting to start or stop any of the pools I receive the following error message.

    Cannot Start Applicaton Pool

    There was an error while performing this operation.

    Details

    Class not registered(Exception from HRESULT: 0x80040154

    (REDB_E_CLASSNOTREG))

    I currently only have one application running on this machine. OpenText DM. Although the machine has been running well for several months, this problem seems to be something that just recently began to occur.

    I have uninstalled the OpenText software, unintall IIS and uninstill WAS Windows Process Activation Service and reinstalled these components. It appeared this corrected the problem but within an hour the problem resurfaced.

    When the problem occurs and the OpenText site goes down I must manually restart the WAS service and the W3SVC service.

    I should note that there does not seem to be any event log messages related to this error either. This also seems to be the only machine in our environment currently expernencing this type of problem.

    Any help or suggests would be greatly appreciated.  Thanks

    </div>

    Read these next.

    I have an HP P3015n printer that was fully functional. We did a firmware upgrade on it. The upgrade appeared to finish normally, but the printer now displays "49 4C01 error." A search of the canon pixma mp250 error e 02 shows little info for this error.

    I can FTP into the print server, but get this:

    230-Hewlett-Packard FTP Print Server Version 3.0.
    Directory:    Terrorist guestbook site .aero Unknown peripheral

    To print a file use the command put <filename> [portx]
    or 'cd' to a desired port and use put <filename>.

    230 User logged in.
    ftp>

    -----A Good version of this printer shows the following:--------------------

    230-Hewlett-Packard FTP Print Server Version 3.0.
    Directory:    Description:
    --------------------------
    PORT          HP LaserJet P3010 Series

    The obvious difference is the "unknown peripheral."

    I've tried the usual steps and had no luck. Any thoughts on what might be my options here?

    • All i can find with regards to this error popping up after a FW upgrade is to roll back to the previous version of the firmware that was installed. Let's wait what Priscilla has to say about it.

      Was this post helpful?thumb_upthumb_down
    • Holding X while booting, then OK, then menu bring you to a menu that lets you:

      select writing over the NAND with AAAA (far too easily by accident) -- this is not the correct approach.

      Now, the display won't even light. I suspect the JetAdmin software has been overwritten.

    • Hello Robert, it's unfortunate that your HP LaserJet P3015n has created challenges for you and your team after upgrading the firmware.  Thanks for the informative details and also thanks to Edwin for his helpful input.

      Knowing you both, I regret asking if you have seen some of the solutions in the post below--especially since Robert states that he had done the usual troubleshooting.  Just in case let me share it.  Most likely you have performed the steps listed in the post regarding a similar code:  49-4C02.  However, you will notice that one member advises:

      A WikiHow link gives steps for initializing the NVRAM to clear the 49-4C02, 49 4c01 service error, but this may not apply to you as you did only a firmware update.

      Based on your FTP results, let me also send this post to our consultant to review.

      Was this post helpful?thumb_upthumb_down
    • Thanks, Priscilla.

      Yes, the 49.4C02 error is generated by a print job that the printer could not interpret. I believe that the 4C01 error is generated when the JetDirect server can't communicate with the printer firmware, so it doesn't know how to send print jobs to the engine.

      As I said, through some unfortunate exuberance, I believe we have erased the JetDirect software. We went from being able to access via 49 4c01 service error or HTTP to no network capability to no display at all now when 49 4c01 service error is applied.

      Thanks for any help you may be able to provide (such as the magic startup sequence to reload the NAND).

    • I thougt it was the 4CO1 and not CO2 error that was generated

    • Edwin_Eekelaers wrote:

      I thougt it was the 4CO1 and not CO2 error that was generated

      Yes, it is the 4C01 that was produced. Now, the printer just stays dark.
    • Hello Robert, thank you very much for your reply.  Our consultant, who hasn't been updated regarding the printer now staying dark, provides the following:

      • Unplug network cable. Any flashing lights on the printer after turning it on? Any sign of life or flash on the display?
    • With no cables connected, 49 4c01 service error, I plug in a power cord and press the power button, 49 4c01 service error. The power button illuminates. The LCD screen stays dark. The 3 LEDs do not light. There are no motor or fan sounds from the printer, 49 4c01 service error. It is completely inert.

    • Hello again Robert, here is some additional information from our consultant:

      ###################
      Issue: HP LaserJet P3015n - 49.4C01 error after firmware update

      Almost dead fish, but not yet.

      Memory RAM
      The random access memory (RAM) on the formatter PCA contains the page, I/O buffers, and the font storage area. It stores printing and font information received from the host system, and can also serve to temporarily store a full page of print-image data before the data is sent to the print engine. Memory capacity can be increased by adding a DIMM to the formatter, 49 4c01 service error. Note that adding memory might also increase the print speed for complex graphics.

      Firmware NAND
      The firmware is contained on NAND flash memory soldered on the formatter board. A remote firmware upgrade process is available, which overwrites the firmware in the NAND flash.

      Nonvolatile memory NVRAM
      The product uses nonvolatile memory (NVRAM) to store device and user configuration settings. The contents of NVRAM are retained when the product is turned off or disconnected.




      Please check heart beat of the "printer"?
      Turn off and wait a while.

      Turn on.

      Observe formatter heartbeat LED number 2.


      ###################

      Please keep us updated as we are also eager for you to have your printer working again.

      Was this post helpful?thumb_upthumb_down
    • Please check heart beat of the "printer"?
      Turn off and wait a while.

      Turn on.

      Observe formatter heartbeat LED number 2.

      Power on = No heartbeat. (The NIC light flickers once when power is removed.)

      There was a heartbeat and I could access it via telnet until we accidently 49 4c01 service error the NAND with AAAA.

      Tomorrow we're all out of the office for a seminar, but Thursday I will crack open the printer and try a remove/replace on the connectors, memory, and formatter board.

      Please, HP, don't let my printer die! :-O

    • Hello Robert, thanks for the quick update, stoicism, and humor.  We will try our best communication packet, system error 61 to let your "printer die".   We eagerly await your next reply.

      I love the fish--yours and the consultant's.  Now I feel that I shouldn't have reigned in the consultant's sense of humor given your reply.  He had written something else that was light-hearted, but I said one instance of humor is enough for someone who is frustrated with his printer.  Now I can hear miles away, the consultant saying "ha, ha, ha".


      Was this post helpful?thumb_upthumb_down
    • Too funny. No, I'm not frustrated with the printer - or HP. Just one of those things that happens sometimes. I mean, someone has to be on the low end of the "average time to failure," right?

      I did reseat all the connectors. There is no additional memory. And, still, no heartbeat. (Just heartache, but that doesn't blink.)

      Give it to me straight, doc. Is my printer toast?

      Was this post helpful?thumb_upthumb_down
    • No Robert don't send it to Texas yet 49 4c01 service error the explosive printer contest. am sure Priscilla will find a solution.

      No thinking like Grumpy Cat yet.

      Was this post helpful?thumb_upthumb_down
    • 1. Tried the engine-test button, 49 4c01 service error. No results.

      2. Removed the formatter board. Tried the engine-test button. No results.

      Green power button is illuminated, but display is still dark.

    • Hello Robert, a remarkable troubleshooter . and humorist. Your sentence:  "Give it to me straight, doc. Is my printer toast?" and Edwin's post made me laugh.again.   Here is some additional information from the consultant.  It came earlier this afternoon:

      #################
      "Without the the main fan on the right side running 184 end to end error count a short time and without the heartbeat the engine controller is not operational. Thus pressing engine test button can't produce anything. See block diagram below.

      HP LaserJet P3010 Series Printers Service Manual (Even though you've shared that you are reviewing the manual, having the link maybe helpful to others visiting the post.)

      What we know:
      Printer was working but developed 49.4C01 error after the firmware update.
      Subsequent writing over the NAND with AAAA led to the following condition:
      Green power button is illuminated, but pressing it doesn't produce any action.
      Display is dark.

      No lights are on or flashing.

      Main fan doesn't run even for a short while.

      No heartbeat of the formatter.

      It is my opinion considering the summary above the printer is bricked. There is 49 4c01 service error working firmware currently on the printer.

      Engine-control system
      The engine-control system coordinates all product functions, according to commands that the formatter sends. The engine-control system drives the laser/scanner system, the image formation system, and the pickup/feed/delivery system.
      The engine control system contains the following major components:
      ● Engine-control unit (ECU)
      ◦ DC controller
      ◦ Low-voltage power supply
      ● High-voltage power supply



      Formatter-control system

      The formatter is responsible for the following procedures:
      ● Controlling sleep mode
      ● Receiving and processing print data from the various product interfaces
      ● Monitoring control-panel functions and relaying product-status information (through the control panel and the network or bidirectional interface)
      ● Developing and coordinating data placement and timing with the DC controller PCA
      ● Storing font information
      ● Communicating with the host computer through the network or the bidirectional interface
      The formatter receives a print job from the network or bidirectional interface and separates it into image information and instructions that control the printing process. The DC controller PCA synchronizes the image-formation system with the paper-input and -output systems, and then signals the formatter to send the print-image data.
      The formatter also provides the electrical interface and mounting 49 4c01 service error for one EIO card and an additional DIMM.

      Remove all EIO devices from the product.

      Page 60, 49 4c01 service error, Removal and replacement procedures: Formatter cover and formatter PCA.

      Power-on checks
      Turn on the power. If the control-panel display remains blank or if it displays random patterns or asterisks, perform the power-on checks to find the cause of the problem.
      1. Verify that the product is plugged into an active electrical outlet that delivers the correct voltage.
      2. Verify that the power switch is in the ON position.
      3. Make sure that the main fan on the right side runs for a short time.
      ● If the control-panel display is blank, but the main fan runs after the power is turned on, print an 49 4c01 service error test page to determine whether the problem is with the control-panel display, the formatter, or other components. See Engine diagnostics on page 134.
      ● The overcurrent/overvoltage protection circuit in the low-voltage power supply unit might be running. Turn the printer off, 49 4c01 service error the power cord, and turn the printer on. If the printer does not function, the fuse melts, or the power supply is malfunctioning, replace the engine controller unit. See Engine control unit (ECU) on page 110.
      ● Verify unrecovered read error the LEDs at the back of the product on the formatter, are functioning correctly. See LED diagnostics on page 133.
      4. Remove any HP Jetdirect or other EIO cards, and then turn off and maxwell render open mxs file error on the product."

      #################


    • It is my opinion considering the summary above the printer is bricked. There is no working firmware currently on the printer.

      Hmm, 49 4c01 service error. Now, I ask in all seriousness, how does one un-brick a printer? By that I mean the printers aren't born with firmware in them, so they must be programmed at 49 4c01 service error point. I will accept that it might be the case that this is a manufacturing process and there is no procedure that can be applied in the field to write the firmware. Is that true?

      Is it true that the (ex) 49 4c01 service error in question resides on the formatter board? If so, will replacing the formatter board with one on which I haven't performed my unique brand of maintenance re-animate the printer? Formatter boards are fairly easy to come by for this printer.

      What is the possibility that I've damaged other components besides the formatter board by wiping out the firmware? I did write over NAND1. But I resisted the urge to "Copy NAND1 to NAND2."

      Finally, one last question (and I really do appreciate your patience and assistance):

      Why has HP programmed what is essentially a kill button into this printer unless it provided a way to re-write the NAND?

    • Hello Robert,

      Thanks for your questions and additional information.  Yes, I will be checking with HP Support on how to unbrick your printer .  When you and your staff return and at your convenience do you mind providing me with a serial number for the "bricked" HP LaserJet P3015n so that I can talk with an HP technician?  Squid error 104 connection reset by peer below the consultant's responses to your questions:

      #############
      Right, the printers aren't born yet with firmware in them like Goa'uld with their genetic memory. Printers are still produced in an ordinary fashion.


      ​Formatter PCA = equivalent of brain and memory. Part number: CE475-67901 (new), CE475-69001 (exchange).

      Engine controller PCA = equivalent of muscles.

      Normal start up initialization
      ● The heartbeat LED indicates that the formatter is functioning correctly. While the product is initializing after you turn it on, the LED blinks rapidly, and then turns off. When the product has finished the initialization sequence, the heartbeat LED pulses on and off.
      ● The main fan's spin up for a short time during the initialization indicates that the engine controller is functioning correctly.

      1. Re: Un-brick

      I 49 4c01 service error already asked [email protected] yesterday to check if there is a way to un-brick the printer in the field. It is fairly easy on some printers with card reader or USB socket.

      2. Re: Firmware and replacing the formatter
      The firmware is contained on NAND flash memory soldered on the formatter board.
      ○ ○ I would try to replace the formatter in question as a starting point to verify that other parts of the printer are performing correctly. It could be that engine controller has been already faulty. See point 4. You can use formatter from other working printer.

      ○ ○ Then run diagnostics:
      Page 134: Print the engine test pages
      NOTE: A damaged formatter might interfere with the engine test. If the engine test page does not print, try removing the formatter and performing the engine test again. If the engine test is then successful, the problem is in the formatter, the control panel, or the cable that connects them together.

      Page 194: Diagnostics menu

      3. Re: Damage to other components by wiping firmware

      This 49 4c01 service error is in my opinion remote. See point 4. There 49 4c01 service error many control and protective mechanisms integrated into the printers.

      4. Re: A kill button?

      Highly disputable under the circumstances. Firmware update on printers is a quite a robust process today. Any corruption or complications are rare.
      The fundamental question here is why the first firmware update led to 49.4C01 error after the reboot?
      ○ Something already wrong with the printer before the update?
      ○ Corrupted data  during the network transfer?
      ○ Freaky coincidence?
      It could be that write over NAND1 would work under other circumstances, 49 4c01 service error. We will never know.

      #############

      Enjoy your off-site seminar.

      Was this post helpful?thumb_upthumb_down
    • [email protected] wrote:

      4. Re: A kill button?

      Highly disputable under the circumstances. Firmware update on printers is a quite a robust process today. Any corruption or complications are rare.
      The fundamental question here is why the first firmware update led to 49.4C01 49 4c01 service error after the reboot?
      ○ Something already wrong with the printer before the update?
      ○ Corrupted data  during the network transfer?
      ○ Freaky coincidence?
      It could be that write over NAND1 would work under other on error vba. We will never know.

      #############

      Let me clarify my question. Completely separate from the firmware upgrade, 49 4c01 service error, the printer, on bootstrap, allows me to use a 3-button sequence to get into an advanced menu. On that menu is the option to overwrite the NAND memory. (The option that was activated by accident by yours truly.) My question is, 49 4c01 service error, under what circumstances would that command be used? If it wipes out the firmware (in the field), 49 4c01 service error, there must be an option to restore the firmware (in the field) or the printer couldn't be returned to service. So, that gave me some hope that an in-field firmware restore can be done.

      Goa'uld? +1 for the Stargate reference.

      Firmware updates: If at first, you don't succeed.



    • Hello Robert, 49 4c01 service error, thanks for the clarification and welcome back from your seminar.  Please see input from the consultant:

      \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
      ● Remove please formatter.
      ● Insert paper into Tray 2, which is the built-in (not optional) tray cassette at the bottom of the printer.
      ● Turn on the printer.
      ● Press and hold the engine test page switch.

      Page 134: Engine diagnostics
      Printing test pages helps you determine whether or not the product engine and the formatter are functioning.
      NOTE: Information pages also can be used to solve product issues. For information about printing information pages, see the product user guide.

      Engine-test button
      To verify that the product engine is functioning, print an engine-test page.

      Print the engine test pages
      NOTE: A damaged formatter might interfere with the engine test. If the engine test page does not print, try removing the formatter and performing the engine test again. If the engine test is then successful, the problem is in the formatter, the control panel, or the cable that connects them together.

      1. Remove the DIMM cover. See DIMM cover and DIMM on page 57.
      2. Press the engine test-page button (callout 1).




      The test page should have a series of horizontal lines. The test page prints from the last tray that the product used to print, unless the product has been turned off and then turned on again since the most recent print job. If the product has been turned off and then on again since the most error_more_data linux socket print job, then the page will print from Tray 2. The product continuously prints test pages as long as the test-page switch is depressed. The blue screen error 116 will not print a test page if it is in Sleep mode.
      /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\



    • 1. Removed the formatter board.
      2. Put tray with paper into the built-in tray.
      3. Apply power - power button lights, fan does not spin.
      4. Press and hold engine test page switch - nothing happens.

      INSTALL NEW FORMATTER BOARD.
      1. Power on the printer.
      2. LCD display lights up and printer POSTs.
      3. Fan does not spin.
      4. Engine test page switch does nothing.
      5. Display activity terminates showing "49.4C01 ERROR"
      6. Heartbeat is active.

      The printer is currently not pulling a DHCP address. I am trying to establish communication with it now.

    • Robert5205 That tell's us the Engine PCB is defective, 49 4c01 service error. It's what controls the fans, and communication between the Formatterand the printer, 49 4c01 service error. With the formatter removed If the engine were functional it would print an engine test print. The whole purpose of that test is to check functionality of the engine. Since it fails the engine is failing it own basic test. 

      From the service manual that [email protected] references, 49 4c01 service error. Pages  284 & 285 item # 6 Engine controller PCA 110V RM1-6281-000CN.

      Was the formatter that you installed last a new one, or one borrowed from another printer?

      Without a functional engine you will not get an IP address.

      Was this post helpful?thumb_upthumb_down
    • The formatter board was from a working printer.

      If the engine PCA is bad, I have sacred 2 setup error wonder about the order. Did the engine PCA go bad, coincidently with and unrelated to the firmware upgrade? After the upgrade, however, the printer was still reachable via IP. Did something I did to the old formatter cause the PCA to go bad? If so, what?

      Too many questions and no log files. I think it's interesting that I could reach the jet direct server, but it couldn't identify the printer, 49 4c01 service error. That may indicate that the engine had failed at that time.

    • It's quite possible that the engine was already going bad, and the firmware update just finished it off when it went to copy the config to the engine.

      On these newer HP printers you can not just swap out the formatter, AND engine at the same time. The reason for this is that a backup copy of the printers configuration is stored on each.

      During the replacement of one, or the other the backup copy of the configuration is written to the new part from the old 49 4c01 service error still  remaining. (Ie. While powered down with the old engine in place, 49 4c01 service error, a new formatter is installed. Upon power up the printers configuration is downloaded to the new formatter from the old 49 4c01 service error It's the same if it's the engine being replaced, but the engine get 49 4c01 service error configuration from the formatter in that case.

      Here is a link from an HP forum that discusses this very error. Pay particular attention to the last 3 comment from davidzuts, and fern88. Error 49.4C01, cannot clear error to install new firmware.

      Edited to add:

      When you replace the engine. Make absolutely sure that you have the original formatter installed, and not one from another printer! If you have the wrong formatter installed your new engine will get the config for the wrong printer. You'll suddenly have 2 identical printers on you network! Not something you want. :o)

    • Robert5205 wrote:

      After the upgrade, however, the printer was still reachable via IP. 

      I think it's interesting that I could reach the jet direct server, but it couldn't identify the printer. That may indicate that the engine had failed at that time.

      Yes since the formatter already the IP address it retained it until you cycled the power, 49 4c01 service error, at which time it could no longer get an IP address.

      It could not identify the printer because the formatter lost communications to the engine.

      These newer HP printers are a lot more complicated than the older one's were. It used to be if the formatter failed you lost the entire printer config., Serial Number, Page Count, Etc. Now there is a backup copy on the engine.

      These are now mated pairs, and you should only replace one at a time.

    • Hmm. Very interesting posts. I'm interpreting that to mean that the new formatter board I put into the printer is now "poisoned"? It was corrupted by the ECU in the non-working printer. But, if I put it into a different printer, that printer's ECU will re-write it and it should be okay?

      That makes sense.

    • I doubt that the formatter you installed was corrupted in any way since the engine is non functional.

       If it was pulled from another working printer you should be ok. When you reinstall it in the original printer it'll get the config from that printers engine, and return it to normal for that printer, on the ODD chance that it did get any info from the engine.

    • Thanks, Ken. I'd like to keep the spare formatter around. But I don't want the corruption to spread.

    • You don't have to worry about any corruption spreading. That's just not a possibility, 49 4c01 service error. Hope that eases your mind.

    • KenBurgess wrote:

      During the replacement of one, or the other the backup copy of the configuration is written to the new part from the old one still  remaining. (Ie. While powered down with the old engine in place, a new formatter is installed. Upon power up the printers configuration is downloaded to the new formatter from the old engine.) It's the same if it's the engine being replaced, but the engine get the configuration from the formatter in that case.

      Maybe you can reconcile your last post with a previous one.

      This seems to indicate that the configuration 49 4c01 service error the bad engine will be written to the new formatter. Now, I interpreted "configuration" to mean whatever was causing the error, ie, corrupted firmware. If not, what exactly is copied?

      You also mentioned that replacing them in the wrong order would create a duplicate printer. What would make the printer identical? MAC?

    • Sent you a PM.

    • Art Imitates Life: DALL·E 2 AI Generates Art Featuring IT Professionals

      Art Imitates Life: DALL·E 2 AI Generates Art Featuring Startup error driver nvd3dum.dll sacred 2 Professionals

      Water Cooler

      In my last post about computer generated art, I tested artificial intelligence's ability to create orange T-Rex art in the style of many famous artists, using OpenAI's DALL·E 2 AI.Quick recap of how DALL·E 2 works. Users can request images of anything by .

    • Snap! Azure outage, malware in JWST images, floppy disks, Voyager 1, & more

      Snap! Azure outage, malware in JWST images, floppy disks, Voyager 1, 49 4c01 service error, & more

      Spiceworks Originals

      Your daily dose of tech news, in brief. While the month may be ending, we're halfway through the week. Let's jump into today's Snap! and see some of the things going on in the world. You need to hear this. Microsoft Azure outage knocks Ubuntu.

    • Monitor our Weblogs

      Monitor our Weblogs

      Security

      Hi,I would like to ask for your recommendations on how I can capture the websites our end users access during office hours.our current firewall doesnt support it as it only logs HTTP connections and we all know that almost all of the websites now are usin.

    • How to keep a record on my phone: of my own calls I will fix or need to fixerror 21 selected to keep a record on my phone: of my own calls I will fix or need to fixIT & Tech Careers

      I am the sole I.T. guy for a company.That has Servers/ NAS, I manage the PIX firewall. take full responsibility of all data including accounting Backups on NAS, Servers, Camera ( recordings).Do Cabling/Crimping as needed ,Set up VPN for remote folks,  49 4c01 service error alt="Spark! Pro series - 31st August 2022 - The Bacon Skype disk + i o error Edition" src="https://content.spiceworksstatic.com/service.community/p/topic_images/attached_image/94afc4f7-7a87-4433-a5be-018c83131efe-fc7257f1-a0b7-4b57-9fe4-9085e104b717-ham-926278_1920.jpg">

      Spark! Pro series - 31st August 2022 - The Bacon Day Edition

      Spiceworks Originals

      Today in History: 1142 Possible date for establishment of the Iroquois (Haudenosaunee) LeagueCenturies before the creation of the United States and its Constitution, democracy had already taken root in North America—among a handful of Indigenous nations. .

    Kafka: Keeps expiring consumers #7270

    Bug Report

    Current behavior

    We have 10 microservices and all interact with each other via kafka. We have noticed it randomly doesnt subscribes to topic, or randomly stops working and it gives kafka error, heartbeat not received while service on its own works fine.

    Input Code

    import{KafkaOptions,Transport}from"@nestjs/microservices";importappConfigfrom"config/appConfig";exportconstmicroServiceConfig: KafkaOptions={transport: Transport.KAFKA,options: {client: {clientId: 'promocode-service',brokers: [.`${appConfig().KafkaHost}`.split(",")],},consumer: {groupId: 'promocode-consumer',sessionTimeout: 300000,retry: {retries: 30},},subscribe: {fromBeginning: false,}}};

    Expected behavior

    Not clear why kafka keeps timing out randomly if I redeploy all works and then again it stops. Is it wrapper causing issues? These random issues makes me wonder what causes it.

    This is running on k8s and this behavior is seen in 1-2 users only, Kafka has enough memory!

    All consumers have different group Id and all have high session timeout as well.

    49 4c01 service error - sorry, that

    A way to reset server-side Firefox Sync data?

    • Multi-Account Containers Version: 6.2.1
    • Operating System + Version: MacOS Mojave 10.14.6
    • Firefox Version: 73.0.1
    • Other installed Add-ons + Version + Enabled/Disabled-Status:

    Actual behavior

    Something messed up in MAC with Sync, and it’s syncing back the erroneous data to my browser. Screen Shot 2020-02-25 at 10 20 48 AM

    Expected behavior

    The ability to wipe the data synced and start from scratch.

    Steps to reproduce

    1. Create some containers
    2. Something I’m not aware of breaks
    3. Get an ever-growing list of duplicate containers populating and slowing down Firefox to a crawl.

    Notes

    about:sync-log

    Try Lightrun to collect production stack traces without stopping your Java applications!

    Brother DCP-T710W

    • Catalog

    • Sign In

    • Contacts

    • Forum

    • Eng

      Error Codes List page 1

      • Code: 1300
      • Description: Defective during duplex-printing
      • Causes: Registration sensor detects paper feed condition at out of specified timing during switchback.
      • Remedy: < User Check > - Check whether the recording paper being used is within the specification.
        1 Registration actuator caught on the surrounding parts Set the registration actuator into place.
        2 Registration sensor defective Replace the registration sensor PCB.
        3 Main PCB defective Replace the main PCB.
      • Code: 1500
      • Description: Paper jam during duplex ejecting
      • Causes: Recording paper is not able to be ejected since it is longer than 840 mm when ejecting the paper. (The registration sensor stays in the paper feeding condition during ejecting.)
      • Remedy: < User Check > - Remove the jammed paper. - Check whether the recording paper being used is within the specification.
        1 Foreign materials in the recording paper path Remove foreign materials.
        2 Registration actuator caught on the surrounding parts Set the registration actuator into place. 3 Main PCB defective Replace the main PCB.
      • Code: 1700
      • Description: Recording paper size error (duplex-printing/duplex-copying)
      • Causes: - The paper width detected by the paper width sensor or the paper length detected by the registration sensor was not suitable for duplex printing.
      • Remedy: < User Check > - Check whether the recording paper being used is within the specification. - Check that dark recording paper is not used.
        1 CR encoder strip stained Clean the CR encoder strip.
        2 PF encoder disk stained Clean the PF encoder disk and flushing guide.
        3 Registration actuator caught on
        the surrounding parts
        Set the registration actuator into place.
        4 CR encoder strip defective Replace the CR encoder strip.
        5 PF encoder disk defective Replace the PF encoder disk.
        6 Registration sensor defective Replace the registration sensor PCB.
        7 Paper width sensor defective Replace the carriage PCB ASSY.
        8 Paper feed motor defective Replace the paper feed motor.
        9 Main PCB defective Replace the main PCB.
      • Code: 1800
      • Description: Paper jam during duplex-printing
      • Causes: Registration sensor does not detect paper feed within specified pulse numbers in the second side paper re-feed.
      • Remedy: < User Check > - Remove the jammed paper. - Check whether the recording paper being used is within the specification. - Check that recording paper are not curled, wrinkled or wet.
        1 Foreign materials in the duplex print paper path Remove foreign materials.
        2 Registration actuator caught on the surrounding parts Set the registration actuator into place.
        3 Registration sensor defective Replace the registration sensor PCB.
        4 Switchback roller defective Replace the switchback roller.
        5 Drive frame ASSY defective Replace the maintenance unit.
        6 Main PCB defective Replace the main PCB.
      • Code: 2000
      • Description: Cannot identify a black ink cartridge.
      • Causes: The ink cartridge detection sensor and the ink remaining sensor are detecting.
      • Remedy: < User Check > - Check if incompatible ink cartridge is loaded. - Reload the ink cartridge. - Replace the ink cartridge.
        1 Each ink cartridge sensor or ink cartridge IC chip PCB defective Replace the ink refill ASSY.
        2 Main PCB defective Replace the main PCB.
      • Code: 2001
      • Description: Cannot identify a yellow ink cartridge.
      • Causes: The ink cartridge detection sensor and the ink remaining sensor are detecting.
      • Remedy: < User Check > - Check if incompatible ink cartridge is loaded. - Reload the ink cartridge. - Replace the ink cartridge.
        1 Each ink cartridge sensor or ink cartridge IC chip PCB defective Replace the ink refill ASSY.
        2 Main PCB defective Replace the main PCB.

      PrintCopy .info service 2001 - 2022

      Error Code
      Parts Catalog
      Service Mode, Troubleshooting
      Compatibility
      Home

      @greg-plamondon I spent a few hours working on this issue last night. I’m proud to report I can’t duplicate this error. That doesn’t really mean a hill of beans here. That just means my environment is a bit different than yours. My dev box only has a handful of clients and is on a pretty fast server. I do have a few ideas that I would like you guys to test. We do need php-fpm to work well to help improve web ui performance. The UI Developers are working on an optimized version of the new ui for 1.6.0 release, but that is a few months out yet.

      What I would like both of you to do is:

      1. Rerun the fog installer to reset everything back to a known configuration (hopefully).
      2. Once the installer has completed I want both of you to modify the following file:
      3. Insert the following section:
      1. To make the file look like this:
      1. Save and exit the editor
      2. Issue the following command to restart apache:

      This directive should tell apache to wait up to 5 minutes for php-fpm to complete its operations. (if it takes that long there is something else really wrong)

      Now Greg, since you had a memory exhaustion issue I want you to do these additional setup.

      1. Edit this file
      2. Look for a line that reads:
      3. Uncomment that line and change the parameter to 2000 to make it look like this:
      4. Save and exit the editor.
      5. Restart php-fpm and apache.

      I think we actually have 2 issues here, and they are both relevant. Both are hitting the timeout issue, while Greg is hitting the next issue too.

      Thank you guys for helping to work this out. I’m pretty sure we can get a resolution, if not we can always make 2 changes to apache and be back to the way 1.5.1 and earlier worked using the built in apache php engine.

      Kafka: Keeps expiring consumers #7270

      Bug Report

      Current behavior

      We have 10 microservices and all interact with each other via kafka. We have noticed it randomly doesnt subscribes to topic, or randomly stops working and it gives kafka error, heartbeat not received while service on its own works fine.

      Input Code

      import{KafkaOptions,Transport}from"@nestjs/microservices";importappConfigfrom"config/appConfig";exportconstmicroServiceConfig: KafkaOptions={transport: Transport.KAFKA,options: {client: {clientId: 'promocode-service',brokers: [...`${appConfig().KafkaHost}`.split(",")],},consumer: {groupId: 'promocode-consumer',sessionTimeout: 300000,retry: {retries: 30},},subscribe: {fromBeginning: false,}}};

      Expected behavior

      Not clear why kafka keeps timing out randomly if I redeploy all works and then again it stops. Is it wrapper causing issues? These random issues makes me wonder what causes it.

      This is running on k8s and this behavior is seen in 1-2 users only, Kafka has enough memory!

      All consumers have different group Id and all have high session timeout as well.

      IIS EXECUTING ASP CLASS PAGES

      <div class="body">

      Hello and thank you for any support you can provide.

      I am runnig IIS 7.5 on a decicated Windws 2008 R2 Server. When I bring up Internet Information Service Manager and display the Application Pools all three of the application pools listed show a status fo Unknown and the icon appears with a red cycle and X.

      When attempting to start or stop any of the pools I receive the following error message.

      Cannot Start Applicaton Pool

      There was an error while performing this operation.

      Details

      Class not registered(Exception from HRESULT: 0x80040154

      (REDB_E_CLASSNOTREG))

      I currently only have one application running on this machine. OpenText DM. Although the machine has been running well for several months, this problem seems to be something that just recently began to occur.

      I have uninstalled the OpenText software, unintall IIS and uninstill WAS Windows Process Activation Service and reinstalled these components. It appeared this corrected the problem but within an hour the problem resurfaced.

      When the problem occurs and the OpenText site goes down I must manually restart the WAS service and the W3SVC service.

      I should note that there does not seem to be any event log messages related to this error either. This also seems to be the only machine in our environment currently expernencing this type of problem.

      Any help or suggests would be greatly appreciated.  Thanks

      </div>

      App crashed after deployed on Heroku. But it's working in my local.

      Anyone please help me .I am also getting the same error . i need an urgent help. I am using django and python 3.6.10 along with tensorflow =2.1 and keras

      Microsoft Windows [Version 6.3.9600] © 2013 Microsoft Corporation. All rights reserved.

      C:\windows\system32>heroku logs --tail » Error: Missing required flag: » -a, --app APP app to run command against » See more help with --help

      C:\windows\system32>heroku logs --tail -a healtech 2021-01-11T15:02:05.933848+00:00 app[web.1]: [2021-01-11 15:02:05 +0000] [11] [I NFO] Worker exiting (pid: 11) 2021-01-11T15:02:05.933853+00:00 app[web.1]: [2021-01-11 15:02:05 +0000] [10] [E RROR] Exception in worker process 2021-01-11T15:02:05.933854+00:00 app[web.1]: Traceback (most recent call last): 2021-01-11T15:02:05.933855+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/site-packages/gunicorn/arbiter.py”, line 583, in spawn_worker 2021-01-11T15:02:05.933855+00:00 app[web.1]: worker.init_process() 2021-01-11T15:02:05.933855+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/site-packages/gunicorn/workers/base.py”, line 119, in init_process 2021-01-11T15:02:05.933856+00:00 app[web.1]: self.load_wsgi() 2021-01-11T15:02:05.933856+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/site-packages/gunicorn/workers/base.py”, line 144, in load_wsgi 2021-01-11T15:02:05.933856+00:00 app[web.1]: self.wsgi = self.app.wsgi() 2021-01-11T15:02:05.933857+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/site-packages/gunicorn/app/base.py”, line 67, in wsgi 2021-01-11T15:02:05.933857+00:00 app[web.1]: self.callable = self.load() 2021-01-11T15:02:05.933857+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/site-packages/gunicorn/app/wsgiapp.py”, line 49, in load 2021-01-11T15:02:05.933858+00:00 app[web.1]: return self.load_wsgiapp() 2021-01-11T15:02:05.933858+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/site-packages/gunicorn/app/wsgiapp.py”, line 39, in load_wsgiapp 2021-01-11T15:02:05.933859+00:00 app[web.1]: return util.import_app(self.app_uri ) 2021-01-11T15:02:05.933859+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/site-packages/gunicorn/util.py”, line 358, in import_app 2021-01-11T15:02:05.933859+00:00 app[web.1]: mod = importlib.import_module(modul e) 2021-01-11T15:02:05.933860+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/importlib/init.py”, line 126, in import_module 2021-01-11T15:02:05.933860+00:00 app[web.1]: return _bootstrap._gcd_import(name[ level:], package, level) 2021-01-11T15:02:05.933861+00:00 app[web.1]: File "

      2021-01-11T15:02:06.408675+00:00 heroku[web.1]: State changed from crashed to st arting 2021-01-11T15:02:49.936312+00:00 heroku[web.1]: Starting process with command 2021-01-11T15:02:50.000000+00:00 app[api]: Build succeeded 2021-01-11T15:02:54.195478+00:00 app[web.1]: [2021-01-11 15:02:54 +0000] [4] [IN FO] Starting gunicorn 20.0.4 2021-01-11T15:02:54.196657+00:00 app[web.1]: [2021-01-11 15:02:54 +0000] [4] [IN FO] Listening at: http://0.0.0.0:36107 (4) 2021-01-11T15:02:54.201883+00:00 app[web.1]: [2021-01-11 15:02:54 +0000] [4] [IN FO] Using worker: sync 2021-01-11T15:02:54.217181+00:00 app[web.1]: [2021-01-11 15:02:54 +0000] [10] [I NFO] Booting worker with pid: 10 2021-01-11T15:02:54.234018+00:00 app[web.1]: [2021-01-11 15:02:54 +0000] [10] [E RROR] Exception in worker process 2021-01-11T15:02:54.234035+00:00 app[web.1]: Traceback (most recent call last): 2021-01-11T15:02:54.234040+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/site-packages/gunicorn/arbiter.py”, line 583, in spawn_worker 2021-01-11T15:02:54.234045+00:00 app[web.1]: worker.init_process() 2021-01-11T15:02:54.234045+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/site-packages/gunicorn/workers/base.py”, line 119, in init_process 2021-01-11T15:02:54.234046+00:00 app[web.1]: self.load_wsgi() 2021-01-11T15:02:54.234046+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/site-packages/gunicorn/workers/base.py”, line 144, in load_wsgi 2021-01-11T15:02:54.234046+00:00 app[web.1]: self.wsgi = self.app.wsgi() 2021-01-11T15:02:54.234051+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/site-packages/gunicorn/app/base.py”, line 67, in wsgi 2021-01-11T15:02:54.234051+00:00 app[web.1]: self.callable = self.load() 2021-01-11T15:02:54.234051+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/site-packages/gunicorn/app/wsgiapp.py”, line 49, in load 2021-01-11T15:02:54.234052+00:00 app[web.1]: return self.load_wsgiapp() 2021-01-11T15:02:54.234052+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/site-packages/gunicorn/app/wsgiapp.py”, line 39, in load_wsgiapp 2021-01-11T15:02:54.234052+00:00 app[web.1]: return util.import_app(self.app_uri ) 2021-01-11T15:02:54.234053+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/site-packages/gunicorn/util.py”, line 358, in import_app 2021-01-11T15:02:54.234053+00:00 app[web.1]: mod = importlib.import_module(modul e) 2021-01-11T15:02:54.234053+00:00 app[web.1]: File “/app/.heroku/python/lib/pytho n3.6/importlib/init.py”, line 126, in import_module 2021-01-11T15:02:54.234054+00:00 app[web.1]: return _bootstrap._gcd_import(name[ level:], package, level) 2021-01-11T15:02:54.234054+00:00 app[web.1]: File "

      Read these next...

      I have an HP P3015n printer that was fully functional. We did a firmware upgrade on it. The upgrade appeared to finish normally, but the printer now displays "49 4C01 error." A search of the web shows little info for this error.

      I can FTP into the print server, but get this:

      230-Hewlett-Packard FTP Print Server Version 3.0.
      Directory:    Description:
      --------------------------
      PORT          Unknown peripheral

      To print a file use the command put <filename> [portx]
      or 'cd' to a desired port and use put <filename>.

      230 User logged in.
      ftp>

      -----A Good version of this printer shows the following:--------------------

      230-Hewlett-Packard FTP Print Server Version 3.0.
      Directory:    Description:
      --------------------------
      PORT          HP LaserJet P3010 Series

      The obvious difference is the "unknown peripheral."

      I've tried the usual steps and had no luck. Any thoughts on what might be my options here?

      • All i can find with regards to this error popping up after a FW upgrade is to roll back to the previous version of the firmware that was installed. Let's wait what Priscilla has to say about it.

        Was this post helpful?thumb_upthumb_down
      • Holding X while booting, then OK, then menu bring you to a menu that lets you:

        select writing over the NAND with AAAA (far too easily by accident) -- this is not the correct approach.

        Now, the display won't even light. I suspect the JetAdmin software has been overwritten.

      • Hello Robert, it's unfortunate that your HP LaserJet P3015n has created challenges for you and your team after upgrading the firmware.  Thanks for the informative details and also thanks to Edwin for his helpful input.

        Knowing you both, I regret asking if you have seen some of the solutions in the post below--especially since Robert states that he had done the usual troubleshooting.  Just in case let me share it.  Most likely you have performed the steps listed in the post regarding a similar code:  49-4C02.  However, you will notice that one member advises:

        A WikiHow link gives steps for initializing the NVRAM to clear the 49-4C02, but this may not apply to you as you did only a firmware update.

        Based on your FTP results, let me also send this post to our consultant to review.

        Was this post helpful?thumb_upthumb_down
      • Thanks, Priscilla.

        Yes, the 49.4C02 error is generated by a print job that the printer could not interpret. I believe that the 4C01 error is generated when the JetDirect server can't communicate with the printer firmware, so it doesn't know how to send print jobs to the engine.

        As I said, through some unfortunate exuberance, I believe we have erased the JetDirect software. We went from being able to access via FTP or HTTP to no network capability to no display at all now when power is applied.

        Thanks for any help you may be able to provide (such as the magic startup sequence to reload the NAND).

      • I thougt it was the 4CO1 and not CO2 error that was generated

      • Edwin_Eekelaers wrote:

        I thougt it was the 4CO1 and not CO2 error that was generated

        Yes, it is the 4C01 that was produced. Now, the printer just stays dark.
      • Hello Robert, thank you very much for your reply.  Our consultant, who hasn't been updated regarding the printer now staying dark, provides the following:

        • Unplug network cable. Any flashing lights on the printer after turning it on? Any sign of life or flash on the display?
      • With no cables connected, I plug in a power cord and press the power button. The power button illuminates. The LCD screen stays dark. The 3 LEDs do not light. There are no motor or fan sounds from the printer. It is completely inert.

      • Hello again Robert, here is some additional information from our consultant:

        ###################
        Issue: HP LaserJet P3015n - 49.4C01 error after firmware update

        Almost dead fish, but not yet.

        Memory RAM
        The random access memory (RAM) on the formatter PCA contains the page, I/O buffers, and the font storage area. It stores printing and font information received from the host system, and can also serve to temporarily store a full page of print-image data before the data is sent to the print engine. Memory capacity can be increased by adding a DIMM to the formatter. Note that adding memory might also increase the print speed for complex graphics.

        Firmware NAND
        The firmware is contained on NAND flash memory soldered on the formatter board. A remote firmware upgrade process is available, which overwrites the firmware in the NAND flash.

        Nonvolatile memory NVRAM
        The product uses nonvolatile memory (NVRAM) to store device and user configuration settings. The contents of NVRAM are retained when the product is turned off or disconnected.




        Please check heart beat of the "printer"?
        Turn off and wait a while.

        Turn on.

        Observe formatter heartbeat LED number 2.


        ###################

        Please keep us updated as we are also eager for you to have your printer working again.

        Was this post helpful?thumb_upthumb_down
      • Please check heart beat of the "printer"?
        Turn off and wait a while.

        Turn on.

        Observe formatter heartbeat LED number 2.

        Power on = No heartbeat. (The NIC light flickers once when power is removed.)

        There was a heartbeat and I could access it via telnet until we accidently overwrote the NAND with AAAA.

        Tomorrow we're all out of the office for a seminar, but Thursday I will crack open the printer and try a remove/replace on the connectors, memory, and formatter board.

        Please, HP, don't let my printer die! :-O

      • Hello Robert, thanks for the quick update, stoicism, and humor.  We will try our best not to let your "printer die".   We eagerly await your next reply.

        I love the fish--yours and the consultant's.  Now I feel that I shouldn't have reigned in the consultant's sense of humor given your reply.  He had written something else that was light-hearted, but I said one instance of humor is enough for someone who is frustrated with his printer.  Now I can hear miles away, the consultant saying "ha, ha, ha".


        Was this post helpful?thumb_upthumb_down
      • Too funny. No, I'm not frustrated with the printer - or HP. Just one of those things that happens sometimes. I mean, someone has to be on the low end of the "average time to failure," right?

        I did reseat all the connectors. There is no additional memory. And, still, no heartbeat. (Just heartache, but that doesn't blink.)

        Give it to me straight, doc. Is my printer toast?

        Was this post helpful?thumb_upthumb_down
      • No Robert don't send it to Texas yet for the explosive printer contest... am sure Priscilla will find a solution.

        No thinking like Grumpy Cat yet...

        Was this post helpful?thumb_upthumb_down
      • 1. Tried the engine-test button. No results.

        2. Removed the formatter board. Tried the engine-test button. No results.

        Green power button is illuminated, but display is still dark.

      • Hello Robert, a remarkable troubleshooter ... and humorist. Your sentence:  "Give it to me straight, doc. Is my printer toast?" and Edwin's post made me laugh...again.   Here is some additional information from the consultant.  It came earlier this afternoon:

        #################
        "Without the the main fan on the right side running for a short time and without the heartbeat the engine controller is not operational. Thus pressing engine test button can't produce anything. See block diagram below.

        HP LaserJet P3010 Series Printers Service Manual (Even though you've shared that you are reviewing the manual, having the link maybe helpful to others visiting the post.)

        What we know:
        Printer was working but developed 49.4C01 error after the firmware update.
        Subsequent writing over the NAND with AAAA led to the following condition:
        Green power button is illuminated, but pressing it doesn't produce any action.
        Display is dark.

        No lights are on or flashing.

        Main fan doesn't run even for a short while.

        No heartbeat of the formatter.

        It is my opinion considering the summary above the printer is bricked. There is no working firmware currently on the printer.

        Engine-control system
        The engine-control system coordinates all product functions, according to commands that the formatter sends. The engine-control system drives the laser/scanner system, the image formation system, and the pickup/feed/delivery system.
        The engine control system contains the following major components:
        ● Engine-control unit (ECU)
        ◦ DC controller
        ◦ Low-voltage power supply
        ● High-voltage power supply



        Formatter-control system

        The formatter is responsible for the following procedures:
        ● Controlling sleep mode
        ● Receiving and processing print data from the various product interfaces
        ● Monitoring control-panel functions and relaying product-status information (through the control panel and the network or bidirectional interface)
        ● Developing and coordinating data placement and timing with the DC controller PCA
        ● Storing font information
        ● Communicating with the host computer through the network or the bidirectional interface
        The formatter receives a print job from the network or bidirectional interface and separates it into image information and instructions that control the printing process. The DC controller PCA synchronizes the image-formation system with the paper-input and -output systems, and then signals the formatter to send the print-image data.
        The formatter also provides the electrical interface and mounting locations for one EIO card and an additional DIMM.

        Remove all EIO devices from the product.

        Page 60, Removal and replacement procedures: Formatter cover and formatter PCA.

        Power-on checks
        Turn on the power. If the control-panel display remains blank or if it displays random patterns or asterisks, perform the power-on checks to find the cause of the problem.
        1. Verify that the product is plugged into an active electrical outlet that delivers the correct voltage.
        2. Verify that the power switch is in the ON position.
        3. Make sure that the main fan on the right side runs for a short time.
        ● If the control-panel display is blank, but the main fan runs after the power is turned on, print an engine test page to determine whether the problem is with the control-panel display, the formatter, or other components. See Engine diagnostics on page 134.
        ● The overcurrent/overvoltage protection circuit in the low-voltage power supply unit might be running. Turn the printer off, unplug the power cord, and turn the printer on. If the printer does not function, the fuse melts, or the power supply is malfunctioning, replace the engine controller unit. See Engine control unit (ECU) on page 110.
        ● Verify that the LEDs at the back of the product on the formatter, are functioning correctly. See LED diagnostics on page 133.
        4. Remove any HP Jetdirect or other EIO cards, and then turn off and turn on the product."

        #################


      • It is my opinion considering the summary above the printer is bricked. There is no working firmware currently on the printer.

        Hmm. Now, I ask in all seriousness, how does one un-brick a printer? By that I mean the printers aren't born with firmware in them, so they must be programmed at some point. I will accept that it might be the case that this is a manufacturing process and there is no procedure that can be applied in the field to write the firmware. Is that true?

        Is it true that the (ex) firmware in question resides on the formatter board? If so, will replacing the formatter board with one on which I haven't performed my unique brand of maintenance re-animate the printer? Formatter boards are fairly easy to come by for this printer.

        What is the possibility that I've damaged other components besides the formatter board by wiping out the firmware? I did write over NAND1. But I resisted the urge to "Copy NAND1 to NAND2."

        Finally, one last question (and I really do appreciate your patience and assistance):

        Why has HP programmed what is essentially a kill button into this printer unless it provided a way to re-write the NAND?

      • Hello Robert,

        Thanks for your questions and additional information.  Yes, I will be checking with HP Support on how to unbrick your printer .  When you and your staff return and at your convenience do you mind providing me with a serial number for the "bricked" HP LaserJet P3015n so that I can talk with an HP technician?  See below the consultant's responses to your questions:

        #############
        Right, the printers aren't born yet with firmware in them like Goa'uld with their genetic memory. Printers are still produced in an ordinary fashion.


        ​Formatter PCA = equivalent of brain and memory. Part number: CE475-67901 (new), CE475-69001 (exchange).

        Engine controller PCA = equivalent of muscles.

        Normal start up initialization
        ● The heartbeat LED indicates that the formatter is functioning correctly. While the product is initializing after you turn it on, the LED blinks rapidly, and then turns off. When the product has finished the initialization sequence, the heartbeat LED pulses on and off.
        ● The main fan's spin up for a short time during the initialization indicates that the engine controller is functioning correctly.

        1. Re: Un-brick

        I have already asked [email protected] yesterday to check if there is a way to un-brick the printer in the field. It is fairly easy on some printers with card reader or USB socket.

        2. Re: Firmware and replacing the formatter
        The firmware is contained on NAND flash memory soldered on the formatter board.
        ○ ○ I would try to replace the formatter in question as a starting point to verify that other parts of the printer are performing correctly. It could be that engine controller has been already faulty. See point 4. You can use formatter from other working printer.

        ○ ○ Then run diagnostics:
        Page 134: Print the engine test pages
        NOTE: A damaged formatter might interfere with the engine test. If the engine test page does not print, try removing the formatter and performing the engine test again. If the engine test is then successful, the problem is in the formatter, the control panel, or the cable that connects them together.

        Page 194: Diagnostics menu

        3. Re: Damage to other components by wiping firmware

        This possibility is in my opinion remote. See point 4. There are many control and protective mechanisms integrated into the printers.

        4. Re: A kill button?

        Highly disputable under the circumstances. Firmware update on printers is a quite a robust process today. Any corruption or complications are rare.
        The fundamental question here is why the first firmware update led to 49.4C01 error after the reboot?
        ○ Something already wrong with the printer before the update?
        ○ Corrupted data  during the network transfer?
        ○ Freaky coincidence?
        It could be that write over NAND1 would work under other circumstances. We will never know.

        #############

        Enjoy your off-site seminar.

        Was this post helpful?thumb_upthumb_down
      • [email protected] wrote:

        4. Re: A kill button?

        Highly disputable under the circumstances. Firmware update on printers is a quite a robust process today. Any corruption or complications are rare.
        The fundamental question here is why the first firmware update led to 49.4C01 error after the reboot?
        ○ Something already wrong with the printer before the update?
        ○ Corrupted data  during the network transfer?
        ○ Freaky coincidence?
        It could be that write over NAND1 would work under other circumstances. We will never know.

        #############

        Let me clarify my question. Completely separate from the firmware upgrade, the printer, on bootstrap, allows me to use a 3-button sequence to get into an advanced menu. On that menu is the option to overwrite the NAND memory. (The option that was activated by accident by yours truly.) My question is, under what circumstances would that command be used? If it wipes out the firmware (in the field), there must be an option to restore the firmware (in the field) or the printer couldn't be returned to service. So, that gave me some hope that an in-field firmware restore can be done.

        Goa'uld? +1 for the Stargate reference.

        Firmware updates: If at first, you don't succeed...



      • Hello Robert, thanks for the clarification and welcome back from your seminar.  Please see input from the consultant:

        \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
        ● Remove please formatter.
        ● Insert paper into Tray 2, which is the built-in (not optional) tray cassette at the bottom of the printer.
        ● Turn on the printer.
        ● Press and hold the engine test page switch.

        Page 134: Engine diagnostics
        Printing test pages helps you determine whether or not the product engine and the formatter are functioning.
        NOTE: Information pages also can be used to solve product issues. For information about printing information pages, see the product user guide.

        Engine-test button
        To verify that the product engine is functioning, print an engine-test page.

        Print the engine test pages
        NOTE: A damaged formatter might interfere with the engine test. If the engine test page does not print, try removing the formatter and performing the engine test again. If the engine test is then successful, the problem is in the formatter, the control panel, or the cable that connects them together.

        1. Remove the DIMM cover. See DIMM cover and DIMM on page 57.
        2. Press the engine test-page button (callout 1).




        The test page should have a series of horizontal lines. The test page prints from the last tray that the product used to print, unless the product has been turned off and then turned on again since the most recent print job. If the product has been turned off and then on again since the most recent print job, then the page will print from Tray 2. The product continuously prints test pages as long as the test-page switch is depressed. The product will not print a test page if it is in Sleep mode.
        /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\



      • 1. Removed the formatter board.
        2. Put tray with paper into the built-in tray.
        3. Apply power - power button lights, fan does not spin.
        4. Press and hold engine test page switch - nothing happens.

        INSTALL NEW FORMATTER BOARD.
        1. Power on the printer.
        2. LCD display lights up and printer POSTs.
        3. Fan does not spin.
        4. Engine test page switch does nothing.
        5. Display activity terminates showing "49.4C01 ERROR"
        6. Heartbeat is active.

        The printer is currently not pulling a DHCP address. I am trying to establish communication with it now.

      • Robert5205 That tell's us the Engine PCB is defective. It's what controls the fans, and communication between the Formatter , and the printer. With the formatter removed If the engine were functional it would print an engine test print. The whole purpose of that test is to check functionality of the engine. Since it fails the engine is failing it own basic test. 

        From the service manual that [email protected] references. Pages  284 & 285 item # 6 Engine controller PCA 110V RM1-6281-000CN.

        Was the formatter that you installed last a new one, or one borrowed from another printer?

        Without a functional engine you will not get an IP address.

        Was this post helpful?thumb_upthumb_down
      • The formatter board was from a working printer.

        If the engine PCA is bad, I have to wonder about the order. Did the engine PCA go bad, coincidently with and unrelated to the firmware upgrade? After the upgrade, however, the printer was still reachable via IP. Did something I did to the old formatter cause the PCA to go bad? If so, what?

        Too many questions and no log files. I think it's interesting that I could reach the jet direct server, but it couldn't identify the printer. That may indicate that the engine had failed at that time.

      • It's quite possible that the engine was already going bad, and the firmware update just finished it off when it went to copy the config to the engine.

        On these newer HP printers you can not just swap out the formatter, AND engine at the same time. The reason for this is that a backup copy of the printers configuration is stored on each.

        During the replacement of one, or the other the backup copy of the configuration is written to the new part from the old one still  remaining. (Ie. While powered down with the old engine in place, a new formatter is installed. Upon power up the printers configuration is downloaded to the new formatter from the old engine.) It's the same if it's the engine being replaced, but the engine get the configuration from the formatter in that case.

        Here is a link from an HP forum that discusses this very error. Pay particular attention to the last 3 comment from davidzuts, and fern88. Error 49.4C01, cannot clear error to install new firmware.

        Edited to add:

        When you replace the engine. Make absolutely sure that you have the original formatter installed, and not one from another printer! If you have the wrong formatter installed your new engine will get the config for the wrong printer. You'll suddenly have 2 identical printers on you network! Not something you want..... :o)

      • Robert5205 wrote:

        After the upgrade, however, the printer was still reachable via IP. 

        I think it's interesting that I could reach the jet direct server, but it couldn't identify the printer. That may indicate that the engine had failed at that time.

        Yes since the formatter already the IP address it retained it until you cycled the power, at which time it could no longer get an IP address.

        It could not identify the printer because the formatter lost communications to the engine.

        These newer HP printers are a lot more complicated than the older one's were. It used to be if the formatter failed you lost the entire printer config., Serial Number, Page Count, Etc. Now there is a backup copy on the engine.

        These are now mated pairs, and you should only replace one at a time.

      • Hmm. Very interesting posts. I'm interpreting that to mean that the new formatter board I put into the printer is now "poisoned"? It was corrupted by the ECU in the non-working printer. But, if I put it into a different printer, that printer's ECU will re-write it and it should be okay?

        That makes sense.

      • I doubt that the formatter you installed was corrupted in any way since the engine is non functional.

         If it was pulled from another working printer you should be ok. When you reinstall it in the original printer it'll get the config from that printers engine, and return it to normal for that printer, on the ODD chance that it did get any info from the engine.

      • Thanks, Ken. I'd like to keep the spare formatter around. But I don't want the corruption to spread.

      • You don't have to worry about any corruption spreading. That's just not a possibility. Hope that eases your mind.

      • KenBurgess wrote:

        During the replacement of one, or the other the backup copy of the configuration is written to the new part from the old one still  remaining. (Ie. While powered down with the old engine in place, a new formatter is installed. Upon power up the printers configuration is downloaded to the new formatter from the old engine.) It's the same if it's the engine being replaced, but the engine get the configuration from the formatter in that case.

        Maybe you can reconcile your last post with a previous one.

        This seems to indicate that the configuration from the bad engine will be written to the new formatter. Now, I interpreted "configuration" to mean whatever was causing the error, ie, corrupted firmware. If not, what exactly is copied?

        You also mentioned that replacing them in the wrong order would create a duplicate printer. What would make the printer identical? MAC?

      • Sent you a PM.

      • Art Imitates Life: DALL·E 2 AI Generates Art Featuring IT Professionals

        Art Imitates Life: DALL·E 2 AI Generates Art Featuring IT Professionals

        Water Cooler

        In my last post about computer generated art, I tested artificial intelligence's ability to create orange T-Rex art in the style of many famous artists, using OpenAI's DALL·E 2 AI.Quick recap of how DALL·E 2 works. Users can request images of anything by ...

      • Snap! Azure outage, malware in JWST images, floppy disks, Voyager 1, & more

        Snap! Azure outage, malware in JWST images, floppy disks, Voyager 1, & more

        Spiceworks Originals

        Your daily dose of tech news, in brief. While the month may be ending, we're halfway through the week. Let's jump into today's Snap! and see some of the things going on in the world. You need to hear this. Microsoft Azure outage knocks Ubuntu...

      • Monitor our Weblogs

        Monitor our Weblogs

        Security

        Hi,I would like to ask for your recommendations on how I can capture the websites our end users access during office hours.our current firewall doesnt support it as it only logs HTTP connections and we all know that almost all of the websites now are usin...

      • How to keep a record on my phone: of my own calls I will fix or need to fix

        How to keep a record on my phone: of my own calls I will fix or need to fix

        IT & Tech Careers

        I am the sole I.T. guy for a company.That has Servers/ NAS, I manage the PIX firewall. take full responsibility of all data including accounting Backups on NAS, Servers, Camera ( recordings).Do Cabling/Crimping as needed ,Set up VPN for remote folks,  Pur...

      • Spark! Pro series - 31st August 2022 - The Bacon Day Edition

        Spark! Pro series - 31st August 2022 - The Bacon Day Edition

        Spiceworks Originals

        Today in History: 1142 Possible date for establishment of the Iroquois (Haudenosaunee) LeagueCenturies before the creation of the United States and its Constitution, democracy had already taken root in North America—among a handful of Indigenous nations. ...

      0 Comments

      Leave a Comment