gllanderas
asked on
Error 8004181d (There is no catalog) of Index Server in Windows 2008 R2 64 bits
Hello,
Working with a Windows 2008 R2 Standard 64 bits.
I have an ASP page to search in the documentation of the Intranet, this search page works fine in Windows 2003 but fails on a Windows 2008 with this message:
iatech/arc hive/2009/ 11/20/how- to-index-i is-7-0-web -sites-in- windows-se rver-2008- by-indexin g-service. aspx but fails with the last part (Set ContentIndexed metabase property). Nevertheless, I manually configured the directories in the Index Server Service and I can see that the the service is Started and with all the documents indexed.
The code that I use to search in the documentation is:
Any idea? Thanks.
Working with a Windows 2008 R2 Standard 64 bits.
I have an ASP page to search in the documentation of the Intranet, this search page works fine in Windows 2003 but fails on a Windows 2008 with this message:
Microsoft OLE DB Provider for Indexing Service error '8004181d'
There is no catalog.
I installed and configured the IIS and IS following this instructions: http://blogs.msdn.com/b/asThere is no catalog.
The code that I use to search in the documentation is:
<%
strScope = "c:\intranet\documents\"
strSearch = Chr(34) & "*a*" & Chr(34)
strSQL = "SELECT FileName, Directory, Characterization"
strSQL = strSQL & " FROM Scope('" & Chr(34) & strScope & "')"
strSQL = strSQL & " WHERE CONTAINS(Contents, '" & strSearch & "') > 0"
strSQL = strSQL & " ORDER BY Rank DESC, HitCount DESC"
Set conIndexSrv = Server.CreateObject("ADODB.Connection")
conIndexSrv.ConnectionString = "provider=msidxs;"
conIndexSrv.CursorLocation = adUseClient
conIndexSrv.Open
Set cmdIndexSrv = Server.CreateObject("ADODB.Command")
Set cmdIndexSrv.ActiveConnection = conIndexSrv
cmdIndexSrv.CommandType = adCmdText
cmdIndexSrv.CommandText = strSQL
Set rstIndexSrv = Server.CreateObject("ADODB.RecordSet")
rstIndexSrv.CursorType = adOpenKeyset
rstIndexSrv.MaxRecords = 100
rstIndexSrv.Open cmdIndexSrv
%>
I tried with different scopes:
c:\intranet\documents\
c:\intranet\documents
c:\intranet\
c:\intranet
intranet
\\server\documents
\\server\documents\
c:\intranet\documents
c:\intranet\
c:\intranet
intranet
\\server\documents
\\server\documents\
Any idea? Thanks.
ASKER
Yes, and I have the catalog listed and it has indexed the documents.
I think the problem is in the access to the catalog not in the catalog itself.
I think the problem is in the access to the catalog not in the catalog itself.
Does the script you are running in same folder as the catalog name?
In other words, the catalog is in documents folder as in:
c:\intranet\documents\
If your script resides in same folder, then simply do:
strScope = Catalogname
In other words, the catalog is in documents folder as in:
c:\intranet\documents\
If your script resides in same folder, then simply do:
strScope = Catalogname
ASKER
No, I have the search page in another directory:
c:\Intranet
c:\Intranet\documents <- with the documents I want to search into
c:\Intranet\web <- with the asp pages, including the search page
I moved the search page into the documents directory and tried with the scopesc:\Intranet\documents <- with the documents I want to search into
c:\Intranet\web <- with the asp pages, including the search page
Intranet
c:\Intranet
documents
Intranet\documents
c:\Intranet\documents
but it doesn't work.
c:\Intranet
documents
Intranet\documents
c:\Intranet\documents
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
In Windows 2000 and 2003 was not necessary to specify the Source Code at the connection string, but it seems that it is necessary in 2008.
http://www.sentryfile.com/forum/messageview.cfm?catid=6&threadid=611