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

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Oz (Oz(no_spam)_at_nospam.com)
Date: 05/17/04 

Date: Mon, 17 May 2004 10:43:40 +0300

Hi John,

Well, in case anyone searching this group has a similar problem, it may have
been drastic, but i finally got FullText to work properly.

Check out this MS Article:

http://support.microsoft.com/?kbid=827449

Thanks for ALL your help John. You really hung in their with me.

Cheers

Oz

"John Kane" <jt-kane@comcast.net> wrote in message
news:#tRBGI2NEHA.3016@tk2msftngp13.phx.gbl...
> Oz,
> This seems to be an installation gone really bad... Below are the
> instructions, I've posted in this newsgroup that has been very successful
in
> resolving a number of SQL FTS related issues. However, with the new error
> (The parameter is incorrect), this re-installation may or may NOT be
> successful and you may have to remove SQL Server and the MSSearch
components
> and re-install SQL Server again.
>
> Re-install" the "Full-text Search" components via deleting (or renaming)
the
> below "tracking key" and re-install (If you're not using a named instance,
> remove "<Instance_Name>\".)
>
> NOTE: be sure to be logged on to the server as either Administrator or as
a
> member of the server's Admin Group!
>
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
> Server\<Instance_Name>\Tracking\
> {E07FDDA7-5A21-11d2-9DAD-00C04F79D434}
>
> Once you've done removed (renamed) the above tracking key, then delete the
> MSSearch directory from either:
>
> drive_letter:\Program Files\Common Files\Microsoft Shared\
> or
> drive_letter::\Program Files\Common Files\System\
>
> Then using your SQL Server 2000 installation CD re-install via "Custom
> Installation" the Full-Text Search component (it should be un-checked).
When
> this completes find and save these files: SearchSetup.log (usually under
> \windows or \winnt folders) and sqlsp.log. If any problems, please post
> these files.
>
> Re-install SQL Server 2000 Service pack (SP3) if this service has been
> applied, so that the newly installed MSSearch components are upgraded to
> SP3a levels and then re-boot &/or restart the MSSearch and MSSQLServer
> services.
>
> Note, if the method above fails (and there are other methods) you might
need
> to open a support case with Microsoft PSS SQL Server Support...
>
> Regards,
> John
>
>
>
> "Oz" <Oz(no_spam)@nospam.com> wrote in message
> news:O6wrjyxNEHA.3816@TK2MSFTNGP12.phx.gbl...
> > John,
> >
> > I did that and therefore reinstalled full-text. Actually i have done
this
> > before, but it's worth walking through it again with you as you may see
> > something i don't. I have not yet applied SP3 to the new full-text
> > installation. However, what i get now is another error.
> >
> > 'Execution of full-text operation failed. The parameter is incorrect'
> >
> > I have also manually tried running
> > sp_fulltext_database 'enable'
> >
> > and that is the same error generated.
> >
> > I used to FT wizard to try and create the FT index.
> >
> > Do you see anything here?
> >
> > Thanks
> >
> > "John Kane" <jt-kane@comcast.net> wrote in message
> > news:u1HdIRwNEHA.892@TK2MSFTNGP09.phx.gbl...
> > > Oz,
> > > When you say that the FTData directory was empty, do you mean NO
files,
> or
> > > just no gatherer log files?
> > > If the former, then this is a problem as the \FTDATA directory should
> look
> > > something like this (edited):
> > >
> > > Directory of F:\MSSQL80\MSSQL\FTDATA
> > >
> > > 05/14/2003 12:45 PM <DIR> .
> > > 05/14/2003 12:45 PM <DIR> ..
> > > 12/06/2003 07:21 PM <DIR> SQL0000500005 -- FT Catalog
> folder
> > > 05/14/2003 12:45 PM <DIR> SQLServer
> > > 0 File(s) 0 bytes
> > >
> > > Directory of F:\MSSQL80\MSSQL\FTDATA\SQL0000500005
> > >
> > > Directory of F:\MSSQL80\MSSQL\FTDATA\SQLServer
> > >
> > > 05/14/2003 12:45 PM <DIR> .
> > > 05/14/2003 12:45 PM <DIR> ..
> > > 05/14/2003 12:45 PM <DIR> Config
> > > 05/10/2004 03:30 AM <DIR> GatherLogs
> > > 05/14/2003 12:45 PM <DIR> Projects
> > > 0 File(s) 0 bytes
> > >
> > > Directory of F:\MSSQL80\MSSQL\FTDATA\SQLServer\Config
> > >
> > > 05/14/2003 12:45 PM <DIR> .
> > > 05/14/2003 12:45 PM <DIR> ..
> > > 05/14/2003 12:45 PM 1,771 Gathrprm.Txt
> > > 06/16/2000 11:30 PM 1,696 noise.chs
> > > 06/16/2000 11:30 PM 1,696 noise.cht
> > > 06/16/2000 11:30 PM 687 noise.dat
> > > 06/16/2000 11:30 PM 149,848 noise.deu
> > > 06/16/2000 11:30 PM 697 noise.eng
> > > 06/16/2000 11:30 PM 697 noise.enu
> > > 06/16/2000 11:30 PM 19,684 noise.esn
> > > 06/16/2000 11:30 PM 49,196 noise.fra
> > > 06/16/2000 11:30 PM 19,616 noise.ita
> > > 06/16/2000 11:30 PM 10,724 noise.jpn
> > > 06/16/2000 11:30 PM 697 noise.kor
> > > 06/16/2000 11:30 PM 13,256 noise.nld
> > > 06/16/2000 11:30 PM 13,728 noise.sve
> > > 04/28/2000 12:06 AM 4,576 Schema.Txt
> > > 05/05/2000 04:35 PM 536 tschs.xml
> > > 05/05/2000 04:35 PM 536 tscht.xml
> > > 05/05/2000 04:35 PM 536 tsdut.xml
> > > 05/05/2000 04:35 PM 536 tseng.xml
> > > 05/05/2000 04:35 PM 536 tsenu.xml
> > > 05/05/2000 04:35 PM 536 tsfra.xml
> > > 05/05/2000 04:35 PM 536 tsger.xml
> > > 05/05/2000 04:35 PM 536 tsita.xml
> > > 05/05/2000 04:35 PM 536 tsjap.xml
> > > 05/05/2000 04:35 PM 536 tskor.xml
> > > 05/05/2000 04:35 PM 536 tsneu.xml
> > > 05/05/2000 04:35 PM 810 tsschema.xml
> > > 05/05/2000 04:35 PM 536 tsspa.xml
> > > 05/05/2000 04:35 PM 536 tsswe.xml
> > > 29 File(s) 296,347 bytes
> > >
> > > Directory of F:\MSSQL80\MSSQL\FTDATA\SQLServer\GatherLogs
> > >
> > > 05/10/2004 03:30 AM <DIR> .
> > > 05/10/2004 03:30 AM <DIR> ..
> > > 05/06/2004 04:06 AM 66 SQL0000500005.142.gthr
> > > 05/08/2004 03:30 AM 66 SQL0000500005.143.gthr
> > > 05/08/2004 06:27 PM 264 SQL0000500005.144.gthr
> > > 05/09/2004 04:04 AM 66 SQL0000500005.145.gthr
> > > 05/10/2004 03:30 AM 66 SQL0000500005.146.gthr
> > > 05/06/2004 04:06 AM 66 SQL0000600005.101.gthr
> > > 05/07/2004 03:32 AM 66 SQL0000600005.102.gthr
> > > 05/08/2004 06:27 PM 264 SQL0000600005.103.gthr
> > > 05/09/2004 04:04 AM 66 SQL0000600005.104.gthr
> > > 05/10/2004 03:30 AM 66 SQL0000600005.105.gthr
> > > 10 File(s) 1,056 bytes
> > >
> > >
> > > While you may not have files in the GatherLog dir, you MUST have the
> above
> > > files in the \FTDATA\SQLServer\Config.
> > > If not, then this *might* be the source of this issue.
> > >
> > > Regards,
> > > John
> > >
> > >
> > >
> > >
> > > "Oz" <Oz(no_spam)@nospam.com> wrote in message
> > > news:eTADCIrNEHA.3988@TK2MSFTNGP09.phx.gbl...
> > > > Ok,
> > > >
> > > > Will do.
> > > >
> > > > I'm talking about the FTData directory. It was there, but it was
> blank.
> > > So
> > > > i couldn't check for gatherer files etc.
> > > >
> > > > Thanks
> > > > "John Kane" <jt-kane@comcast.net> wrote in message
> > > > news:uBU3C6pNEHA.1340@TK2MSFTNGP12.phx.gbl...
> > > > > 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.
> > > > > >
> > > > > > 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
> > > > > > > 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...
> > > > > > > > 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.aspx?scid=KB;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.aspx?scid=kb;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\Applications\
> > > > 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
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Relevant Pages