Fuzzy Lookup/product level is insufficient

I installed SQL Server 2005 Standard Edition on my XP sp2 workstation, developed an SSIS package, which has run for a week on my workstation.

I installed SQL Server 2005 Standard Edition on a Win2003 sp1 server, created the dtsx and install manifest on my workstation, and installed it on the server.

If I run the package on my workstation, pointed to the server database it runs fine.

If I run the dtsx on the server, it fails with the error:

The product level is insufficient for component "Fuzzy Lookup on Name" (83)

Yes, I have SSIS installed on both machines, I have verified that I have the SSIS service on the server.

Any Ideas?

Thanks!

BobP

Bob,
Fuzzy Lookup/Fuzzy Grouping components are part of the Advanced Transformations that are only available in the Enterprise Edition of SQL.
Per MS all transformations/features are available in the BIDS when you are developing. So you really need to becareful about what features you use in your packages.
Larry Poep|||

Thanks
BobP

FUNCTIONS

I just installed SSRS 2005 and I have experience with SQL.

How come this function does not work?

SELECT SUBSTRING(YEAR_MONTH, 1, 2) AS Expr1
FROM table1

I get a message which states that this command is not supported by the provider?

It works fine with other SQL tools like winsql?

thanks

Refer to the responses to your identical post in the Transact_SQL forum.

Often, the quality of the responses received is related to our ability to ‘bounce’ ideas off of each other. In the future, to make it easier for us to offer you assistance, and to prevent folks from wasting time on already answered questions, please don't post to multiple newsgroups. Choose the one that best fits your question and post there. Only post to another newsgroup if you get no answer in a day or two (or if you accidentally posted to the wrong newsgroup –and you indicate that you've already posted elsewhere).

Full-text search services on existing cluster node?

We have a two node cluster that is currently running two instances of SQL 2000.
It turns out that one node has full-text search installed while the other
node does not. Is there a way to install full-text search capabilities on an
existing node? Our research has provided an inconclusive answer. Short of
having to do a full re-install to the one node, is there a way to add
full-text search to an existing node?Hello,
You may want to refer to the following steps to install full-text search
service on the node:
1. Use the Searchstp.exe program to install the full-text search service.
If the full-text search service is not installed on the computer, the
Searchstp.exe program will create it.
2. Use the Ftsetup.exe program to configure the full-text search service
and to configure the instance of SQL Server as an application that uses the
full-text search service. On SQL Server clusters, the Ftsetup.exe program
also creates the required configuration files to maintain the failover
properties for the full-text search resource.
Searchstp.exe is under setupCD: x86\FullText\ftsetup.exe. You may want to
run searchstp.exe of SP4 folder to upgrade it to the proper latest version.
The Ftsetup.exe program uses the following parameter options:
? ApplicationName : For a default instance of SQL Server, the parameter
value must be SQLServer. For a named instance of SQL Server, the parameter
value must be SQLServer\ Instance Name .
? User : For a local system account, the parameter value must be 0. For a
domain user account, the value of the parameter must be Domain Name \ User
Account .
? IsMasterNode : This parameter indicates whether the Ftsetup.exe program
runs on the node that owns the disk where the FTDATA folder will be
created. The parameter value must be 0 or 1.
? IsUpgrade : This parameter indicates whether the FtSetup.exe program is
upgrading the full-text search service to a later version. This parameter
value must be 0 or 1.
? IsCluster : This parameter indicates whether the Ftsetup.exe program runs
on a clustered instance of SQL Server. For a stand-alone instance of SQL
Server, the parameter value must be 0. For a clustered instance of SQL
Server, the parameter value must be 1.
? IsUninstall : This parameter indicates whether the Ftsetup.exe program
removes the full-text search service. If the Ftsetup.exe program installs
the full-text search service, the parameter value must be 0. If the
Ftsetup.exe program removes the full-text search service, the parameter
value must be 1. However, if the parameter value is 1, the values for the
IsMasterNode parameter, the IsUpgrade parameter, and the IsCluster
parameter must all be set to 0.
You shall also remove the registry entries for a clean removal of the
full-text search service. To do so, remove the following registry keys on
both nodes of the SQL Server cluster:
? HKEY_LOCAL_MACHINE\Software\Microsoft\Search
? HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSSCNTRS
? HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSSEARCH
? HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSSGATHERER
? HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSSGTHRSVC
? HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSSINDEX
Since the issue might be complex, we probably will not be able to resolve
the issue through the newsgroups. If above steps does not work for you, I
recommend that you open a Support incident with Microsoft Product Support
Services so that a dedicated Support Professional can assist with this
case. If you need any help in this regard, please let me know.
For a complete list of Microsoft Product Support Services phone numbers,
please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Full-text search services on existing cluster node?

