Post reply

Full-text catalog created BUT does not populate

  • January 17, 2007 at 7:50 am

    #63034

    Hi,

    We've recently copied databases from one server to another. Now, a free-text catlog (that works fine on original server) will not populate on the new server.

    After attempting population the free-text catalog properties remain "Item count: 0, Catalog size: 0MB". I do not receive any error message - it just seems like the catalog does not populate.

    I would expect around 3000 items and a size of 3MB.

    Could anybody offer any suggestions as to why the catalog will not populate.

     

    Thanks, Stephen.

  • January 18, 2007 at 8:03 am

    #684015

    I'm the DBA for Steve (Developer).  On this new server, we have created a new test database (from a backup of another database which does have records in it, though not a lot.  We choose a table, created a new index, then a new full text catalog which we attempted to schedule. We then started a full population.

    The 'start full population' returned nothing as before.  The schedule did not run either.

    We think it must be something on the server itself

     

    Madame Artois

  • August 30, 2007 at 3:00 am

    #730366

    i am having the same problem... help.. anyone !

  • August 30, 2007 at 3:14 am

    #730368

    SQL Server adds itself as an Administrator to the Microsoft Search service (MSSearch). When the service logon account for the MSSQLServer service is changed through Control Panel, the service logon account no longer has administrative privileges over the MSSearch service.

    Workaround

    1. Logon to the Server.

     Open the SQL Server Enterprise Manager. From the Action menu point to Properties, and then click Security

    2. Change the ‘Startup service account’ to System Account.  (ie ‘local system’ account is the standard).

    3. Stop and then restart the MSSQLServer service.

    4. Change the Startup service account back to the domain account you want. (Make sure that you perform this task through the SQL Server Enterprise Manager and not Control Panel.)

    5. Stop and then restart both the MSSQLServer and MSSearch services. SQL Server should now have administrative control over the Microsoft Search service.

     

    This is how we got round the situation.  Give it a go

     

     

    Madame Artois

  • August 30, 2007 at 4:54 am

    #730380

    thanks for the reply. i will try it and post the result.

     

    It seems that you are on 2000. I am using 2005 !

  • August 30, 2007 at 5:40 am

    #730385

    We are on 2000 but the solution was supplied by Microsoft.  Perhaps they can tell you if it also applies to 2005

    Madame Artois

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply