Post reply

Failed to Pause Catalog - can''t find this error anywhere!

  • August 20, 2007 at 7:16 am

    #727947

    Thanks Guys,

    I had the same issue. My pasword for the SQL full text service expired. I updated the password of this service and back up job is happy now.  This issue can also occur if the SQL full text service is in stopped state for some reason.

    Regards,

    Senthil

  • December 28, 2007 at 1:40 pm

    #763415

    My full-text search is running and still I get the same error message when backing up. How to I check and change the login account uses to run? Thanks.

  • March 4, 2009 at 3:00 am

    #952968

    Hi all,

    We do have the same issue .... even it persists still....

    1. We used to backup of the DB's without enabling Full text catalogs service in our server.

    2. From past couple weeks the backup is failing for one DB.

    3. Im able to take the backup through GUI.

    4. But when i try through procedure it starts failing.

    Unable to find the reason and came to conclusion DB is corrupt.

    Can anyone help me out to fix this issue ASAP.

  • March 5, 2009 at 8:09 pm

    #954610

    We have the same issue but via a maintenance plan backup or query window for that matter. There are a couple of work-arounds we have found.

    - Use the same service account for SQL Server Service and Full Text Service.

    - Use LocalSystem for the Full Text Service.

    Unfortunately, for us, this is not the solution. We are attempting to use the 'least privileged execution' model with domain user accounts for our SQL Server Services on all of our SQL Servers.

    See: http://msdn.microsoft.com/en-us/library/ms143504(SQL.90).aspx

    Even following the permissions, rights and authorities we cannot perform a full backup on a database with a full text catalog. It looks like a MS PSS case is next !

    RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

  • March 29, 2010 at 10:58 pm

    #1141952

    I'm getting this same issue, but, this time due to my 00010008.ci file is corrupt;

    Is is a case to reinstall Full Text Search?

    :w00t:

    Thanks in Advance!!

    Best Regards,
    Marcos Rosa / marcosfac@gmail.com

  • July 12, 2010 at 11:27 am

    #1191612

    I've had this problem from time to time. I typically experience it after restoring a database utilizing Full-Text to a new location. It's caused because the new location does not have the same folder structure for the Full-text files. You may have a problem with your Full-Text folders or a corrupt file in the Full-Text location on disk.

    Rebuilding the indexes with the command ALTER FULLTEXT CATALOG catalog_name REBUILD had always resolved the issue for me.

    http://sql-ution.com

  • July 30, 2010 at 12:14 pm

    #1200499

    A solution could also be installing the ntlm security provider service that comes with sql server 2005 sp2.

    see problem 3: http://support.microsoft.com/kb/936302

Viewing 7 posts - 16 through 21 (of 21 total)

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