Adding Fulltext to existing installation 
Author Message
 Adding Fulltext to existing installation

I have a box with SQL2000 SP3 default instance which has
been upgraded from SQL7 and which did not have Fulltext
installed. I have just run through setup to add the full
text component but cannot see sight nor sound of it within
Ent. Mgr. I ran setup again to check and full text is
already ticked so setup thinks it is there.

There is also a clean install of a SQL2000 named instance
with working fulltext catalogues on the same box. This is
un-service packed just at the moment. Might this
be 'interfering' with the default instance?

Any wisdom appreciated.

Simon



Mon, 15 Aug 2005 22:55:06 GMT
 Adding Fulltext to existing installation

could be Q270671.

Can you full text index a table use the sp's?

I would bring that instance up to the same SP level.  

All instance will share the same SQL FTS sp level (the
mssearch binaries).

Quote:
>-----Original Message-----
>I have a box with SQL2000 SP3 default instance which has
>been upgraded from SQL7 and which did not have Fulltext
>installed. I have just run through setup to add the full
>text component but cannot see sight nor sound of it
within
>Ent. Mgr. I ran setup again to check and full text is
>already ticked so setup thinks it is there.

>There is also a clean install of a SQL2000 named instance
>with working fulltext catalogues on the same box. This is
>un-service packed just at the moment. Might this
>be 'interfering' with the default instance?

>Any wisdom appreciated.

>Simon
>.



Tue, 16 Aug 2005 01:13:14 GMT
 Adding Fulltext to existing installation
Simon,
Can you review the Win2K Application event log for "No such interface
supported" as this error indicates a recent SQL 2000 SP3 bug that breaks SQL
Server 2000 FT Indexing on servers where either SQL Server 2000 was upgraded
from SQL Server 7.0 or if SQL Server 7.0 is the default installation and the
SQL 2000 server is a named instance. Note, this error message, *might* be
over-written by now in your Application event log, depending upon the event
log settings.

If you do have this error, then search this newsgroup for that error and you
will find instructions on how to resolve it.
Regards,
John


Quote:
> could be Q270671.

> Can you full text index a table use the sp's?

> I would bring that instance up to the same SP level.

> All instance will share the same SQL FTS sp level (the
> mssearch binaries).

> >-----Original Message-----
> >I have a box with SQL2000 SP3 default instance which has
> >been upgraded from SQL7 and which did not have Fulltext
> >installed. I have just run through setup to add the full
> >text component but cannot see sight nor sound of it
> within
> >Ent. Mgr. I ran setup again to check and full text is
> >already ticked so setup thinks it is there.

> >There is also a clean install of a SQL2000 named instance
> >with working fulltext catalogues on the same box. This is
> >un-service packed just at the moment. Might this
> >be 'interfering' with the default instance?

> >Any wisdom appreciated.

> >Simon
> >.



Fri, 19 Aug 2005 23:56:13 GMT
 Adding Fulltext to existing installation
John,
There are no 'No such interface supported' messages in the
app. log. (It goes back over a month)

Hilary,
When I run:
if (select DATABASEPROPERTY(DB_NAME(),
N'IsFullTextEnabled')) <> 1
exec sp_fulltext_database N'enable'

I get the following error:
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.
So I don't think it's a 270671.

On further investigation, I think the salient point is
that I removed the Builtin\Administrators login so local
admins don't have access.

Q295034 says:
START QUOTE
You do not need to add back the BUILTIN\Administrators
account. It is fully sufficient for the service account
for SQL Server and SQL Server Agent to have login rights
(and be sysadmins), and to add [NT Authority\System] as a
syadmin to represent the local system and thereby enable
full-text search to work properly.
END QUOTE

Q263712 says:
START QUOTE
 "If full-text search is to be used on the cluster, you
must add the [NT Authority\System] account to the server
sysadmin group. For example:
Grant [NT Authority\System] a logon to SQL Server:
EXEC sp_grantlogin [NT Authority\System]
Add that account to the sysadmins role:


END QUOTE

When I run "EXEC sp_grantlogin [NT Authority\System]" I
get "Server: Msg 15401, Level 11, State 1, Procedure
sp_grantlogin, Line 41
Windows NT user or group 'NT Authority\System' not found.
Check the name again."

Has anyone had success with this?

Quote:
>-----Original Message-----
>Simon,
>Can you review the Win2K Application event log for "No
such interface
>supported" as this error indicates a recent SQL 2000 SP3
bug that breaks SQL
>Server 2000 FT Indexing on servers where either SQL

Server 2000 was upgraded
Quote:
>from SQL Server 7.0 or if SQL Server 7.0 is the default

installation and the
Quote:
>SQL 2000 server is a named instance. Note, this error
message, *might* be
>over-written by now in your Application event log,

depending upon the event
Quote:
>log settings.

>If you do have this error, then search this newsgroup for
that error and you
>will find instructions on how to resolve it.
>Regards,
>John



>> could be Q270671.

>> Can you full text index a table use the sp's?

>> I would bring that instance up to the same SP level.

>> All instance will share the same SQL FTS sp level (the
>> mssearch binaries).

>> >-----Original Message-----
>> >I have a box with SQL2000 SP3 default instance which
has
>> >been upgraded from SQL7 and which did not have Fulltext
>> >installed. I have just run through setup to add the
full
>> >text component but cannot see sight nor sound of it
>> within
>> >Ent. Mgr. I ran setup again to check and full text is
>> >already ticked so setup thinks it is there.

>> >There is also a clean install of a SQL2000 named
instance
>> >with working fulltext catalogues on the same box. This
is
>> >un-service packed just at the moment. Might this
>> >be 'interfering' with the default instance?

>> >Any wisdom appreciated.

>> >Simon
>> >.

>.



Sat, 20 Aug 2005 01:17:43 GMT
 Adding Fulltext to existing installation
I have done it many times.  Did you try it through the GUI?

Quote:
> John,
> There are no 'No such interface supported' messages in the
> app. log. (It goes back over a month)

> Hilary,
> When I run:
> if (select DATABASEPROPERTY(DB_NAME(),
> N'IsFullTextEnabled')) <> 1
> exec sp_fulltext_database N'enable'

> I get the following error:
> 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.
> So I don't think it's a 270671.

> On further investigation, I think the salient point is
> that I removed the Builtin\Administrators login so local
> admins don't have access.

> Q295034 says:
> START QUOTE
> You do not need to add back the BUILTIN\Administrators
> account. It is fully sufficient for the service account
> for SQL Server and SQL Server Agent to have login rights
> (and be sysadmins), and to add [NT Authority\System] as a
> syadmin to represent the local system and thereby enable
> full-text search to work properly.
> END QUOTE

> Q263712 says:
> START QUOTE
>  "If full-text search is to be used on the cluster, you
> must add the [NT Authority\System] account to the server
> sysadmin group. For example:
> Grant [NT Authority\System] a logon to SQL Server:
> EXEC sp_grantlogin [NT Authority\System]
> Add that account to the sysadmins role:


> END QUOTE

> When I run "EXEC sp_grantlogin [NT Authority\System]" I
> get "Server: Msg 15401, Level 11, State 1, Procedure
> sp_grantlogin, Line 41
> Windows NT user or group 'NT Authority\System' not found.
> Check the name again."

> Has anyone had success with this?

> >-----Original Message-----
> >Simon,
> >Can you review the Win2K Application event log for "No
> such interface
> >supported" as this error indicates a recent SQL 2000 SP3
> bug that breaks SQL
> >Server 2000 FT Indexing on servers where either SQL
> Server 2000 was upgraded
> >from SQL Server 7.0 or if SQL Server 7.0 is the default
> installation and the
> >SQL 2000 server is a named instance. Note, this error
> message, *might* be
> >over-written by now in your Application event log,
> depending upon the event
> >log settings.

> >If you do have this error, then search this newsgroup for
> that error and you
> >will find instructions on how to resolve it.
> >Regards,
> >John



> >> could be Q270671.

> >> Can you full text index a table use the sp's?

> >> I would bring that instance up to the same SP level.

> >> All instance will share the same SQL FTS sp level (the
> >> mssearch binaries).

> >> >-----Original Message-----
> >> >I have a box with SQL2000 SP3 default instance which
> has
> >> >been upgraded from SQL7 and which did not have Fulltext
> >> >installed. I have just run through setup to add the
> full
> >> >text component but cannot see sight nor sound of it
> >> within
> >> >Ent. Mgr. I ran setup again to check and full text is
> >> >already ticked so setup thinks it is there.

> >> >There is also a clean install of a SQL2000 named
> instance
> >> >with working fulltext catalogues on the same box. This
> is
> >> >un-service packed just at the moment. Might this
> >> >be 'interfering' with the default instance?

> >> >Any wisdom appreciated.

> >> >Simon
> >> >.

> >.



Sat, 20 Aug 2005 09:54:13 GMT
 Adding Fulltext to existing installation
Hilary,

I've tried it with cut and pasted TSQL from the KB
articles, as below, and through SEM. Both get the same
error 15401. In case I'm being thick (no comments
please :) ), do I replace any or all of [NT
Authority/System] or type as is?

Regards,
Simon

Quote:
>-----Original Message-----
>I have done it many times.  Did you try it through the
GUI?

message

>> John,
>> There are no 'No such interface supported' messages in
the
>> app. log. (It goes back over a month)

>> Hilary,
>> When I run:
>> if (select DATABASEPROPERTY(DB_NAME(),
>> N'IsFullTextEnabled')) <> 1
>> exec sp_fulltext_database N'enable'

>> I get the following error:
>> 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.
>> So I don't think it's a 270671.

>> On further investigation, I think the salient point is
>> that I removed the Builtin\Administrators login so local
>> admins don't have access.

>> Q295034 says:
>> START QUOTE
>> You do not need to add back the BUILTIN\Administrators
>> account. It is fully sufficient for the service account
>> for SQL Server and SQL Server Agent to have login rights
>> (and be sysadmins), and to add [NT Authority\System] as
a
>> syadmin to represent the local system and thereby enable
>> full-text search to work properly.
>> END QUOTE

>> Q263712 says:
>> START QUOTE
>>  "If full-text search is to be used on the cluster, you
>> must add the [NT Authority\System] account to the server
>> sysadmin group. For example:
>> Grant [NT Authority\System] a logon to SQL Server:
>> EXEC sp_grantlogin [NT Authority\System]
>> Add that account to the sysadmins role:

Authority\System]

>> END QUOTE

>> When I run "EXEC sp_grantlogin [NT Authority\System]" I
>> get "Server: Msg 15401, Level 11, State 1, Procedure
>> sp_grantlogin, Line 41
>> Windows NT user or group 'NT Authority\System' not
found.
>> Check the name again."

>> Has anyone had success with this?

>> >-----Original Message-----
>> >Simon,
>> >Can you review the Win2K Application event log for "No
>> such interface
>> >supported" as this error indicates a recent SQL 2000
SP3
>> bug that breaks SQL
>> >Server 2000 FT Indexing on servers where either SQL
>> Server 2000 was upgraded
>> >from SQL Server 7.0 or if SQL Server 7.0 is the default
>> installation and the
>> >SQL 2000 server is a named instance. Note, this error
>> message, *might* be
>> >over-written by now in your Application event log,
>> depending upon the event
>> >log settings.

>> >If you do have this error, then search this newsgroup
for
>> that error and you
>> >will find instructions on how to resolve it.
>> >Regards,
>> >John



>> >> could be Q270671.

>> >> Can you full text index a table use the sp's?

>> >> I would bring that instance up to the same SP level.

>> >> All instance will share the same SQL FTS sp level
(the
>> >> mssearch binaries).

>> >> >-----Original Message-----
>> >> >I have a box with SQL2000 SP3 default instance which
>> has
>> >> >been upgraded from SQL7 and which did not have
Fulltext
>> >> >installed. I have just run through setup to add the
>> full
>> >> >text component but cannot see sight nor sound of it
>> >> within
>> >> >Ent. Mgr. I ran setup again to check and full text
is
>> >> >already ticked so setup thinks it is there.

>> >> >There is also a clean install of a SQL2000 named
>> instance
>> >> >with working fulltext catalogues on the same box.
This
>> is
>> >> >un-service packed just at the moment. Might this
>> >> >be 'interfering' with the default instance?

>> >> >Any wisdom appreciated.

>> >> >Simon
>> >> >.

>> >.

>.



Sat, 20 Aug 2005 20:44:18 GMT
 Adding Fulltext to existing installation
say hello to Mark Allison for me.

Try this

if not exists (select * from master.dbo.syslogins where
loginname = N'NT Authority\System')
        exec sp_grantlogin N'NT Authority\System'
        exec sp_defaultdb N'NT Authority\System', N'master'
        exec sp_defaultlanguage N'NT Authority\System',
N'us_english'
GO
exec sp_addsrvrolemember N'NT Authority\System', sysadmin
GO

Quote:
>-----Original Message-----
>Hilary,

>I've tried it with cut and pasted TSQL from the KB
>articles, as below, and through SEM. Both get the same
>error 15401. In case I'm being thick (no comments
>please :) ), do I replace any or all of [NT
>Authority/System] or type as is?

>Regards,
>Simon
>>-----Original Message-----
>>I have done it many times.  Did you try it through the
>GUI?

in
>message

>>> John,
>>> There are no 'No such interface supported' messages in
>the
>>> app. log. (It goes back over a month)

>>> Hilary,
>>> When I run:
>>> if (select DATABASEPROPERTY(DB_NAME(),
>>> N'IsFullTextEnabled')) <> 1
>>> exec sp_fulltext_database N'enable'

>>> I get the following error:
>>> 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.
>>> So I don't think it's a 270671.

>>> On further investigation, I think the salient point is
>>> that I removed the Builtin\Administrators login so
local
>>> admins don't have access.

>>> Q295034 says:
>>> START QUOTE
>>> You do not need to add back the BUILTIN\Administrators
>>> account. It is fully sufficient for the service account
>>> for SQL Server and SQL Server Agent to have login
rights
>>> (and be sysadmins), and to add [NT Authority\System]
as
>a
>>> syadmin to represent the local system and thereby
enable
>>> full-text search to work properly.
>>> END QUOTE

>>> Q263712 says:
>>> START QUOTE
>>>  "If full-text search is to be used on the cluster, you
>>> must add the [NT Authority\System] account to the
server
>>> sysadmin group. For example:
>>> Grant [NT Authority\System] a logon to SQL Server:
>>> EXEC sp_grantlogin [NT Authority\System]
>>> Add that account to the sysadmins role:

>Authority\System]

>>> END QUOTE

>>> When I run "EXEC sp_grantlogin [NT Authority\System]" I
>>> get "Server: Msg 15401, Level 11, State 1, Procedure
>>> sp_grantlogin, Line 41
>>> Windows NT user or group 'NT Authority\System' not
>found.
>>> Check the name again."

>>> Has anyone had success with this?

>>> >-----Original Message-----
>>> >Simon,
>>> >Can you review the Win2K Application event log for "No
>>> such interface
>>> >supported" as this error indicates a recent SQL 2000
>SP3
>>> bug that breaks SQL
>>> >Server 2000 FT Indexing on servers where either SQL
>>> Server 2000 was upgraded
>>> >from SQL Server 7.0 or if SQL Server 7.0 is the
default
>>> installation and the
>>> >SQL 2000 server is a named instance. Note, this error
>>> message, *might* be
>>> >over-written by now in your Application event log,
>>> depending upon the event
>>> >log settings.

