Groups | Blog | Home
all groups > sql server full text search > february 2004 >

sql server full text search : Interface not supported - Full Text Searching


anthonyh NO[at]SPAM mtservices.co.uk
2/9/2004 4:20:07 AM
I have reposted this question because my machine crashed during
submittion. If this question appears twice then sorry!

My system is

Windows XP Pro
SQL Server 2000 - SP3
VS.NET 2003

I am trying to generate a full text index on a table but I am getting
'Interface not supported' errors all over the place.

I opened up the MMC using srchadm.msc and tried opening the 'search'
option to which I received the error - Snap-In not initialized.

I then re-registered all the dll's in the MSSearch\bin directory and
got a little further. My local machine shows under Search in the MMC
but I now receive the following error msg:

Unable to connect to host AREA51. No such interface supported.

Any suggestions would be most appreciated.

Again please accept my apologies for being slightly off topic.

Regards

Hilary Cotter
2/9/2004 7:42:43 AM
I believe that this interface has been disabled. You should not be using
srchadm to administer sql fts anyway. It provided a window into it, that was
somewhat useful, but its functionality was also available using tsql and SQL
DMO.

[quoted text, click to view]

John Kane
2/10/2004 1:13:34 PM
Anthony,
Because of the error you are seeing (80004002 - No such interface supported)
and that you are using SQL Server 2000 SP3, you should check out KB article
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

Depending upon if this SQL Server 2000 is a named instance and upgraded from
SQL Server 7.0 or if SQL Server 7.0 was or is the default instance, you may
be encountering this bug.

Regards,
John



[quoted text, click to view]

anthonyh NO[at]SPAM mtservices.co.uk
2/11/2004 3:47:33 AM
Hi John,

Thanks for you reply.

Since my original post, I have uninstalled SQL Server 2000 including
MSSearch and reinstalled. Even without the service pack I still get
the 'Interface Not Supported' error everytime I try to create a new
catalog in EM.

I have never had SQL Server 7 installed on my machine so the upgrade
problem doesn't apply.

It appears that the problem lies with MSSearch - its running but does
not appear to be accessible. I haven't a clue why.

Just to review, my PC is currently running:

Windows XP Professional SP1
Microsoft Office XP
Visual Studio.NET 2003
IIS 5.1
SQL Server 2000 (Developer)

SQL Server was received as part of our MSDN Subscription. I don't
know if there are any issues with this release of SQL Server. Has
anyone had problems with this release as opposed to the market
release?

Again thanks for trying to assist.

Kind regards

Anthony






[quoted text, click to view]
anthonyh NO[at]SPAM mtservices.co.uk
2/11/2004 4:08:56 AM
I'd just like to add, that although I accept what Hilary said about
using Srchadm.msc, I still think that I should be able to expand the
'Search' branch of the tree menu.

I am now getting an error saying:

A connection to the Search Services on AREA51 could not be
established, without a valid connection this host will be unusable. Do
you want to add this host anyway?

This is why I think that MSSearch is causing my problem, but again I
haven't a clue why!

Any more ideas would be greatly appreciated.

Kind regards

John Kane
2/11/2004 10:20:22 AM
You're welcome, Anthony,
There are other issues that can also cause this error, but the most common
one was the one described in the Kb article.
You might want to consider opening a support case with Microsoft PSS SQL
Server support as they have methods for extended debugging of issues like
this. Since, you never had SQL Server 7.0 installed or SQL 2000 upgraded
from SQL 7.0 and considering that you've already un-installed SQL Server
2000 including the MSSearch components and re-installed them, I too agree
that this is an unusual error and most likely related to some missing dll
registration &/or an incorrectly or missing registry key &/or value.

Regards,
John


[quoted text, click to view]

AddThis Social Bookmark Button