No full text languages
-
Hi,
The following select
select
* from sys.fulltext_languages
retnurns me no rows. I have Windows XP x64 and SQL 2005 Developer version 9.00.2047.00 (X64). I have installed full text also and it is runing.
Does enybody have any idea why I have no full text langueges defined
Regards
-
Certainly, unusual as with SQL Server 2005 developer edition SQL FTS is installed by default. I don't have an X64 box to test this on, but can you create and query a FT Catalog? If so, could you run the following SQL quieres on your x64 problem machine and post the results?
select * from sys.fulltext_index_columns
select * from sys.fulltext_catalogs
Regards,
John
SQL Full Text Search Blog
http://jtkane.spaces.live.com/
John T. Kane -
Hi,
I have one full text catalog and the second select gives me the following row:
12 HOME_Informacije C:\MySQL\FTData\HOME_Informacije 0 1 1 65537 1
The first one gives me no rows. The reason for this is that I can't create full text index on my text column. And for this reason I was started searching solution for my problem. So I was fount out, that I haven’t full text languages in my SQL.
There are my SQL statements and an error when I create full text catalog index.
CREATE FULLTEXT CATALOG [HOME_Informacije]
IN PATH N'C:\MySQL\FTData' WITH ACCENT_SENSITIVITY = ON AUTHORIZATION [dbo]
go
CREATE FULLTEXT INDEX ON [dbo].[CLANEK] KEY INDEX [PK_CLANEK] ON [HOME_Informacije] WITH CHANGE_TRACKING AUTO
ALTER FULLTEXT INDEX ON [dbo].[CLANEK] ADD ([NAZIV])
Informational: No full-text supported languages found.
Informational: No full-text supported languages found.
Msg 7680, Level 16, State 1, Line 1
Default full-text index language is not a language supported by full-text search.
Regards,
Toni
-
1. Is it on cluster?
2. What is the startup account for SQL and FTS?
3. can you please run below command and send post back
sp_fulltext_service
'update_languages'
-
The informational messages about "No full-text supported languages found." is a bit misleading, but this message is informative "Default full-text index language is not a language supported by full-text search."
Can you tell us what is the default language of this SQL Server 2005? Post the output of sp_configure and the output of SELECT @@language.
Using "HOME_Informacije" as a guess, I suspec that the default language is Hungarian and if I am correct then this language is not one of the default supported Full-Text Search languages supported by SQL Server 2005. If so, then you may need to drop and re-create your FT Catalog and use the Neutral "Language for Word Breaker". If this is not correct, then the above informantion request will provide more information on this problem.
Thanks,
John
SQL Full Text Search Blog
http://jtkane.spaces.live.com/
John T. Kane -
My SQL is running on a single x64 PC. The SQL and FTS services have a local system account as logon account. My default collation on my windows is Slovenian and my SQL server has Slovenian_CI_AS collation. The SQL server language is English (United States).
My SQL settings are (results of sp_configure with advanced options):
name minimum maximum config_value run_value
----------------------------------- ----------- ----------- ------------ -----------
Ad Hoc Distributed Queries 0 1 0 0
affinity I/O mask -2147483648 2147483647 0 0
affinity mask -2147483648 2147483647 0 0
affinity64 I/O mask -2147483648 2147483647 0 0
affinity64 mask -2147483648 2147483647 0 0
Agent XPs 0 1 0 0
allow updates 0 1 0 0
awe enabled 0 1 0 0
blocked process threshold 0 86400 0 0
c2 audit mode 0 1 0 0
clr enabled 0 1 1 1
cost threshold for parallelism 0 32767 5 5
cross db ownership chaining 0 1 0 0
cursor threshold -1 2147483647 -1 -1
Database Mail XPs 0 1 0 0
default full-text language 0 2147483647 1033 1033
default language 0 9999 0 0
default trace enabled 0 1 1 1
disallow results from triggers 0 1 0 0
fill factor (%) 0 100 0 0
ft crawl bandwidth (max) 0 32767 100 100
ft crawl bandwidth (min) 0 32767 0 0
ft notify bandwidth (max) 0 32767 100 100
ft notify bandwidth (min) 0 32767 0 0
index create memory (KB) 704 2147483647 0 0
in-doubt xact resolution 0 2 0 0
lightweight pooling 0 1 0 0
locks 5000 2147483647 0 0
max degree of parallelism 0 64 0 0
max full-text crawl range 0 256 4 4
max server memory (MB) 16 2147483647 2147483647 2147483647
max text repl size (B) 0 2147483647 65536 65536
max worker threads 128 32767 0 0
media retention 0 365 0 0
min memory per query (KB) 512 2147483647 1024 1024
min server memory (MB) 0 2147483647 0 0
nested triggers 0 1 1 1
network packet size (B) 512 32767 4096 4096
Ole Automation Procedures 0 1 0 0
open objects 0 2147483647 0 0
PH timeout (s) 1 3600 60 60
precompute rank 0 1 0 0
priority boost 0 1 0 0
query governor cost limit 0 2147483647 0 0
query wait (s) -1 2147483647 -1 -1
recovery interval (min) 0 32767 0 0
remote access 0 1 1 1
remote admin connections 0 1 1 1
remote login timeout (s) 0 2147483647 20 20
remote proc trans 0 1 0 0
remote query timeout (s) 0 2147483647 600 600
Replication XPs 0 1 0 0
scan for startup procs 0 1 0 0
server trigger recursion 0 1 1 1
set working set size 0 1 0 0
show advanced options 0 1 1 1
SMO and DMO XPs 0 1 1 1
SQL Mail XPs 0 1 0 0
transform noise words 0 1 0 0
two digit year cutoff 1753 9999 2049 2049
user connections 0 32767 0 0
user options 0 32767 0 0
Web Assistant Procedures 0 1 0 0
xp_cmdshell 0 1 0 0
SELECT @@language; returns me us_english.
The following statement
sp_fulltext_service 'update_languages'
returns me
Informational: No full-text supported languages found.
I understand that my language is not supported with full-text search. I was dropped and created a catalog many times. Even when I try to create full text index with English language I get the same error like:
ALTER FULLTEXT INDEX ON [dbo].[CLANEK] ADD ([NAZIV] LANGUAGE 'English')
Informational: No full-text supported languages found.
Informational: No full-text supported languages found.
Msg 7696, Level 16, State 10, Line 1
Invalid locale ID was specified. Please verify that the locale ID is correct and corresponding language resource has been installed.
Regards,
Toni
-
Has there never been a solution to this? I just did a new install of 2005 EE SP2 with Advanced services (i.e. Full-Text Indexing) and it is having this same problem (this is the first time I have seen this problem in about a dozen installs).
This server was installed as a named instance and was setup with the default English character set and sort order.
-
I am having the exact same issue right now guys - anyone know how to fix this?
I've created a brand new test database, using 1033 ENG and I get the same error. Another note - unlike a lot of others, my problem just started occuring recently. My SQL database has been working like a charm since 4/07, and now it just started acting up.
I have updated all BIOS, checked for registry corruption, updated Firmware for every piece of hardware in the machine. I have also done a repair install on the OS.
I am running SQL 2005 on Windows Server 2003.
Also I have found on other forums that sometimes the SQL Server account & the SQL Server FullText account will have trouble talking to each other and need to be set to Logon As a local system account instead of a Network Service Account.
I am currently working w/ Microsoft to see if they can find a solution. I have been working with them for three days already - any help would be GREATLY appreciated.
Thanks much.
-
Ok... noob to this board... but came across the thread by way of Google. I was having this problem - exact same errors. Exact same diagnosis.
I think I got lucky... I did find an article that seemed to claim it had something to do with the account that the indexing service was trying to start up with. However, that was not enough.
I am on Vista x64, and also running SQL Server 2005, and prior to that, and concurrently still installed SQL Server 2005 Express (advanced). So I am not sure if there is a commonality there or not.
However, I was able to go into Programs and Features and "change" Microsoft SQL Server 2005 (64-bit) to get this fixed. However, after trying more simple methods, the only way it worked for me was to uninstall the FTS options that had been installed. When that finished I immediately did the same thing but this time INSTALLED FTS.
After the installation completed, I went into SQL Server Configuration Manager and under the SQL Server 2005 Services detail Right Click SQL Server Full Text Search -> Properties.
Stop the service here.
Change the Built In Account to Network Service
Start the service.
Start SQL Server (that was stopped during the uninstall process)
Went back into SQL Server Management Studio
Selected properties from my database - > files -> uncheck the full-text
Then saved.
Then went back into the same setting and re-enabled it.
Then when I went to the table level - > create full-text index. I can now select a language (before I saw an empty drop-down list)
Ok, I could be answering too early because I have not tested it yet... But it created it in a flash!!!
-
I had to uninstall and re-install FT too and it worked. Followed the steps above.
-
finally i got this solution by google 'sql server sys.fulltext_languages is empty'
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply