Paper capture recognition service experienced an error. (17)

I am using Adobe 9 Pro Extended and it is fine until a few days earlier the OCR stopped working. It will say something like Acrobat could not perform recognition (OCR) because:
Unable to process the page because the paper capture recognition service experienced an error. (17)
I tried repairing and already updating to the newest update. Document scanned in 300dpi always worked until now.
Any expert knows what is error 17? Thanks.

Attempt to run Acrobat 9.5.3 OCR on MacBook Pro under Snow Leopard generates the error message:
   Acrobat could not perform recognition (OCR) because:
   Unable to process the page because the Paper Capture recognition service experienced and error. (17)
   Ignore future errors in this document.
Login as Administrator, launch Acrobat, open one page PDF document without OCR, ..., OCR successful, close document, note additional warning message:
   Suit Product Activation Needed
   Adobe Acrobat was installed as part of a suite. To enable Adobe Acrobat, please start another component of this suite (such as Adobe Photoshop).
Switch back to user account, quit and relaunch Acrobat and OCR works fine.
Looking back at my records I see that I ran into the same error on 11/11/11 probably under Acrobat 9.4.6, but I didn't record the fix.

Similar Messages

Workaround for OCR "Unknown Error"/"Paper Capture recognition service experienced an error"

Problem Description:
When attempting to "Recognize Text", one of the following error messages appears:
"Unknown Error." when using one of the "Searchable Image" or "Searchable Image (Exact)" settings, or
"Unable to process the page because the Paper Capture recognition service experienced an error. (6)" when using the "ClearScan" setting.
Problem Origin:
It seems to be a compatibility issue in the PDF and not in the OCR algorithm itself, although this is speculation and not an official statement.
Problem Workaround:
A possible solution consists of saving the afflicted PDF pages as PNG images (lossless), opening the PNGs in Acrobat, and then performing OCR. Specifically,
Page Thumbnails -> Right-click afflicted pages -> Extract Pages...
File -> Open extracted pages
File -> Save as -> Image -> PNG
Right-click PNG files -> Convert to Adobe PDF
Tools -> Recognize Text -> In This File
File -> Open original PDF
Page Thumbnails -> Right-click afflicted pages -> Replace Pages...
This has worked for every problem instance that I've come across, and there appears to be no quality loss. If anyone else can verify this solution, I would appreciate it.

Attempt to run Acrobat 9.5.3 OCR on MacBook Pro under Snow Leopard generates the error message:
   Acrobat could not perform recognition (OCR) because:
   Unable to process the page because the Paper Capture recognition service experienced and error. (17)
   Ignore future errors in this document.
Login as Administrator, launch Acrobat, open one page PDF document without OCR, ..., OCR successful, close document, note additional warning message:
   Suit Product Activation Needed
   Adobe Acrobat was installed as part of a suite. To enable Adobe Acrobat, please start another component of this suite (such as Adobe Photoshop).
Switch back to user account, quit and relaunch Acrobat and OCR works fine.
Looking back at my records I see that I ran into the same error on 11/11/11 probably under Acrobat 9.4.6, but I didn't record the fix.

Clearscan OCR ERROR: Paper Capture recognition service experienced and error (6)

I get the following error when I try to run a Clearscan OCR over my PDF:
"Acrobat could not perform recognition (OCR) because:
Unable to process the page because the Paper Capture recognition service experienced an error. (6)"
The problem seems like it might be resolved with a PDF made from 300dpi scans, but I do not like the quality loss so I would rather run this on the 600dpi scans. I wish I could get more information on this "error" that the Paper Capture recognition service experienced. Any ideas?