We have a two node cluster that is currently running two instances of SQL 20
00.
It turns out that one node has full-text search installed while the other
node does not. Is there a way to install full-text search capabilities on an
existing node? Our research has provided an inconclusive answer. Short of
having to do a full re-install to the one node, is there a way to add
full-text search to an existing node?Hello,
You may want to refer to the following steps to install full-text search
service on the node:
1. Use the Searchstp.exe program to install the full-text search service.
If the full-text search service is not installed on the computer, the
Searchstp.exe program will create it.
2. Use the Ftsetup.exe program to configure the full-text search service
and to configure the instance of SQL Server as an application that uses the
full-text search service. On SQL Server clusters, the Ftsetup.exe program
also creates the required configuration files to maintain the failover
properties for the full-text search resource.
Searchstp.exe is under setupCD: x86\FullText\ftsetup.exe. You may want to
run searchstp.exe of SP4 folder to upgrade it to the proper latest version.
The Ftsetup.exe program uses the following parameter options:
ApplicationName : For a default instance of SQL Server, the parameter
value must be SQLServer. For a named instance of SQL Server, the parameter
value must be SQLServer\ Instance Name .
User : For a local system account, the parameter value must be 0. For a
domain user account, the value of the parameter must be Domain Name \ User
Account .
IsMasterNode : This parameter indicates whether the Ftsetup.exe program
runs on the node that owns the disk where the FTDATA folder will be
created. The parameter value must be 0 or 1.
IsUpgrade : This parameter indicates whether the FtSetup.exe program is
upgrading the full-text search service to a later version. This parameter
value must be 0 or 1.
IsCluster : This parameter indicates whether the Ftsetup.exe program runs
on a clustered instance of SQL Server. For a stand-alone instance of SQL
Server, the parameter value must be 0. For a clustered instance of SQL
Server, the parameter value must be 1.
IsUninstall : This parameter indicates whether the Ftsetup.exe program
removes the full-text search service. If the Ftsetup.exe program installs
the full-text search service, the parameter value must be 0. If the
Ftsetup.exe program removes the full-text search service, the parameter
value must be 1. However, if the parameter value is 1, the values for the
IsMasterNode parameter, the IsUpgrade parameter, and the IsCluster
parameter must all be set to 0.
You shall also remove the registry entries for a clean removal of the
full-text search service. To do so, remove the following registry keys on
both nodes of the SQL Server cluster:
HKEY_LOCAL_MACHINE\Software\Microsoft\Se
arch
HKEY_LOCAL_MACHINE\System\CurrentControl
Set\Services\MSSCNTRS
HKEY_LOCAL_MACHINE\System\CurrentControl
Set\Services\MSSEARCH
HKEY_LOCAL_MACHINE\System\CurrentControl
Set\Services\MSSGATHERER
HKEY_LOCAL_MACHINE\System\CurrentControl
Set\Services\MSSGTHRSVC
HKEY_LOCAL_MACHINE\System\CurrentControl
Set\Services\MSSINDEX
Since the issue might be complex, we probably will not be able to resolve
the issue through the newsgroups. If above steps does not work for you, I
recommend that you open a Support incident with Microsoft Product Support
Services so that a dedicated Support Professional can assist with this
case. If you need any help in this regard, please let me know.
For a complete list of Microsoft Product Support Services phone numbers,
please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.

Full-Text Search is not installed, or a full-text component cannot