>>> >If you do have this error, then search this newsgroup
>for
>>> that error and you
>>> >will find instructions on how to resolve it.
>>> >Regards,
>>> >John



>>> >> could be Q270671.

>>> >> Can you full text index a table use the sp's?

>>> >> I would bring that instance up to the same SP level.

>>> >> All instance will share the same SQL FTS sp level
>(the
>>> >> mssearch binaries).

>>> >> >-----Original Message-----
>>> >> >I have a box with SQL2000 SP3 default instance
which
>>> has
>>> >> >been upgraded from SQL7 and which did not have
>Fulltext
>>> >> >installed. I have just run through setup to add the
>>> full
>>> >> >text component but cannot see sight nor sound of it
>>> >> within
>>> >> >Ent. Mgr. I ran setup again to check and full text
>is
>>> >> >already ticked so setup thinks it is there.

>>> >> >There is also a clean install of a SQL2000 named
>>> instance
>>> >> >with working fulltext catalogues on the same box.
>This
>>> is
>>> >> >un-service packed just at the moment. Might this
>>> >> >be 'interfering' with the default instance?

>>> >> >Any wisdom appreciated.

>>> >> >Simon
>>> >> >.

>>> >.

>>.

>.



Sun, 21 Aug 2005 00:10:56 GMT
 Adding Fulltext to existing installation
I've tried it on 4 servers. 2 succeded (Win2k) and 2
failed (NT4). Is NT Authority\System a win2k thing?

I'll pass on your regards to Mark next time I see him
(He's moved on from CC)

Quote:
>-----Original Message-----
>say hello to Mark Allison for me.

>Try this

>if not exists (select * from master.dbo.syslogins where
>loginname = N'NT Authority\System')
>    exec sp_grantlogin N'NT Authority\System'
>    exec sp_defaultdb N'NT Authority\System', N'master'
>    exec sp_defaultlanguage N'NT Authority\System',
>N'us_english'
>GO
>exec sp_addsrvrolemember N'NT Authority\System', sysadmin
>GO

>>-----Original Message-----
>>Hilary,

>>I've tried it with cut and pasted TSQL from the KB
>>articles, as below, and through SEM. Both get the same
>>error 15401. In case I'm being thick (no comments
>>please :) ), do I replace any or all of [NT
>>Authority/System] or type as is?

>>Regards,
>>Simon
>>>-----Original Message-----
>>>I have done it many times.  Did you try it through the
>>GUI?

>in
>>message

>>>> John,
>>>> There are no 'No such interface supported' messages
in
>>the
>>>> app. log. (It goes back over a month)

>>>> Hilary,
>>>> When I run:
>>>> if (select DATABASEPROPERTY(DB_NAME(),
>>>> N'IsFullTextEnabled')) <> 1
>>>> exec sp_fulltext_database N'enable'

>>>> I get the following error:
>>>> 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.
>>>> So I don't think it's a 270671.

>>>> On further investigation, I think the salient point is
>>>> that I removed the Builtin\Administrators login so
>local
>>>> admins don't have access.

>>>> Q295034 says:
>>>> START QUOTE
>>>> You do not need to add back the BUILTIN\Administrators
>>>> account. It is fully sufficient for the service
account
>>>> for SQL Server and SQL Server Agent to have login
>rights
>>>> (and be sysadmins), and to add [NT Authority\System]
>as
>>a
>>>> syadmin to represent the local system and thereby
>enable
>>>> full-text search to work properly.
>>>> END QUOTE

>>>> Q263712 says:
>>>> START QUOTE
>>>>  "If full-text search is to be used on the cluster,
you
>>>> must add the [NT Authority\System] account to the
>server
>>>> sysadmin group. For example:
>>>> Grant [NT Authority\System] a logon to SQL Server:
>>>> EXEC sp_grantlogin [NT Authority\System]
>>>> Add that account to the sysadmins role:

>>Authority\System]

>>>> END QUOTE

>>>> When I run "EXEC sp_grantlogin [NT Authority\System]"
I
>>>> get "Server: Msg 15401, Level 11, State 1, Procedure
>>>> sp_grantlogin, Line 41
>>>> Windows NT user or group 'NT Authority\System' not
>>found.
>>>> Check the name again."

>>>> Has anyone had success with this?

>>>> >-----Original Message-----
>>>> >Simon,
>>>> >Can you review the Win2K Application event log
for "No
>>>> such interface
>>>> >supported" as this error indicates a recent SQL 2000
>>SP3
>>>> bug that breaks SQL
>>>> >Server 2000 FT Indexing on servers where either SQL
>>>> Server 2000 was upgraded
>>>> >from SQL Server 7.0 or if SQL Server 7.0 is the
>default
>>>> installation and the
>>>> >SQL 2000 server is a named instance. Note, this error
>>>> message, *might* be
>>>> >over-written by now in your Application event log,
>>>> depending upon the event
>>>> >log settings.

>>>> >If you do have this error, then search this
newsgroup
>>for
>>>> that error and you
>>>> >will find instructions on how to resolve it.
>>>> >Regards,
>>>> >John



>>>> >> could be Q270671.

>>>> >> Can you full text index a table use the sp's?

>>>> >> I would bring that instance up to the same SP
level.

