IIS Index Server - MS Indexing Service Catalog settings will not stay set

This is Interesting: Free IT Magazines  
Home > Archive > IIS Index Server > March 2005 > MS Indexing Service Catalog settings will not stay set





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author MS Indexing Service Catalog settings will not stay set
DrDrew

2005-03-23, 6:09 pm

I apologize for the lengthy description of my problem, but I wanted to
make sure that I gave enough background.

Here is my scenario:

I work for an organization that is divided into two divisions: Division
A and Division B. I have an intranet website for my organization that
both of these divisions use which is written in ASP and hosted on a
Windows 2000 server which is running IIS 5.0. There is a search
feature that is available on the website which utilizes MS Indexing
Service to search through a repository of MS Word documents. However,
this repository of Word documents is divided into two folders: a
Divison A folder and a Division B folder. When a Division A employee
does a search they do not want to get any results returned for
documents which relate to Division B. When a Division B employee does
a search they do not want to get any results returned for documents
which relate to Division A.

The way I solved this problem was to create two seperate search
webpages in ASP so that Division A would have their own page and
Division B would have their own page. After this, I created two
catalogs in the MS Indexing Service: one for Division A and one for
Division B. Since I want to use virtual paths in the search results, I
associated both of these catalogs with the intranet website using the
"WWW Server" setting. I then used the Indexing Service MMC to view the
directories for the Division A catalog and indicated that I did not
want the directory that has Division B documents in it to be included
in the index. I then did the same thing for the Division B catalog
only vice versa. This solution seemed to work initially and I was
getting the expected results. Unfortunately, this turned out to be a
short lived success.

Every few days my settings where I indicated that I did not want to
include certain directories in the catalog are changed so that all
directories associated with the website are now indexed. I am thinking
it may have something to do with having multiple catalogs associated
with the same website, is this something the Indexing Service cannot
handle? Also I am starting to doubt the effectiveness of the way I set
things up. Is their a flaw in my design that I described above?

Thanks,
DrDrew

George Cheng [MSFT]

2005-03-29, 6:20 pm

When you index a website it picks up all vdirs that have "index this
resource" enabled.
You should set ntfs permissions on the documents. Index server will only
return results if the user has permissions to the documents.
Or you could modify your formscope so you are searching only that
particular folder.

Thank You

George Cheng

Microsoft Application Center & Index Server Support

Note: This article has no warranties implicit or explicit.
All the content is given on the "as is" basis and the user
takes full responsibility for its use and assumption.
Microsoft Corporation Copyright 2004
All Rights Reserved

--------------------
| From: "DrDrew" <aleftwich@gmail.com>
| Newsgroups: microsoft.public.inetserver.indexserver
| Subject: MS Indexing Service Catalog settings will not stay set
| Date: 23 Mar 2005 08:02:48 -0800
| Organization: http://groups.google.com
| Lines: 43
| Message-ID: <1111593768.001365.122020@g14g2000cwa.googlegroups.com>
| NNTP-Posting-Host: 208.20.221.71
| Mime-Version: 1.0
| Content-Type: text/plain; charset="iso-8859-1"
| X-Trace: posting.google.com 1111593772 18991 127.0.0.1 (23 Mar 2005
16:02:52 GMT)
| X-Complaints-To: groups-abuse@google.com
| NNTP-Posting-Date: Wed, 23 Mar 2005 16:02:52 +0000 (UTC)
| User-Agent: G2/0.2
| Complaints-To: groups-abuse@google.com
| Injection-Info: g14g2000cwa.googlegroups.com; posting-host=208.20.221.71;
| posting-account=vuwu-w0AAABntOnfTBQE_auyJb8SmhwW
| Path:
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.
sul.t-online.de!t-online.de!news.glorb.com!postnews.google.com!g14g2000cwa.g
ooglegroups.com!not-for-mail
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.inetserver.indexserver:31131
| X-Tomcat-NG: microsoft.public.inetserver.indexserver
|
| I apologize for the lengthy description of my problem, but I wanted to
| make sure that I gave enough background.
|
| Here is my scenario:
|
| I work for an organization that is divided into two divisions: Division
| A and Division B. I have an intranet website for my organization that
| both of these divisions use which is written in ASP and hosted on a
| Windows 2000 server which is running IIS 5.0. There is a search
| feature that is available on the website which utilizes MS Indexing
| Service to search through a repository of MS Word documents. However,
| this repository of Word documents is divided into two folders: a
| Divison A folder and a Division B folder. When a Division A employee
| does a search they do not want to get any results returned for
| documents which relate to Division B. When a Division B employee does
| a search they do not want to get any results returned for documents
| which relate to Division A.
|
| The way I solved this problem was to create two seperate search
| webpages in ASP so that Division A would have their own page and
| Division B would have their own page. After this, I created two
| catalogs in the MS Indexing Service: one for Division A and one for
| Division B. Since I want to use virtual paths in the search results, I
| associated both of these catalogs with the intranet website using the
| "WWW Server" setting. I then used the Indexing Service MMC to view the
| directories for the Division A catalog and indicated that I did not
| want the directory that has Division B documents in it to be included
| in the index. I then did the same thing for the Division B catalog
| only vice versa. This solution seemed to work initially and I was
| getting the expected results. Unfortunately, this turned out to be a
| short lived success.
|
| Every few days my settings where I indicated that I did not want to
| include certain directories in the catalog are changed so that all
| directories associated with the website are now indexed. I am thinking
| it may have something to do with having multiple catalogs associated
| with the same website, is this something the Indexing Service cannot
| handle? Also I am starting to doubt the effectiveness of the way I set
| things up. Is their a flaw in my design that I described above?
|
| Thanks,
| DrDrew
|
|

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com