Groups | Blog | Home
all groups > sql server full text search > may 2004 >

sql server full text search : Execution of a full-text operation failed. The parameter is incorrect.


lindap NO[at]SPAM empiredirect.co.uk
5/5/2004 7:21:23 AM
When I try to execute the following stored procedure:
exec sp_fulltext_database 'enable'

I get the following error:

Server: Msg 7619, Level 16, State 1, Procedure sp_fulltext_database,
Line 46
[Microsoft][ODBC SQL Server Driver][SQL Server]Execution of a
full-text operation failed. The parameter is incorrect.

I have change the account to use the system account but I still get
this error.

John Kane
5/5/2004 7:15:51 PM
Linda,
What is the version of SQL Server that you are using? Could you post the
full output of -- SELECT @@version
When you changed the account to the System account, did you use SQL Server's
Enterprise Manager's server property security tab? If not, you MUST make all
changes to the MSSQLServer startup account & password via the EM server
property security tab for any of these changes to affect the MSSearch
service as well. You must re-make these account changes here.

As you're from the UK, this *might* be more related to your specific
language or sub-language wordbreaker dll's and less of a permission issue,
assuming that your FT-enabled table's column "Language for Word Breaker" is
set to UK_English and not US_English.

Regards,
John



[quoted text, click to view]

anonymous NO[at]SPAM discussions.microsoft.com
5/6/2004 3:30:58 AM
Hi John,

Thanks for your reply.

I ran the following:
SELECT @@version
SELECT @@language

Which returned the following results:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195:
Service Pack 4)
British

When I changed the account to the System account, I used
SQL Server's Enterprise Manager's server property security
tab.
The full text search has been working fine for months but
when the server was rebooted I could not enable the full
text search.

Thanks,

Linda
John Kane
5/6/2004 7:55:15 AM
You're welcome, Linda,
Could you also run the following T-SQL and post the output?

use <your_database>
go
sp_configure 'default full-text language'
go
exec sp_help_fulltext_columns

I'm mainly interested in confirm that the default FT language (and
FULLTEXT_LANGUAGE) are the same as your @@language value (British).

Thanks,
John


[quoted text, click to view]

Linda
5/6/2004 8:18:16 AM

anonymous NO[at]SPAM discussions.microsoft.com
5/7/2004 1:19:17 AM
Hi John,

Below is the output that I get from running the following:
use empiremaster
go
sp_configure 'default full-text language'
go
exec sp_help_fulltext_columns

default full-text language 0
2147483647 1033 1033

Server: Msg 15601, Level 16, State 1, Procedure
sp_help_fulltext_columns, Line 8
[Microsoft][ODBC SQL Server Driver][SQL Server]Full-Text
Search is not enabled for the current database. Use
sp_fulltext_database to enable Full-Text Search.

Thanks again,

John Kane
5/7/2004 7:46:33 PM
Linda,
Thanks for the info. Your default FT language (run_value = 0) is Neutral,
while the table specific column is (FULLTEXT_LANGUAGE = 1033) is US_English
and your @@language value (British). Obviously, a miss-match here...
Assuming the text in the FT-enable column is English and you want to use
"British" (UK_English), could you run the below T-SQL code?

use master
go
sp_configure 'default full-text language', 2057
go
reconfigure with override
go

Then drop and re-create your FT Catalog and using the FT Indexing Wizard,
and set the "Language for Word Breaker" to UK_English and then run a Full
Population and re-test your query. If the error re-occurs when you run the
query, please post your query as well as the sp_configure and
sp_help_fulltext_columns output.

Thanks,
John




[quoted text, click to view]

anonymous NO[at]SPAM discussions.microsoft.com
5/10/2004 3:42:51 AM

Hi John,

I have ran your piece of code:
use master
go
sp_configure 'default full-text language', 2057
go
reconfigure with override
go
and it has changed the language but I can not drop or
recreate the catalogues because I get the error message
saying that the database is not full-text enabled yet.
But when I run:
use empiremaster
go
exec sp_fulltext_database 'enable'

I get the following message:

Server: Msg 7619, Level 16, State 1, Procedure
sp_fulltext_database, Line 46
[Microsoft][ODBC SQL Server Driver][SQL Server]Execution
of a full-text operation failed. The parameter is
incorrect.

Below is the result I get from running:
use empiremaster
go
sp_configure 'default full-text language'
go
exec sp_help_fulltext_columns

default full-text language 0
2147483647 2057 2057

Server: Msg 15601, Level 16, State 1, Procedure
sp_help_fulltext_columns, Line 8
[Microsoft][ODBC SQL Server Driver][SQL Server]Full-Text
Search is not enabled for the current database. Use
sp_fulltext_database to enable Full-Text Search.

Many thanks,

John Kane
5/10/2004 8:05:33 PM
Linda,
Because the error Msg 7619 (The parameter is incorrect) occurred when you
ran " exec sp_fulltext_database 'enable' " against your empiremaster
database, I believe this to be a more serious error than just one of a
miss-match between language configurations.

At this time, I'd recommend that you place a support call to Microsoft's PSS
SQL Server support and open a case with them as they will have extended
debugging procedures for SQL FTS, so that the real issue on this server can
be identified and fixed.

Regards,
John


[quoted text, click to view]

AddThis Social Bookmark Button