>>>> >> All instance will share the same SQL FTS sp level
>>(the
>>>> >> mssearch binaries).

>>>> >> >-----Original Message-----
>>>> >> >I have a box with SQL2000 SP3 default instance
>which
>>>> has
>>>> >> >been upgraded from SQL7 and which did not have
>>Fulltext
>>>> >> >installed. I have just run through setup to add
the
>>>> full
>>>> >> >text component but cannot see sight nor sound of
it
>>>> >> within
>>>> >> >Ent. Mgr. I ran setup again to check and full
text
>>is
>>>> >> >already ticked so setup thinks it is there.

>>>> >> >There is also a clean install of a SQL2000 named
>>>> instance
>>>> >> >with working fulltext catalogues on the same box.
>>This
>>>> is
>>>> >> >un-service packed just at the moment. Might this
>>>> >> >be 'interfering' with the default instance?

>>>> >> >Any wisdom appreciated.

>>>> >> >Simon
>>>> >> >.

>>>> >.

>>>.

>>.

>.



Sun, 21 Aug 2005 19:22:29 GMT
 Adding Fulltext to existing installation
Simon,
Where all of the servers - SQL Server 2000 - or were some (those that failed
?) SQL Server 7.0 on NT 4.0 ?
Regards,
John


Quote:
> I've tried it on 4 servers. 2 succeded (Win2k) and 2
> failed (NT4). Is NT Authority\System a win2k thing?

> I'll pass on your regards to Mark next time I see him
> (He's moved on from CC)

> >-----Original Message-----
> >say hello to Mark Allison for me.

> >Try this

> >if not exists (select * from master.dbo.syslogins where
> >loginname = N'NT Authority\System')
> > exec sp_grantlogin N'NT Authority\System'
> > exec sp_defaultdb N'NT Authority\System', N'master'
> > exec sp_defaultlanguage N'NT Authority\System',
> >N'us_english'
> >GO
> >exec sp_addsrvrolemember N'NT Authority\System', sysadmin
> >GO

> >>-----Original Message-----
> >>Hilary,

> >>I've tried it with cut and pasted TSQL from the KB
> >>articles, as below, and through SEM. Both get the same
> >>error 15401. In case I'm being thick (no comments
> >>please :) ), do I replace any or all of [NT
> >>Authority/System] or type as is?

> >>Regards,
> >>Simon
> >>>-----Original Message-----
> >>>I have done it many times.  Did you try it through the
> >>GUI?

> >in
> >>message

> >>>> John,
> >>>> There are no 'No such interface supported' messages
> in
> >>the
> >>>> app. log. (It goes back over a month)

> >>>> Hilary,
> >>>> When I run:
> >>>> if (select DATABASEPROPERTY(DB_NAME(),
> >>>> N'IsFullTextEnabled')) <> 1
> >>>> exec sp_fulltext_database N'enable'

> >>>> I get the following error:
> >>>> 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.
> >>>> So I don't think it's a 270671.

> >>>> On further investigation, I think the salient point is
> >>>> that I removed the Builtin\Administrators login so
> >local
> >>>> admins don't have access.

> >>>> Q295034 says:
> >>>> START QUOTE
> >>>> You do not need to add back the BUILTIN\Administrators
> >>>> account. It is fully sufficient for the service
> account
> >>>> for SQL Server and SQL Server Agent to have login
> >rights
> >>>> (and be sysadmins), and to add [NT Authority\System]
> >as
> >>a
> >>>> syadmin to represent the local system and thereby
> >enable
> >>>> full-text search to work properly.
> >>>> END QUOTE

> >>>> Q263712 says:
> >>>> START QUOTE
> >>>>  "If full-text search is to be used on the cluster,
> you
> >>>> must add the [NT Authority\System] account to the
> >server
> >>>> sysadmin group. For example:
> >>>> Grant [NT Authority\System] a logon to SQL Server:
> >>>> EXEC sp_grantlogin [NT Authority\System]
> >>>> Add that account to the sysadmins role:

> >>Authority\System]

> >>>> END QUOTE

> >>>> When I run "EXEC sp_grantlogin [NT Authority\System]"
> I
> >>>> get "Server: Msg 15401, Level 11, State 1, Procedure
> >>>> sp_grantlogin, Line 41
> >>>> Windows NT user or group 'NT Authority\System' not
> >>found.
> >>>> Check the name again."

> >>>> Has anyone had success with this?

> >>>> >-----Original Message-----
> >>>> >Simon,
> >>>> >Can you review the Win2K Application event log
> for "No
> >>>> such interface
> >>>> >supported" as this error indicates a recent SQL 2000
> >>SP3
> >>>> bug that breaks SQL
> >>>> >Server 2000 FT Indexing on servers where either SQL
> >>>> Server 2000 was upgraded
> >>>> >from SQL Server 7.0 or if SQL Server 7.0 is the
> >default
> >>>> installation and the
> >>>> >SQL 2000 server is a named instance. Note, this error
> >>>> message, *might* be
> >>>> >over-written by now in your Application event log,
> >>>> depending upon the event
> >>>> >log settings.

> >>>> >If you do have this error, then search this
> newsgroup
> >>for
> >>>> that error and you
> >>>> >will find instructions on how to resolve it.
> >>>> >Regards,
> >>>> >John



