OCR was not successful (no text was found) on one or more pages

[Bob Buckland ?:-\)]

Hi Alex,

For your second question, MS Office Document Imaging does not, to my knowledge have any dependencies other than those for install
Office 2003. There could, on the other hand, be something installed on one machine, or associated with a file type, that is
interfering with Office document imaging.

It's also possible that the JPG to TIFF conversion is creating a file where the text isn't clear enough to be seen as 'text', or
that the compression choice used in the TIFF output you're creating is a problem to MODI. That issue has come up from time to time.
If you like, you can zip the original JPG and the TIFF file you're using.

Check the locale and language settings in the Windows control panel as well as those of Office in the Language Settings tools in
Start=>Programs=>Microsoft Office Tools.

=======
Bob,



Thank you for prompt reply.

I'm aware of MODI OCR limited capabilities. But all we need for now is OCR
of small .jpeg images in multi-threaded .NET 1.1 application. We don't want
to spent couple grand for third party product on top of MSDN subscription we
already have. I'm aware also that MODI OCR is not thread safe. We adjusted
our code accordingly.

I'll check to see, if we have the same fonts installed on test bed and
production server. Checking OCR options in MODI application (Microsoft
Office\Microsoft Office Tools\Microsoft Office Document
Imaging->Tools->Options->OCR) i see the same language settings. Microsoft
Office Language Settings on both machines show me identical stuff as well. >>

Test file is one page TIF document i created exporting small .jpeg image via
Microsoft Office Picture Manager. I can e-mail test file, if you need it.

Are you aware of any implicit dependencies of MODI on Windows components,
i.e. ASP.NET enabled, E-mail services enabled, Front Page 2002 extensions
etc.?

AlexK >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx

 

[Bob Buckland ?:-\)]

Hi Alex,

For your second question, MS Office Document Imaging does not, to my knowledge have any dependencies other than those for install
Office 2003. There could, on the other hand, be something installed on one machine, or associated with a file type, that is
interfering with Office document imaging.

It's also possible that the JPG to TIFF conversion is creating a file where the text isn't clear enough to be seen as 'text', or
that the compression choice used in the TIFF output you're creating is a problem to MODI. That issue has come up from time to time.
If you like, you can zip the original JPG and the TIFF file you're using.

Check the locale and language settings in the Windows control panel as well as those of Office in the Language Settings tools in
Start=>Programs=>Microsoft Office Tools.

=======
Bob,



Thank you for prompt reply.

I'm aware of MODI OCR limited capabilities. But all we need for now is OCR
of small .jpeg images in multi-threaded .NET 1.1 application. We don't want
to spent couple grand for third party product on top of MSDN subscription we
already have. I'm aware also that MODI OCR is not thread safe. We adjusted
our code accordingly.

I'll check to see, if we have the same fonts installed on test bed and
production server. Checking OCR options in MODI application (Microsoft
Office\Microsoft Office Tools\Microsoft Office Document
Imaging->Tools->Options->OCR) i see the same language settings. Microsoft
Office Language Settings on both machines show me identical stuff as well. >>

Test file is one page TIF document i created exporting small .jpeg image via
Microsoft Office Picture Manager. I can e-mail test file, if you need it.

Are you aware of any implicit dependencies of MODI on Windows components,
i.e. ASP.NET enabled, E-mail services enabled, Front Page 2002 extensions
etc.?

AlexK >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx

 

[Bob Buckland ?:-\)]

Hi Alex,

For your second question, MS Office Document Imaging does not, to my knowledge have any dependencies other than those for install
Office 2003. There could, on the other hand, be something installed on one machine, or associated with a file type, that is
interfering with Office document imaging.

It's also possible that the JPG to TIFF conversion is creating a file where the text isn't clear enough to be seen as 'text', or
that the compression choice used in the TIFF output you're creating is a problem to MODI. That issue has come up from time to time.
If you like, you can zip the original JPG and the TIFF file you're using.

Check the locale and language settings in the Windows control panel as well as those of Office in the Language Settings tools in
Start=>Programs=>Microsoft Office Tools.

=======
Bob,



Thank you for prompt reply.

I'm aware of MODI OCR limited capabilities. But all we need for now is OCR
of small .jpeg images in multi-threaded .NET 1.1 application. We don't want
to spent couple grand for third party product on top of MSDN subscription we
already have. I'm aware also that MODI OCR is not thread safe. We adjusted
our code accordingly.

