Mombu the Microsoft Forum

Go Back   Mombu the Microsoft Forum > Microsoft > MS Search Service on Act/Act Sql 2k SP3 Cluster Failing
User Name
Password
REGISTER NOW! Mark Forums Read




Reply
 
1 6th September 06:11
paulb
External User
 
Posts: 1
Default MS Search Service on Act/Act Sql 2k SP3 Cluster Failing



Help:
FullText catalog wasn't populating and believe we were
able to tie it to a failover.

Followed steps listed in kb240867. now the ms search
resource will not come on line through cluster
administrator.

Here is what the event log shows:
The Gatherer property mapping file cannot be opened.
Error: 80070003. The default values are being used. You
may have to copy the property mapping file from the setup
CD, or reinstall the application.

followed by:
An error occurred during the online operation for
instance <SQL Server Fulltext (INST2)>: 80070003 - The
system cannot find the path specified.
  Reply With Quote


 


2 6th September 06:11
jt-kane
External User
 
Posts: 1
Default MS Search Service on Act/Act Sql 2k SP3 Cluster Failing



Paul,
1) An error occurred during the online operation for instance
<SQL Server Full text>: 80070002 - The system cannot find the file
specified.
2) The Gatherer property mapping file cannot be opened. Error:
80070002. The default values are being used. You may have to copy the
property mapping file from the setup CD, or reinstall the application

Some of the changes which trigger these errors are:
================================================== =
1) Changing the FTDATA folder location.
2) Changing the SQL startup account.
3) Failover of the sql virtual server.

Reasons why these errors occur:
===============================
These errors means that the data\config directory for the SQL server
full text application is not on disk at the location specified. The
mapping file is the first file it is trying to read, though, there is
no specific use for this file in SQL. There are other files in this
directory that are most likely missing and not reported. such as noise
files and the fulltext schema.tx file.

Possble solutions &/or workarounds:
===================================
1) One workaround is to copy the FTDATA config directory
(\FTDATA\SQLServer\*.*) from another SQL instance,
and take the instance offline/online.

NOTE: The FTDATA config (\FTDATA\SQLServer\Config) directory is under
the SQL install path, so it should be on the shared disk. The most
likely it is the registry key that has an incorrect value.

2) Using Regedt32, edit the following Register key and value:
HKLM\Software\Microsoft\Search\1.0\Gathering
Manager\Applications\SQLServer (REG_SZ) ApplicationPath
<ApplicationPath>\Config\gatherprm.txt

NOTE: After making this Registry change, you should failover. There
are addtional files that MSSearch requires in this folder.
Additionally, you may have to grant the Cluster Service account
explicit Full Control to the above ApplicationPath's FTDATA folder.

Some additional info, you should also re-register the following dll's:

in ..\MSSearch\Bin
==================
ftsqlpar.dll
mssadmin.dll
msscntrs.dll
mssmmcsi.dll
mssmsg.dll
mssmulpi.dll
mssph.dll
mssrch.dll
msstools.dll
nlhtml.dll
objcreat.dll
offfilt.dll
propdefs.dll
srchadm.dll
srchidx.dll
tquery.dll

in ..\MSSearch\Common
=====================
mssitlb.dll


in ..WINNT\System32\
====================
athprxy.dll

Regards,
John
  Reply With Quote


 


Reply


Thread Tools
Display Modes




Copyright © 2006 SmartyDevil.com - Dies Mies Jeschet Boenedoesef Douvema Enitemaus -
666