> >>>> >> could be Q270671.

> >>>> >> Can you full text index a table use the sp's?

> >>>> >> I would bring that instance up to the same SP
> level.

> >>>> >> All instance will share the same SQL FTS sp level
> >>(the
> >>>> >> mssearch binaries).

> >>>> >> >-----Original Message-----
> >>>> >> >I have a box with SQL2000 SP3 default instance
> >which
> >>>> has
> >>>> >> >been upgraded from SQL7 and which did not have
> >>Fulltext
> >>>> >> >installed. I have just run through setup to add
> the
> >>>> full
> >>>> >> >text component but cannot see sight nor sound of
> it
> >>>> >> within
> >>>> >> >Ent. Mgr. I ran setup again to check and full
> text
> >>is
> >>>> >> >already ticked so setup thinks it is there.

> >>>> >> >There is also a clean install of a SQL2000 named
> >>>> instance
> >>>> >> >with working fulltext catalogues on the same box.
> >>This
> >>>> is
> >>>> >> >un-service packed just at the moment. Might this
> >>>> >> >be 'interfering' with the default instance?

> >>>> >> >Any wisdom appreciated.

> >>>> >> >Simon
> >>>> >> >.

> >>>> >.

> >>>.

> >>.

> >.



Sun, 21 Aug 2005 22:39:20 GMT
 Adding Fulltext to existing installation
John,

They are all SQL2000.
Server# SP  OS           Login created
======= === ============ =============
35      3   NT4 Server   No
39      3   NT4 Server   No
51      2   NT4 Server   No
55      2   NT4 Server   No
43      3   NT4 Server   Yes
70      3   Win2k Server Yes
99      3   Win2k Prof   Yes

Some if not all of the 'failing' servers had SQL7 on
originally although none were upgraded. SQL7 would have
been uninstalled and a fresh SQL2000 install.

Regards,
Simon

Quote:
>-----Original Message-----
>Simon,
>Where all of the servers - SQL Server 2000 - or were some
(those that failed
>?) SQL Server 7.0 on NT 4.0 ?
>Regards,
>John


message

>> I've tried it on 4 servers. 2 succeded (Win2k) and 2
>> failed (NT4). Is NT Authority\System a win2k thing?

>> I'll pass on your regards to Mark next time I see him
>> (He's moved on from CC)

>> >-----Original Message-----
>> >say hello to Mark Allison for me.

>> >Try this

>> >if not exists (select * from master.dbo.syslogins where
>> >loginname = N'NT Authority\System')
>> > exec sp_grantlogin N'NT Authority\System'
>> > exec sp_defaultdb N'NT Authority\System', N'master'
>> > exec sp_defaultlanguage N'NT Authority\System',
>> >N'us_english'
>> >GO
>> >exec sp_addsrvrolemember N'NT Authority\System',
sysadmin
>> >GO

>> >>-----Original Message-----
>> >>Hilary,

>> >>I've tried it with cut and pasted TSQL from the KB
>> >>articles, as below, and through SEM. Both get the same
>> >>error 15401. In case I'm being thick (no comments
>> >>please :) ), do I replace any or all of [NT
>> >>Authority/System] or type as is?

>> >>Regards,
>> >>Simon
>> >>>-----Original Message-----
>> >>>I have done it many times.  Did you try it through
the
>> >>GUI?

wrote
>> >in
>> >>message

>> >>>> John,
>> >>>> There are no 'No such interface supported' messages
>> in
>> >>the
>> >>>> app. log. (It goes back over a month)

>> >>>> Hilary,
>> >>>> When I run:
>> >>>> if (select DATABASEPROPERTY(DB_NAME(),
>> >>>> N'IsFullTextEnabled')) <> 1
>> >>>> exec sp_fulltext_database N'enable'

>> >>>> I get the following error:
>> >>>> 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.
>> >>>> So I don't think it's a 270671.

>> >>>> On further investigation, I think the salient
point is
>> >>>> that I removed the Builtin\Administrators login so
>> >local
>> >>>> admins don't have access.

>> >>>> Q295034 says:
>> >>>> START QUOTE
>> >>>> You do not need to add back the

BUILTIN\Administrators

- Show quoted text -

Quote:
>> >>>> account. It is fully sufficient for the service
>> account
>> >>>> for SQL Server and SQL Server Agent to have login
>> >rights
>> >>>> (and be sysadmins), and to add [NT
Authority\System]
>> >as
>> >>a
>> >>>> syadmin to represent the local system and thereby
>> >enable
>> >>>> full-text search to work properly.
>> >>>> END QUOTE

>> >>>> Q263712 says:
>> >>>> START QUOTE
>> >>>>  "If full-text search is to be used on the cluster,
>> you
>> >>>> must add the [NT Authority\System] account to the
>> >server
>> >>>> sysadmin group. For example:
>> >>>> Grant [NT Authority\System] a logon to SQL Server:
>> >>>> EXEC sp_grantlogin [NT Authority\System]
>> >>>> Add that account to the sysadmins role:

>> >>Authority\System]

>> >>>> END QUOTE

>> >>>> When I run "EXEC sp_grantlogin [NT
Authority\System]"
>> I
>> >>>> get "Server: Msg 15401, Level 11, State 1,
Procedure
>> >>>> sp_grantlogin, Line 41
>> >>>> Windows NT user or group 'NT Authority\System' not
>> >>found.
>> >>>> Check the name again."