I'll check to see, if we have the same fonts installed on test bed and
production server. Checking OCR options in MODI application (Microsoft
Office\Microsoft Office Tools\Microsoft Office Document
Imaging->Tools->Options->OCR) i see the same language settings. Microsoft
Office Language Settings on both machines show me identical stuff as well. >>

Test file is one page TIF document i created exporting small .jpeg image via
Microsoft Office Picture Manager. I can e-mail test file, if you need it.

Are you aware of any implicit dependencies of MODI on Windows components,
i.e. ASP.NET enabled, E-mail services enabled, Front Page 2002 extensions
etc.?

AlexK >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx

 

[Bob Buckland ?:-\)]

Hi Alex,

For your second question, MS Office Document Imaging does not, to my knowledge have any dependencies other than those for install
Office 2003. There could, on the other hand, be something installed on one machine, or associated with a file type, that is
interfering with Office document imaging.

It's also possible that the JPG to TIFF conversion is creating a file where the text isn't clear enough to be seen as 'text', or
that the compression choice used in the TIFF output you're creating is a problem to MODI. That issue has come up from time to time.
If you like, you can zip the original JPG and the TIFF file you're using.

Check the locale and language settings in the Windows control panel as well as those of Office in the Language Settings tools in
Start=>Programs=>Microsoft Office Tools.

=======
Bob,



Thank you for prompt reply.

I'm aware of MODI OCR limited capabilities. But all we need for now is OCR
of small .jpeg images in multi-threaded .NET 1.1 application. We don't want
to spent couple grand for third party product on top of MSDN subscription we
already have. I'm aware also that MODI OCR is not thread safe. We adjusted
our code accordingly.

I'll check to see, if we have the same fonts installed on test bed and
production server. Checking OCR options in MODI application (Microsoft
Office\Microsoft Office Tools\Microsoft Office Document
Imaging->Tools->Options->OCR) i see the same language settings. Microsoft
Office Language Settings on both machines show me identical stuff as well. >>

Test file is one page TIF document i created exporting small .jpeg image via
Microsoft Office Picture Manager. I can e-mail test file, if you need it.

Are you aware of any implicit dependencies of MODI on Windows components,
i.e. ASP.NET enabled, E-mail services enabled, Front Page 2002 extensions
etc.?

AlexK >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx

 

[Bob Buckland ?:-\)]

Hi Alex,

For your second question, MS Office Document Imaging does not, to my knowledge have any dependencies other than those for install
Office 2003. There could, on the other hand, be something installed on one machine, or associated with a file type, that is
interfering with Office document imaging.

It's also possible that the JPG to TIFF conversion is creating a file where the text isn't clear enough to be seen as 'text', or
that the compression choice used in the TIFF output you're creating is a problem to MODI. That issue has come up from time to time.
If you like, you can zip the original JPG and the TIFF file you're using.

Check the locale and language settings in the Windows control panel as well as those of Office in the Language Settings tools in
Start=>Programs=>Microsoft Office Tools.

=======
Bob,



Thank you for prompt reply.

I'm aware of MODI OCR limited capabilities. But all we need for now is OCR
of small .jpeg images in multi-threaded .NET 1.1 application. We don't want
to spent couple grand for third party product on top of MSDN subscription we
already have. I'm aware also that MODI OCR is not thread safe. We adjusted
our code accordingly.

I'll check to see, if we have the same fonts installed on test bed and
production server. Checking OCR options in MODI application (Microsoft
Office\Microsoft Office Tools\Microsoft Office Document
Imaging->Tools->Options->OCR) i see the same language settings. Microsoft
Office Language Settings on both machines show me identical stuff as well. >>

Test file is one page TIF document i created exporting small .jpeg image via
Microsoft Office Picture Manager. I can e-mail test file, if you need it.

Are you aware of any implicit dependencies of MODI on Windows components,
i.e. ASP.NET enabled, E-mail services enabled, Front Page 2002 extensions
etc.?

AlexK >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx

 

[Bob Buckland ?:-\)]

Hi Alex,

For your second question, MS Office Document Imaging does not, to my knowledge have any dependencies other than those for install
Office 2003. There could, on the other hand, be something installed on one machine, or associated with a file type, that is
interfering with Office document imaging.

It's also possible that the JPG to TIFF conversion is creating a file where the text isn't clear enough to be seen as 'text', or
that the compression choice used in the TIFF output you're creating is a problem to MODI. That issue has come up from time to time.
If you like, you can zip the original JPG and the TIFF file you're using.

