kevingoff

I am trying to query a table that is on both my test and production machine.
It works fine on test. It does not work on production (a cluster). I don't
see any error messages in sql or the event viewer. When I run a query on
test it returns a result set. Production does not. I see this in the
gather logs:

7/22/2003 11:44:32 AM Add The gatherer has started
7/22/2003 11:44:34 AM Add The initialization has completed
7/22/2003 11:44:38 AM Add Started Full crawl
7/22/2003 11:44:38 AM MSSQL75://SQLServer/385a3eea Add Error
fetching U
RL, (8007007f - The specified procedure could not be found. )
7/22/2003 11:44:40 AM Add Completed Full crawl
7/22/2003 12:11:26 PM Add Started Full crawl
7/22/2003 12:11:30 PM MSSQL75://SQLServer/385a3eea Add Error
fetching U
RL, (8007007f - The specified procedure could not be found. )
7/22/2003 12:11:32 PM Add Completed Full crawl
7/22/2003 12:12:00 PM Add Started Full crawl
7/22/2003 12:12:00 PM MSSQL75://SQLServer/385a3eea Add Error
fetching U
RL, (8007007f - The specified procedure could not be found. )
7/22/2003 12:12:02 PM Add Completed Full crawl
7/22/2003 12:12:52 PM Add Started Full crawl
7/22/2003 12:12:52 PM MSSQL75://SQLServer/385a3eea Add Error
fetching U
RL, (8007007f - The specified procedure could not be found. )
7/22/2003 12:12:54 PM Add Completed Full crawl
7/22/2003 12:13:08 PM Add Started Full crawl
7/22/2003 12:13:08 PM MSSQL75://SQLServer/385a3eea Add Error
fetching U
RL, (8007007f - The specified procedure could not be found. )
7/22/2003 12:13:10 PM Add Completed Full crawl

I get no error when I query the production box, just an empty result set.

Thanks,
Kevin

john kane

Kevin,
Thanks for providing the gatherer log info. The primary error is "8007007f -
The specified procedure could not be found" and this is somewhat common in a
clustered with MSSearch. The cause and resolutions can vary depending upon
if a file or registry key is missing or incorrectly set.

Has this server been recently upgraded to SP3? If so, you might also want to
checkout KB article 817301 "PRB:
Microsoft Search Full-Text Catalog Population Fails When You Upgrade SQL
Server 2000 Failover Cluster to SQL Server 2000 Service Pack 3" at
http://support.microsoft.com/default.aspx?scid=kb;en-us;817301

If the above workarounds does not resolve this issue for you, there are
other troubleshooting methods and resolutions available.
Regards,
John

kevingoff

I tried to register query and tquery. Both registered ok but the same
problem still exists. I tried the recommendation from the article to
register all DLL's in the MSSearch DLL folder (bin directory). I did this
and still have the same problem after trying to repopulate the index.

The index item count viewable in EM shows a count of 1.

Any ideas?

john kane

Kevin,
The bellow info while good is not enough to determine what is causing the
error "8007007f - The specified procedure could not be found" to be raised
on your clustered servers. Did you review the files and register key
settings and permissions from the below workarounds? If so, what did you
find different? Is the Schema.Txt under \FTDATA\SQLServer\Config directory
exactly the same as on your SQL Server 2000 Setup CD?

Do you have SQL Server 2000 SP2 or SP3 applied on this problem server? Could
you post the full output of:
SELECT @@version

There are some additional "extended" FTS/MSSearch debugging that can be
done, but these require SP2 or above be installed and most likely you will
have to open a support case with Microsoft PSS SQL Server support to pursue
these options....

Regards,
John