>> >>>> Has anyone had success with this?

>> >>>> >-----Original Message-----
>> >>>> >Simon,
>> >>>> >Can you review the Win2K Application event log
>> for "No
>> >>>> such interface
>> >>>> >supported" as this error indicates a recent SQL
2000
>> >>SP3
>> >>>> bug that breaks SQL
>> >>>> >Server 2000 FT Indexing on servers where either
SQL
>> >>>> Server 2000 was upgraded
>> >>>> >from SQL Server 7.0 or if SQL Server 7.0 is the
>> >default
>> >>>> installation and the
>> >>>> >SQL 2000 server is a named instance. Note, this
error
>> >>>> message, *might* be
>> >>>> >over-written by now in your Application event log,
>> >>>> depending upon the event
>> >>>> >log settings.

>> >>>> >If you do have this error, then search this
>> newsgroup
>> >>for
>> >>>> that error and you
>> >>>> >will find instructions on how to resolve it.
>> >>>> >Regards,
>> >>>> >John



>> >>>> >> could be Q270671.

>> >>>> >> Can you full text index a table use the sp's?

>> >>>> >> I would bring that instance up to the same SP
>> level.

>> >>>> >> All instance will share the same SQL FTS sp
level
>> >>(the
>> >>>> >> mssearch binaries).

>> >>>> >> >-----Original Message-----
>> >>>> >> >I have a box with SQL2000 SP3 default instance
>> >which
>> >>>> has
>> >>>> >> >been upgraded from SQL7 and which did not have
>> >>Fulltext
>> >>>> >> >installed. I have just run through setup to add
>> the
>> >>>> full
>> >>>> >> >text component but cannot see sight nor sound
of
>> it
>> >>>> >> within
>> >>>> >> >Ent. Mgr. I ran setup again to check and full
>> text
>> >>is
>> >>>> >> >already ticked so setup thinks it is there.

>> >>>> >> >There is also a clean install of a SQL2000
named
>> >>>> instance
>> >>>> >> >with working fulltext catalogues on the same
box.
>> >>This
>> >>>> is
>> >>>> >> >un-service packed just at the moment. Might
this
>> >>>> >> >be 'interfering' with the default instance?

>> >>>> >> >Any wisdom appreciated.

>> >>>> >> >Simon
>> >>>> >> >.

>> >>>> >.

>> >>>.

>> >>.

>> >.

>.



Tue, 23 Aug 2005 21:04:11 GMT
 Adding Fulltext to existing installation
Thanks for the info, Simon!
What I was trying determine is if SQL7 on was originally
installed and then SQL Server 2000 upgraded to SP3 as
there is a known bug for this scerino.

John

Quote:
>-----Original Message-----
>John,

>They are all SQL2000.
>Server# SP  OS           Login created
>======= === ============ =============
>35      3   NT4 Server   No
>39      3   NT4 Server   No
>51      2   NT4 Server   No
>55      2   NT4 Server   No
>43      3   NT4 Server   Yes
>70      3   Win2k Server Yes
>99      3   Win2k Prof   Yes

>Some if not all of the 'failing' servers had SQL7 on
>originally although none were upgraded. SQL7 would have
>been uninstalled and a fresh SQL2000 install.

>Regards,
>Simon
>>-----Original Message-----
>>Simon,
>>Where all of the servers - SQL Server 2000 - or were
some
>(those that failed
>>?) SQL Server 7.0 on NT 4.0 ?
>>Regards,
>>John


in
>message

>>> I've tried it on 4 servers. 2 succeded (Win2k) and 2
>>> failed (NT4). Is NT Authority\System a win2k thing?

>>> I'll pass on your regards to Mark next time I see him
>>> (He's moved on from CC)

>>> >-----Original Message-----
>>> >say hello to Mark Allison for me.

>>> >Try this

>>> >if not exists (select * from master.dbo.syslogins
where
>>> >loginname = N'NT Authority\System')
>>> > exec sp_grantlogin N'NT Authority\System'
>>> > exec sp_defaultdb N'NT Authority\System', N'master'
>>> > exec sp_defaultlanguage N'NT Authority\System',
>>> >N'us_english'
>>> >GO
>>> >exec sp_addsrvrolemember N'NT Authority\System',
>sysadmin
>>> >GO

>>> >>-----Original Message-----
>>> >>Hilary,

>>> >>I've tried it with cut and pasted TSQL from the KB
>>> >>articles, as below, and through SEM. Both get the
same
>>> >>error 15401. In case I'm being thick (no comments
>>> >>please :) ), do I replace any or all of [NT
>>> >>Authority/System] or type as is?

>>> >>Regards,
>>> >>Simon
>>> >>>-----Original Message-----
>>> >>>I have done it many times.  Did you try it through
>the
>>> >>GUI?

>wrote
>>> >in
>>> >>message

>>> >>>> John,
>>> >>>> There are no 'No such interface supported'
messages
>>> in
>>> >>the
>>> >>>> app. log. (It goes back over a month)

