You are viewing limited content. For full access, please sign in.

Question

Question

LFFTS BlockedExtensions List registry key?

asked on February 14, 2014

We have a client getting an error with the text engine, and the event log says we can exclude specific electronic doc types from indexing by modifying the BlockedExtensions list in the registry, we were just wondering where we need to put that key in and what exactly for the value?  Here's our error,

 

The TextProvider process was terminated due to an unhandled exception when extracting text from a document. Search catalog: *. Entry ID: *. This is usually caused by a problematic IFilter or a corrupted document. Please install a proper IFilter and see if it solves the problem. You can also skip the problematic type of electronic documents by modifying the BlockedExtensions list in registry.

 

0 0

Answer

SELECTED ANSWER
replied on February 14, 2014

This warning basically means that efile text extraction failed - TextProvider is the library that specifically handles efile text extraction. The most common reason this fails is that the specific file is in a format you simply don't have a method to extract with on this machine - say that the corresponding iFilter isn't installed. It will also show if there were other reasons text extraction failed, such as the scenario Blake mentions.

 

There's actually a few keys that could be relevant to configuring which file types you want TextProvider to try to generate text from. By default, it will simply try for everything.

 

  • PermittedExtensions - REG_SZ. Which file extensions are permitted by TextProvider to extract text from. Multiple extensions are separated by semicolons. For example: doc;txt;pdf
  • BlockedExtensions - REG_SZ. Which file extensions are blocked by TextProvider to extract text from. Multiple extensions are separated by semicolons. If the same extension both appears in PermittedExtensions and BlockedExtensions, it will be blocked.
  • OnlyExtractFromPermitted - DWORD. If set to non-zero, TextProvider will only extract text from PermittedExtensions. Otherwise all extensions are permitted.

 

  • For 32-bit Windows: HKEY_LOCAL_MACHINE\SOFTWARE\Laserfiche\TextProvider
  • For 64-bit Windows:
    • 64-bit application: HKEY_LOCAL_MACHINE\SOFTWARE\Laserfiche\TextProvider
    • 32-bit application: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Laserfiche\TextProvider.
    • Note that if only the x64 keys are set, both 32 and 64 bit TextProviders will use that key.
0 0

Replies

replied on February 14, 2014

What version of Laserfiche are they using? We were having this same error message when PDF files were corrupted in our repository. I would first do an Entry ID search for the ID number specified in the error message and make sure it isn't a corrupt file issue.

0 0
replied on September 2, 2014

@Justin,

What if those keys don't exist?  I don't have a "TextProvider" key in either "HKLM\Software\Laserfiche" or "HKLM\Wow6432Node\Laserfiche".  I am getting the same error on all my pdf files.  The pdf ifilter has been installed.

0 0
replied on September 2, 2014

Go ahead and add them. If they don't exist then TextProvider is falling back on its defaults, which you are trying to tweak anyway.

 

0 0
replied on December 15, 2014 Show version history

Should I create all 3? (i.e. PermittedExtensions - REG_SZ, BlockedExtensions - REG_SZ., OnlyExtractFromPermitted - DWORD. )

 

What will i put as value data for each or should i leave it blank?

 

Attached is a screenshot of my settings.

RegEdit.png
RegEdit.png (89.65 KB)
0 0
replied on December 15, 2014

You don't have to create all 3. If you don't have the PermittedExtensions key, then LFFTS will attempt to extract text from any electronic documents. If you are adding PermittedExtensions to troubleshoot something, then you also want to set the OnlyExtractFromPermitted key as well.

And yes, just "pdf" is the correct value to have. You can add multiple extensions delimited by semi-colon.

Is there a specific problem you're trying to solve?

0 0
replied on August 10, 2017

I know this post is a few years old, but we are experiencing the same issue.  Anytime a PDF is imported into Laserfiche this error is encountered.  

I have tried about every combination of Laserfiche New Document and Text Generation settings as well as the registry keys on this post, along with restarting the computer every time, and still have no luck.  The only item i can narrow this down to is the version of Adobe Reader.  We have the latest version DC.  For workstations with Adobe Pro X installed, we do not have this issue.

Any other ideas that we can try?  We just upgraded to Laserfiche 10.2.1.  Had this same issue on 10.0.  Did not have this problem with 9.2.

Thanks

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.