Check the locale and language settings in the Windows control panel as well as those of Office in the Language Settings tools in
Start=>Programs=>Microsoft Office Tools.

=======
Bob,



Thank you for prompt reply.

I'm aware of MODI OCR limited capabilities. But all we need for now is OCR
of small .jpeg images in multi-threaded .NET 1.1 application. We don't want
to spent couple grand for third party product on top of MSDN subscription we
already have. I'm aware also that MODI OCR is not thread safe. We adjusted
our code accordingly.

I'll check to see, if we have the same fonts installed on test bed and
production server. Checking OCR options in MODI application (Microsoft
Office\Microsoft Office Tools\Microsoft Office Document
Imaging->Tools->Options->OCR) i see the same language settings. Microsoft
Office Language Settings on both machines show me identical stuff as well. >>

Test file is one page TIF document i created exporting small .jpeg image via
Microsoft Office Picture Manager. I can e-mail test file, if you need it.

Are you aware of any implicit dependencies of MODI on Windows components,
i.e. ASP.NET enabled, E-mail services enabled, Front Page 2002 extensions
etc.?

AlexK >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx

 

[Bob Buckland ?:-\)]

Hi Alex,

For your second question, MS Office Document Imaging does not, to my knowledge have any dependencies other than those for install
Office 2003. There could, on the other hand, be something installed on one machine, or associated with a file type, that is
interfering with Office document imaging.

It's also possible that the JPG to TIFF conversion is creating a file where the text isn't clear enough to be seen as 'text', or
that the compression choice used in the TIFF output you're creating is a problem to MODI. That issue has come up from time to time.
If you like, you can zip the original JPG and the TIFF file you're using.

Check the locale and language settings in the Windows control panel as well as those of Office in the Language Settings tools in
Start=>Programs=>Microsoft Office Tools.

=======
Bob,



Thank you for prompt reply.

I'm aware of MODI OCR limited capabilities. But all we need for now is OCR
of small .jpeg images in multi-threaded .NET 1.1 application. We don't want
to spent couple grand for third party product on top of MSDN subscription we
already have. I'm aware also that MODI OCR is not thread safe. We adjusted
our code accordingly.

I'll check to see, if we have the same fonts installed on test bed and
production server. Checking OCR options in MODI application (Microsoft
Office\Microsoft Office Tools\Microsoft Office Document
Imaging->Tools->Options->OCR) i see the same language settings. Microsoft
Office Language Settings on both machines show me identical stuff as well. >>

Test file is one page TIF document i created exporting small .jpeg image via
Microsoft Office Picture Manager. I can e-mail test file, if you need it.

Are you aware of any implicit dependencies of MODI on Windows components,
i.e. ASP.NET enabled, E-mail services enabled, Front Page 2002 extensions
etc.?

AlexK >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx

 

[Bob Buckland ?:-\)]

Hi Alex,

For your second question, MS Office Document Imaging does not, to my knowledge have any dependencies other than those for install
Office 2003. There could, on the other hand, be something installed on one machine, or associated with a file type, that is
interfering with Office document imaging.

It's also possible that the JPG to TIFF conversion is creating a file where the text isn't clear enough to be seen as 'text', or
that the compression choice used in the TIFF output you're creating is a problem to MODI. That issue has come up from time to time.
If you like, you can zip the original JPG and the TIFF file you're using.

Check the locale and language settings in the Windows control panel as well as those of Office in the Language Settings tools in
Start=>Programs=>Microsoft Office Tools.

=======
Bob,



Thank you for prompt reply.

I'm aware of MODI OCR limited capabilities. But all we need for now is OCR
of small .jpeg images in multi-threaded .NET 1.1 application. We don't want
to spent couple grand for third party product on top of MSDN subscription we
already have. I'm aware also that MODI OCR is not thread safe. We adjusted
our code accordingly.

I'll check to see, if we have the same fonts installed on test bed and
production server. Checking OCR options in MODI application (Microsoft
Office\Microsoft Office Tools\Microsoft Office Document
Imaging->Tools->Options->OCR) i see the same language settings. Microsoft
Office Language Settings on both machines show me identical stuff as well. >>

Test file is one page TIF document i created exporting small .jpeg image via
Microsoft Office Picture Manager. I can e-mail test file, if you need it.

Are you aware of any implicit dependencies of MODI on Windows components,
i.e. ASP.NET enabled, E-mail services enabled, Front Page 2002 extensions
etc.?

AlexK >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

