Scanning to Acrobat 8.1.3

Acrobat 8.3.1, OSX 10.6.8. Create pdf > from scanner (Epson stylus photo Rx620), no devices are list from which to select; how do I solve this? NB. I've updated Epson drivers and scanning works with Preview, but would be more efficient via Acrobat.

It's almost 3 months later and I still have the same problem (with Acrobat 8.1.6 Pro).
I've removed, reinstalled Acrobat Pro and upgraded it countless times. In each case, the initial 8.0 installation from the CD works fine. Subsequently, the first upgrade offered is 8.1.3 which dies when opening the PDF with the form. The subsequent upgrades all do the same.
I've tried disabling programs started at boot (except ones needed for hardware on the system) and I've stopped services too with no change. I've disabled Norton Internet Security which had no affect on the problem.
This is pretty frustrating.
Any ideas?
Thanks
Mike
Message was edited by: mikebk824

Similar Messages

  • I have just updated Acrobat to version 10.1.13. I am using a MAC Running Yosemite.  When I try to scan a document, after the printer scans Adobe Acrobat quits and I get an unexpected closure error.

    I have just updated Acrobat to version 10.1.13. I am using a MAC Running Yosemite.  When I try to scan a document, after the printer scans Adobe Acrobat quits and I get an unexpected closure error.  I am running Mac OS 10.10.1.  This only started happening when I installed the update of Adobe Acrobat.

    Hi MEW1,
    Is the printer connected wirelessly or wired?
    Go to Preferences and under categories go to > Convert to Pdf then select the Image Capture and then hit ok button.
    Close Acrobat and then relaunch it and see if it helps you while you do scanning.
    Regards,
    Rave

  • While editing a scanned pdf, Acrobat will not recognize the current font & change to very different font. How can I choose the font I want to match the current document?

    While editing a scanned pdf, Acrobat will not recognize the current font & change to very different font. How can I choose the font I want to match the current document?

     Thanks for answering. The version is XI.0.10. I just did the update yesterday hoping that I could now properly edit a scanned pdf document. Yes, it's happening on most all scanned documents. I followed your steps & found the list of fonts used in the document & then attempted to edit. The same occurs. When I type in a correction, I get an error alert... "the original font (in this case Fd 5805) is not available or can't be used in editing. Acrobat is using the font Minion Pro in its place." 
    When I select the text & right click as you suggested, my only choices are cut, copy, delete or select all, no "edit text".
    I have no other options to choose another font. Thanks for any help you can direct my way. 
    Debbie
          From: sukritd15 <[email protected]>
    To: Deborah Karr <[email protected]>
    Sent: Friday, February 13, 2015 5:35 AM
    Subject:  While editing a scanned pdf, Acrobat will not recognize the current font & change to very different font. How can I choose the font I want to match the current document?
    While editing a scanned pdf, Acrobat will not recognize the current font & change to very different font. How can I choose the font I want to match the current document?
    created by sukritd15 in Creating, Editing & Exporting PDFs - View the full discussionHi Deborah , I would like to know couple of things before I assist you further.1.Which version of Acrobat are you using ?2.Is it happening for all the scanned PDF' or any particular PDF? You can try these steps,Launch the scanned PDF >right click >Document Properties(from the drop down list) >Fonts(on the dialog box)>From here you will get the fonts used in that PDF . While editing the PDF ,select the text that are editing or typing in with the help of selection tool .After you select the text ,right click on the text and choose "edit text" from the drop down list .From there you will be able to choose the desired font . RegardsSukrit Dhingra If the reply above answers your question, please take a moment to mark this answer as correct by visiting: https://forums.adobe.com/message/7190881#7190881 and clicking ‘Correct’ below the answer Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: Please note that the Adobe Forums do not accept email attachments. If you want to embed an image in your message please visit the thread in the forum and click the camera icon: https://forums.adobe.com/message/7190881#7190881 To unsubscribe from this thread, please visit the message page at , click "Following" at the top right, & "Stop Following"  Start a new discussion in Creating, Editing & Exporting PDFs by email or at Adobe Community For more information about maintaining your forum email notifications please go to https://forums.adobe.com/thread/1516624.

  • Turn off the annoying OCR scan in Acrobat 9.

    Please provide a way to turn of the annoying OCR scan in Acrobat 9. It is un-needed
    and really slows things down.  I want to read the file not edit it.

    Doug Lerner2 wrote:
    Well I hope they turn that into an option sometime.
    You can send your Request to Apple by using this link...
    http://www.apple.com/feedback/

  • Windows DEP error when scanning in Acrobat Pro 9.2

    Hi--
    I scan in Acrobat Pro using create docuemnt>from scanner, via a TWAIN driver.  I upgraded from 9.1.3 to 9.2 recently, last week sometime, and this is the first time I've tried to scan.  If I try to scan, I get an error that Windows DEP is closing the program (note: I don't know why the image below says 9.1, as the version is 9.2).  I triec the DEP settings from the defualt for essential windows programs and services to specifically excluding Acrobat 9.  I also repaired my Arcrobat 9 installation.  I have Windows XP SP3, no new Windows updates are available.  None of those things fixed the problem.  Help!

    I started having this issue about a month ago and have done some systematic testing regarding this.  First some particulars:
    OS = Windows XP SP3, all updates installed and current.
    Scanner = RICOH IS330DC with TWAIN driver
    Adobe Acrobat Pro 8.x and 9.2 (see S.O.E below for explanation)
    Scanning operations were typicaly done through AA using the scanners "Native" interface.  MSOffice Document Scanning was also used.
    Sequence of Events:
    Installed WXP aprox. June of 2008, have been installing all updates automaticaly
    Installed AA 8.x at the same time, installing all updates as they are released.
    Performed scanning operations on a daily basis of over a year with NO DEP errors (thousands of scan operations on a daily basis)
    Scanning operations slowed beginning of October of 2009 but still had not received any DEP errors.
    Scanning resumed November 5, 2009.  Started scanning process from within AA (Create new PDF from...Scanner).  AA scan dialogue window opened, selected scan button.  Waited for Adobe to open "Native" scanner interface.  Received the following message instead:  "To help protect your computer, Windows has closed this program".
    Attempted to scan with AA 9.2 NOT using native scanner interface, received identical result.
    Upgraded to AA 9.2, on November 10, 2009
    Scanned a document both with and without using "Native" scanner interface.  No change in DEP message.
    Attempted to add AA 9.2 to "exclusion" list in DEP settings (OptIn setting).  I did not receive the message regarding DEP "must be enabled for Adobe Acrobat" that some have reported (possibly specific to Vista/W7 installations?).  Although windows allowed adding AA to DEP exclusion list, results were the same.
    Scanned a document using MS Office Document Scanning feature and using scanner "Native" interface.  NO DEP MESSAGES RECEIVED.
    Scanned a document using MS Office Document Scanning feature WITHOUT using scanner "Native" interface.  NO DEP MESSAGES RECEIVED.
    Disabling DEP (AlwaysOff) does resolve the problem but is NOT recommended as DEP is a critical security feature.  As such this work-around is NOT acceptable.
    The results of the testing were:
    Windows and specificaly DEP are allowing the Microsoft supplpied MS Office Document Scanning utility to use the same RICOH supplied drivers and "Native" scanner interface that DEP is NOT allowing Adobe Acrobat to use.  Simply put, even though in WXP I can add Acrobat 9.2 to the exclusion list, Windows DEP still will not allow Acrobat 9.2 to exectue programs or drivers on it's own.  Which is why I believe this is not a RICOH driver issue but either a Microsoft issue or Adobe issue or most likely Microsoft having an issue with Adobe Acrobat.
    Yes, a workaround would be to use MS Document Scanning and right now that is what I am having to do.  However I find it terribly inconvenient that I have to go an extra step to convert thousands of pages of text from tiff to pdf. when I have paid hundreds of dollars for Acrobat to do it directly to .pdf .  Besides, the custom programming and batch job features I use and rely on were developed specificaly for Acrobat and REQUIRE me to use it and not some other utility.  It is simply NOT cost effective for me to use MS Document Scanning and still be able to provide the services I provide.
    My questions are these:
    Is Adobe actively addressing this issue?
    Why is MS Office Document Scanning able to use the scanner drivers and dialogue window when Adobe Acrobat can not?  Why is MS Windows specificaly identifying secondary code execution by Adobe Acrobat as a problem while secondary code execution by MS office is considered acceptable?
    What happened over the last three months that suddenly made DEP aware of Adobe Acrobat being untrustworthy in regards to code execution where as before it WAS trustworthy, at least in regards to Windows XP installations.
    Prior to this issue I had NEVER even heard of DEP (again Windows XP user).  Did Microsoft release a DEP upgrade to Windows XP users that we were not aware of?  Did Microsoft include DEP as a new feature in a recent WXP SP3 security update (over the last three months) and this is why we are seeing this now?
    Regardless of When DEP was released and for who (WXP, Vista, W7), my questions #1 and #2 are still valid.  Can someone at Adobe please address this?
    ****** UPDATE #1 - 11/23/2009 ******
    When adding items to the DEP exclusion list, it will only allow the addition of ".exe" (executables).  I have not been able to find a way of adding .dll files or any other extension types.

  • Can't scan in Acrobat 10.1.1 / Lion 10.7.1

    I cannot scan using Acrobat X (10.1.1) and an Epson Perfection 4990 scanner because it does not show up in the "select a device" dropdown box.  I can scan using the  application Epson supplies, but the resulting scan is 10-20 as large as I want, and I then have to deal with it in Acrobat anyway.  Neither Adobe nor Epson has been of any assistance. Adobe says the driver is bundled in Lion so it can't be uninstalled and reinstalled, which would not do much good anyway if the Acrobat application does not recognize the scanner.  Apple applications Preview and Image Capture recognize it, but that doesn't do me any more good than using the Epson application.

    Are you sure of the math?  a 200dpi colour scan taking 500K represents an original document of two inches square.  You do know that each dot of those "dpi" needs three bytes of stoarage if you are scanning in RGB, and four if CMYK? Eight bits are used to hold the amount of each primary colour in each dot.
    RoughMath:
    500K roughly 500000 bytes. Number of dots 500000/3 = 166666
    Assuming a square picture:  side length is sq root of 166666 =408 dots
    408 dots at 200dpi is two inches
    Regarding size: the larger the resolution, the smaller the resulting size. A ten inch high document scanned at 100dpi is a thousand dots high. Displayed on a 72dpi monitor, the picture is 1000/72 = 13.88 inches high. Printed at 300 dpi, it will end up 1000/300 = 3.33 inches high.
    It is the resolution of the output device that determines the physical size of the document. It is the resolution of the scan that determines the quality of the picture.  Your 12 Mp digital camera doesn't need you to print out your photos twelve times bigger than your old 1Mp camera.

  • I can no longer scan in Acrobat. I all of a sudden get an error saying rmslant.dll is missing

    I keep getting an error now saying" The program can;t start because rmslant.dll is missing. from your computer.  Try reinstalling the program to fix the problem.  I have reinstalled Acrobat but to no avail.  I am still able to scan from Paint and other programs on my computer so the scanner is working.  Any suggestions?

    Hi sllimovi,
    Has anything else changed recently on your computer? Please see this forum thread: Canon scanners stopped working with Acrobat X
    Please let us know how it goes.
    Best,
    Sara

  • Experience Scanning with Acrobat 9 on a Mac

    Friends asked for a copy of a 4-page document we'd used in a study group.  I'll just scan it in with Acrobat!  Then we have the benefits of its being electronic.  Plus it'll give me a chance to try out Acrobat 9, which I just got, and scanning on my Mac (on Windows until recently).
    Why it took me an hour to scan the document:
    Acrobat can assemble a PDF file from scanned pages and OCR it.  I'll just scan in this four page doc and send it out as PDF.  Simple, right?
    Bring up the Acrobat panel to Create PDF From Scanner, and it says to select a scanner.  There are none on the list.  Hmm.
    When I set up my Mac a few weeks ago I tested and was able to scan.  Maybe it's because my printer/scanner is now plugged in via TimeCapsule rather than directly as before.  Can my Mac see it?  How do I know?  Can it see the printer device--perhaps both printer and scanner don't come online at the same time.  Bring up Sys Prefs, it shows a green light by the TimeCapsule-connected printer.  Ah, but it did that yesterday even though it could NOT print to it.  Bring up the Print Queue for that printer and click Utility.   ...scanning for printers...found none.  Do I believe that?  Try printing to it.  It works.  Finding none doesn't mean it isn't working.
    Try plugging the printer/scanner directly into the Mac.  No difference.
    Follow the "maybe scan is different from printing" thought.  Where is the System Prefs for Scan/Fax?  Doesn't seem to be one.  Maybe it's just TWAIN drivers.  How was it I tested scanning initially?  Search [Finder] for scanner.  Nothing obvious.  Futz around a bit.  Ah, it was Image Capture.
    Image Capture CAN see the scanner.  So I could scan in by hand to separate files and assemble in Acrobat.  Sure would be easier if Acrobat had control of the scanner as it [presumably] knows more about what it needs re scan settings.  Search Internet for problem.  Aha, found it on the third hit.  The Epson TWAIN (scan) driver must not be Universal binary.  Acrobat sees only Mac Universal binaries.
    Check Adobe documentation to see if there's a way around this.  None found.  They don't even acknowledge the Universal binary requirement when talking about Mac.
    So, scan separate pages using Image Capture.  Ahh.  The document's printed on really thin paper so type from the back side is bleeding through, badly.  How can I adjust the contrast on the scanner to compensate?  Nothing obvious.  What if I tell Image Capture it's Text?  No, that just seems to change Bit Depth to 1.  Changing it back to 8 causes the Document type to be Photo.  Well, at least there's a setting for B&W Photo.
    Scan to TIFF files (the default).  Go into Acrobat and create a PDF from the four TIFFs.  Run OCR.  Hmm.  Still looks awful because of bleed through in image--OCR just adds invisible (selectable, searchable) text on top, without discarding image--and file size is rather large.  It's good enough, but now I'm curious as I've had better results with this in the past with Acrobat 8 on Windows, though it's been so long I can't remember exactly how.
    Back to the Internet to read about OCR in Acrobat 9.  Ahh.  I think they phased out the previous method I used and replaced it with "ClearScan", a new technology which creates Type 3 approximation fonts on the fly and places those visible on top with the scanned image, greatly compressed (and de-skewed) underneath.  They recommend scanning at 300 dpi (I'd used whatever the default was, 150 I think).
    OK.  Try scanning again.  Set to 300 dpi.  Hmm.  Must be SOME way to change the contrast to correct the bleed through.  Ahh.  It's set to "Image Correction: None".  I'd missed that before--my bad.  Try "Manual".  I get a control panel.  No contrast but I can affect brightness separately in Dark, Midtones, and Light.  Turning up Light does it.  Scan all the pages again.  Bleed through is gone (as seen in Preview windows that pop up).
    Go into Acrobat and recreate the PDF from the TIFFs.  Well, it won't let me see the files.  I scanned them into /tmp.  (I've set up a symlink of /tmp to /FinderVisibleRoot/tmp (along with other hidden / dirs).)  tmp is greyed out though not others in that dir.  Futz around a bit trying other operations which open a file panel, come back, and now tmp's not greyed out.  Sigh.
    Create the PDF from the TIFFs.  Looks exactly like before, bleed through and all.  WTF?  Check the TIFFs in Preview--as expected; no bleed through.  Perhaps something got cached.  Close and restart Acrobat and try again.  Same result.
    The Image Capture adjustment to Brightness must not have changed the actual scan but some meta data stored in the TIFF. ??
    Where can I tell Acrobat to honor that?  There are no options when I open files to be combined to create the PDF.  "Try again, Luke."   Nope.
    Let's try just one file at a time with Create PDF From File.  Same problem.  The files panel for opening those files DOES have a Settings... button, but it's greyed out.  It's set to "All Types", which includes TIFF.  What if I change it to just TIFF?  AHA!!  Now the Settings... button is active.  Not obvious to me (I get why, given multiple types could be selected, but my gosh).
    Now I can control how Acrobat changes the incoming TIFFs (I'm guessing PDF doesn't support TIFF directly so converts to JPEG, CCITT, etc.).  Not exactly sure how conversion works so futz with a few of what I imagine are the obvious options.  No effect.  Hmm.
    Ah.  Maybe Image Capture (or the driver) is actually creating a color profile to affect the image adjustments I made, and embedding that in the TIFF.  Can color profiles be put in TIFFs?  I didn't think so.  Turns out they can.  And retaining embedded profiles was turned on in the conversion settings by default for all image types EXCEPT greyscale. :-)  Turn it on for greyscale and try again.  Voila!
    OK.  Go back to Merge Files Into Single PDF to do all the pages.  Oops.  There's no Settings... option where I can tell it to keep the embedded profiles.  Sigh.  Use Create PDF From File for each page then merge those.
    Now run OCR with ClearScan on the resulting PDF, and keep only very low resolution of original scan.  Result is a small (196K for 4 pg), clean looking, fully searchable document!
    The on-the-fly Type 3 fonts it created aren't great (flaws visible when zoomed).  I think an older technology we had at Adobe of trying to match scanned chars to available fonts stands a better chance for high fidelity (and this may still be avail in a non-ClearScan option).  However, I still like the new ClearScan technology for some uses like this, where fidelity isn't such an issue.
    Hopefully, the Universal binary problem on Mac with Acrobat will go away at some point (when I get a new printer? ) so I'll just be able to scan directly into PDF.  And Adobe will need to add Settings for Merge Files Into A Single PDF to control color profile handling, etc.
    Thanks to all the Adobe forum folk whose posts informed me for this task.
    --Dan

    When I posted the message, it showed me "More Like This" with some relevant threads.  Relevance was pretty cool.
    I read there are Acrobat app-wide conversion settings for importing different file types.  If I set Preferences/Convert To PDF/TIFF settings, it affects files specified to Merge Files Into A Single PDF.  It's still inconsistent that I specify it one way for Create PDF From File and another for Merge Files Into A Single PDF, but at least it can be done.

  • Scanning conflict   Acrobat 9 pro   "Color Format Selected Not Supported"

    I have had several conflicts with Adobe Acrobat 9 and my HP C5180 printer/scanner/copier.   I have downloaded new drivers from HP.   When I try to create  a PDF from the scanner,  I get this conflict warning:   "Color Format Selected Not supported".    So, I change the color format selections in both HP and Acrobat and I still get the warning.    I must admit I haven't tried the black and white color format.  But I want to scan simple color images.  No luck.  
    Has anyone else had such a problem?

    This may have nothing to do with your problem, but -- at least with Acrobat 8, there is a 100MB limit to the scanned image. Are you trying to scan something larger than that?

  • Scanning in Acrobat 9.2 Results in Windows DEP Closing Acrobat

    I started having this issue about a month ago and have done some systematic testing regarding this.  First some particulars:
    OS = Windows XP SP3, all updates installed and current.
    Scanner = RICOH IS330DC with TWAIN driver
    Adobe Acrobat Pro 8.x and 9.2 (see S.O.E below for explanation)
    Scanning operations were typicaly done through AA using the scanners "Native" interface.  MSOffice Document Scanning was also used.
    Sequence of Events:
    Installed WXP aprox. June of 2008, have been installing all updates automaticaly
    Installed AA 8.x at the same time, installing all updates as they are released.
    Performed scanning operations on a daily basis of over a year with NO DEP errors (thousands of scan operations on a daily basis)
    Scanning operations slowed beginning of October of 2009 but still had not received any DEP errors.
    Scanning resumed November 5, 2009.  Started scanning process from within AA (Create new PDF from...Scanner).  AA scan dialogue window opened, selected scan button.  Waited for Adobe to open "Native" scanner interface.  Received the following message instead:  "To help protect your computer, Windows has closed this program".
    Attempted to scan with AA 9.2 NOT using native scanner interface, received identical result.
    Upgraded to AA 9.2, on November 10, 2009
    Scanned a document both with and without using "Native" scanner interface.  No change in DEP message.
    Attempted to add AA 9.2 to "exclusion" list in DEP settings (OptIn setting).  I did not receive the message regarding DEP "must be enabled for Adobe Acrobat" that some have reported (possibly specific to Vista/W7 installations?).  Although windows allowed adding AA to DEP exclusion list, results were the same. Note that when adding items to the DEP exclusion list, it will only allow the addition of ".exe" (executables).  I have not been able to find a way of adding .dll files or any other extension types.
    Scanned a document using MS Office Document Scanning feature and using scanner "Native" interface.  NO DEP MESSAGES RECEIVED.
    Scanned a document using MS Office Document Scanning feature WITHOUT using scanner "Native" interface.  NO DEP MESSAGES RECEIVED.
    Disabling DEP (AlwaysOff) does resolve the problem but is NOT recommended as DEP is a critical security feature.  As such this work-around is NOT acceptable.
    The results of the testing were:
    Windows and specificaly DEP are allowing the Microsoft supplpied MS Office Document Scanning utility to use the same RICOH supplied drivers and "Native" scanner interface that DEP is NOT allowing Adobe Acrobat to use.  Simply put, even though in WXP I can add Acrobat 9.2 to the exclusion list, Windows DEP still will not allow Acrobat 9.2 to exectue programs or drivers on it's own.  Which is why I believe this is not a RICOH driver issue but either a Microsoft issue or Adobe issue or most likely Microsoft having an issue with Adobe Acrobat.
    Yes, a workaround would be to use MS Document Scanning and right now that is what I am having to do.  However I find it terribly inconvenient that I have to go an extra step to convert thousands of pages of text from tiff to pdf. when I have paid hundreds of dollars for Acrobat to do it directly to .pdf .  Besides, the custom programming and batch job features I use and rely on were developed specificaly for Acrobat and REQUIRE me to use it and not some other utility.  It is simply NOT cost effective for me to use MS Document Scanning and still be able to provide the services I provide.
    My questions are these:
    Is Adobe actively addressing this issue?
    Why is MS Office Document Scanning able to use the scanner drivers and dialogue window when Adobe Acrobat can not?  Why is MS Windows specificaly identifying secondary code execution by Adobe Acrobat as a problem while secondary code execution by MS office is considered acceptable?
    What happened over the last three months that suddenly made DEP aware of Adobe Acrobat being untrustworthy in regards to code execution where as before it WAS trustworthy, at least in regards to Windows XP installations.
    Prior to this issue I had NEVER even heard of DEP (again Windows XP user).  Did Microsoft release a DEP upgrade to Windows XP users that we were not aware of?  Did Microsoft include DEP as a new feature in a recent WXP SP3 security update (over the last three months) and this is why we are seeing this now?
    Regardless of When DEP was released and for who (WXP, Vista, W7), my questions #1 and #2 are still valid.  Can someone at Adobe please address this?

    I started having this issue about a month ago and have done some systematic testing regarding this.  First some particulars:
    OS = Windows XP SP3, all updates installed and current.
    Scanner = RICOH IS330DC with TWAIN driver
    Adobe Acrobat Pro 8.x and 9.2 (see S.O.E below for explanation)
    Scanning operations were typicaly done through AA using the scanners "Native" interface.  MSOffice Document Scanning was also used.
    Sequence of Events:
    Installed WXP aprox. June of 2008, have been installing all updates automaticaly
    Installed AA 8.x at the same time, installing all updates as they are released.
    Performed scanning operations on a daily basis of over a year with NO DEP errors (thousands of scan operations on a daily basis)
    Scanning operations slowed beginning of October of 2009 but still had not received any DEP errors.
    Scanning resumed November 5, 2009.  Started scanning process from within AA (Create new PDF from...Scanner).  AA scan dialogue window opened, selected scan button.  Waited for Adobe to open "Native" scanner interface.  Received the following message instead:  "To help protect your computer, Windows has closed this program".
    Attempted to scan with AA 9.2 NOT using native scanner interface, received identical result.
    Upgraded to AA 9.2, on November 10, 2009
    Scanned a document both with and without using "Native" scanner interface.  No change in DEP message.
    Attempted to add AA 9.2 to "exclusion" list in DEP settings (OptIn setting).  I did not receive the message regarding DEP "must be enabled for Adobe Acrobat" that some have reported (possibly specific to Vista/W7 installations?).  Although windows allowed adding AA to DEP exclusion list, results were the same. Note that when adding items to the DEP exclusion list, it will only allow the addition of ".exe" (executables).  I have not been able to find a way of adding .dll files or any other extension types.
    Scanned a document using MS Office Document Scanning feature and using scanner "Native" interface.  NO DEP MESSAGES RECEIVED.
    Scanned a document using MS Office Document Scanning feature WITHOUT using scanner "Native" interface.  NO DEP MESSAGES RECEIVED.
    Disabling DEP (AlwaysOff) does resolve the problem but is NOT recommended as DEP is a critical security feature.  As such this work-around is NOT acceptable.
    The results of the testing were:
    Windows and specificaly DEP are allowing the Microsoft supplpied MS Office Document Scanning utility to use the same RICOH supplied drivers and "Native" scanner interface that DEP is NOT allowing Adobe Acrobat to use.  Simply put, even though in WXP I can add Acrobat 9.2 to the exclusion list, Windows DEP still will not allow Acrobat 9.2 to exectue programs or drivers on it's own.  Which is why I believe this is not a RICOH driver issue but either a Microsoft issue or Adobe issue or most likely Microsoft having an issue with Adobe Acrobat.
    Yes, a workaround would be to use MS Document Scanning and right now that is what I am having to do.  However I find it terribly inconvenient that I have to go an extra step to convert thousands of pages of text from tiff to pdf. when I have paid hundreds of dollars for Acrobat to do it directly to .pdf .  Besides, the custom programming and batch job features I use and rely on were developed specificaly for Acrobat and REQUIRE me to use it and not some other utility.  It is simply NOT cost effective for me to use MS Document Scanning and still be able to provide the services I provide.
    My questions are these:
    Is Adobe actively addressing this issue?
    Why is MS Office Document Scanning able to use the scanner drivers and dialogue window when Adobe Acrobat can not?  Why is MS Windows specificaly identifying secondary code execution by Adobe Acrobat as a problem while secondary code execution by MS office is considered acceptable?
    What happened over the last three months that suddenly made DEP aware of Adobe Acrobat being untrustworthy in regards to code execution where as before it WAS trustworthy, at least in regards to Windows XP installations.
    Prior to this issue I had NEVER even heard of DEP (again Windows XP user).  Did Microsoft release a DEP upgrade to Windows XP users that we were not aware of?  Did Microsoft include DEP as a new feature in a recent WXP SP3 security update (over the last three months) and this is why we are seeing this now?
    Regardless of When DEP was released and for who (WXP, Vista, W7), my questions #1 and #2 are still valid.  Can someone at Adobe please address this?

  • Scanning with Acrobat 9

    I am having some strange problems with an application after an upgrade from Acrobat Pro 5 to Acrobat Pro 9. What the application is supposed to do is to scan a document to PDF, save it to some temporary location, display it on the screen and later save it to the database. For scanning, I am using the MenuItemExecute("scan") method of the Acrobat application object (I don't think there is any other way!). The scanning is triggered by a button on the application's form, and the scanned document is displayed also on the application's form using the OpenInWindowEx method of AcroAVDoc. Acrobat's window is kept hidden.
    In the past, clicking on the "Scan" button would open the settings dialog of the scanner's TWAIN driver, and the result of the scanning would get displayed properly without any trace of Acrobat running behind the scenes. With Acrobat 9, however, the Acrobat window gets displayed; the scanned image first appears inside it and a second later gets transferred to my form. That would not have been so bad (I call the Hide method of AcroApp immediately afterwards to make Acrobat disappear), but the problem is, it works terribly unreliably.
    On one scanning attempt out of ten, the Acrobat would appear minimized in the task bar and only the scanning dialog will be displayed (the Acrobat's internal dialog, not the TWAIN driver's). Then after the scanning, the application would crash when trying to call GetActiveDoc() of AcroApp or GetPDDoc() of AcroAVDoc. The error message is meaningless: something like "Cannot call method '~' of object '~'". On other occasions the scanned page would appear in the Acrobat's own window and stay there without being transferred to the application's form. It's just crazy.
    Is there some trick with scanning from the new Acrobat that I am not aware of? Everything seems to be very unstable with the new version. Thanks in advance!
     

    We had a VBScript that used IAC for Acrobat 7 to scan to a file of specified name, that died under 9. I think the change was really a result of changing from MDI to SDI under Acrobat 8.
    Anyway, our tweaked VBScript function that now works under 9 looks like this (yeah, we leave Acrobat visible, but perhaps you'll see something here) ...
        function AcrobatScanToFile(outputFullPath)
        'Launch Acrobat to scan a document to a specific path
            const MAXIMIZE_ACROBAT = 1 ' 1-yes; 0-no
            dim success
            success = True
            dim ScanOK
            dim app
            set app = createobject("AcroExch.App")
            ScanOK = app.MenuItemExecute("Scan")
            dim AVDoc
            set AVDoc = createobject("AcroExch.AVDoc")
            set AVDoc = app.GetActiveDoc
            if AVDoc.IsValid then
                dim PDDoc
                set PDDoc = createobject("AcroExch.PDDoc")
                set PDDoc = AvDoc.GetPDDoc
                if PDDoc.Save(1,outputFullPath) <> True then
                    success = False
                end if
                PDDoc.Close
            else
                success = False
            end if
            if success then
                AVDoc.BringToFront
                AVDoc.Maximize MAXIMIZE_ACROBAT
            end if
            'AVDoc.Close 0
            'app.Exit
            AcrobatScanTofile = success
        end function

  • Problems Scanning with Acrobat XI Pro for Mac

    I am running Acrobat 11.0.10 on a Mac computer (Yosemite 10.10.2).  Ever since i have updated Acrobat, when i attempt to scan documents with my Epson Photo RX620 it won't scan.
    When i try it without image correction, it tells me "an Error occurred while scanning".  If I attempt to scan using manual image correction, it will scan the document, and when it gets to the end of the scan, it says scanning canceled.
    Prior to the update, I was having no issues scanning with the same equipment.  Does anyone have any suggestions?
    Thanks!

    Hey JeffSPHR,
    Please refer this KB doc link mentioned below and try troubleshooting scanner issues:
    Troubleshoot scanning problems | Mac OS
    Let me know if this helps.
    Regards,
    Anubha

  • Emailing Scans in Acrobat 10

    It is incredably frustrating that I have to save a file before I can email it in Acrobat 10. This was not the case in 9. Does anyone know if you can do this. A lot of the scans I email I do not want a saved copy of because the scan was for someone else and plus once I send it I have copy of it.
    Please Adobe fix this so it operates like acrobat 9.

    Hi
          It is still possible to do the same thing using Acrobat X. In fact the entire workflow looks much better. Please follow the steps below:
          1. User scans a piece of paper to Acrobat X. You should now have a new scanned document loaded in Acrobat
          2. No need to save the document.
          3. Click the email icon in Acrobat tool bar or else click on the Share pane on the right.
          4. Select the attach to email radio button in the share pane.
          5. Click Attach button and you have your email with attachment ready to fly.
          6. User should be happy now.
    Please let me know if you still face any issues.
    -Ravish

  • Problem with 2nd scan in Acrobat Std 8

    I submitted this problem a few days ago, but it seems to have disappeared from the forum.
    I am Using Acrobat Std 8.1.4 with a Canon MP530 all-in-one printer (in Twain mode).  Since approximately a month ago, the following problem started with no apparent reason (no chg in hardware, no obvious chg in software except for Adobe & Microsoft updates):
    I do "Create Pdf" | "From Scanner" and it works fine the first time.  If I try to scan again within the same session (to a new pdf or to an existing pdf), I get the following error message:
    Error while interfacing with the scanner; the selected scanner was not found.
    I re-installed the printer drivers a couple of days ago (but I am not sure this did anything to the Twain drivers).
    I would appreciate any suggestions.
    Thanks,
    Gabriel

    Any insightful suggestions from Acrobat or Twain gurus?
    Any suggestions on how to diagnose the problem?
    Thanks,
    Gabriel

  • Scan in Acrobat X to Adobe Reader

    Can I, and if so, how do I scan a book using Acrobat X and a flat bed Epson V700 scanner to create a file that works in Adobe Reader?

    Scan it as a PDF file? I think this should be an option of the software of your scanner.

  • Scan to Acrobat 8 Pro from Samung CLX-3160FN - crash

    I have been trying to use Adobe Acrobat Pro 8 to scan on my Samsung CLX 3160FN multi-function printer. After going through the process of scanning it gives me this message: Adobe Acrobat 8.0 has stopped working. Here are the problem details:
    Problem Event Name: APPCRASH
    Application Name: Acrobat.exe
    Application Version: 8.0.0.456
    Application Timestamp: 453c8d7f
    Fault Module Name: kernel32.dll
    Fault Module Version: 6.0.6001.18000
    Fault Module Timestamp: 4791a76d
    Exception Code: c00000fd
    Exception Offset: 0004c2c7
    OS Version: 6.0.6001.2.1.0.768.3
    Locale ID: 1033
    Additional Information 1: bd1f
    Additional Information 2: bca06298edd1bf55d841f814fea9ef5f
    Additional Information 3: 4a40
    Additional Information 4: 73407c83da6334b9a3069918812e1069
    Specs to my computer:
    Windows Home Vista Premium
    Intel Core 2 Duo CPU T5250 @ 1.5 GHz
    2 GB RAM
    NVIDIA GeForce8400M GT
    32-bit Operating System
    I just purchased Adobe Acrobat Pro 9 (upgrade) and it is doing the same thing on my other computer which has Windows Vista Business.
    Any suggestions?

    Environment is Windows Vista with a Samsung CLX-3160FN and Acrobat Standard 8.1.3. New machine with plenty of memory. Had the same problem. Acrobat would shut down..."Acrobat has stopped working, etc.". Something is not right with Acrobat and Vista, and I suspect that Adobe needs to fix it. I finally managed to get it to work, but the native printer interface must be used...Adobe's much more functional (used to be functional) interface is not fully available.
    Here is what I did: got all of the Samsung Vista drivers from the Samsung download site and installed them. What seemed to make the most difference was Network Scan, SetIP, SyncThru Web Admin Service, and SmartThru4, but I downloaded and installed every single Vista driver and software that Samsung had on the site. I installed the printer on the network...it was previously a direct local connection via USB. I discovered the device on SyncThru, and installed it on Network Scan. SetIP simply showed me that I had discovered the CLS-3160FN. Then I restarted all devices. Now I can scan using the SmartThru4 interface if I wish, but it is a little awkward. As I said, a workable Acrobat scanner interface is the ideal solution. So now I can use Acrobat to create a PDF with a scanner, but when I select that device on the Acrobat scan dialog box, I must choose WIA-Samsung 3160 Series as the scanner option, otherwise Acrobat fails and gives the Acrobat has stopped working error message. After I accept the initial Adobe dialog box (which does not allow me to select paper size, color or resolution), I am presented with the native scanner dialog box, which I must adjust to properly scan (default is flatbed, not ADF, legal paper, color, basic resolution...I can't seem to change the defaults). It then works pretty much normally, but I don't get the progress boxes that show the scan progress of each page. There is a box, but it does not show progress.
    In summary, Adobe needs to fix this problem in Acrobat when used with Vista. I only use Acrobat to combine files and scan hard documents to PDF. 50% of the functionality was lost when I upgraded to Vista until I found this solution.

Maybe you are looking for

  • I have a VI that belongs to a library that is not properly licensed on the laptop Im using. How do I get it licensed?

    I have an error stating a VI belongs to a library that is not properly licensed on the laptop I'm using.  Can anyone tell me how do I get it licensed?  (version LabVIEW 8.5.1) Nick Salemi Teledyne Energy Systems, Inc. [email protected] 410-891-2225

  • Taxinn

    Hi Gurus, I am using the Taxinn Procedure, maintain the condition record. While creating the PO condition value appear, but while creating the excise invoice the Base value is zero and condition amt for BED,AED,SED,ECS not picking up. Plz suggest Tha

  • Query on adopting ms project in a small organization

    we are a small team of 14 people in my organizaton, presently tracking our tasks and updating it on excel. We need to generate report and also track our tasks in a more organized manner. We have a workgroup of 14 windows 8.1 systems. Can I install Sh

  • How to crop multiple images to the exact same pixel size?

    I have hundreds of scans all from one book and I am trying to straighten and crop them all out to the same pixel amounts. For example, I have a bunch of scans that are 1000x1000 pixels with overscan on all sides, they are also all at an angle. In the

  • Exchange 2013

    Hi Guys, Getting a 500 internal server error after authenticating to ecp or owa. In Exchange 2010 there was a forms based authentication service that had to be enabled. I don't have that service in 2013. By the way this is a stand-alone server. Any t