- HP Support Forum Home
- >
- Printers & All-In-Ones
- >
- Print S/W & Drivers
- >
- Scan to PDF not working with J4680 All-in-One
HP Support Forums
Join in the conversation.
- Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
Scan to PDF not working with J4680 All-in-One
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
02-15-2009 04:13 AM
I can't get the scan to PDF file (both PDF and searchable PDF) to work as intended with my new J4680.
It works fine with other formats (e.g. TIF, JPG), but not with PDF.
It scans properly, asks nicely for additional pages, and then tries to create the PDF file. This is where the process fails.
An empty PDF file (size 0) is created and it aborts with an error message:
unexpected error, click OK to close program and execute the following steps:
- restart program; - boot computer and try again; - reinstall software and try again
8, [( 6, 261, -2147417851)]
(freely translated from German - except for the error number ;-)
Of course none of the above suggestions or any combination thereof, nor restarting the printer works. Any ideas???
Solved! Go to Solution.
Re: Scan to PDF not working with J4680 All-in-One
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
02-16-2009 05:56 PM
Make it easier for other people to find solutions, by marking my answer with \'Accept as Solution\' if it solves your problem.
Click on the BLUE KUDOS button on the left to say "Thanks"
I am an ex-HP Employee.
Re: Scan to PDF not working with J4680 All-in-One
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
02-19-2009 05:54 AM
Thanks, the problem is solved for now.
HP suppot somehow pointed me in the right direction. I uninstalled all(!) drivers from 'older' HP equipment (OfficeJect 6110, ScanJet,...), reinstalled the J4680 completely, and from there on everything worked.
The internal error (WIN XP) seems to be related to a conflict with older drivers.
I hope this helps in case somebody encounters similar problems.
Thanks again,
Alex
