This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal


Sep 30, 2014, 1:01 PM
11 Posts
topic has been resolvedResolved

Error full text indexing

  • Category: Mail
  • Platform: Windows
  • Release: 9.0
  • Role: Developer,End User
  • Tags: index
  • Replies: 4

When I try to create a full text index over my mail database, I receive the following error on the status line at the bottom of the Notes Client:

Error 'Invalid Drive': Michael J Quigley

I get the same results no matter how I try to create the index. (File, Application Properties, Administrator client, 'Search this view', etc.

The log file includes the following entry:

Error full text indexing document NT00000000 \\s03\home\pgmmjq\IBMNotes\mquigley.ft (rc=309) Invalid drive

I've read other threads about problems with an invalid document. But I cannot locate any document using the ID referenced above. Does anyone have any suggestions?

Thanks,

Michael

Sep 30, 2014, 1:57 PM
113 Posts
try mapping a drive
This technote describes similar error, that was worked around by using a mapped drive instead of UNC path


Title:        Full-text index creation fails with "Error full text indexing document NT00000000 <path/database.ft> (rc=309) Invalid drive" when using UNC path
Doc #:        1420497
URL:        
http://www.ibm.com/support/docview.wss?uid=swg21420497
Sep 30, 2014, 2:08 PM
17 Posts
Error full text indexing

The error sounds like an earlier logged issue we have, SPR GFLY6X9RME, which reported that the Full Text Search Engine did not accept \\UNC filenames.  This is an enhancement to review support for that.

Check to see whether you are using a UNC path structure, if so, try the workaround noted in the following technote,

Title: Full-text index creation fails with "Error full text indexing document NT00000000 <path/database.ft> (rc=309) Invalid drive" when using UNC path
Doc #: 1420497
URL: http://www.ibm.com/support/docview.wss?uid=swg21420497

Sep 30, 2014, 6:27 PM
11 Posts
A drive mapping solved the issue

Brandon and Richard,

Thanks so much for your quick and helpful replies. I hadn't seen the technote. I'm glad there's an enhancement request in for UNC paths. Changing my path information to a mapped drive-letter solved the issue. Everything seemed to work fine with the single exception of creating a full text index.

Thanks again,

Michael

Nov 19, 2015, 1:07 AM
12 Posts
Regarding the enhancement request
   We could suggest opening a pmr with us and having an engineer add your additional interest onto the existing associated enhancement request spr to add weight on it's interest of being supplied as a feature in a new/upgraded release.

This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal