Search seems to be working. I have crawled several external sites, but
I am seeing errors in the gatherer log with respect to the content of
the portal: The errors are:

1/29/2005 1:40:30 AM Modify
sps://minotaur/site$$$catlisting/bucketid=2/
The address could not be found, (0x80040D7B - Document filtering
cannot be completed because the document server did not respond within
the specified timeout. Try crawling the server later, or increase the
timeout values. )

1/29/2005 1:40:30 AM Modify sps://minotaur/site$$$category/bucketid=1/
The address could not be found, (0x80040D7B - Document filtering
cannot be completed because the document server did not respond within
the specified timeout. Try crawling the server later, or increase the
timeout values. )

1/29/2005 1:40:29 AM Modify sps://minotaur/site$$$category/
The address could not be found, (0x80040D7B - Document filtering
cannot be completed because the document server did not respond within
the specified timeout. Try crawling the server later, or increase the
timeout values. )

1/29/2005 1:40:29 AM Modify sps://minotaur/site$$$keylisting/
The address could not be found, (0x80040D7B - Document filtering
cannot be completed because the document server did not respond within
the specified timeout. Try crawling the server later, or increase the
timeout values. )

1/29/2005 1:40:29 AM Modify sps://minotaur/site$$$people
The address could not be found, (0x80040D7B - Document filtering
cannot be completed because the document server did not respond within
the specified timeout. Try crawling the server later, or increase the
timeout values. )

1/29/2005 1:40:28 AM Modify sps://minotaur/site$$$catlisting/
The address could not be found, (0x80040D7B - Document filtering
cannot be completed because the document server did not respond within
the specified timeout. Try crawling the server later, or increase the
timeout values. )

1/29/2005 1:40:28 AM Modify sps://minotaur
The address could not be found, (0x80040D7B - Document filtering
cannot be completed because the document server did not respond within
the specified timeout. Try crawling the server later, or increase the
timeout values. )

1/29/2005 1:40:24 AM Modify sts2://minotaur/webid=/
The address could not be found, (0x80040D7B - Document filtering
cannot be completed because the document server did not respond within
the specified timeout. Try crawling the server later, or increase the
timeout values. )

One thing that should be said is that I removed and reinstalled SPS,
WSS, and IIS, making sure that FPSE2002 was not on the box. I applied
SP1 for both WSS and SPS. I created the portal, and then added the old
content databases to the new portal. There are 6 databases associated
with the portal. Is that a problem?

After I added the external content sources, it says it has 1800+
documents indexed. But, before that it only showed 70, and I have 300+
.mht and .doc files in the doclibs.

Hollis D. Paul [MVP - Outlook]
Hollis@outhousebythesound.com
Mukilteo, WA USA

Re: The portal can't be found by search by Shane

Shane
Sat Jan 29 13:50:55 CST 2005

I have ran into this on my virtual pc test environments. Usually the
problem comes from the search time out. Adjusting it to 60 seconds solved
these errors for me. Go to SPS central admin then Manage the search
settings. From there go to your server name under servers and topology.
Time out settings is the third section on that page. I bumped those 2
numbers up and reran my search. No more errors.

Hope this helps


Shane

"Hollis D. Paul" <Hollis@outhousebythesound.com> wrote in message
news:VA.00001eae.00ebd828@obts-outlookdev.outlookbythesound.mukwoods...
> Search seems to be working. I have crawled several external sites, but
> I am seeing errors in the gatherer log with respect to the content of
> the portal: The errors are:
>
> 1/29/2005 1:40:30 AM Modify
> sps://minotaur/site$$$catlisting/bucketid=2/
> The address could not be found, (0x80040D7B - Document filtering
> cannot be completed because the document server did not respond within
> the specified timeout. Try crawling the server later, or increase the
> timeout values. )
>
> 1/29/2005 1:40:30 AM Modify sps://minotaur/site$$$category/bucketid=1/
> The address could not be found, (0x80040D7B - Document filtering
> cannot be completed because the document server did not respond within
> the specified timeout. Try crawling the server later, or increase the
> timeout values. )
>
> 1/29/2005 1:40:29 AM Modify sps://minotaur/site$$$category/
> The address could not be found, (0x80040D7B - Document filtering
> cannot be completed because the document server did not respond within
> the specified timeout. Try crawling the server later, or increase the
> timeout values. )
>
> 1/29/2005 1:40:29 AM Modify sps://minotaur/site$$$keylisting/
> The address could not be found, (0x80040D7B - Document filtering
> cannot be completed because the document server did not respond within
> the specified timeout. Try crawling the server later, or increase the
> timeout values. )
>
> 1/29/2005 1:40:29 AM Modify sps://minotaur/site$$$people
> The address could not be found, (0x80040D7B - Document filtering
> cannot be completed because the document server did not respond within
> the specified timeout. Try crawling the server later, or increase the
> timeout values. )
>
> 1/29/2005 1:40:28 AM Modify sps://minotaur/site$$$catlisting/
> The address could not be found, (0x80040D7B - Document filtering
> cannot be completed because the document server did not respond within
> the specified timeout. Try crawling the server later, or increase the
> timeout values. )
>
> 1/29/2005 1:40:28 AM Modify sps://minotaur
> The address could not be found, (0x80040D7B - Document filtering
> cannot be completed because the document server did not respond within
> the specified timeout. Try crawling the server later, or increase the
> timeout values. )
>
> 1/29/2005 1:40:24 AM Modify sts2://minotaur/webid=/
> The address could not be found, (0x80040D7B - Document filtering
> cannot be completed because the document server did not respond within
> the specified timeout. Try crawling the server later, or increase the
> timeout values. )
>
> One thing that should be said is that I removed and reinstalled SPS,
> WSS, and IIS, making sure that FPSE2002 was not on the box. I applied
> SP1 for both WSS and SPS. I created the portal, and then added the old
> content databases to the new portal. There are 6 databases associated
> with the portal. Is that a problem?
>
> After I added the external content sources, it says it has 1800+
> documents indexed. But, before that it only showed 70, and I have 300+
> mht and .doc files in the doclibs.
>
> Hollis D. Paul [MVP - Outlook]
> Hollis@outhousebythesound.com
> Mukilteo, WA USA
>
>



Re: The portal can't be found by search by Hollis

Hollis
Sat Jan 29 16:45:20 CST 2005

In article <OdwEZvjBFHA.3416@TK2MSFTNGP09.phx.gbl>, Shane wrote:
> I have ran into this on my virtual pc test environments. Usually the
> problem comes from the search time out. Adjusting it to 60 seconds solved
> these errors for me.
>
It worked for me, also. Thank you.

Hollis D. Paul [MVP - Outlook]
Hollis@outhousebythesound.com
Mukilteo, WA USA