Comments
4 comments
-
More error items for clues:
07 Mar 2017 10:04:07.052 [19] ERROR RedGate.SQLSearch.Addin.LoggingErrorHandler - Exception while re-indexing Litmos on 10.150.140.111:
Exception: An item with the same key has already been added.
07 Mar 2017 10:04:35.288 [38] ERROR RedGate.SQLSearch.Addin.LoggingErrorHandler - Exception while re-indexing Litmos on 10.150.140.111:
Exception: database is locked
database is locked
07 Mar 2017 10:04:35.358 [35] ERROR RedGate.SQLSearch.Addin.Tab.Controller - Search failed: 'Litmos on 10.150.140.111' is not indexed -
I had the same problem.
Go to Usersyour_user_nameAppDataLocalRed GateSQLSearch 2Indexes
Delete the sqlservername.__SQLSearch_JobsIndex__
and
sqlservername.dbname
files.
Close the SSMS tab that has SQL Search and open a new one.
Worked for me. -
Thanks dpaproskijr. That solved the problem for me as well, although it didn't work until I:
1) deleted the 2 files
2) quit SSMS
3) reopened SSMS
Thanks again. -
Having also experienced this issue I agree with the solution. I do however see an issue in that the error is not propogated to the UI in any way which raises reliability questions. I have a number of users that are heavily reliant on SQL Search due to the number of objects in the databases in question and it is quite disturbing that, short of the log file, there is no visible clue that the indexing has failed.
Add comment
Please sign in to leave a comment.
Using SSMS 2014 (12.0.4100.1), server is SQL Server 2014 Enterprise (12.0.5522.0).
06 Mar 2017 09:02:39.983 [27] ERROR RedGate.SQLSearch.Addin.Tab.Controller - Search failed: 'Litmos on 10.150.140.111' is not indexed