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

Question

Question

MS Office ifilter installation

asked on June 28, 2017

I have a customer that has placed LFFTS 10.2.1 on a seperate Windows 2012 R2 x64 server.  When we initially reindexed, we found a lot of warnings in the search engine event log about missing ifilters.  I installed the acrobat v9 ifilter for x64 and the MS Office 2010 filter pack for x64.  Then I added the paths to the acrobat ifilters and the MS ifilters to the PATH Environment Variable and rebooted the server.  After the server cam up, I re-indexed the whole repository again.  The PDF ifilter warnings are gone, but I am still getting warnings for the office documents.  Any other suggestions?

0 0

Answer

SELECTED ANSWER
replied on June 30, 2017

Hi,

Can your doc file be opened with Office? If it is corrupted, then it is possible that extracting text fails.

If file is not corrupted, download the doc file from https://mbs.microsoft.com/downloads/public/fileexchange.doc and extract text from it. I am able to extract text from it with Microsoft Office 2010 Filter.

If it is failed to extract text from the file I provided, please install windows updates related to Microsoft Office, and re-install the Microsoft Office 2010 Filter, and see if it resolves the issue.

If the issue still exists, please check if you want these files to be searchable. If no, just ignore the errors. If yes, please try following ways:
1. Find a proper IFilter
2. Extract text in Client for these files, see help. Client uses a different way to extract text from LFFTS. Once the text has been extracted in Client, LFFTS don't need to extract text when indexing.

If none of previous works, you may open a support case, and send us: one of your documents if possible, the version of Microsoft Office 2010 Filter.

0 0

Replies

replied on June 29, 2017

Hi,

Would you please copy or export the office file to a local folder on machine you run LFFTS, and then run the following commands:

"C:\Program Files\Common Files\Laserfiche\Text Provider\TextProvider64.exe" -cmd -ExtractTextFromFile C:\your-office-file.docx c:\your-text-file-output-64.txt

"C:\Program Files (x86)\Common Files\Laserfiche\Text Provider\TextProvider.exe" -cmd -ExtractTextFromFile C:\your-office-file.docx c:\your-text-file-output-32.txt

After that, check the content in c:\your-text-file-output-64.txt and c:\your-text-file-output-32.txt. If at least one of them has text, then the IFilter is installed correctly.

You may also want to have a look at this post
 

0 0
replied on June 29, 2017

The Office files that are throwing the warning are all the old Office format (pre open office xml).  Running the Textprovider64.exe on Open Office formats (docx) works, but on the old format (doc) does not produce text.

I ran the canextractlist command and the doc extension is listed, but it just is not pulling the text.

 

Whats next?

0 0
SELECTED ANSWER
replied on June 30, 2017

Hi,

Can your doc file be opened with Office? If it is corrupted, then it is possible that extracting text fails.

If file is not corrupted, download the doc file from https://mbs.microsoft.com/downloads/public/fileexchange.doc and extract text from it. I am able to extract text from it with Microsoft Office 2010 Filter.

If it is failed to extract text from the file I provided, please install windows updates related to Microsoft Office, and re-install the Microsoft Office 2010 Filter, and see if it resolves the issue.

If the issue still exists, please check if you want these files to be searchable. If no, just ignore the errors. If yes, please try following ways:
1. Find a proper IFilter
2. Extract text in Client for these files, see help. Client uses a different way to extract text from LFFTS. Once the text has been extracted in Client, LFFTS don't need to extract text when indexing.

If none of previous works, you may open a support case, and send us: one of your documents if possible, the version of Microsoft Office 2010 Filter.

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

Sign in to reply to this post.