Ok I think I might have a workaround *IF* this error is only thrown on a few offending pages. If you have only one page, OR if it is essential that all pages then this will probably not be a workaround for you.
*FYI* this workaround also applies to the stupid "Unknown Error" that occurs in non-Clearscanned OCR. ("Unknown Error" -- Ha, this is the type of error handling I use when I don't care about anyone using my programs, sounds like Adobe feels the same way).
Since Acrobat spits out such a stupid error, and since it doesn't work in any other scan mode (non-clearscan in any DPI) for these pages, and since there is no log file to look at for the 'paper capture recognition service' to even diagnose the problem, and since they seem completely ok with their absoutely horrible error handling here and since Adobe seems incapable of fixing this error for the last few versions and since they don't care enough to offer any help in their KB regarding an issue affecting hundreds (maybe a few thousand) of users here is a POSSIBLE workaround to clearscan your document if you get this error:
(The following instructions are for Acrobat X (you might have to click 'show and hide pannels' at the top-right of the TOOLS BOX if some of these options are not available; 9 has the same bug and workaround but where you find things are different of course)
1) Scan your pages OR save your pdf as INDIVIDUAL PAGES (there must be a way to export your pdf into individual pages, you might need to use the batch manager (tools->action wizard on Acrobat X))
2) Tools->Action Wizard->Save individual files as pdf: If you don't have individual pdf pages (you have jpegs or tiff) then convert them to PDF FIRST (yes that's right, despite the seemingly obvious thought that a batch Clearscan would actually *gasp* batch Clearscan your files, it won't, it will only convert them to PDFs
3) Tools->Recognize Text->In Multiple Files: Now select to clearscan all your individual files
4) You will get an error on offending pages where Clearscan would normally give you an 'error 6' BUT this method will get around the moronic error-THEN-exit design of Clearscan and allow you to actually Clearscan most of your document
5) Create->Combine Files into Single PDF: Once all pages have been Clearscanned you can reassemble the individual pages to the full document
If you needed that particular page to be clearscanned, this method will not work for you. If you just want 99% of your document to be clearscanned, then hopefully this will help.
We have to admit that Clearscan is a one-of-a-kind technology. The OCR scientists should be given a raise for this. The software engineers and support staff, on the other hand, should go back to the community college they flunked out of and learn a bit more about programming.

Paper Capture Recognition Service error

I have a user, using a HP Scanjet N8460 series scanner.
We are trying to put our documents into PDF for storage, and so have a lot to do.
She reported to me that out of 50 scans, 15 times, she got the following error:
"Unable to process the page because the Paper Capture Recognition Service experienced an error"
I did not see anything in the FAQ's about it. Is this something that is known, can someone give me some direction in resolving?
Thanks