>>> >>>> Hilary,
>>> >>>> When I run:
>>> >>>> if (select DATABASEPROPERTY(DB_NAME(),
>>> >>>> N'IsFullTextEnabled')) <> 1
>>> >>>> exec sp_fulltext_database N'enable'

>>> >>>> I get the following error:
>>> >>>> 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.
>>> >>>> So I don't think it's a 270671.

>>> >>>> On further investigation, I think the salient
>point is
>>> >>>> that I removed the Builtin\Administrators login
so
>>> >local
>>> >>>> admins don't have access.

>>> >>>> Q295034 says:
>>> >>>> START QUOTE
>>> >>>> You do not need to add back the
>BUILTIN\Administrators
>>> >>>> account. It is fully sufficient for the service
>>> account
>>> >>>> for SQL Server and SQL Server Agent to have login
>>> >rights
>>> >>>> (and be sysadmins), and to add [NT
>Authority\System]
>>> >as
>>> >>a
>>> >>>> syadmin to represent the local system and thereby
>>> >enable
>>> >>>> full-text search to work properly.
>>> >>>> END QUOTE

>>> >>>> Q263712 says:
>>> >>>> START QUOTE
>>> >>>>  "If full-text search is to be used on the
cluster,
>>> you
>>> >>>> must add the [NT Authority\System] account to the
>>> >server
>>> >>>> sysadmin group. For example:
>>> >>>> Grant [NT Authority\System] a logon to SQL
Server:
>>> >>>> EXEC sp_grantlogin [NT Authority\System]
>>> >>>> Add that account to the sysadmins role:

>>> >>Authority\System]

>>> >>>> END QUOTE

>>> >>>> When I run "EXEC sp_grantlogin [NT
>Authority\System]"
>>> I
>>> >>>> get "Server: Msg 15401, Level 11, State 1,
>Procedure
>>> >>>> sp_grantlogin, Line 41
>>> >>>> Windows NT user or group 'NT Authority\System'
not
>>> >>found.
>>> >>>> Check the name again."

>>> >>>> Has anyone had success with this?

>>> >>>> >-----Original Message-----
>>> >>>> >Simon,
>>> >>>> >Can you review the Win2K Application event log
>>> for "No
>>> >>>> such interface
>>> >>>> >supported" as this error indicates a recent SQL
>2000
>>> >>SP3
>>> >>>> bug that breaks SQL
>>> >>>> >Server 2000 FT Indexing on servers where either
>SQL
>>> >>>> Server 2000 was upgraded
>>> >>>> >from SQL Server 7.0 or if SQL Server 7.0 is the
>>> >default
>>> >>>> installation and the
>>> >>>> >SQL 2000 server is a named instance. Note, this
>error
>>> >>>> message, *might* be
>>> >>>> >over-written by now in your Application event
log,
>>> >>>> depending upon the event
>>> >>>> >log settings.

>>> >>>> >If you do have this error, then search this
>>> newsgroup
>>> >>for
>>> >>>> that error and you
>>> >>>> >will find instructions on how to resolve it.
>>> >>>> >Regards,
>>> >>>> >John


message

>>> >>>> >> could be Q270671.

>>> >>>> >> Can you full text index a table use the sp's?

>>> >>>> >> I would bring that instance up to the same SP
>>> level.

>>> >>>> >> All instance will share the same SQL FTS sp
>level
>>> >>(the
>>> >>>> >> mssearch binaries).

>>> >>>> >> >-----Original Message-----
>>> >>>> >> >I have a box with SQL2000 SP3 default
instance
>>> >which
>>> >>>> has
>>> >>>> >> >been upgraded from SQL7 and which did not
have
>>> >>Fulltext
>>> >>>> >> >installed. I have just run through setup to
add
>>> the
>>> >>>> full
>>> >>>> >> >text component but cannot see sight nor
sound
>of
>>> it
>>> >>>> >> within
>>> >>>> >> >Ent. Mgr. I ran setup again to check and full
>>> text
>>> >>is
>>> >>>> >> >already ticked so setup thinks it is there.

>>> >>>> >> >There is also a clean install of a SQL2000
>named
>>> >>>> instance
>>> >>>> >> >with working fulltext catalogues on the same
>box.
>>> >>This
>>> >>>> is
>>> >>>> >> >un-service packed just at the moment. Might
>this
>>> >>>> >> >be 'interfering' with the default instance?

>>> >>>> >> >Any wisdom appreciated.

>>> >>>> >> >Simon
>>> >>>> >> >.

>>> >>>> >.

>>> >>>.

>>> >>.

>>> >.

>>.

>.



Wed, 14 Sep 2005 00:18:59 GMT
 
 [ 11 post ] 

 Relevant Pages 

1. Installation SQL server 2000: previous installation - files pending

2. MDac Installation during SQL 2000 Installation Fails

3. Error: A previous program installation created pending file operations on the installation machine

4. MDAC installation during SQL 2000 Installation

5. sql 2000 installation error, auto close installation windows

6. Hyphens in computername prevent SQL Server installation through the SMS 2.0 installation

7. MDAC error on SQL 2000 installation

8. very slow after installation

9. DB installation on a remote server

10. SQL Server 2000 Beta 2 installation

11. Installation of SQL Server 7 Desktop Edition on Windows 98 - PROBLEM

12. SQL Server installation on Win NT


 
Powered by phpBB® Forum Software