| Author |
Message |
David McKenzie
Guest
|
Posted:
Mon Jan 10, 2005 9:26 pm Post subject:
Indexing failure - anyone seen this? |
|
|
Persuing my SQL Server event log (looking for something else), I found this:
One or more documents stored in image columns with extension 'XLS' did not
get full-text indexed because loading the filter failed with error '0x1'.
Note: These documents will not be passed to MSSearch for indexing, and
therefore this failure will not be reflected in the end of crawl summary
statistics. |
|
| Back to top |
|
 |
Wei-Dong XU [MSFT]
Guest
|
Posted:
Tue Jan 11, 2005 10:46 am Post subject:
RE: Indexing failure - anyone seen this? |
|
|
Hi David,
Have your database box applied the SQL service pack 3? There is two KB
articles introducing this issue:
FIX: SQL Server Full-Text Population by Using a Single-Threaded Filter DLL
or a PDF Filter DLL May Not Succeed
http://support.microsoft.com/?id=323040
Full-Text Query Does Not Return the Expected Result Set
http://support.microsoft.com/?id=308841
In addition, from my view, this should be one SQL server issue. if the sp3
can't resolve this for you, I'd suggest you can post this to SQL server
queue for further assistance!
Please feel free to let me know if there is any further question.
Best Regards,
Wei-Dong XU (WD.XU)
Microsoft Product Support Services
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights. |
|
| Back to top |
|
 |
Mike Walsh
Guest
|
Posted:
Tue Jan 11, 2005 11:39 am Post subject:
Re: Indexing failure - anyone seen this? |
|
|
Thanks for the links, Wei-Dong.
Both have now been added to the KB Articles section of the WSS FAQ (Category
= "Full-Text Search")
Mike Walsh, Helsinki, Finland
WSS FAQ at http://wss.collutions.com
Please post questions to the newsgroup only.
"Wei-Dong XU [MSFT]" <v-wdxu@online.microsoft.com> wrote in message
news:1IMSYi59EHA.2660@cpmsftngxa10.phx.gbl...
| Quote: | Hi David,
Have your database box applied the SQL service pack 3? There is two KB
articles introducing this issue:
FIX: SQL Server Full-Text Population by Using a Single-Threaded Filter DLL
or a PDF Filter DLL May Not Succeed
http://support.microsoft.com/?id=323040
Full-Text Query Does Not Return the Expected Result Set
http://support.microsoft.com/?id=308841
In addition, from my view, this should be one SQL server issue. if the sp3
can't resolve this for you, I'd suggest you can post this to SQL server
queue for further assistance!
Please feel free to let me know if there is any further question.
Best Regards,
Wei-Dong XU (WD.XU)
Microsoft Product Support Services
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no
rights. |
|
|
| Back to top |
|
 |
Wei-Dong XU [MSFT]
Guest
|
Posted:
Tue Jan 11, 2005 12:35 pm Post subject:
Re: Indexing failure - anyone seen this? |
|
|
You are welcome, Mike! :0) Hope the service pack can resolve the issue for
David!
Furthermore, I have researched more for David on this issue. There are more
truobleshooting suggestions:
1. Another KB article introducing this issue:
Q308771 PRB: A Full-Text Search May Not Return Any Hits If It Fails to
Index a File
http://support.microsoft.com/?id=308771
2. The Ifilter can't handle protected data; for examle the password
encrypted data in Excel file. If your excel file have the
password-protected contents, the filter can index nothing for that part and
the function LoadIFilterEx() returns a '0x1' (S_FALSE) which corresponds to
the failure event.
If the metadata (not the concept envolved with .net, the office file
metadata ) of excel is corrupted, the filter can also not handle the data.
So you can check your excel files in the document library to see whether
any one has the password protected data or corrupted, which may be the
culprit for this error message.
a. if password protected, remove the password and start the full populatoin
on the catalog in SQL server
b. if file corrupted, please go to www.officerecovery.com and download the
demo version ExcelRecovery for the repairing. If demo version can't fix,
the full version may be needed. Then run full population on the catalog.
3. Please ensure the Office filter (OFFFilt.dll) is located at the box. It
should be placed at:
%ProgramFiles%\Common Files\System\MSSearch\Bin
The key here is the error code '0x1' which means that the filter dll may
not be loaded successfully. Perhaps you will need to re-register the
component. Steps:
Open a command prompt and navigate to %ProgramFiles%\Common
Files\System\MSSearch\Bin
1) Unregister the dll: regsvr32 mspfilt.dll /u
2) Reregister the dll: regsvr32 mspfilt.dll
*from my view, this dll should always be registered very well. This
suggestion can be applied at the last.
Please feel free to let me know if this issue remains.
Best Regards,
Wei-Dong XU (WD.XU)
Microsoft Product Support Services
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights. |
|
| Back to top |
|
 |
Mike Walsh
Guest
|
Posted:
Tue Jan 11, 2005 1:34 pm Post subject:
Re: Indexing failure - anyone seen this? |
|
|
http://support.microsoft.com/?id=308771
Thanks I've added this one too.
Mike Walsh, Helsinki, Finland
"Wei-Dong XU [MSFT]" <v-wdxu@online.microsoft.com> wrote in message
news:81ejEf69EHA.3512@cpmsftngxa10.phx.gbl...
| Quote: |
You are welcome, Mike! :0) Hope the service pack can resolve the issue for
David!
Furthermore, I have researched more for David on this issue. There are
more
truobleshooting suggestions:
1. Another KB article introducing this issue:
Q308771 PRB: A Full-Text Search May Not Return Any Hits If It Fails to
Index a File
http://support.microsoft.com/?id=308771
2. The Ifilter can't handle protected data; for examle the password
encrypted data in Excel file. If your excel file have the
password-protected contents, the filter can index nothing for that part
and
the function LoadIFilterEx() returns a '0x1' (S_FALSE) which corresponds
to
the failure event.
If the metadata (not the concept envolved with .net, the office file
metadata ) of excel is corrupted, the filter can also not handle the data.
So you can check your excel files in the document library to see whether
any one has the password protected data or corrupted, which may be the
culprit for this error message.
a. if password protected, remove the password and start the full
populatoin
on the catalog in SQL server
b. if file corrupted, please go to www.officerecovery.com and download the
demo version ExcelRecovery for the repairing. If demo version can't fix,
the full version may be needed. Then run full population on the catalog.
3. Please ensure the Office filter (OFFFilt.dll) is located at the box. It
should be placed at:
%ProgramFiles%\Common Files\System\MSSearch\Bin
The key here is the error code '0x1' which means that the filter dll may
not be loaded successfully. Perhaps you will need to re-register the
component. Steps:
Open a command prompt and navigate to %ProgramFiles%\Common
Files\System\MSSearch\Bin
1) Unregister the dll: regsvr32 mspfilt.dll /u
2) Reregister the dll: regsvr32 mspfilt.dll
*from my view, this dll should always be registered very well. This
suggestion can be applied at the last.
Please feel free to let me know if this issue remains.
Best Regards,
Wei-Dong XU (WD.XU)
Microsoft Product Support Services
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no
rights. |
|
|
| Back to top |
|
 |
|
|
|
|