How is the paper capture (or OCR) being used? If you are trying to archive documents, you would only want to use it for developing search funtions. In any case, the quality of the text will dictate how well the OCR works and that is a major problem if you are actually replacing graphics text with OCR text. What I am suggesting is that you need to carefully look at your work flow and the desired output before you put much more time into this. Try some samples and look at the results. OCR is not required, but does allow searching (at least if the OCR is half-way decent. However, it can be hidden text (best for archiving) or replace the graphic (usually not a good idea when archiving).
I am assuming that you are doing all of this through Acrobat and thus the paper capture is within Acrobat. Some scanners do OCR also and it can be important to determine which you are getting.
More information on exactly how you are using Acrobat to perform the processing you are doing would be useful. I am just guessing on what you are doing. Also, Paper Capture in Acrobat was changed in name several versions back, so it sounds like you are using AA5, but I have no clue for sure. All that would help us help you.

Paper Capture Recognition Service

I have a user, using a HP Scanjet N8460 series scanner.
We are trying to put our documents into PDF for storage, and so have a lot to do.
She reported to me that out of 50 scans, 15 times, she got the following error:
"Unable to process the page because the Paper Capture Recognition Service experienced an error"
I did not see anything in the FAQ's about it. Is this something that is known, can someone give me some direction in resolving?
Thanks

First, here is a solution (it looks long, but to be honest it is simple, but I just have an exaple in case someone did not understand the "steps" of hte procedure. It you understand the 4 main steps, then there is no need to read the sub steps or the examples):
1.     Bookmark AND "print to PDF" ALL pages which thrown the "Unable to process..." error message either:
          By trial and error, or through a patch process (mentioned in sfxjhw2's post in the post script)
          (for trial and error, notice that Adobe Acrobat will show the page it has last processed while running an OCR...
          it will be in top left corner of screen, but may revert to page 1 quickly after click "ok" on the error message)
For the Trial And Error approach: lets say for example that I notice that pg 12 gave me my first error.
After clicking "ok" on the error message, I am back to square one as Adobe discards all the work done once it hits this error.
            A.     So, as a preliminary step. I would bookmark the page throwing the error (bookmark page 12) as "ERROR" then,
run an OCR up to the page thrwoing the error, but not including the error page (ex, OCR pages 1-11, but NOT 12).
            B.     Then Run OCR on the next ten or twenty pages AFTER the error page (ex pg OCR pages 13-23, but NOT 12)
            C.     Bookmark the next page (in that group) which generates an error (if any)
Repeat this process until the "whole" document is OCRed (of course pages throwing errors will not be OCRed)
Full example, I ran OCR on whole document, and pg 12 caused it to stop, and it discarded all the work it did. So,
I first bookmark pg 12 as "error", then
go to "document">"OCR text recognition">"recognize text using OCR">"From page 1 to 11". It successfully runs, then
skip page 12 (it is already bookmarked as "error"), then
go to "document">"OCR text recognition">"recognize text using OCR">"From page 13 to 23". Page 20 throws an error, so next...
Bookmark page 20 as "error"
go to "document">"OCR text recognition">"recognize text using OCR">"From page 13 to 19". It successfully runs, then
skip page 20 (it is already bookmarked as "error"), then
go to "document">"OCR text recognition">"recognize text using OCR">"From page 21 to 31". It successfully runs, then
go to "document">"OCR text recognition">"recognize text using OCR">"From page 32 to 42". It successfully runs, then
go to "document">"OCR text recognition">"recognize text using OCR">"From page 43 to 53". Page 50 throws asn error, so next...
Bookmark page 50 as "error"
go to "document">"OCR text recognition">"recognize text using OCR">"From page 43 to 49". It successfully runs, then
skip page 50 (it is already bookmarked as "error"), then
go to "document">"OCR text recognition">"recognize text using OCR">"From page 51 to 61". It successfully runs, then
Final Save file (btw you should probably be saving the file as you go)
            D.     "Print to pdf" those pages (and only those pages) which you have bookmarked as "error"
For The Batch Method: if you have a document over a few hundred pages there is a better way using batch process. Export your PDF (or print your document to pdf) with each page as an individual PDF file. And then Batch process each PDF into an OCRed PDF. You will then have to search through those pages to find out which ones have not been ocred (im guessing by sorting by "date modified" or by saving them with a new name, ie "filename - ocr.pdf" (see quote below my ps, by "sfxjhw2")
3.     Run OCR on those "error" pages
4.     drag and drop or copy and paste those pages into your original OCRed pdf document.
Now for the complaint... I have seen this question posted many times in Adobe forums, just to point out a few:
http://forums.adobe.com/message/3765069
http://boardreader.com/thread/OCR_Error_1wblzXai76.html
http://forums.adobe.com/message/1171341#1171341.
It irks me that
this problem has persisted through many versions of Acrobat
Adobe has failed to either fix it or post an obvious solution in the forums
Adobe has not even done a better job with error handling (causing the whole program to stop the OCR instead of asking if you would like to skip the page, continue, and and bookmark the page that has not been OCRed).
Hope this helps.
And, to Adobe, all in all great product, just wish the error handling was a little better, this problem was fixed, and there was better menu control to change the font on comments and the typewritter.
MBB
Here is a great post by a person who addressed part of this problem:
[post #10 in reply to http://forums.adobe.com/message/3765069]
sfxjhw2, Community Member Sep 16, 2011 2:47 PM
Ok I think I might have a workaround *IF* this error is only thrown on a few offending pages. If you have only one page, OR if it is essential that all pages then this will probably not be a workaround for you.
*FYI* this workaround also applies to the stupid "Unknown Error" that occurs in non-Clearscanned OCR.   ("Unknown Error" -- Ha, this is the type of error handling I use when I don't care about anyone using my programs, sounds like Adobe feels the same way).
Since Acrobat spits out such a stupid error, and since it doesn't work in any other scan mode (non-clearscan in any DPI) for these pages, and since there is no log file to look at for the 'paper capture recognition service' to even diagnose the problem, and since they seem completely ok with their absoutely horrible error handling here and since Adobe seems incapable of fixing this error for the last few versions and since they don't care enough to offer any help in their KB regarding an issue affecting hundreds (maybe a few thousand) of users here is a POSSIBLE workaround to clearscan your document if you get this error:
(The following instructions are for Acrobat X (you might have to click 'show and hide pannels' at the top-right of the TOOLS BOX if some of these options are not available; 9 has the same bug and workaround but where you find things are different of course)
1) Scan your pages OR save your pdf as INDIVIDUAL PAGES (there must be a way to export your pdf into individual pages, you might need to use the batch manager (tools->action wizard on Acrobat X))
2) Tools->Action Wizard->Save individual files as pdf: If you don't have individual pdf pages (you have jpegs or tiff) then convert them to PDF FIRST (yes that's right, despite the seemingly obvious thought that a batch Clearscan would actually *gasp* batch Clearscan your files, it won't, it will only convert them to PDFs
3) Tools->Recognize Text->In Multiple Files: Now select to clearscan all your individual files
4) You will get an error on offending pages where Clearscan would normally give you an 'error 6' BUT this method will get around the moronic error-THEN-exit design of Clearscan and allow you to actually Clearscan most of your document
5) Create->Combine Files into Single PDF: Once all pages have been Clearscanned you can reassemble the individual pages to the full document
If you needed that particular page to be clearscanned, this method will not work for you. If you just want 99% of your document to be clearscanned, then hopefully this will help.
We have to admit that Clearscan is a one-of-a-kind technology. The OCR scientists should be given a raise for this. The software engineers and support staff, on the other hand, should go back to the community college they flunked out of and learn a bit more about programming.

Acrobat 7.0 OCR: Unable to process the page because the Paper Capture recognition service unexpectedly terminated

Hello,
This error occurs on some computers and but not others. I even tested it with the most basic word document, no formatting and scanned it.
It works on a few systems but others get the message:
Unable to process the page because the Paper Capture recognition service unexpectedly terminated.
Does anyone have any suggestions? Did 7.0 have issues?
Thanks

You still didn't answer for Michael the version of 7 At one time adobe prodived and standrad version and a pro version. Standard basically done the same thing as the Print to PDF feature in the Print Menu (of the Macintosh).
Pro added features such as forms creation.
Also the exact version number can be found in the about acrobat under the Acrobat menu.
example for my version would be:

OCR fails - "Paper Capture recognition service" error

Hi all
I get this error message when trying to use Acrobat X Pro (10.1.4.38) OCR feature installed as part of CS6 Master Collection. I have reinstalled everything and AFAIK all the the other MC apps are working and updated properly. There doesn't seem to be a way to <just> uninstall/reinstall Acrobat on its own so I'm at a loss...
CS6 Master Collection, Win7 64bit Intel i7 12GB ram, no other apps running.

I would start with an update, not a reinstall. The update can be done either from the Help>repair in Acrobat or by going to the Programs & Preferences in the Control Panel and running it there. If you succeed in the repair, then run the updates (again from the Help>Updates) or download the updates from http://www.adobe.com/support/downloads/product.jsp?product=1&platform=Windows and install them in order. However, it appears you have the updates, so the repair is what I would try.
If you do a reinstall, then I would also run the cleaner utility that Adobe provides for Acrobat. The URL is posted in several of the discussions on this forum.

Acrobat could not access the recognition service

I am getting the following error message when attempting to use the OCR function in Adobe Acrobat 8.1.3
Acrobat could not access the recognition service:
Unable to locate the Paper Capture recognition Service. Your installation may be corrupt.
This is probably due to either a low memory situation or an corrupt installation. If the problem is not cleared up by shutting down other applications and/or rebooting, then please re-install Acrobat.
It is certainly not a 'low memory situation'. It is not a 'corrupt user profile'. It was not fixed by uninstalling and re-installing.
Help...

Just to be sure, you are trying to use the OCR that is part of AA8 and not the OCR service that is an online service? I think the latter was setup for use with AA8 Std. What menus and selections are you making to get OCR?

Acrobat could not access the recognition service when OCRing

I am getting the error message "Acrobat could not access the recognition service because unable to locate the paper capture recognition service." I get this message when trying to OCR documents. I tried the fix for Acrobat 8 where you copy the drsd832.dll file and this still didn't work. I also tried turning the security (enhanced) settings to 'off' which also didn't work. I was wondering if any of you have encountered a similar problem and have found a solution. I am getting this problem in a networked corporate environment on multiple computers. It is also happening to files on the network rather than files on the local computers.

Just to be sure, you are trying to use the OCR that is part of AA8 and not the OCR service that is an online service? I think the latter was setup for use with AA8 Std. What menus and selections are you making to get OCR?

Neuratron's Photoscope prevents Paper Capture from working

I have been using Acrobat 9 Professional for some time without any problems. I installed Sibelius5 with Neuratron's Photoscope a few weeks ago and Paper Capture simply stopped working. I tried repairing the installation, and finally uninstalled Acrobat and re-installed it to no avail. I have spent literally hours trying to fix this problem.
I finally did a search here on the Acrobat forums and found the post: http://forums.adobe.com/message/1178373#1178373
I found a copy of the Paper Capture driver drs832.dll located here: C:\Program Files\Adobe\Acrobat 9.0\Acrobat\plug_ins\PaperCapture and copied over the ******* version that Photoscope dumped in C:\Windows\System32. Now my Acrobat Paper Capture applications work perfectly once more.
I just wanted to share and prevent anyone from going through what I've gone through.
Acrobat ERROR Message encountered:
"Acrobat could not access the recognition service because: Unable to locate the Paper Capture recognition service. Your installation may be corrupt. This is probably due to either a low memory situation or a corrupt installation. If the problem is not clears up by shutting down other applications and/or rebooting, then please re-install Acrobat. Acrobat could not perform recognition (OCR) on this page because:"

Thanks for sharing.

OCR with Acrobat 8.2.3 occassionally stops with error (5) cannot access paper capture service

After I updated to acrobat 8.2.3 (no other changes in my computer software), OCR recognition occassionally stops with an error that reports the paper capture service is not accessible/available. This is not a fatal error because OCR can continue in the document but the page is not fully processed. The error appears to occur after decomposing and before recognizing text. This problem did not happen with 8.2.2. I have two computers with 8.2.3 and this happens on both computers. I would be happy to downgrade to 8.2.2 until Adobe fixes this problem but apparently adobe does not allow removing the 8.2.3 update.
I tried opening the .pdf directly from the Adobe open menu as someone had suggested in another forum, but the problem persists.
I use this OCR capability almost daily on large (>100 page) files so I need at least a temporary solution right away. Any suggestions?

Not sure if this is a Flash Player problem. You are more likely to get a reply if you post your question in the AS3 forum.

BO 4.0 Advanced Analysis for OLAP - The MDAS service encountered an error.

Hi guru's,
We are running BO 4.0 SP02 Patch 11 with SAP BW 7 and experiencing the following error with Advanced Analysis for OLAP:
"Analysis edition for OLAP
The MDAS service encountered an error."
After you click show details:
"com.crystaldecisions.thirdparty.org.omg.CORBA.MARSHAL minor code: 0x0 completed: No"
I have researched into this and found forums such as:
http://forums.sdn.sap.com/thread.jspa?threadID=2053481
SAP KB 1560100 - BI4.0 Advanced Analysis Web problem: The MDAS Service encountered an error
SAP KB 1661163 - An error is generated when selecting a query or cube in Analysis for OLAP: Error 15
However, none of these have helped our situation too much.
We have rebuilt the windows server 2008 R2 recently, hence the process we followed was a fresh install of BO 4.0 SP02 platform & tools, and then patch 11 on top of these.
Crystal, WEBI's (using the same BICS connections as the AA's) and Dashboards are all working as per expected.
The errors are for every AA including ones with only 2 variable selections (light queries) to ones with many more. Hence it is platform wide for Advanced Analysis.
I have also tried creating new AA using existing BICS, new BICS existing AA, new BICS new AA all with no luck.
We have also created new Adaptive Processing Servers with only the MDAS as a common service, turned on tracing etc but nothing springs to us as to what is going wrong.
Any ideas would be greatly appreciated?
Thanks all,

