Re: I can't seem to access my fulltext data

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Its difficult to assess what the problem could be. Could you check the event
log from messages coming from MSSearch or MSSCi? This might refer to your
gatherer logs, which can be accessed by using the gthrlog.vbs utility.
go to c:\program files\Common files\system\mssearch\bin, copy the
gthrlog.vbs to c:\winnt\system32 directory or add the above path to your
path (control panel - system - Environment - user and in the path variable
append the above path in the path value (separate it from the entry before
with a ;).
Click on set, apply and OK. Run path from the command prompt to ensure you
did this correctly. You may have to close down all dos boxes to get this to
update
correctly, if not a log off log on normally works.
Now navigate to your gather log location. On my machine it is at C:\Program
Files\Microsoft SQL Server\MSSQL\FTDATA\SQLServer\­GatherLogs
then type cscript.vbs gthrlog SQL0000600006.7.gthr or whatever you find
there. these logs have time stamps on them, look for a date relevant one
to examine.

The most common reason for such a failure is the the SQL Server Service
account was changed through control panel as opposed to through EM. Refer to
this kb article for more information.

http://support.microsoft.com/default.aspx?scid=kb;en-us;295034

http://support.microsoft.com/default.aspx?scid=kb;en-us;317746

http://support.microsoft.com/default.aspx?scid=kb;en-us;295772



--
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

"dkoz" <dkoz@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D0FA563F-B9B0-4ABF-887B-DEA64EE7DDE9@xxxxxxxxxxxxxxxx
> Hilary,
> I have had a similiar issue; I cannot read any of my data from a simple
> query or returning all rows from SQL. I tried to reinstal my *.dll files
for
> MSSearch, to no avail.
> I am running Server 2003, SQL 2000 sp3.
> Any help would be appreciated.
> Derek
>
> "Hilary Cotter" wrote:
>
> > Its hard to say - their may have been some catalog corruption, but there
> > should have been error messages logged in the event log, or in the
gatherer
> > logs.
> >
> > --
> > 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
> >
> > "tshad" <tscheiderich@xxxxxxxxxxxxxxx> wrote in message
> > news:e26H3zMMFHA.3760@xxxxxxxxxxxxxxxxxxxxxxx
> > >
> > > "Hilary Cotter" <hilary.cotter@xxxxxxxxx> wrote in message
> > > news:uiDrhnMMFHA.4044@xxxxxxxxxxxxxxxxxxxxxxx
> > > > Possibly, can you try to run a full population.
> > >
> > > I did try the full population, but that didn't seem to help. But when
I
> > did
> > > a rebuild catalog and then full population it worked fine.
> > >
> > > Why would it do that and how would I get around that?
> > >
> > > I can't have people trying to use our site and finding that their
searches
> > > won't work.
> > >
> > > Thanks,
> > >
> > > Tom
> > > >
> > > > Btw its cscript gthrlog SQL0000600006.7.gthr
> > > >
> > > > My mistake
> > > >
> > > >
> > > > "tshad" <tscheiderich@xxxxxxxxxxxxxxx> wrote in message
> > > > news:e$rh5NMMFHA.3960@xxxxxxxxxxxxxxxxxxxxxxx
> > > >>> Can you check for any messages in the event log from MSSearch or
> > MSSCI?
> > > >>>
> > > >>> You might also want to use the gthrlog.vbs to examine your
gatherer
> > logs
> > > >>> for
> > > >>> this catalog.
> > > >>> Go to c:\program files\Common files\system\mssearch\bin copy the
> > > >>> gthrlog.vbs
> > > >>> to c:\winnt\system32 directory or add the above path to your
> > > >>> path (control panel - system - Environment - user and in the path
> > > >>> variable
> > > >>> append the above path in the path value (separate it from the
entry
> > > >>> before
> > > >>> with a ;).
> > > >>> Click on set, apply and OK. Run path from the command prompt to
ensure
> > > >>> you
> > > >>> did this correctly. You may have to close down all dos boxes to
get
> > > >>> this to
> > > >>> update
> > > >>> correctly, if not a log off log on normally works.
> > > >>> Now navigate to your gather log location. On my machine it is at
> > > >>>
> > > >>>
> > > >>> C:\Program Files\Microsoft SQL
> > > >>> Server\MSSQL\FTDATA\SQLServer\­GatherLogs>
> > > >>>
> > > >>>
> > > >>> then type cscript.vbs gthrlog SQL0000600006.7.gthr or whatever you
> > find
> > > >>> there.
> > > >>> these logs have time stamps on them, look for a date relevant one
to
> > > >>> examine.
> > > >>
> > > >> We don't have cscript.vbs on our server which is a "Windows 2003
> > Server".
> > > >>
> > > >> But the date of the only file in the GatherLogs folder is 3/15/05
and
> > > >> this happened today.
> > > >>
> > > >> There is no entry in the Event log or the Sql Server Logs about
this
> > > >> either - the last entry was 2:00 am this morning for our backups.
> > > >>
> > > >> However, I did look at the FullTextCatalogs in the Databases folder
on
> > EM
> > > >> and saw that the JobDescriptions Catalog is idle. Is this normal?
> > > >>
> > > >> Thanks,
> > > >>
> > > >> Tom
> > > >>>
> > > >>>
> > > >>>
> > > >>> --
> > > >>> 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
> > > >>>
> > > >>> "tshad" <tscheiderich@xxxxxxxxxxxxxxx> wrote in message
> > > >>> news:eeSITHLMFHA.3016@xxxxxxxxxxxxxxxxxxxxxxx
> > > >>>> I am running on Sql Server 2000.
> > > >>>>
> > > >>>> This was set up a couple of weeks ago and ran fine. I came in
today
> > > >>>> and
> > > >>> was
> > > >>>> looking at some of my asp.net pages and started to get the error:
> > > >>>>
> > > >>>> Execution of a full-text operation failed. The catalog does not
exist
> > > >>>> or
> > > >>> is
> > > >>>> currently unavailable
> > > >>>>
> > > >>>> I tried just a simple query:
> > > >>>>
> > > >>>> select * from position where Contains(jobDescription,'sales')
> > > >>>>
> > > >>>> and got the same error.
> > > >>>>
> > > >>>> What causes the problem? When I right-click on the table and go
the
> > > >>>> fulltext menu and wizard, it says it is already set up for
FullText
> > > >>>> indexing.
> > > >>>>
> > > >>>> Thanks,
> > > >>>>
> > > >>>> Tom
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>
> > > >>>
> > > >>
> > > >>
> > > >
> > > >
> > >
> > >
> >
> >
> >


.



Relevant Pages

  • Re: fulltext search not working
    ... MSSearch service components or registry key &/or values at the server level ... with Microsoft SQL Server support. ... > the FTS component as the server is a production database and is hosted on ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Cascade update to two fields in a table...
    ... Both of these refer to UserName in tblUsers. ... you cannot set up cascading foreing keys, ... The SQL Server developers ...
    (comp.databases.ms-sqlserver)
  • Re: High CPU over extended time period
    ... What is the exact version of SQL Server that you are using? ... Pack level to get a fix for a possible known bug related to MSSearch & ... "Microsoft Search" and MssCi source events. ... > The CPU usage does not drop it stack on 100%. ...
    (microsoft.public.sqlserver.fulltext)
  • RE: Cannot generate SSPI context
    ... Let us refer to the following steps to troubleshoot the issue: ... How to troubleshoot the "Cannot generate SSPI context" error message ... How to use Kerberos authentication in SQL Server ... from your newsreader: microsoft.private.directaccess.partnerfeedback. ...
    (microsoft.public.windows.server.sbs)
  • Re: Microsoft Search service cannot be administered under the present user error SP3
    ... Is the MSSearch service started and running under the System ... Have you or anyone else change the MSSQLServer account &/or password via ... database as master and the default language of English or use the following ... has this server ever been upgrade from SQL Server 7.0 or is this SQL Server ...
    (microsoft.public.sqlserver.fulltext)