I am unable to get Full Text Indexing to work with SQL Server 2000 Developers
Edition. When I execute this command:
EXEC sp_fulltext_database 'enable'
This is what I get:
(1 row(s) affected)
Server: Msg 7609, Level 17, State 2, Procedure sp_fulltext_database, Line 46
Full-Text Search is not installed, or a full-text component cannot be loaded.
I attempted to install FTS again from the CD, but it indicates that it is
already installed.
Here is the version I am using:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05
Copyright 1988-2003 Microsoft Corporation Developer Edition on Windows NT
5.1 (Build 2600: Service Pack 2)
When I run this at the command prompt:
net start mssearch
I get this:
The requested service has already been started.
More help is available by typing NET HELPMSG 2182
I’m not sure where to go from here.
Hello,
The possible causes of this kind of issue may be as followings:
* Full-Text Search(FTS) is installed AFTER SQL Service Service Pack(SP).
This is the most common cause. Reapplying the SP fixes FTS.
* Microsoft Search service is not installed or started
* SQL server or Microsoft Search service is not started as a administrative
user
To narrow down the issue, I suggest that you perform the following steps:
1. Make sure SQL server and Microsoft Search service are started as the
same domain\administrative user account
2. Install the latest SQL SP4 or reinstall SP3.
Microsoft SQL Server 2000 Service Pack 4
<http://www.microsoft.com/downloads/d...FC8D-C20E-4446
-99A9-B7F0213F8BC5&displaylang=en#filelist>
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Dale,
Sorry for the late reply on this thread, but this type of question is best
answered in the fulltext newsgroup.
The key bit of info here is the SQL Server edition "SQL Server 2000
Developers Edition" as FTS is not installed by default as it is with Std.
Edition and above. You can "re-install" the FTS components via removing or
renaming the following product tracking registry key (remove :
"<Instance_Name>\" if this is not a named instance):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\<Instance_Name>\Tracking\{E07FDDA7-5A21-11d2-9DAD-00C04F79D434}
Then you will be able to re-install the FTS / MSSearch components. You may
also want to review the procedures in KB article 827449 "How to manually
reinstall the Microsoft Search service for an instance of SQL 2000" at
http://support.microsoft.com/default...b;EN-US;827449
Sophie, the advise that you've provided is wrong and will cause known
problems, i.e.. high CPU utilization (there is a KB article on this).
Specifically, the Microsoft Search service MUST be started and running under
the "System account" (LocalSystem), while the MSSQLServer service can be
started and running under either LocalSystem or DOMAIN\Account (but NOT the
DOMAIN\Administrators account!). All this I've learned from years of
experience with SQL FTS since 1998 SQL 7.0 Beta3 while at MSFT...
Regards,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Sophie Guo [MSFT]" <v-sguo@.online.microsoft.com> wrote in message
news:Lg1hyhFqFHA.2152@.TK2MSFTNGXA01.phx.gbl...
> Hello,
> The possible causes of this kind of issue may be as followings:
>
> * Full-Text Search(FTS) is installed AFTER SQL Service Service Pack(SP).
> This is the most common cause. Reapplying the SP fixes FTS.
> * Microsoft Search service is not installed or started
> * SQL server or Microsoft Search service is not started as a
> administrative
> user
>
> To narrow down the issue, I suggest that you perform the following steps:
> 1. Make sure SQL server and Microsoft Search service are started as the
> same domain\administrative user account
> 2. Install the latest SQL SP4 or reinstall SP3.
> Microsoft SQL Server 2000 Service Pack 4
> <http://www.microsoft.com/downloads/d...FC8D-C20E-4446
> -99A9-B7F0213F8BC5&displaylang=en#filelist>
>
> I hope the information is helpful.
>
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ================================================== ===
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>

Full-Text Search is not installed, or a full-text component cannot

Active-active cluster. The second node was reinstalled after a hardware
failure.
The MS Search service is started.
But when I try to query full-text the error message shows up:
Server: Msg 7609, Level 17, State 1, Line 1
Full-Text Search is not installed, or a full-text component cannot be loaded.
How can I reinstall full-text on cluster environment without affect the node
is working ?
thank you
Shimon
I believe you need to evict this node from the cluster, reinstall SQL Server
there and then upgrade it to add it back to the cluster. I have forwarded
this to microsoft.public.sqlserver.clustering for their response to this, as
this is really a clustering question.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Shima" <Shima@.discussions.microsoft.com> wrote in message
news:F1A440E4-2781-408A-B7CE-356968CDCF13@.microsoft.com...
> Active-active cluster. The second node was reinstalled after a hardware
> failure.
> The MS Search service is started.
> But when I try to query full-text the error message shows up:
> Server: Msg 7609, Level 17, State 1, Line 1
> Full-Text Search is not installed, or a full-text component cannot be
> loaded.
> How can I reinstall full-text on cluster environment without affect the
> node
> is working ?
> thank you
> Shimon
|||When you evict a node from a cluster and replace it, you must also clean the
node from the SQL installation. Run the SQL installer and remove the old
node. Then you can re-add it to SQL, which will also re-install full-text.
Don't forget to reapply any service packs and hotfixes to the new node.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23sOoM$sFGHA.3176@.TK2MSFTNGP12.phx.gbl...
>I believe you need to evict this node from the cluster, reinstall SQL
>Server there and then upgrade it to add it back to the cluster. I have
>forwarded this to microsoft.public.sqlserver.clustering for their response
>to this, as this is really a clustering question.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Shima" <Shima@.discussions.microsoft.com> wrote in message
> news:F1A440E4-2781-408A-B7CE-356968CDCF13@.microsoft.com...
>
|||Any time you need to rebuild a piece of hardware in a cluster, it should be
evicted. You need to run SQL Server setup to evict it from the SQL Server
piece of the cluster and then you need to evict the node from the cluster.
Once you add the node back into the cluster, you then need to run SQL Server
setup again to add the node back in for SQL Server. That operation will
reinstall all of the software components.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23sOoM$sFGHA.3176@.TK2MSFTNGP12.phx.gbl...
>I believe you need to evict this node from the cluster, reinstall SQL
>Server there and then upgrade it to add it back to the cluster. I have
>forwarded this to microsoft.public.sqlserver.clustering for their response
>to this, as this is really a clustering question.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Shima" <Shima@.discussions.microsoft.com> wrote in message
> news:F1A440E4-2781-408A-B7CE-356968CDCF13@.microsoft.com...
>

Full-Text Search is not enabled for the current database

We are having problems with Full-Text searching...
Recently we installed a SQL application that needs to access full-text
searching.
It gave the following error:
"The crawl seed <MSSQL75://SQLServer/0539c240> in project <SQLServer
SQL0001400006> cannot be accessed. Error: 8007052e - Logon failure: unknown
user name or bad password."
Upgrading from SQL2kSP3a to SQL2kSP4 didn't change our situation.
Changing to system account following instructions in KB277549 also didn't
fix the problem.
We decided to reinstall the MSSearch service following commands in KB827449.
We received the following error:
"Full-Text Search is not enabled for the current database. Use
sp_fulltext_database to enable full-text search for the database."
Then we ran EXEC sp_fulltext_database 'enable'.
This didn't resolve the problem as we received error message:
"Microsoft search service cannot be administered under present user account."
Current Status recap:
* MSSearch service is started
* In EM > Support Services > Full Text Search is running
* In EM > R-click on Full-Text Catalogs > Rebuild All Catalogs produces
error:
"Microsoft search service cannot be administered under present user account."
* In EM > R-click on catalog within Full-Text Catalog > Rebuild Catalog
produces error:
"Full-Text Search is not enabled for the current database. Use
sp_fulltext_database to enable full-text search for the database."
Not sure if this is user account related or bad install of MSSearch.
Before reloading SQL or contacting MS Support, any advice is appreciated.
Thanks!
D Krage,
As you have reviewed KB 277549 (Q277549) PRB: Unable to Build Full-Text
Catalog After You Modify MSSQLServer Logon Account Through [NT4.0) Control
Panel [or Win2K Component Services] at
http://support.microsoft.com/default...;EN-US;277549, did you do
all of the "Steps to Reproduce Behavior", including stopping & re-starting
the MSSearch & MSSQLServer?
The error you're getting (Logon failure: unknown user name or bad password)
is typical of the above. Additionally, have you or anyone else removed or
altered the BUILTIN\Administrators login? If so, can you re-add it or alter
it back to its original values, including the master database and with
sysadmin rights?
You may also want to review KB article 317746 "PRB: SQL Server Full-Text
Search Does Not Populate Catalogs" at
http://support.microsoft.com/default...b;en-us;317746
However, since you've moved ahead with re-installing the MSSearch components
via the procedures in KB 827449, the above most likely no longer applies. At
this time, the following is the primary error: "Microsoft search service
cannot be administered under present user account." and usually, this error
indicates a missing or altered BUILTIN\Administrators login, but you might
also want to checkout the steps at
http://www.doughughes.net/index.cfm/...nk/entryId-126 as others have
had success with this method in correcting this error.
Hope that helps!
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"d krage" <d krage@.discussions.microsoft.com> wrote in message
news:4C845DC5-B0D7-4F45-A0FC-FB3DCF5F8427@.microsoft.com...
> We are having problems with Full-Text searching...
> Recently we installed a SQL application that needs to access full-text
> searching.
> It gave the following error:
> "The crawl seed <MSSQL75://SQLServer/0539c240> in project <SQLServer
> SQL0001400006> cannot be accessed. Error: 8007052e - Logon failure:
> unknown
> user name or bad password."
> Upgrading from SQL2kSP3a to SQL2kSP4 didn't change our situation.
> Changing to system account following instructions in KB277549 also didn't
> fix the problem.
> We decided to reinstall the MSSearch service following commands in
> KB827449.
> We received the following error:
> "Full-Text Search is not enabled for the current database. Use
> sp_fulltext_database to enable full-text search for the database."
> Then we ran EXEC sp_fulltext_database 'enable'.
> This didn't resolve the problem as we received error message:
> "Microsoft search service cannot be administered under present user
> account."
> Current Status recap:
> * MSSearch service is started
> * In EM > Support Services > Full Text Search is running
> * In EM > R-click on Full-Text Catalogs > Rebuild All Catalogs produces
> error:
> "Microsoft search service cannot be administered under present user
> account."
> * In EM > R-click on catalog within Full-Text Catalog > Rebuild Catalog
> produces error:
> "Full-Text Search is not enabled for the current database. Use
> sp_fulltext_database to enable full-text search for the database."
> Not sure if this is user account related or bad install of MSSearch.
> Before reloading SQL or contacting MS Support, any advice is appreciated.
> Thanks!
|||Thanks for your reply John. As it turns out the error indicated a problem
with user rights, however, the problem turns out to be a bad install of
MSSearch.
Here is what corrected the problem...from Google groups.
http://groups.google.com/group/micro...b7c7692a0e2ff1
According to Google search results, there should be a
HKLM\Software\Microsoft\Search\1.0\Applications\SQ L Server key. This did not
exist, but existed on two of our other servers. The article said to go to
regedit under HKLM\Software\Microsoft\MSSQLServer\Tracking and rename the key
{E07FDDA7-5A21-11d2-9DAD-00C04F79D434}. I renamed the key by putting an X in
front of the name. This makes the SQL Server think that the Search service is
not installed with SQL Server.
After this, shut down all affected services and ran the SQL 2000 install
from CD and did a Custom to modify the installation. All components were
already checked except the Search, so checked the search. Did not uncheck
other components or this would uninstall the other components.
After doing this and rebooting, catalog creation appeared to work. Added
item to database and number of items in catalog increased. Reapplied Service
pack 4 to update the SQL search files. Rebooted. Our SQL app search function
is now working.
Hope this can help someone else out there.
d Krage
"John Kane" wrote:

> D Krage,
> As you have reviewed KB 277549 (Q277549) PRB: Unable to Build Full-Text
> Catalog After You Modify MSSQLServer Logon Account Through [NT4.0) Control
> Panel [or Win2K Component Services] at
> http://support.microsoft.com/default...;EN-US;277549, did you do
> all of the "Steps to Reproduce Behavior", including stopping & re-starting
> the MSSearch & MSSQLServer?
> The error you're getting (Logon failure: unknown user name or bad password)
> is typical of the above. Additionally, have you or anyone else removed or
> altered the BUILTIN\Administrators login? If so, can you re-add it or alter
> it back to its original values, including the master database and with
> sysadmin rights?
> You may also want to review KB article 317746 "PRB: SQL Server Full-Text
> Search Does Not Populate Catalogs" at
> http://support.microsoft.com/default...b;en-us;317746
> However, since you've moved ahead with re-installing the MSSearch components
> via the procedures in KB 827449, the above most likely no longer applies. At
> this time, the following is the primary error: "Microsoft search service
> cannot be administered under present user account." and usually, this error
> indicates a missing or altered BUILTIN\Administrators login, but you might
> also want to checkout the steps at
> http://www.doughughes.net/index.cfm/...nk/entryId-126 as others have
> had success with this method in correcting this error.
> Hope that helps!
> John
> --
> SQL Full Text Search Blog
> http://spaces.msn.com/members/jtkane/
>
> "d krage" <d krage@.discussions.microsoft.com> wrote in message
> news:4C845DC5-B0D7-4F45-A0FC-FB3DCF5F8427@.microsoft.com...
>
>
|||You're welcome, d Krage,
After reviewing the Google groups link & thread as that was an old one from
back in 2001 as I was the person who helped Chris with "The solution that
John found to my problem was this:" back when I was fulltime at Microsoft...
I'm now a bit older and wiser, but it still is good to be remembered!
Thanks,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"d krage" <dkrage@.discussions.microsoft.com> wrote in message
news:8F7D817F-B35C-4689-97E4-C79B711842B8@.microsoft.com...[vbcol=seagreen]
> Thanks for your reply John. As it turns out the error indicated a problem
> with user rights, however, the problem turns out to be a bad install of
> MSSearch.
> Here is what corrected the problem...from Google groups.
> http://groups.google.com/group/micro...b7c7692a0e2ff1
> According to Google search results, there should be a
> HKLM\Software\Microsoft\Search\1.0\Applications\SQ L Server key. This did
> not
> exist, but existed on two of our other servers. The article said to go to
> regedit under HKLM\Software\Microsoft\MSSQLServer\Tracking and rename the
> key
> {E07FDDA7-5A21-11d2-9DAD-00C04F79D434}. I renamed the key by putting an X
> in
> front of the name. This makes the SQL Server think that the Search service
> is
> not installed with SQL Server.
> After this, shut down all affected services and ran the SQL 2000 install
> from CD and did a Custom to modify the installation. All components were
> already checked except the Search, so checked the search. Did not uncheck
> other components or this would uninstall the other components.
> After doing this and rebooting, catalog creation appeared to work. Added
> item to database and number of items in catalog increased. Reapplied
> Service
> pack 4 to update the SQL search files. Rebooted. Our SQL app search
> function
> is now working.
> Hope this can help someone else out there.
> d Krage
> "John Kane" wrote:

Full-Text Search in SQL Server 2005 express

I installed SQL Server 2005 express with advanced services which is supposed to include full-text search capability but I can't get it to work. When I try to create a full-text catalog it gives me an error because it does not think the full-text service is installed or loaded. I can't seem to find a reference to the full-text search feature to enable or install it. any ideas?

There are problems as you already know but there is a work around solution in the link below. Hope this helps.

http://www.wherecanibuyit.co.uk/ASP/full-text-search.html

|||

That was helpful. Thanks. I had to remove sql server 2005 express and reinstall it and then everything worked fine.

Caddre:

There are problems as you already know but there is a work around solution in the link below. Hope this helps.

http://www.wherecanibuyit.co.uk/ASP/full-text-search.html

|||

dsa1971:

That was helpful. Thanks. I had to remove sql server 2005 express and reinstall it and then everything worked fine.

Caddre:

There are problems as you already know but there is a work around solution in the link below. Hope this helps.

http://www.wherecanibuyit.co.uk/ASP/full-text-search.html

I am glad I could help.

Full-text search - catalog refuses to populate

Hello

I'm trying to get full-text searching to work on SQL Server 2000 (with SP3 installed).

I have a table containing many text fields that I want to search and so far have successfully gone through the "Full-Text wizard" selecting the text fields from the table I want as searchable. I then try and start full population of the catalog but its always remains zero in size when I check its properties. Hence when I try a query like:

SELECT Name FROM tblTextDocs WHERE CONTAINS(mainbody, 'find this')

It results in the error message:

Server: Msg 7619, Level 16, State 1, Line 1
Execution of a full-text operation failed. The catalog does not exist or is currently unavailable. Please retry the action again later and if this symptom persists, contact the system administrator.

It would appear that the catalog simply refuses to populate. I've tried starting population via Enterprise Manager and also by doing sp_fulltext_catalog 'MyCatalog', 'start_full'. The Full-text support service says it is running correctly and no other problems with the server have been experienced.

Any suggestions would be much appreciated.

Regards

SamBy the "Full Text Support Service" do you mean the "Microsoft Search" service?|||Originally posted by MCrowley
By the "Full Text Support Service" do you mean the "Microsoft Search" service?

Yes - the Microsoft Search service. I have no problems in stopping/starting it too.|||This error might occur if changing SQL Server Account to Non-Admin for Full-Text Search Makes Existing Catalogs Unusable.

To access existing full-text search catalogs, rebuild and repopulate them. The existing catalogs can also be accessed by switching back to an administrator account.