Urgent Attention Required for IM C2010 Printer Issue.

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • Gift
    replied
    I would agree with you if it were a single printer or 2-3 printers at the same location. However, this issue is occurring across 20-23 different customer locations. Additionally, even after disconnecting the LAN, the machine is unable to print anything, even after performing a memory clear and HDD format.
    That's hard to believe that this affects so many devices at the same time. Did they all received a firmwareupdate beforehand? Did you try and reset the machine with the data clear feature in admin tools (aka not SP mode)?

    Usually in these cases issues are gone if you hook up your laptop with a direct lan connection and to a test print.

    Leave a comment:


  • nadimtopsecret
    replied
    Update -
    Tried with replacing a BICU, but not resolve

    Leave a comment:


  • nadimtopsecret
    replied
    Originally posted by slimslob

    And in the early days of the MP CXX03 occurred worldwide.
    Yes, that's correct. However, I’ve also gathered information from India and they haven’t faced any similar cases so far in the IM C2010. Additionally, in our country, over 60+ devices of the same model have been installed, but only 20-25 of them are affected.

    Leave a comment:


  • slimslob
    replied
    Originally posted by nadimtopsecret


    I would agree with you if it were a single printer or 2-3 printers at the same location. However, this issue is occurring across 20-23 different customer locations. Additionally, even after disconnecting the LAN, the machine is unable to print anything, even after performing a memory clear and HDD format.
    And in the early days of the MP CXX03 occurred worldwide.

    Leave a comment:


  • nadimtopsecret
    replied
    You can check the video of the problems video here -

    Leave a comment:


  • nadimtopsecret
    replied
    Originally posted by slimslob

    As soon as a corrupted job comes in on the LAN cable, it is queued to the engine. The engine then will not accept anything else until that job. Until you identify that job and delete it at the source you are not going to be able to do anything else. The only other methods will cause the customer to lose all jobs currently in queue. One of the methods that used to be used for jobs causing SC899 was to enable user authentication for the printer. When you connect the LAN cable all jobs will be rejected that do not have a valid user.

    I would agree with you if it were a single printer or 2-3 printers at the same location. However, this issue is occurring across 20-23 different customer locations. Additionally, even after disconnecting the LAN, the machine is unable to print anything, even after performing a memory clear and HDD format.

    Leave a comment:


  • nadimtopsecret
    replied
    Originally posted by copier tech

    Did you get a chance to update the ACT versions ?
    Yes, ACT is activated in the machine.

    Leave a comment:


  • slimslob
    replied
    Originally posted by nadimtopsecret


    I believe this issue is quite different from the earlier one.

    After installing the new printer, I noticed the problem started when I tried to set up the IP address and connected the LAN cable to the machine. Before establishing LAN connectivity, I was able to copy/print via USB and counter printing was functioning normally. However, the situation changed as soon as the LAN was connected.
    As soon as a corrupted job comes in on the LAN cable, it is queued to the engine. The engine then will not accept anything else until that job. Until you identify that job and delete it at the source you are not going to be able to do anything else. The only other methods will cause the customer to lose all jobs currently in queue. One of the methods that used to be used for jobs causing SC899 was to enable user authentication for the printer. When you connect the LAN cable all jobs will be rejected that do not have a valid user.

    Leave a comment:


  • nadimtopsecret
    replied
    Originally posted by luca72

    months ago the same thing happened to a customer, with mp3353, 2501 and 4054, only that the internal prints worked.
    there were some windows pc in the network that had self-installed the printer with wsd port, in addition to the one installed by the IT with regular ip port, the customers when they printed sometimes without checking used the wsd one, and the sc code occurred, I disabled wsd and ssdp, and removed the duplicate printers with wsd port... but I repeat, they printed the counter and internal print....Isn't postscript needed?

    I believe this issue is quite different from the earlier one.

    After installing the new printer, I noticed the problem started when I tried to set up the IP address and connected the LAN cable to the machine. Before establishing LAN connectivity, I was able to copy/print via USB and counter printing was functioning normally. However, the situation changed as soon as the LAN was connected.

    Leave a comment:


  • luca72
    replied
    Originally posted by nadimtopsecret


    I've attempted replacing both the SSD and HDD, but the issue persists. It's important to note that this problem has occurred in over 20 devices across various customer locations. Interestingly, only few devices of the same model are functioning correctly. Additionally, one of our clients has two IM C2010 models — one is working fine, while the other is affected.
    months ago the same thing happened to a customer, with mp3353, 2501 and 4054, only that the internal prints worked.
    there were some windows pc in the network that had self-installed the printer with wsd port, in addition to the one installed by the IT with regular ip port, the customers when they printed sometimes without checking used the wsd one, and the sc code occurred, I disabled wsd and ssdp, and removed the duplicate printers with wsd port... but I repeat, they printed the counter and internal print....Isn't postscript needed?

    Leave a comment:


  • copier tech
    replied
    Originally posted by nadimtopsecret


    I've attempted replacing both the SSD and HDD, but the issue persists. It's important to note that this problem has occurred in over 20 devices across various customer locations. Interestingly, only few devices of the same model are functioning correctly. Additionally, one of our clients has two IM C2010 models — one is working fine, while the other is affected.
    Did you get a chance to update the ACT versions ?

    Leave a comment:


  • nadimtopsecret
    replied
    Originally posted by luca72

    it shouldn't!... but on previous versions that symptom was created by crumpled paper at the bottom, behind the drawer.
    you can also try formatting only the IMH partition of the hdd via sp

    I've attempted replacing both the SSD and HDD, but the issue persists. It's important to note that this problem has occurred in over 20 devices across various customer locations. Interestingly, only few devices of the same model are functioning correctly. Additionally, one of our clients has two IM C2010 models — one is working fine, while the other is affected.

    Leave a comment:


  • luca72
    replied
    Originally posted by nadimtopsecret

    Yes, you're right.
    it shouldn't!... but on previous versions that symptom was created by crumpled paper at the bottom, behind the drawer.
    you can also try formatting only the IMH partition of the hdd via sp

    Leave a comment:


  • nadimtopsecret
    replied
    Originally posted by luca72

    if I understood correctly, beyond the problems with the PCs, you said that it doesn't even print the counter, or the network settings page?...right?
    Yes, you're right.

    Leave a comment:


  • luca72
    replied
    Originally posted by nadimtopsecret

    Ohh ! My mistakes that I didn't mention it before.
    I'll check with the ACT enable then update you soon.
    if I understood correctly, beyond the problems with the PCs, you said that it doesn't even print the counter, or the network settings page?...right?

    Leave a comment:

Working...