'Microsoft Search service cannot be administered under the present user error' SP3

Hi,
We have SQL Server private installation on which we are developing an
application and public installation on whict we will be deploying the
application. All instances have run Windows 2003 Enterprise Edition with SQL
2000 SP3. However, the public installation MS Search is not functioning
correctly. Basically it will not full-text indeed databases and produces
the following error
1> exec sp_fulltext_database 'enable'
2> go
(1 row affected)
Msg 7635, Level 16, State 1, Server SIMP001, Procedure sp_fulltext_database,
Lin
e 46
The Microsoft Search service cannot be administered under the present user
account
Now, we have tried many things to try and solve this error, mainly based on
search newsgroups, which are itemized below:
1 Reboot System and reexecute sp_
2 Complete reinstall of SQL on system, then reapplication of SP3
3 Same as above (2) but reapply SP3a
4 Remove SQL Server installation subkey in order that can reinstall
full-text search only, then reapply SP3
5 Check from keys under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\A pplications\ to make sure
SQL Server was there. It wasn't, removed SQL subkey and reinstalled,
re-adding full-text search as an option (to re-install full-text) then
reapplied SP3
6 Try reinstall, but do not reapply SP3 until have full-text enabled the
database.
None of the above worked. We still have a none functioning mssearch and
full-text disabled database on the system.
We have even tried enabling on a blank database. This does not work either.
PLEASE HELP! Getting desperate as the whole application depends on having
search ability.
Thanks
Oz
You will probably need to use the steps in the following article to bypass
this error:
How to manually reinstall the Microsoft Search service for an instance of
SQL Server 2000
http://support.microsoft.com/default.aspx?scid=kb;[LN];827449
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Oz,
In addition to the many things you tried below... a couple of things
specific to MSSearch and the MSSQLServer services...
1. Is the MSSearch service started and running under the System
(LocalSystem) account? If not, then change it to LocalSystem and stop and
re-start this service.
2. Have you or anyone else change the MSSQLServer account &/or password via
Win2K's Component service? IF so, then you MUST re-change the change via the
Enterprise Manager's server property security tab as this is the only place
where the two services security are kept in sync. See KB article 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...B;EN-US;277549
3. Have you or anyone else removed or modified the BUILTIN\Administrator
login on this server? If so, you MUST either re-add it with all of it's
normal default rights, especially sysadmin rights and with the default
database as master and the default language of English or use the following
T-SQL code to add the correct permissions:
exec sp_grantlogin N'NT Authority\System'
exec sp_defaultdb N'NT Authority\System', N'master'
exec sp_defaultlanguage N'NT Authority\System','us_english'
exec sp_addsrvrolemember N'NT Authority\System', sysadmin
Additionally, but not necessarily related to the error in the subject line,
has this server ever been upgrade from SQL Server 7.0 or is this SQL Server
2000 a "named instance" with a default installation of SQL Server 7.0? As
this might be related to a post-SP3 bug. See KB 814035 (Q814035) FIX: A
Full-Text Population Fails After You Apply SQL Server 2000 Service Pack 3
at:
http://support.microsoft.com/default...b;en-us;814035 (80004002 -
No such interface supported)
Regards,
John
"Oz" <Oz(no_spam)@.nospam.com> wrote in message
news:eytulHGNEHA.2468@.TK2MSFTNGP11.phx.gbl...
> Hi,
> We have SQL Server private installation on which we are developing an
> application and public installation on whict we will be deploying the
> application. All instances have run Windows 2003 Enterprise Edition with
SQL
> 2000 SP3. However, the public installation MS Search is not functioning
> correctly. Basically it will not full-text indeed databases and produces
> the following error
> 1> exec sp_fulltext_database 'enable'
> 2> go
> (1 row affected)
> Msg 7635, Level 16, State 1, Server SIMP001, Procedure
sp_fulltext_database,
> Lin
> e 46
> The Microsoft Search service cannot be administered under the present user
> account
> Now, we have tried many things to try and solve this error, mainly based
on
> search newsgroups, which are itemized below:
> 1 Reboot System and reexecute sp_
> 2 Complete reinstall of SQL on system, then reapplication of SP3
> 3 Same as above (2) but reapply SP3a
> 4 Remove SQL Server installation subkey in order that can reinstall
> full-text search only, then reapply SP3
> 5 Check from keys under
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\A pplications\ to make
sure
> SQL Server was there. It wasn't, removed SQL subkey and reinstalled,
> re-adding full-text search as an option (to re-install full-text) then
> reapplied SP3
> 6 Try reinstall, but do not reapply SP3 until have full-text enabled the
> database.
> None of the above worked. We still have a none functioning mssearch and
> full-text disabled database on the system.
> We have even tried enabling on a blank database. This does not work
either.
> PLEASE HELP! Getting desperate as the whole application depends on having
> search ability.
> Thanks
> Oz
>
|||Hi John,
Thanks for replying to my message. Unfortunately i forgot to add these items
as items i had also tried.
- Have not modified Administrator account, but i ran the SQL script anyway.
- MS Search has always been running as local system
- Changed the security settings using Ent Mgr to Local System and back again
to the user account.
- SQL account is not a local administrator. Tried adding it Administrators,
still, no joy.
Thanks
O
"John Kane" <jt-kane@.comcast.net> wrote in message
news:eaSiYlKNEHA.2976@.TK2MSFTNGP10.phx.gbl...
> Oz,
> In addition to the many things you tried below... a couple of things
> specific to MSSearch and the MSSQLServer services...
> 1. Is the MSSearch service started and running under the System
> (LocalSystem) account? If not, then change it to LocalSystem and stop and
> re-start this service.
> 2. Have you or anyone else change the MSSQLServer account &/or password
via
> Win2K's Component service? IF so, then you MUST re-change the change via
the
> Enterprise Manager's server property security tab as this is the only
place
> where the two services security are kept in sync. See KB article 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...B;EN-US;277549
> 3. Have you or anyone else removed or modified the BUILTIN\Administrator
> login on this server? If so, you MUST either re-add it with all of it's
> normal default rights, especially sysadmin rights and with the default
> database as master and the default language of English or use the
following
> T-SQL code to add the correct permissions:
> exec sp_grantlogin N'NT Authority\System'
> exec sp_defaultdb N'NT Authority\System', N'master'
> exec sp_defaultlanguage N'NT Authority\System','us_english'
> exec sp_addsrvrolemember N'NT Authority\System', sysadmin
> Additionally, but not necessarily related to the error in the subject
line,
> has this server ever been upgrade from SQL Server 7.0 or is this SQL
Server[vbcol=seagreen]
> 2000 a "named instance" with a default installation of SQL Server 7.0? As
> this might be related to a post-SP3 bug. See KB 814035 (Q814035) FIX: A
> Full-Text Population Fails After You Apply SQL Server 2000 Service Pack 3
> at:
> http://support.microsoft.com/default...b;en-us;814035 (80004002 -
> No such interface supported)
> Regards,
> John
>
> "Oz" <Oz(no_spam)@.nospam.com> wrote in message
> news:eytulHGNEHA.2468@.TK2MSFTNGP11.phx.gbl...
> SQL
produces[vbcol=seagreen]
> sp_fulltext_database,
user[vbcol=seagreen]
> on
> sure
> either.
having
>
|||John
Is there a log file somewhere that i could try and see what precisely is
causing this problem.
Thanks
"John Kane" <jt-kane@.comcast.net> wrote in message
news:eaSiYlKNEHA.2976@.TK2MSFTNGP10.phx.gbl...
> Oz,
> In addition to the many things you tried below... a couple of things
> specific to MSSearch and the MSSQLServer services...
> 1. Is the MSSearch service started and running under the System
> (LocalSystem) account? If not, then change it to LocalSystem and stop and
> re-start this service.
> 2. Have you or anyone else change the MSSQLServer account &/or password
via
> Win2K's Component service? IF so, then you MUST re-change the change via
the
> Enterprise Manager's server property security tab as this is the only
place
> where the two services security are kept in sync. See KB article 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...B;EN-US;277549
> 3. Have you or anyone else removed or modified the BUILTIN\Administrator
> login on this server? If so, you MUST either re-add it with all of it's
> normal default rights, especially sysadmin rights and with the default
> database as master and the default language of English or use the
following
> T-SQL code to add the correct permissions:
> exec sp_grantlogin N'NT Authority\System'
> exec sp_defaultdb N'NT Authority\System', N'master'
> exec sp_defaultlanguage N'NT Authority\System','us_english'
> exec sp_addsrvrolemember N'NT Authority\System', sysadmin
> Additionally, but not necessarily related to the error in the subject
line,
> has this server ever been upgrade from SQL Server 7.0 or is this SQL
Server[vbcol=seagreen]
> 2000 a "named instance" with a default installation of SQL Server 7.0? As
> this might be related to a post-SP3 bug. See KB 814035 (Q814035) FIX: A
> Full-Text Population Fails After You Apply SQL Server 2000 Service Pack 3
> at:
> http://support.microsoft.com/default...b;en-us;814035 (80004002 -
> No such interface supported)
> Regards,
> John
>
> "Oz" <Oz(no_spam)@.nospam.com> wrote in message
> news:eytulHGNEHA.2468@.TK2MSFTNGP11.phx.gbl...
> SQL
produces[vbcol=seagreen]
> sp_fulltext_database,
user[vbcol=seagreen]
> on
> sure
> either.
having
>
|||You're welcome, Oz,
Yes, there are MSSearch gatherer log files located under
\FTDATA\SQLServer\GatherLogs\ that can be "read" using gthrlog.vbs, however,
they most likely will have the same error (MSSearch service cannot be
admin..), so they are of little value in this issue.
Is this SQL Server installed on a Domain Controller (DC) server or is the
MSSQLServer startup account the DOMAIN\Administrator account?
While this should work, it's been my experience that with Full-Text Search
(FTS) on DC's that this is a problem for the "Microsoft Search" (MSSearch)
service. If you are using the DOMAIN\Administrator account, create a local
machine account and add this account into the DC's Administrator Group and
then change the MSSQLServer startup account in the Enterprise Manager (this
change MUST be done here) server's security tab. This should stop and
restart SQL Server and if all is successfully completed, FTS on a DC
*should* work...
Regards,
John
"Oz" <Oz(no_spam)@.nospam.com> wrote in message
news:OqqhS1ONEHA.3348@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> John
> Is there a log file somewhere that i could try and see what precisely is
> causing this problem.
> Thanks
> "John Kane" <jt-kane@.comcast.net> wrote in message
> news:eaSiYlKNEHA.2976@.TK2MSFTNGP10.phx.gbl...
and[vbcol=seagreen]
> via
> the
> place
> Component
> http://support.microsoft.com/default...B;EN-US;277549
BUILTIN\Administrator[vbcol=seagreen]
> following
> line,
> Server
As[vbcol=seagreen]
3[vbcol=seagreen]
(80004002 -[vbcol=seagreen]
with[vbcol=seagreen]
functioning[vbcol=seagreen]
> produces
> user
based[vbcol=seagreen]
the[vbcol=seagreen]
and
> having
>
|||Hi John,
Yes, it is running on a DC. I will try your suggestions and see if it makes
any difference.
Thanks
Oz
"John Kane" <jt-kane@.comcast.net> wrote in message
news:OeY1j4QNEHA.2144@.TK2MSFTNGP10.phx.gbl...
> You're welcome, Oz,
> Yes, there are MSSearch gatherer log files located under
> \FTDATA\SQLServer\GatherLogs\ that can be "read" using gthrlog.vbs,
however,
> they most likely will have the same error (MSSearch service cannot be
> admin..), so they are of little value in this issue.
> Is this SQL Server installed on a Domain Controller (DC) server or is the
> MSSQLServer startup account the DOMAIN\Administrator account?
> While this should work, it's been my experience that with Full-Text Search
> (FTS) on DC's that this is a problem for the "Microsoft Search" (MSSearch)
> service. If you are using the DOMAIN\Administrator account, create a local
> machine account and add this account into the DC's Administrator Group and
> then change the MSSQLServer startup account in the Enterprise Manager
(this[vbcol=seagreen]
> change MUST be done here) server's security tab. This should stop and
> restart SQL Server and if all is successfully completed, FTS on a DC
> *should* work...
> Regards,
> John
>
> "Oz" <Oz(no_spam)@.nospam.com> wrote in message
> news:OqqhS1ONEHA.3348@.TK2MSFTNGP09.phx.gbl...
> and
password[vbcol=seagreen]
via[vbcol=seagreen]
277549[vbcol=seagreen]
> BUILTIN\Administrator
it's[vbcol=seagreen]
> As
A[vbcol=seagreen]
Pack[vbcol=seagreen]
> 3
> (80004002 -
an[vbcol=seagreen]
the[vbcol=seagreen]
> with
> functioning
present[vbcol=seagreen]
> based
make[vbcol=seagreen]
then
> the
> and
>
|||Hi John,
It's just occurred, to me, there is nothing in those directories as i cannot
enable the database for full-text!
"John Kane" <jt-kane@.comcast.net> wrote in message
news:OeY1j4QNEHA.2144@.TK2MSFTNGP10.phx.gbl...
> You're welcome, Oz,
> Yes, there are MSSearch gatherer log files located under
> \FTDATA\SQLServer\GatherLogs\ that can be "read" using gthrlog.vbs,
however,
> they most likely will have the same error (MSSearch service cannot be
> admin..), so they are of little value in this issue.
> Is this SQL Server installed on a Domain Controller (DC) server or is the
> MSSQLServer startup account the DOMAIN\Administrator account?
> While this should work, it's been my experience that with Full-Text Search
> (FTS) on DC's that this is a problem for the "Microsoft Search" (MSSearch)
> service. If you are using the DOMAIN\Administrator account, create a local
> machine account and add this account into the DC's Administrator Group and
> then change the MSSQLServer startup account in the Enterprise Manager
(this[vbcol=seagreen]
> change MUST be done here) server's security tab. This should stop and
> restart SQL Server and if all is successfully completed, FTS on a DC
> *should* work...
> Regards,
> John
>
> "Oz" <Oz(no_spam)@.nospam.com> wrote in message
> news:OqqhS1ONEHA.3348@.TK2MSFTNGP09.phx.gbl...
> and
password[vbcol=seagreen]
via[vbcol=seagreen]
277549[vbcol=seagreen]
> BUILTIN\Administrator
it's[vbcol=seagreen]
> As
A[vbcol=seagreen]
Pack[vbcol=seagreen]
> 3
> (80004002 -
an[vbcol=seagreen]
the[vbcol=seagreen]
> with
> functioning
present[vbcol=seagreen]
> based
make[vbcol=seagreen]
then
> the
> and
>
|||Also John,
I have always been running a local (i.e. Domain user) account as the SQL
account, althought it is not a member of the administrators group. This is
one of the things i tried (adding it to the admins group), but didn't help.
Thanks
"John Kane" <jt-kane@.comcast.net> wrote in message
news:OeY1j4QNEHA.2144@.TK2MSFTNGP10.phx.gbl...
> You're welcome, Oz,
> Yes, there are MSSearch gatherer log files located under
> \FTDATA\SQLServer\GatherLogs\ that can be "read" using gthrlog.vbs,
however,
> they most likely will have the same error (MSSearch service cannot be
> admin..), so they are of little value in this issue.
> Is this SQL Server installed on a Domain Controller (DC) server or is the
> MSSQLServer startup account the DOMAIN\Administrator account?
> While this should work, it's been my experience that with Full-Text Search
> (FTS) on DC's that this is a problem for the "Microsoft Search" (MSSearch)
> service. If you are using the DOMAIN\Administrator account, create a local
> machine account and add this account into the DC's Administrator Group and
> then change the MSSQLServer startup account in the Enterprise Manager
(this[vbcol=seagreen]
> change MUST be done here) server's security tab. This should stop and
> restart SQL Server and if all is successfully completed, FTS on a DC
> *should* work...
> Regards,
> John
>
> "Oz" <Oz(no_spam)@.nospam.com> wrote in message
> news:OqqhS1ONEHA.3348@.TK2MSFTNGP09.phx.gbl...
> and
password[vbcol=seagreen]
via[vbcol=seagreen]
277549[vbcol=seagreen]
> BUILTIN\Administrator
it's[vbcol=seagreen]
> As
A[vbcol=seagreen]
Pack[vbcol=seagreen]
> 3
> (80004002 -
an[vbcol=seagreen]
the[vbcol=seagreen]
> with
> functioning
present[vbcol=seagreen]
> based
make[vbcol=seagreen]
then
> the
> and
>
|||You're welcome, Oz,
When you said "It's just occurred, to me, there is nothing in those
directories as i cannot enable the database for full-text!"
What directories were you referring to?
Could you change the MSSQLServer service startup account to the system
account (LocalSystem) via the Enterprise Manager's server property security
tab? This should stop and restart SQL Server and attempt to FT-enable the
Pubs database and the authors table and let me know the result of the that?
Thanks,
John
"Oz" <Oz(no_spam)@.nospam.com> wrote in message
news:usHda6lNEHA.3944@.tk2msftngp13.phx.gbl...
> Also John,
> I have always been running a local (i.e. Domain user) account as the SQL
> account, althought it is not a member of the administrators group. This
is
> one of the things i tried (adding it to the admins group), but didn't
help.[vbcol=seagreen]
> Thanks
> "John Kane" <jt-kane@.comcast.net> wrote in message
> news:OeY1j4QNEHA.2144@.TK2MSFTNGP10.phx.gbl...
> however,
the[vbcol=seagreen]
Search[vbcol=seagreen]
(MSSearch)[vbcol=seagreen]
local[vbcol=seagreen]
and[vbcol=seagreen]
> (this
is[vbcol=seagreen]
stop[vbcol=seagreen]
> password
> via
only[vbcol=seagreen]
> 277549
> it's
default[vbcol=seagreen]
subject[vbcol=seagreen]
7.0?[vbcol=seagreen]
FIX:[vbcol=seagreen]
> A
> Pack
> an
> the
Edition[vbcol=seagreen]
> present
reinstall[vbcol=seagreen]
> make
reinstalled,[vbcol=seagreen]
> then
enabled[vbcol=seagreen]
mssearch[vbcol=seagreen]
work
>