Very Computer

by **Steve Clar** » Sun, 02 Mar 2003 09:19:18

Sharepoint search proxy not installed in iis - Win2k Pro.
Not talking about indexing, I mean sharepoint search proxy
iis. I created an indexing catalog & corresponding folder,
but under tracking, there is no Sharepoint search proxy to
choose from, so search doesn't find any results.

Please help, gotta get search working.

Thank You

by **David Scot** » Tue, 04 Mar 2003 04:48:21

It shouldnt matter, I have a similar setup too - IIS that comes with Win2k
Pro and XP Pro does not have the ability to create virtual webs (such as the
search proxy web) - as long as IIS has an application mapping (in
'Configuration' on the home for .IDQ files you should be good to go.

The search page htx file is setup to use the default Team Services catalog
which on a workstation installation like yours and mine will be pointing to
the 'Web' Index Catalog.

David

Quote:> Sharepoint search proxy not installed in iis - Win2k Pro.
> Not talking about indexing, I mean sharepoint search proxy
> iis. I created an indexing catalog & corresponding folder,
> but under tracking, there is no Sharepoint search proxy to
> choose from, so search doesn't find any results.

> Please help, gotta get search working.

> Thank You

by **Steve Clar** » Tue, 04 Mar 2003 10:26:16

Came to the same conclusions. We went ahead & upgraded to
Win2k Server, solved all the problems.

Thanks

Quote:>-----Original Message-----
>It shouldnt matter, I have a similar setup too - IIS

that comes with Win2k

Quote:>Pro and XP Pro does not have the ability to create

virtual webs (such as the

Quote:>search proxy web) - as long as IIS has an application
mapping (in
>'Configuration' on the home for .IDQ files you should be
good to go.

>The search page htx file is setup to use the default

Team Services catalog

>which on a workstation installation like yours and mine
will be pointing to
>the 'Web' Index Catalog.

>David

>> Sharepoint search proxy not installed in iis - Win2k
Pro.
>> Not talking about indexing, I mean sharepoint search
proxy
>> iis. I created an indexing catalog & corresponding
folder,
>> but under tracking, there is no Sharepoint search
proxy to
>> choose from, so search doesn't find any results.

>> Please help, gotta get search working.

>> Thank You

>.

by **MVP** » Tue, 04 Mar 2003 16:44:30

David,

I think I'd better include this in the search problem part of the newsgroup
FAQ.

Can you please fill in the blanks (ZZZZ) on the following and otherwise
confirm that this is OK ? (I already have .idq mapping in another item)

"Title: I have problems with Search when using W2K Pro or XPPro on my STS
Server. What might be my problem ?

Answer:

On an installation of STS on W2K Pro or XP Pro, the search page .htx file
points to the Web Index Catalog rather than the directory structure where
STS places documents. Amend this so that it points to the correct (default
X:\inetpub\wwwroot) location(s).

You will find the htx file at ZZZZZZZZZZZ "

Thanks (by the way, I always used to recognize ITEC_MAN why change to a
normal name?)

Mike Walsh
Helsinki
Finland

> It shouldnt matter, I have a similar setup too - IIS that comes with Win2k
> Pro and XP Pro does not have the ability to create virtual webs (such as
the
> search proxy web) - as long as IIS has an application mapping (in
> 'Configuration' on the home for .IDQ files you should be good to go.

> The search page htx file is setup to use the default Team Services catalog
> which on a workstation installation like yours and mine will be pointing
to
> the 'Web' Index Catalog.

> David

> > Sharepoint search proxy not installed in iis - Win2k Pro.
> > Not talking about indexing, I mean sharepoint search proxy
> > iis. I created an indexing catalog & corresponding folder,
> > but under tracking, there is no Sharepoint search proxy to
> > choose from, so search doesn't find any results.

> > Please help, gotta get search working.

> > Thank You

by **ITEC_MA** » Wed, 05 Mar 2003 12:49:44

Sorry, is David Scott (ITEC_MAN) better? :)

under wwwroot\_layouts\ and any subwebs in their \_layouts\ directory

and the program files\common files\microsoft shared\web server
extensions\50\templates\1033\layouts directory

you will find the htx files. Note however that changing the references of
OWS_Search_Proxy in these files to say 'Web' does not seem to make any
difference - it seems to be the setting up the .idq mapping to the
C:\windows\system32\idq.dll (with GET, HEAD, POST in the limit to field and
ticking the 'script engine' and 'check that file exists' boxes) that fixes
my Workstation (2000 and XP) installs...

David... I mean ITEC_MAN !

> David,

> I think I'd better include this in the search problem part of the
newsgroup
> FAQ.

> Can you please fill in the blanks (ZZZZ) on the following and otherwise
> confirm that this is OK ? (I already have .idq mapping in another item)

> "Title: I have problems with Search when using W2K Pro or XPPro on my STS
> Server. What might be my problem ?

> Answer:

> On an installation of STS on W2K Pro or XP Pro, the search page .htx file
> points to the Web Index Catalog rather than the directory structure where
> STS places documents. Amend this so that it points to the correct (default
> X:\inetpub\wwwroot) location(s).

> You will find the htx file at ZZZZZZZZZZZ "

> Thanks (by the way, I always used to recognize ITEC_MAN why change to a
> normal name?)

> Mike Walsh
> Helsinki
> Finland

> > It shouldnt matter, I have a similar setup too - IIS that comes with
Win2k
> > Pro and XP Pro does not have the ability to create virtual webs (such as
> the
> > search proxy web) - as long as IIS has an application mapping (in
> > 'Configuration' on the home for .IDQ files you should be good to go.

> > The search page htx file is setup to use the default Team Services
catalog
> > which on a workstation installation like yours and mine will be pointing
> to
> > the 'Web' Index Catalog.

> > David

> > > Sharepoint search proxy not installed in iis - Win2k Pro.
> > > Not talking about indexing, I mean sharepoint search proxy
> > > iis. I created an indexing catalog & corresponding folder,
> > > but under tracking, there is no Sharepoint search proxy to
> > > choose from, so search doesn't find any results.

> > > Please help, gotta get search working.

> > > Thank You

by **MVP** » Wed, 05 Mar 2003 15:06:10

Well I prefer 'David "ITEC_MAN" Scott' but it's a matter of taste <g>.

Thanks for this.

I suppose I need another re-write concentrating (solely ?) on the idq
mapping changes.

Can you clarify what you mean by "in the limit to field" ? For instance.

Mike Walsh etc.

> Sorry, is David Scott (ITEC_MAN) better? :)

> under wwwroot\_layouts\ and any subwebs in their \_layouts\ directory

> and the program files\common files\microsoft shared\web server
> extensions\50\templates\1033\layouts directory

> you will find the htx files. Note however that changing the references of
> OWS_Search_Proxy in these files to say 'Web' does not seem to make any
> difference - it seems to be the setting up the .idq mapping to the
> C:\windows\system32\idq.dll (with GET, HEAD, POST in the limit to field
and
> ticking the 'script engine' and 'check that file exists' boxes) that
fixes
> my Workstation (2000 and XP) installs...

> David... I mean ITEC_MAN !

> > David,

> > I think I'd better include this in the search problem part of the
> newsgroup
> > FAQ.

> > Can you please fill in the blanks (ZZZZ) on the following and otherwise
> > confirm that this is OK ? (I already have .idq mapping in another item)

> > "Title: I have problems with Search when using W2K Pro or XPPro on my
STS
> > Server. What might be my problem ?

> > Answer:

> > On an installation of STS on W2K Pro or XP Pro, the search page .htx
file
> > points to the Web Index Catalog rather than the directory structure
where
> > STS places documents. Amend this so that it points to the correct
(default
> > X:\inetpub\wwwroot) location(s).

> > You will find the htx file at ZZZZZZZZZZZ "

> > Thanks (by the way, I always used to recognize ITEC_MAN why change to a
> > normal name?)

> > Mike Walsh
> > Helsinki
> > Finland

> > > It shouldnt matter, I have a similar setup too - IIS that comes with
> Win2k
> > > Pro and XP Pro does not have the ability to create virtual webs (such
as
> > the
> > > search proxy web) - as long as IIS has an application mapping (in
> > > 'Configuration' on the home for .IDQ files you should be good to go.

> > > The search page htx file is setup to use the default Team Services
> catalog
> > > which on a workstation installation like yours and mine will be
pointing
> > to
> > > the 'Web' Index Catalog.

> > > David

> > > > Sharepoint search proxy not installed in iis - Win2k Pro.
> > > > Not talking about indexing, I mean sharepoint search proxy
> > > > iis. I created an indexing catalog & corresponding folder,
> > > > but under tracking, there is no Sharepoint search proxy to
> > > > choose from, so search doesn't find any results.

> > > > Please help, gotta get search working.

> > > > Thank You