nickjnford

Q: Why won't my new Canon LiDE 210 scanner work?

My Mac Mini running Mavericks recognizes that the scanner is connected (by USB cable) but when I click Open.. there is an error message "Failed to open a session on the device". I opened Software Update and there are no updates available. I am very confused about this because the documentation with the scanner says that I should install the software bundled with the product but I have read that OS X handles scanning (and printing) itself. What should I do to get my scanner working? I have tried rebooting the computer to no effect.

Mac mini (Late 2012), OS X Mavericks (10.9.1)

Posted on Feb 23, 2014 8:20 AM

Close

Q: Why won't my new Canon LiDE 210 scanner work?

  • All replies
  • Helpful answers

  • by den.thed,

    den.thed den.thed Feb 23, 2014 8:40 AM in response to nickjnford
    Level 7 (27,395 points)
    Feb 23, 2014 8:40 AM in response to nickjnford

    Does it scan using Image Capture?

     

    see > Mac Basics: Using a scanner

  • by Eric Root,

    Eric Root Eric Root Feb 23, 2014 9:40 AM in response to nickjnford
    Level 9 (69,881 points)
    iTunes
    Feb 23, 2014 9:40 AM in response to nickjnford

    If den.thed suggestion doesn't work, try installing the software as Canon stated. HP has separate software.

  • by nickjnford,

    nickjnford nickjnford Feb 23, 2014 10:45 AM in response to Eric Root
    Level 1 (0 points)
    Feb 23, 2014 10:45 AM in response to Eric Root

    No result with either Image Capture, System Preferences Printers & scanners, or with VueScan software. Error message "Failed to open a session with the device". VueScan message "No scanners were found connected to your computer". Tried different USB ports and rebooting the computer. Have tried with and without the Canon driver that came bundled with the scanner. The Canon website confirms that the driver is compatible with OS 10.9. The scanner makes noises when starting the software. The scanner is correctly identified in the list of devices in the System Preferences Printers & scanners dialog so the computer obviously knows that it is connected. It just looks to me like Macs will not work scanners.

  • by karlmd,

    karlmd karlmd Apr 21, 2014 10:50 AM in response to nickjnford
    Level 1 (0 points)
    Apr 21, 2014 10:50 AM in response to nickjnford

    So it seems there's no resolution to this problem yet? I have the same issue and can't find a solution anywhere online at this time. I have a MacBook Pro on OS X 10.9.1.

  • by Graham.D,

    Graham.D Graham.D May 9, 2014 7:30 AM in response to karlmd
    Level 1 (0 points)
    May 9, 2014 7:30 AM in response to karlmd

    I found I needed to unlock the scanning mechanism located on the bottom surface of the scanner.  Once I had done this, I was able to scan successfully in Preview and Image Capture.  I discovered this by watching the scanner with the lid open when I plugged the scanner into the USB port.  The movement tried to move and then stopped.  That made me think the platten was jammed, and then I thought perhaps it was locked when it was shipped.

  • by skh1454,

    skh1454 skh1454 Jun 14, 2014 4:23 PM in response to nickjnford
    Level 1 (0 points)
    Jun 14, 2014 4:23 PM in response to nickjnford

    It appears Mavericks does not support the LiDE 20 drivers or CanoScan Toolbox -- I had the same problem with my MacBook when I upgraded to Mavericks.  The scanner worked great under the previous systems.  My problem is that the Mac does not recognize that the scanner is connected.  I tried installing a couple versions of some driver software (from Ellert) which some users claim works, but it did nothing for me.  But VueScan did work for me.  The only problem is that VueScan basic is $40; if you want OCR, the "pro" version is $80.  I can get a new LiDE 110 for $50 -- with more features and much higher resolution, and (according to Canon) it's compatible with OSX 10.9.  Looks likes it time for a new scanner.

  • by LondonBlue,

    LondonBlue LondonBlue Jul 21, 2014 2:15 AM in response to nickjnford
    Level 1 (0 points)
    Jul 21, 2014 2:15 AM in response to nickjnford

    For some reason my LiDE 210 scanner stopped being recognised. It had worked in Mavericks but in 10.9.4 it wasn't playing ball.

     

    I reinstalled the Canon utilities with no luck. I then went to Printers & Scanners in system preferences, deleted the CanoScan LiDE 210 (click on the - sign) and then re-added it. Then I set "scan button" to "Open Image Capture". And bizarrely, although I had disconnected and reconnected the USB cable at the computer end, I hadn't done so on the scanner end. For some reason, some combination of these caused the scanner to spring back into life and it's now working. Apologies it's not very scientific but it did seem to work. I wonder if it's a USB power issue of some kind. The cable is not damaged, to my knowledge, and I plug directly into my Mac Mini (ie not via a hub or splitter). It's a pain to do this kind of guesswork but it does seem that all is not lost.

  • by TheUDM,

    TheUDM TheUDM Sep 2, 2014 10:00 PM in response to nickjnford
    Level 1 (0 points)
    Sep 2, 2014 10:00 PM in response to nickjnford

    Had the same problem. Found out that the reason was USB-cable. Replaced it and now my scanner works!

  • by Chelsea-Steve,

    Chelsea-Steve Chelsea-Steve Sep 16, 2014 5:13 AM in response to nickjnford
    Level 1 (0 points)
    Sep 16, 2014 5:13 AM in response to nickjnford

    So I too had this problem with a brand new Lide 210 straight out of the box and did all of the above. After a long frustrating time, installing, uninstalling etc etc, I unplugged the lead from the back of the scanner and plugged it back in again. It worked.

  • by contrarymotion,

    contrarymotion contrarymotion Apr 10, 2016 3:11 PM in response to LondonBlue
    Level 1 (4 points)
    Apr 10, 2016 3:11 PM in response to LondonBlue

    Thank you!

     

    Julian

  • by VikingOSX,

    VikingOSX VikingOSX Apr 10, 2016 4:03 PM in response to nickjnford
    Level 7 (20,591 points)
    Mac OS X
    Apr 10, 2016 4:03 PM in response to nickjnford

    [redacted - /viking]