Anyone had trouble with SpeedSearch for SalesLogix?

I certainly have.

This is a great tool for searching both the database and the file system.  I have worked with several clients that use SpeedSearch for things like resume searches, communication (History) searches, and ticket problem / resolution searches.  Every once in a while though this tool decides to stop working on some systems.

My most recent errors include (from the Event Viewer):

Event Type: Error
Event Source: SLX DirectoryWatch
Event Category: None
Event ID: 4
Date:  4/17/2009
Time:  5:49:39 PM
User:  N/A
Computer: 
Description:
The description for Event ID ( 4 ) in Source ( SLX DirectoryWatch ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: WriteChangeToDB Error for File: <file name removed>  List index out of bounds (0).

Event Type: Error
Event Source: SalesLogix SpeedSearch
Event Category: None
Event ID: 4
Date:  4/20/2009
Time:  9:47:55 AM
User:  N/A
Computer: 
Description:
IsScheduleRunning Error: Access violation at address 04251D3E in module ‘SLXSearchService.exe’. Read of address 00000008

While I don’t have the answers to all SpeedSearch issues, here is a short list of troubleshooting steps I generally go through when this happens:

1. Has it ever worked?  If the answer is no, then review the documentation from Sage on configuring SpeedSearch.
2. Restart the SpeedSearch Service: Start–>Control Panel–>Administrative Tools–>Services,  right-click on SpeedSearch and select restart, then see if that fixes it
3. If you are indexing files, ensure the user that the service is running under has permissions to those files.
4. Open the SalesLogix Administrator and go to Manage–> SpeedSearch Configuration…, go to the Schedules tab and look for any red items in the list.  If you find one, click on it an this may give you an indication of the error.  Try manually running the indexes by selecting the index and clicking “Run Now”.
5. If you are still having problems, you can try deleting the IndexUpdates table and then manually running all of the indexes again (only recommended for professionals, do this at your own risk!!!)  Sometimes this table gets bloated and needs to be cleaned out.

Does anyone else out there have additional tips on SpeedSearch?  If so, please comment.

Thanks for reading!

My intention with this blog is to give back to the community.  I have leaned on many a Google search, blog post, and forum discussion to find answers  to questions about SalesLogix and other topics.  This has been like asprin to my technical headaches.  Now it is my time to give back, so this is the “New Era”.  I hope that everyone that lands on this blog finds something useful.  If you have any questions or topics you would like me to blog about, please send me an email (chad.crabb@sincerasolutions.com).

Thanks for reading!