Microsoft KB Archive/910067

= You may receive the &quot;Property IsAccentSensitive is not available for FullTextCatalog '[CatalogName]'&quot; error message when you try to open a full-text catalog after you restore a database in SQL Server 2005 =

Article ID: 910067

Article Last Modified on 11/17/2005

-

APPLIES TO


 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Workgroup Edition

-





SYMPTOMS
Consider the following scenario. In Microsoft SQL Server 2005, you restore a database from a backup. Then, you try to open a full-text catalog by using SQL Server Management Studio. In this scenario, you may receive the following error message:

Property IsAccentSensitive is not available for FullTextCatalog '[ ]'. This property may not exist for this object, or may not be retrievable due to insufficient access rights. (Microsoft.SqlServer.Smo)

Additionally, when you try to query the information about the AccentSensitivity property of the full-text catalog by using the FULLTEXTCATALOGPROPERTY Transact-SQL function, you receive a null value. For example, you use a Transact-SQL statement that is similar to the following Transact-SQL statement to query the information about the AccentSensitivity property. select FULLTEXTCATALOGPROPERTY('','AccentSensitivity') When you use this statement, you receive a null value. However, when you query the information about the AccentSensitivity property directly from the full-text catalog view, SQL Server returns the correct information. For example, you can use the following Transact-SQL statement to query the information. select * from sys.fulltext_catalogs This problem may occur when the following conditions are true:
 * You back up a database and then delete the database.
 * The database has a full-text catalog.
 * Before you restore the database, you create one or more databases. Therefore, the previous database ID is used by the newly created databases.



CAUSE
This problem occurs because SQL Server stores a wrong full-text catalog name for the existing full-text catalog when you restore the database.



WORKAROUND
To work around this problem, safely detach the restored database. Then, reattach the restored database.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

Keywords: kbprb kbexpertiseadvanced kbsql2005fts KB910067

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.