Ala,
You specify the name of the catalog, not the path to it. If this still doesn't work, go to SQL server and ensure the user that DNN uses to connect has sys admin permission.
Peter

I tried just the name of the catalog in the first place but when it didn't work I started experimenting - that's why I tried paths also. I gave all possible admin permission to the DNN admin account on the SQL server and it is still giving me the same error. Indexing service seems to be working OK because I can search docs in the DMX folder using built-in "Query the Catalog" feature.

Any other ideas?

AlaMakota

Ala,

Basically a 'link server' SQL statement is run when you click 'attach'. You can try to use an SQL management tool to run this directly to see what error comes out of this. So your code would be something like:

EXEC sp_addlinkedserver 'MyCatalog', 'Index Server', 'MSIDXS', 'MyCatalog'

After this a test is done to determine if the catalog attached or not. This is done through a 'faked query':

SELECT TOP 1 * FROM OPENQUERY(MyCatalog, 'SELECT Filename, Rank FROM SCOPE() WHERE FREETEXT(''extra'') ORDER BY Rank DESC') AS Docs

If this does not produce an error, then the catalog must have attached correctly.

Peter

I am not an expert in SQL script/queries but I tried to follow your directions and this is the error I got doing the "faked query":

System.Data.SqlClient.SqlException: Could not execute query against OLE DB provider 'MSIDXS'. [OLE/DB provider returned message: Service is not running. ] OLE DB error trace [OLE/DB Provider 'MSIDXS' ICommandText::Execute returned 0x80070002]. at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText) at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions) SELECT TOP 1 * FROM OPENQUERY(DNNdocs, 'SELECT Filename, Rank FROM SCOPE() WHERE FREETEXT(''extra'') ORDER BY Rank DESC') AS Docs

I don't know what service it is talking about but my DNN installation is running on SQL server and everything seems to be working OK. Any other ideas what can be wrong?

Thanks
Alamakota

It appears the indexing service (this is called MSIDXS) is turned off ...

Under Computer Management > Indexing Service it says "Started" in the Status column...

I can also go to "Query the Catalog" and it will find files with a given text in the DMX folder...

A.

The error occurs outside the module and states it is not functioning. I'm afraid I can't look into your system. Some element in the chain in linking to the indexing service is malfunctioning. You can see the linked server in the SQL enterprise manager? And can you see a result when you go into Query analyzer and try to run the query SELECT TOP 1 * FROM OPENQUERY(DNNdocs, 'SELECT Filename, Rank FROM SCOPE() WHERE FREETEXT(''extra'') ORDER BY Rank DESC') AS Docs ?
Peter

I don't see Indexing Service as a linked server (master database/syservers table). I have DNN running physically on a separate machine than my SQL server - can this be a problem?

When I run EXEC sp_addlinkedserver 'MyCatalog', 'Index Server', 'MSIDXS', 'MyCatalog' command using DNN's SQL page first nothing happens and then when I try to do it again I get the following error message:

System.Data.SqlClient.SqlException: The server 'DNNdocs' already exists. at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText) at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions) EXEC sp_addlinkedserver 'DNNdocs', 'Index Server', 'MSIDXS', 'DNNdocs'

I assumed that I have to replace the 'MyCatalog' with 'DNNdocs' which is the name of my Catalog under Indexing Services. What does it mean than that The server 'DNNdocs' already exists? Where? I cannot find it and I am lost. Without that feature the module is kind of useless for us...

Thanks for your help so far.
A.

Ala,
This procedure will not work on separate servers. I'm working on a solution for this, but for now you cannot use the indexing service on another server.
Peter

I had the indexing service working at one time, but now it is not. When trying to detach and reattach, I got the following message... Sql Server could not attach to the named Indexing Service catalog.

My DB is running on separate server from web server, but it always has been and at one time this was working. Is it related to a newer release of DMX?

I'm planning to move the repository for DMX to the SQL box, which I guess would remedy this problem (the SQL box has more storage space as well.) You mentioned the permissions were a bit "tricky" to have the DMX repository on a separate box from the web server. Can you elaborate? I guess somehow the NETWORK SERVICE account needs read/write permissions to the DMX folder on the SQL box?

Mike

Just to make sure again: what needs to be on the same box to make it work? I have web server with DNN, Indexing Service and DMX repository on one box and SQL server on another.

Thanks
A.

Mike/Ala,

There has been a significant overhaul of full-text search. It has now been integrated with SQL server greatly inreasing its performance (it became almost useless at 10.000+ documents due to the resource consumption on the server). One (unforeseen) side-effect is that for those that run their SQL server on another machine than the indexing service, the linking doesn't happen. I'm working on resolving this (there is a solution and it is being tested now by one of the customers).

Peter

PS Mike: about the 'tricky' permissions: what you need to know is that the WEB SERVER's NETWORK SERVICE account needs permission on the network share (i.e. \\docserver\somedir), and not the doc server's NETWORK SERVICE account. You probably need a domain controller to do this properly.

Peter i'm interested in the solution you're testing at the moment. Could you give me any more info on this?

If you setup index server on the seperate SQL server and set the path to index as a UNC path to the DMX repository on the web server, that would work wouldn't it? Your catalog would be local to the SQL server and you repository would be local to DNN. Am I missing something here? Going to try it out today.

Index server can't index using UNC paths. You can enter the path and it lets you enter the credentials, but it always returns no results from a query.

Yes, the indexing service is local on a machine as far as I know. The challenge becomes integrating the indexing service on the SQL server when they are on separate systems. I am trying out solutions for this, but until I can prove it's working I won't give too much publicity on this. In the latest version you can try to use servername.catalog (i.e. server's name DOT catalog name) in the full indexinging catalog box. But I cannot guarantee yet if it'll work.
Peter

Would it be possible to give the option in the module of:

linking to the index server from SQL server
or
querying the catalog direct?

Performance isn't an issue for me, I would like to be able to query the local index server without using sql server.

James,
I guess it could be done in code but it is really unelegant. The old solution loads a list of ALL documents in a portal into the server's memory. Then the match was made with the returns from the Indexing Service. I guess if all else fails I might have to revert to this solution although it is easy to see that this won't work in larger repositories.
Peter

Peter,

Are you still planning to provide an option for querying the catalog directly? I'm very interested in that feature. Because of how our SQL server is hosted, I don't think I'll ever get a linked server to my Web Server.

Chi Ho Yeung

Chi,
I can't promise that as it will need to be well separated and configurable. But I see your point and will look into it.
Peter