What are the challenges you face when working across database platforms? Take the survey
Options

Getting generic index error on single database

rkretsch17rkretsch17 Posts: 6
edited March 27, 2017 11:43AM in SQL Search
I'm unable to index a single database. I was able to index it just fine about a week ago. Not sure what is causing this. I can index the same database just fine on another server. And I can index other databases on the same server fine too.

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

Comments

  • Options
    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
  • Options
    dpaproskijrdpaproskijr Posts: 4 New member
    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.
  • Options
    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.
  • Options
    supergillssupergills Posts: 1 New member
    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.
Sign In or Register to comment.