Hi All,
After conversing with SAP support technicians we have found what is causing this issue.
On the windows servers we have the following installed locally:
- BO platform 4.0 SP02
- BO platform 4.0 SP02 patch 11
- BO client tools 4.0 SP02
- BO client tools 4.0 SP02 patch 11
- Crystal reports 2011 SP02
- Crystal reports 2011 SP02 patch 11
- Crystal reports for Ent SP02
- Crystal reports for Ent SP02 patch 11
It seems that the crystal reports 2011 or cr for Ent was causing an issue in the .WAR files that BOE uses to run Advanced Analysis for OLAP.
After uninstalling the two crystal products and removing any left over cr files in program files on the server, AA for OLAP works successfully in our environment.
The other point after this was i stopped the tomcat and SIA, i renamed the BOE folder under <install dir>\SAP BO4.0\Tomcat6\webapps and restarted the tomcat and then the SIA. In 4.0 when the tomcat is started again it will go and recreate the BOE folder from the BO directories effectively recreating the apps .WAR files under the webapps\BOE folder.
SAP will hopefully document this issue for other clients.
Cheers,

While Importing Foundation Services Facing the Error in (EPM 11.1.2 )

I have created a new application on test server to make a replica of production environment. All other things are ok but user and groups are not imported while importing the foundation services bkp....
The error is as follows
Artifact Path = Native Directory
Artifact Name = Users
Error Message =
EPMCSS-106102: Failed to get user by
identity. Users with identities native:/
/nvid=a673a448b09a6d1e:-543b0ebb:
1306f92702a:-5539?USER not found.EPMCSS-
106102: Failed to get user by identity.
Users with identities native://nvid=
a673a448b09a6d1e:-543b0ebb:1306f92702a:-
553a?USER not found. EPMCSS-106102:
Failed to get user by identity. Users
with identities native://nvid=
a673a448b09a6d1e:-543b0ebb:1306f92702a:-
553b?USER not found.
The same error for Groups
Artifact Path = Native Directory
Artifact Name = Groups
Error Message =
EPMCSS-156160: Failed to get group for
identity. Group with identity native://
nvid=a673a448b09a6d1e:6ad7e2f1:
12e8613cdc4:-c9?GROUP not found.EPMCSS-
156160: Failed to get group for
identity. Group with identity native://
nvid=a673a448b09a6d1e:6ad7e2f1:
12e8613cdc4:-c2?GROUP not found. EPMCSS-
156160: Failed to get group for
identity. Group with identity native://
nvid=a673a448b09a6d1e:6ad7e2f1:
12e8613cdc4:-c3?GROUP not found. EPMCSS-
156160: Failed to get group for
identity. Group with identity native://
nvid=a673a448b09a6d1e:6ad7e2f1:
12e8613cdc4:-c8?GROUP not found. EPMCSS-
156160: Failed to get group for
identity. Group with identity native://
nvid=a673a448b09a6d1e:6ad7e2f1:
12e8613cdc4:-c6?GROUP not found.