For Everyday MS Office tips to "use right away" -
http://microsoft.com/events/series/administrativetipsandtricks.mspx

 

[AlexK]

Bob,

Thank you for following this problem.

Both installations got the same Start=>Programs=>Microsoft Office Tools
settings.

I made sure that all Windows components on both servers are the same.

In order to test your assumption on Fonts dependencies i did the following:
- using Microsoft Paint i created test .jpg file (Arial Bold, 9pts,
Western). Font settings are identical to text messages i need to OCR in
production. Obviously Paint used local font.
- i converted this file to .tif
- ran MODI OCR and failed the same way

I don't think this is .JPG to .TIFF convertion problem. I copied test .tif
file from test bed server. No luck.

I use "fresh" Server 2003 EE installation without any 3rd party tools: just
OS + Microsoft Office Tools. If somebody in Microsoft is really interested,
i can send VMWARE 5.5 image of failing installation.

AlexK

 

[AlexK]

Bob,

Thank you for following this problem.

Both installations got the same Start=>Programs=>Microsoft Office Tools
settings.

I made sure that all Windows components on both servers are the same.

In order to test your assumption on Fonts dependencies i did the following:
- using Microsoft Paint i created test .jpg file (Arial Bold, 9pts,
Western). Font settings are identical to text messages i need to OCR in
production. Obviously Paint used local font.
- i converted this file to .tif
- ran MODI OCR and failed the same way

I don't think this is .JPG to .TIFF convertion problem. I copied test .tif
file from test bed server. No luck.

I use "fresh" Server 2003 EE installation without any 3rd party tools: just
OS + Microsoft Office Tools. If somebody in Microsoft is really interested,
i can send VMWARE 5.5 image of failing installation.

AlexK

 

[AlexK]

Bob,

Thank you for following this problem.

Both installations got the same Start=>Programs=>Microsoft Office Tools
settings.

I made sure that all Windows components on both servers are the same.

In order to test your assumption on Fonts dependencies i did the following:
- using Microsoft Paint i created test .jpg file (Arial Bold, 9pts,
Western). Font settings are identical to text messages i need to OCR in
production. Obviously Paint used local font.
- i converted this file to .tif
- ran MODI OCR and failed the same way

I don't think this is .JPG to .TIFF convertion problem. I copied test .tif
file from test bed server. No luck.

I use "fresh" Server 2003 EE installation without any 3rd party tools: just
OS + Microsoft Office Tools. If somebody in Microsoft is really interested,
i can send VMWARE 5.5 image of failing installation.

AlexK

 

[AlexK]

Bob,

Thank you for following this problem.

Both installations got the same Start=>Programs=>Microsoft Office Tools
settings.

I made sure that all Windows components on both servers are the same.

In order to test your assumption on Fonts dependencies i did the following:
- using Microsoft Paint i created test .jpg file (Arial Bold, 9pts,
Western). Font settings are identical to text messages i need to OCR in
production. Obviously Paint used local font.
- i converted this file to .tif
- ran MODI OCR and failed the same way

I don't think this is .JPG to .TIFF convertion problem. I copied test .tif
file from test bed server. No luck.

I use "fresh" Server 2003 EE installation without any 3rd party tools: just
OS + Microsoft Office Tools. If somebody in Microsoft is really interested,
i can send VMWARE 5.5 image of failing installation.

AlexK

 

[AlexK]

Bob,

Thank you for following this problem.

Both installations got the same Start=>Programs=>Microsoft Office Tools
settings.

I made sure that all Windows components on both servers are the same.

In order to test your assumption on Fonts dependencies i did the following:
- using Microsoft Paint i created test .jpg file (Arial Bold, 9pts,
Western). Font settings are identical to text messages i need to OCR in
production. Obviously Paint used local font.
- i converted this file to .tif
- ran MODI OCR and failed the same way

I don't think this is .JPG to .TIFF convertion problem. I copied test .tif
file from test bed server. No luck.

I use "fresh" Server 2003 EE installation without any 3rd party tools: just
OS + Microsoft Office Tools. If somebody in Microsoft is really interested,
i can send VMWARE 5.5 image of failing installation.

AlexK

 

[AlexK]

Bob,

Thank you for following this problem.

Both installations got the same Start=>Programs=>Microsoft Office Tools
settings.

I made sure that all Windows components on both servers are the same.

In order to test your assumption on Fonts dependencies i did the following:
- using Microsoft Paint i created test .jpg file (Arial Bold, 9pts,
Western). Font settings are identical to text messages i need to OCR in
production. Obviously Paint used local font.
- i converted this file to .tif
- ran MODI OCR and failed the same way

