Clicky

Hello guys/gals
I have a single workstation (XP Pro SP3) with a USB Canon DR2010C scanner that will not scan duplex - it is not a hardware issue - have tried different DR2010's and same issue - if you set to duplex you get the front side but the back side images never appear. This happens if you have it set to to straight duplex or on "Drop blank pages". I have stripped the drivers out - reloaded - updated to most recent versions (1.3) and updated the Capture Perfect software to 3.0.097 (most current versions of both from Canon's website).  Canon tech support suggested setting everything back to default but that did not correct the issue either.  If you switch the scanner to another workstation it scans correctly.  I have tried both the ISIS and TWAIN configurations - same result

It started in the middle of the day last week - reset the system via a Restore Point to a couple days prior and it did not correct it either

Any idea as to what i may be missing here? All of our support vendors on this are as confused as I have been on this.  

asked 08/06/2011 04:17

BBerry0103's gravatar image

BBerry0103 ♦♦


11 Answers:
Two ideas: (1) Try a different USB port. (2) Try a different USB cable (I never cease to be amazed at how many problems are due to a bad cable). (3) That scanner comes bundled with other software besides Capture Perfect. Try it with one or more of those other packages (PaperPort, OmniPage, eCopy), or even with other software that supports TWAIN, such as IrfanView (<http://www.irfanview.com>). I'm not suggesting that these are permanent solutions – just trying to troubleshoot and isolate the problem. Regards, Joe
link
joewinograd's gravatar image

joewinograd

Er, make that three ideas. :)
link
joewinograd's gravatar image

joewinograd

:D Joe,
 No worries -  The more ideas the better at this point -

A) actually tried a new port after the Uninstall process - no dice there - got same thing
B) Have not tried a new cable - it is "suppose" to be a new setup so I did assume that the tech's who did the original install used a new one - but then again that is an assumption ( I am taking over support for their imaging systems as of this week and see what they give me!)
C) I used the PIXTran software and have gotten same results - also we primarily use EMC's ApplicationXtender Document Mgmt software and got same results from there  - I uninstalled AX before reloading the drivers and updating them to most recent versions - it has not been reloaded yet as the original thought was it was an app issue with AX but getting same results no matter what we use so far
link
BBerry0103's gravatar image

BBerry0103

Since you're getting the same results with other software, that at least rules out Capture Perfect as the culprit...one down and lots to go. :)

OK, here's what we know: (1) it works fine on another workstation, so that tells us it's not the scanner, but (2) it does not work after resetting to a Restore Point from a time prior to the problem, so that tells us it's not the software environment.

If it's not the scanner and not the software, what's left? The XP hardware! Or something connected to the XP hardware (cable). Regards, Joe
link
joewinograd's gravatar image

joewinograd

is the station on which it works at the same update level, and has the same OS?
link
nobus's gravatar image

nobus

Joe,
Changed out everything now that is possible to be changed - no change - now its getting really weird - if you scan direct to a file - it does duplex - when you view the image after all the pages that you would expect are there.....Reloaded the AX app - tried to scan direct and get the same thing as if I am scanning to Capt. Perf.  

Nobus: Yes they have the same OS and patch level / same software sets installed
link
BBerry0103's gravatar image

BBerry0103

the only valid test i see is installing a pre -SP3 XP on a disk , or partition to test
link
nobus's gravatar image

nobus

> Reloaded the AX app - tried to scan direct and get the same thing as if I am scanning to Capt. Perf.

Pretty much says that the AX app creates a conflict. But isn't the AX app also on the other machine that works fine?!

Btw, when you say "scan direct" in the above line, exactly what do you mean?
link
joewinograd's gravatar image

joewinograd

Scan direct - just scan and create a file instead of scanning the document and saving it after it is done - sorry that was a bit confusing I know.

AX is not causing the conflict.  The only reason i tossed it back on is the fact that you could get it to half work by scanning direct first - AX works in this same fashion - as you scan the files are created in the document store.  

Here is the funny part - at first it didnt work - did same thing as before - I strolled through the registry looking for something / anything that didnt look right - everything seemed to be in order

Exited there - relaunched the scanner app - and guess what - YEP it works fine...Scans as expected.

AX working correctly as well - I do not have a clue as to what made it work now as apposed to before

Thanks for all of your insight on this and giving me someone to bounce stuff off of .....
link
BBerry0103's gravatar image

BBerry0103

joewinograd was very helpful on this matter
link
BBerry0103's gravatar image

BBerry0103

Phase of the moon? :)  Sounds like one of those occasional, temporary glitches that goes away as mysteriously as it appears. Let's hope it stays away! Regards, Joe
link
joewinograd's gravatar image

joewinograd

Your answer
[hide preview]

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Tags:

×5
×1
×1

Asked: 08/06/2011 04:17

Seen: 419 times

Last updated: 08/08/2011 06:27