Cannot set up Full text catalogs - get "Property IsAccentSensitive is not available for FullTextCatalog"

I am trying to set up a full text index on my database (for the first time, no pre-existing catalogs)

It will create the catalog fine, but if I open its properties I get the message:

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

At the Full Text Catalog Properties diaglog, the properties window is greyed out, and whilst I can attempt to change tables/views, when I click OK to close the dialog I get :

"Cannot execute changes.

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

I have read the MS page:  http://support.microsoft.com/kb/910067
My database exhibits exactly the same characteristics, i.e. select FULLTEXTCATALOGPROPERTY('<CatalogName>','AccentSensitivity') produces a null - however the workaround (to detach and reattach the database) does not work.

I would be grateful for any suggestions as I am stuck! Thanks in advance!

LVL 1
Gazza72Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

rob_farleyCommented:
What kind of error are you getting when you detach and reattach?

Or are you meaning that detaching and reattaching doesn't seem to solve the problem?

Rob
0
Gazza72Author Commented:
Thanks for the response,

Detaching and reattaching doesn't seem to solve the problem.
0
rob_farleyCommented:
That problem describes a situation where the catalog name is wrong. Can you perhaps drop it and recreate it?

Rob
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Gazza72Author Commented:
I can remove the catalog and recreate it, and I still have the same problem.

As a test, I also created a completely new database, and the problem exists there as well.
0
rob_farleyCommented:
Ok... can you show me the results of:
select * from sys.fulltext_catalogs

And can you also do:
select * from sys.databases

I'm also wondering if it's related to users set up for your services. If you run SQL Configuration Manager, can you see what users are being used for your services? Then can you use SQL Configuration Manager to change the users to something else and then set them back again?

(Just reminds me of a problem that a client had recently, where there were occasional permission problems because someone had changed a service account using Computer Management, not SQL Config Manager)

Rob

0
Gazza72Author Commented:
If I go into sql config manager I can see the users. As its a production machine, I cant try changing the account at the moment but It looks like I would be able to.

MSSQLServer is logged on as the nt account I created specifically for the server. HOWEVER integration services is logged on as  NT Authority\Network Service. I wonder if this might be a problem.

SQL output attached.

ee.txt
0
rob_farleyCommented:
That NT Account - did you set that as the service account during the install, or using the Services section of Computer Management, or using the SQL Config Manager tool?

is_fulltext_enabled is only turned on on the msdb database. Can you run this please on your user databases?

sp_fulltext_database 'enable'

See if this does it for you...

Rob
0
Gazza72Author Commented:
Thanks for that,


sp_fulltext_database 'enable' : The SP worked fine, but the problem still exists. I tried removing and recreating the catalog, and the problem is still there.

I cannot remember exactly when i set the NT account up- but I am certain I created the account pre-install, then named it as part of the install.
0
rob_farleyCommented:
So...

select name, is_fulltext_enabled
from sys.databases

...says that it's enabled on the databases you need it to be.

Can you run it on the system databases too? It's just that fultext is supposed to be enabled on all databases in SQL2008, and I'm wondering if it's that that's causing the database id syncing problem.

And... can you do the detach/attach thing again after each database has had that proc run on it?

Thanks,

Rob
0
Gazza72Author Commented:
Yes.

I cannot do it on the system databases:
Msg 9966, Level 16, State 1, Procedure sp_fulltext_database, Line 33
Cannot use full-text search in master, tempdb, or model database.

I detached the database, reattached. Still got the problem. Created a new one and that has the same problem too.

I am wondering if maybe the FT catalogs config is stored on disk somewhere where I have not granted permission for the service?
0
rob_farleyCommented:
Ah - you're not storing it in the data folder then?

Make sure that your NT account (actually, the group that it's become part of) has full control of the folder that where you're storing the files.

Rob
0
Gazza72Author Commented:
I'm not sure where it is being stored, I saw a FTDATA folder, and assumed maybe that was it.
I've not told it to save them elsewhere, so I think its in the same filegroup as the database.
I've been checking all the permissions, i did find the nt account i was using was not a part of the sql group, so added it.
However i've still got the same problem.

Starting to think I'll have to re-install sql server to get round this.
0
rob_farleyCommented:
You shouldn't have to reinstall. But... I would try setting the users using SQL Config Manager. Then try recreating the full text catalogs completely. With SQL 2008, you shouldn't have issues with the file system if your service accounts were set using SQL Config Manager.

It is SQL 2008, right?

Also, what operating system are you using, and what account is MSSQLFDLauncher running as (check in SQL Config Manager)?

Rob
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Gazza72Author Commented:
Yes, its sql 2008, running on windows 2008 server 64 bit.

MSSQLFDlauncher is not listed in the config manager-  

Hmm. I've just googled it, and it looks essential. This could the the problem!
0
rob_farleyCommented:
Ah yes... could be. I think we've found the problem.
0
Gazza72Author Commented:
I've scheduled maintenance for tomorrow and will get this installed and  will let you know how it went
0
Gazza72Author Commented:
That indeed was the problem- the full text search feature was not added when SQL 2008 was installed.
I no longer get the error messages. Pity SQL wasn't smart enough to not let you create full text catalogs if the full text system is not installed!

Many thanks for your help- thats a big problem solved!

0
Greg911PCommented:
Same here - identical problem - but with SQLSERVER2012..   feature wasnt installed - why didnt I think of this too?

Obvious once pointed out.  Thanks, this wil have saved me hours of pointless trial and error!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.