I don't think this is .JPG to .TIFF convertion problem. I copied test .tif
file from test bed server. No luck.

I use "fresh" Server 2003 EE installation without any 3rd party tools: just
OS + Microsoft Office Tools. If somebody in Microsoft is really interested,
i can send VMWARE 5.5 image of failing installation.

AlexK

 

[AlexK]

Bob,

Thank you for following this problem.

Both installations got the same Start=>Programs=>Microsoft Office Tools
settings.

I made sure that all Windows components on both servers are the same.

In order to test your assumption on Fonts dependencies i did the following:
- using Microsoft Paint i created test .jpg file (Arial Bold, 9pts,
Western). Font settings are identical to text messages i need to OCR in
production. Obviously Paint used local font.
- i converted this file to .tif
- ran MODI OCR and failed the same way

I don't think this is .JPG to .TIFF convertion problem. I copied test .tif
file from test bed server. No luck.

I use "fresh" Server 2003 EE installation without any 3rd party tools: just
OS + Microsoft Office Tools. If somebody in Microsoft is really interested,
i can send VMWARE 5.5 image of failing installation.

AlexK

 

[AlexK]

Bob,

Thank you for following this problem.

Both installations got the same Start=>Programs=>Microsoft Office Tools
settings.

I made sure that all Windows components on both servers are the same.

In order to test your assumption on Fonts dependencies i did the following:
- using Microsoft Paint i created test .jpg file (Arial Bold, 9pts,
Western). Font settings are identical to text messages i need to OCR in
production. Obviously Paint used local font.
- i converted this file to .tif
- ran MODI OCR and failed the same way

I don't think this is .JPG to .TIFF convertion problem. I copied test .tif
file from test bed server. No luck.

I use "fresh" Server 2003 EE installation without any 3rd party tools: just
OS + Microsoft Office Tools. If somebody in Microsoft is really interested,
i can send VMWARE 5.5 image of failing installation.

AlexK

 

[AlexK]

Bob,

Thank you for following this problem.

Both installations got the same Start=>Programs=>Microsoft Office Tools
settings.

I made sure that all Windows components on both servers are the same.

In order to test your assumption on Fonts dependencies i did the following:
- using Microsoft Paint i created test .jpg file (Arial Bold, 9pts,
Western). Font settings are identical to text messages i need to OCR in
production. Obviously Paint used local font.
- i converted this file to .tif
- ran MODI OCR and failed the same way

I don't think this is .JPG to .TIFF convertion problem. I copied test .tif
file from test bed server. No luck.

I use "fresh" Server 2003 EE installation without any 3rd party tools: just
OS + Microsoft Office Tools. If somebody in Microsoft is really interested,
i can send VMWARE 5.5 image of failing installation.

AlexK

 

[Beat]

Hi Alex
I have exactly the same problem new w2k3 Server no other application
installed. It seems that SP1 produce this error. I unistallled SP1 and OCR
extraction works. To make it more strange I did following test. New VMWare
Image W2k3 Server with SP1 and than Office 2003 Document Imaging ->
everything is working fine on a older HP Notebook. I use now exactly the same
image (no changes) on a newer HP Notebook -> OCR extraction no longer
works.!!! thats realy strange to me.
It seems that also CPU Speed can influence the OCR extraction.

Regards
Beat

 

[Beat]

Hi Alex
I have exactly the same problem new w2k3 Server no other application
installed. It seems that SP1 produce this error. I unistallled SP1 and OCR
extraction works. To make it more strange I did following test. New VMWare
Image W2k3 Server with SP1 and than Office 2003 Document Imaging ->
everything is working fine on a older HP Notebook. I use now exactly the same
image (no changes) on a newer HP Notebook -> OCR extraction no longer
works.!!! thats realy strange to me.
It seems that also CPU Speed can influence the OCR extraction.

Regards
Beat

 

[Beat]

Hi Alex
I have exactly the same problem new w2k3 Server no other application
installed. It seems that SP1 produce this error. I unistallled SP1 and OCR
extraction works. To make it more strange I did following test. New VMWare
Image W2k3 Server with SP1 and than Office 2003 Document Imaging ->
everything is working fine on a older HP Notebook. I use now exactly the same
image (no changes) on a newer HP Notebook -> OCR extraction no longer
works.!!! thats realy strange to me.
It seems that also CPU Speed can influence the OCR extraction.

Regards
Beat