Hi
I experienced this error as well today. I manually deleted the existing native users (not the admin user) in the target environment and a subsequent import was fine.
Cheers

The event logging service encountered an error while processing an incoming event published from Microsoft-Windows-Security-Auditing.

Last night, some of our systems installed updates released on 11/13/2014.
KB3021674
KB2901983
KB3023266
KB3014029
KB3022777
KB3020388
KB890830
Today, all of the servers running Windows Server 2008 R2 started logging the following error in the Security log over and over:
Log Name:      Security
Source:        Microsoft-Windows-Eventlog
Date:          1/15/2015 11:12:39 AM
Event ID:      1108
Task Category: Event processing
Level:         Error
Keywords:      Audit Success
User:          N/A
Description:
The event logging service encountered an error while processing an incoming event published from Microsoft-Windows-Security-Auditing.
Servers running Windows Server 2008 that also installed the updates are not experiencing the problem. It looks like one of the updates may have introduced this problem with Server 2008 R2.

...Did you for sure confirm that:
https://technet.microsoft.com/library/security/MS15-001
is the cause?
I did. I had a VM that was not experiencing the problem. I took a snapshot and tested the patches one by one. Installing only KB3023266 immediately caused the issue to occur (after reboot). A similar process was used to confirm that
installing KB2675611 resolved the problem.
Note that I found the installation of KB2675611 is usually quick, but it took several hours hours to install on some of our systems. We had installed this patch a few months ago on a couple of servers and it was always quick to install. But,
it seems like installing it on a symptomatic system can cause it to take a long time.

"itunes has experienced an error and needs to close"

while trying to import my c.d. collection to itunes, i quite often get the message "itunes has experienced an error and needs to close. do you want to send the error to microsoft?" it usually takes me about 20 minutes to import 1 c.d. to itunes becuase i have to keep re-opening itunes after it closes. i never lose anything i have already imported. sometimes i will get through 5 songs before i get the error message, sometimes i cant get through a single song. whats the deal here??

What if you try importings CDs to your computer (not to iTunes) Is this normally working? If yes the problem is in ITunes and if no the problem is maybe your CD player. If the problem is in iTunes you should try to download the latest version from the Apple pages and then update/reinstall.

Paper capture recognition service experienced an error. (17)

Similar Messages

Maybe you are looking for