Re: Error 7619 - Cannot enable FTS on any database
From: Mark \(DT\) (mark_at_demontools.net)
Date: 08/11/04
- Next message: John Kane: "Re: Error when starting Incremental Population"
- Previous message: Paul Bell: "RE: Error when starting Incremental Population"
- In reply to: John Kane: "Re: Error 7619 - Cannot enable FTS on any database"
- Next in thread: John Kane: "Re: Error 7619 - Cannot enable FTS on any database"
- Reply: John Kane: "Re: Error 7619 - Cannot enable FTS on any database"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 11 Aug 2004 03:41:13 +0100
Hi John,
Thanks for the help. I worked through these instructions, however there's
definitely something odd going on with this server:
Even after having stopped the Microsoft Search, SQL Server and SQL Agent
services, set them to Manual and rebooted, I still can't delete the MSSearch
folder - I get the error "the directory is not empty", even when it is;
however the reinstall of the Full Text components from the CD replaced the
files in these folders;
After reinstalling Full Text the error "The server threw an exception."
remains trying to enable Full Text.
Having checked just to see, I then went to install SP3a. I double clicked
the icon to launch the extractor and allows it to re-extract to the default
directory, forgetting that this previously existed - it overwrote the files
fine until it got to MSSearch.exe then prompted "Cannot find the file or
directory", then continued to write all the other files and completed.
I ran the extract again specifying a new folder, which it created. The same
error appeared when it got to mssearch.exe.
I then tried deleting the folder just created above, since it was not
needed. The delete then failed on the folder "search" - "the directory is
not empty", even when it is. It still fails after a reboot.
There seems to be some strange permission issue on this server that only
affects folders related to Full Text Searching, wherever they are as any
folder containing these files can't be deleted, and so I can't install SP3a.
Is there any clue in this that someone could shed light on, I am mystified
:-)
Thanks,
Mark
"John Kane" <jt-kane@comcast.net> wrote in message
news:eWdLcicfEHA.236@tk2msftngp13.phx.gbl...
> You're welcome, Mark,
> The hex code 0x80070005 translates to "Access is denied". Were you
directly
> logged on as Admin or as a member of the Admin Group on the server where
SQL
> Server is installed? If not, re-try deleting the \MSSearch folder again
and
> if so, then try re-booting the server with the "Microsoft Search" service
> set to startup as either manual or disenabled. Since, the procedures in KB
> 827449 article failed to resolve this, try the below steps as well
>
> 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 as in
removing
> SQL Server & re-installing it) you might need to open a support case with
> Microsoft PSS SQL Server Support...
>
> Regards,
> John
>
>
>
>
>
> "Mark (DT)" <mark@demontools.net> wrote in message
> news:4116d1a9$0$29940$cc9e4d1f@news.dial.pipex.com...
> > Hi John,
> >
> > Many thanks for your help.
> >
> > I followed these instructions - the error message when trying to enable
> Full
> > Text Searching is different now:
> >
> > (1 row(s) affected)
> >
> > Server: Msg 7619, Level 16, State 1, Procedure sp_fulltext_database,
Line
> 46
> > Execution of a full-text operation failed. The server threw an
exception.
> >
> > In the MyFTSetup logfile, there is this error:
> >
> > FulltextSetup returned error code: 0x80070005
> >
> > The only thing I wasn't able to do was to actually delete the MSSearch
> > folder. This is because the subdirectory Bin would not delete, due to
the
> > error "the directory is not empty". View Hidden Files and Folders is on,
> > Show System Files is on, and even at the command prompt the directory
> really
> > is empty. I've checked the permissions on the folder and all is fine,
but
> > even after a reboot with SQL Server and SQL Agent stopped (and the MS
> Search
> > service removed) the folder could not be deleted. I'm not sure if this
is
> a
> > clue.
> >
> > The MS Search service is back up and running, registry keys are back in
> > place, and the contents of the MSSearch folder are back as they were
> before,
> > so the install went over the top of the existing empty folders.
> >
> > The MS Search install seemed to go fine - it's the part that makes SQL
> > Server aware of the installed service (the FTSetup log file) which threw
> the
> > error.
> >
> > There are no errors in the Event log at all.
> >
> > Any ideas?
> >
> > Thanks,
> > Mark
> >
> >
> >
> > "John Kane" <jt-kane@comcast.net> wrote in message
> > news:OevCW%231eEHA.1048@tk2msftngp13.phx.gbl...
> > > Mark,
> > > Due to the fact that both the OS and SQL Server 2000 was re-installed
on
> > > this server as well as the Error Msg 7619 and specifically the message
> > text
> > > " An unexpected error occurred", I'd recommend that you remove the
> > existing
> > > SQL and MSSearch FT Search components via 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.aspx?scid=kb;EN-US;827449
> > >
> > > If the above procedures do not work successfully, please post any
> > additional
> > > errors message text from SQL Server as well as from your server's
> > > Application event log source events "Microsoft Search" and MssCi.
> > >
> > > Regards,
> > > John
> > >
> > >
> > >
> > > "Mark (DT)" <mark@demontools.net> wrote in message
> > > news:4112d864$0$2279$cc9e4d1f@news.dial.pipex.com...
> > > > Hi,
> > > >
> > > > I'm hoping someone might be able to help with a problem we're having
> > with
> > > > SQL Server:
> > > >
> > > > A couple of months ago our server had to be rebuilt after installing
> > some
> > > > hotfixes from Windows Update; the server hung on shut down, was
reset,
> > and
> > > > didn't come back up again.
> > > >
> > > > The OS was reinstalled as was SQL Server. After reinstalling SQL
> Server
> > > the
> > > > databases were recreated and reattached.
> > > >
> > > > One of the databases had and still has a full text catalog which
used
> to
> > > > work fine. However since around the time of the rebuild (can't be
sure
> > > it's
> > > > directly related) no database can be enabled for Full Text search.
> > > >
> > > > If I run (on any database):
> > > >
> > > > sp_fulltext_database enable
> > > >
> > > > I receive:
> > > >
> > > > (1 row(s) affected)
> > > > Server: Msg 7619, Level 16, State 1, Procedure sp_fulltext_database,
> > Line
> > > 46
> > > > Execution of a full-text operation failed. An unexpected error
> occurred.
> > > >
> > > > The only cause I have been able to find for a similar issue is
related
> > to
> > > > changing the account that either the Microsoft Search service or SQL
> > > Server
> > > > run in. However this has not been done; both run under the Local
> System
> > > > account.
> > > >
> > > > The current situation is that I have a database with a catalog that
> > can't
> > > be
> > > > dropped because full text is not enabled. However full text search
> > cannot
> > > be
> > > > enabled on this or any database, whether a pre-existing or a new
one.
> > > >
> > > > The Microsoft Search service is running fine. The FTS icon in
> Enterprise
> > > > Manager is green and properties can be viewed OK. I have checked the
> > > > permissions on the FT folders and SYSTEM has full control.
> > > >
> > > > Short of a full rebuild both the server Company (data centre) who
> > provide
> > > > our servers and us are completely stumped.
> > > >
> > > > Can anyone suggest a solution or anything to check or try? (Win 2k,
> SQL
> > > 2000
> > > > SP3)
> > > >
> > > > Many thanks,
> > > > Mark
> > > >
> > > >
> > >
> > >
> >
> >
>
>
- Next message: John Kane: "Re: Error when starting Incremental Population"
- Previous message: Paul Bell: "RE: Error when starting Incremental Population"
- In reply to: John Kane: "Re: Error 7619 - Cannot enable FTS on any database"
- Next in thread: John Kane: "Re: Error 7619 - Cannot enable FTS on any database"
- Reply: John Kane: "Re: Error 7619 - Cannot enable FTS on any database"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
