Pardon me for posting a question that may have already been answered...I've
searched this newsgroup but have been unable to find a solution to the
current problem.

I have an installation of SPS 2003 (Beta 2 Technical Refresh) in a small
server farm--one server running SQL Server 2000 SP3a, a second server
running SPS 2003 and acting as the web, search, index, and job server.

Within our portal, I have created a number of areas and sub-areas, and
within one of these sub-areas I have uploaded documents (Word, Excel, and
Visio) into the Document Library for that area. (As an aside, I'm not
pleased with the document management functionality--or lack thereof--in SPS
2003 unless you install the backwards-compatible document library. But
that's another story.)

What I have found is that searches on words I know to be inside one of these
documents do not return any results. In fact, the only searches that return
results are searches that include content from external web sites. (Which,
unbeknownst to me, are now being indexed simply because I created a portal
listing that references the external web site.)

Any suggestions? I have installed the Indexing Service on the
web/search/index server, made sure it is allowed as a web service extension
in IIS, and restarted the IIS services. That was two days ago, and it still
doesn't work. (I have tried to be patient.)

Thanks in advance for your help.

Regards,
Scott Lowe
Mercurion Systems, Inc.

Re: V2 TR: Document indexing apparently not functioning by Scott

Scott
Wed Aug 20 18:33:25 CDT 2003

James,

Thanks for the quick response. A perusal of the gatherer logs for the
Portal_Content index shows only a couple of errors reported:

0x80041201 - Object was not found
0x8002802B - Element was not found

The first error is reported for a number of items that I have
created--contacts lists, issues lists, and document libraries in various
areas and subareas of the portal site.

So what do you think? I'm going to check the web to see if I can find
anything on these errors. In the meantime, any help you (or anyone else)
can provide would be greatly appreciated.

Regards,
Scott Lowe
Mercurion Systems, Inc.



"James Edelen [MVP]" <jj4@mvps.org> wrote in message
news:O%23DRP61ZDHA.652@tk2msftngp13.phx.gbl...
> It defiantly should work faster than that (usually they are searchable in
15
> mins). I would check the content source gatherer logs for any information
> or indication as to why they are not indexing.
>
> --
> James Edelen
> Microsoft MVP - SharePoint Portal Server
> Microsoft MVP - Windows XP Media Center
> Microsoft Associate Expert
> Expert Zone - http://www.microsoft.com/windowsxp/expertzone
> "Scott Lowe" <sloweNOSPAM@NOSPAMmercurionsystems.com> wrote in message
> news:e9cgZF1ZDHA.1940@TK2MSFTNGP10.phx.gbl...
> > Pardon me for posting a question that may have already been
> answered...I've
> > searched this newsgroup but have been unable to find a solution to the
> > current problem.
> >
> > I have an installation of SPS 2003 (Beta 2 Technical Refresh) in a small
> > server farm--one server running SQL Server 2000 SP3a, a second server
> > running SPS 2003 and acting as the web, search, index, and job server.
> >
> > Within our portal, I have created a number of areas and sub-areas, and
> > within one of these sub-areas I have uploaded documents (Word, Excel,
and
> > Visio) into the Document Library for that area. (As an aside, I'm not
> > pleased with the document management functionality--or lack thereof--in
> SPS
> > 2003 unless you install the backwards-compatible document library. But
> > that's another story.)
> >
> > What I have found is that searches on words I know to be inside one of
> these
> > documents do not return any results. In fact, the only searches that
> return
> > results are searches that include content from external web sites.
> (Which,
> > unbeknownst to me, are now being indexed simply because I created a
portal
> > listing that references the external web site.)
> >
> > Any suggestions? I have installed the Indexing Service on the
> > web/search/index server, made sure it is allowed as a web service
> extension
> > in IIS, and restarted the IIS services. That was two days ago, and it
> still
> > doesn't work. (I have tried to be patient.)
> >
> > Thanks in advance for your help.
> >
> > Regards,
> > Scott Lowe
> > Mercurion Systems, Inc.
> >
> >
>
>



Re: V2 TR: Document indexing apparently not functioning by James

James
Thu Aug 21 12:26:19 CDT 2003

I failed to mention this in my previous post, but I would also try turnning
on logging of index successes (this is in the content source properties as
well) and then try a full reindex. Make sure that your files are actually
getting indexed. If for some reason, they are not showing up in the success
index log (or failed index log) then that the gatherer is skipping them
rather than just not indexing them properly.

--
James Edelen
Microsoft MVP - SharePoint Portal Server
Microsoft MVP - Windows XP Media Center
Microsoft Associate Expert
Expert Zone - http://www.microsoft.com/windowsxp/expertzone
"Scott Lowe" <sloweNOSPAM@NOSPAMmercurionsystems.com> wrote in message
news:Oe544N3ZDHA.1940@TK2MSFTNGP10.phx.gbl...
> James,
>
> Thanks for the quick response. A perusal of the gatherer logs for the
> Portal_Content index shows only a couple of errors reported:
>
> 0x80041201 - Object was not found
> 0x8002802B - Element was not found
>
> The first error is reported for a number of items that I have
> created--contacts lists, issues lists, and document libraries in various
> areas and subareas of the portal site.
>
> So what do you think? I'm going to check the web to see if I can find
> anything on these errors. In the meantime, any help you (or anyone else)
> can provide would be greatly appreciated.
>
> Regards,
> Scott Lowe
> Mercurion Systems, Inc.
>
>
>
> "James Edelen [MVP]" <jj4@mvps.org> wrote in message
> news:O%23DRP61ZDHA.652@tk2msftngp13.phx.gbl...
> > It defiantly should work faster than that (usually they are searchable
in
> 15
> > mins). I would check the content source gatherer logs for any
information
> > or indication as to why they are not indexing.
> >
> > --
> > James Edelen
> > Microsoft MVP - SharePoint Portal Server
> > Microsoft MVP - Windows XP Media Center
> > Microsoft Associate Expert
> > Expert Zone - http://www.microsoft.com/windowsxp/expertzone
> > "Scott Lowe" <sloweNOSPAM@NOSPAMmercurionsystems.com> wrote in message
> > news:e9cgZF1ZDHA.1940@TK2MSFTNGP10.phx.gbl...
> > > Pardon me for posting a question that may have already been
> > answered...I've
> > > searched this newsgroup but have been unable to find a solution to the
> > > current problem.
> > >
> > > I have an installation of SPS 2003 (Beta 2 Technical Refresh) in a
small
> > > server farm--one server running SQL Server 2000 SP3a, a second server
> > > running SPS 2003 and acting as the web, search, index, and job server.
> > >
> > > Within our portal, I have created a number of areas and sub-areas, and
> > > within one of these sub-areas I have uploaded documents (Word, Excel,
> and
> > > Visio) into the Document Library for that area. (As an aside, I'm not
> > > pleased with the document management functionality--or lack
thereof--in
> > SPS
> > > 2003 unless you install the backwards-compatible document library.
But
> > > that's another story.)
> > >
> > > What I have found is that searches on words I know to be inside one of
> > these
> > > documents do not return any results. In fact, the only searches that
> > return
> > > results are searches that include content from external web sites.
> > (Which,
> > > unbeknownst to me, are now being indexed simply because I created a
> portal
> > > listing that references the external web site.)
> > >
> > > Any suggestions? I have installed the Indexing Service on the
> > > web/search/index server, made sure it is allowed as a web service
> > extension
> > > in IIS, and restarted the IIS services. That was two days ago, and it
> > still
> > > doesn't work. (I have tried to be patient.)
> > >
> > > Thanks in advance for your help.
> > >
> > > Regards,
> > > Scott Lowe
> > > Mercurion Systems, Inc.
> > >
> > >
> >
> >
>
>



Re: V2 TR: Document indexing apparently not functioning by Scott

Scott
Thu Aug 21 19:19:44 CDT 2003

OK, after turning on logging for successes and exclusions, a review of the
gatherer logs shows....well, nothing decipherable.

All *.aspx pages were excluded, due to a default exclude content rule. I
would assume this is to avoid the content of the *.aspx page (the actual
code) from being indexed and included during searches. The only other
consistent errors listed were:

"Filter cannot be created, install a filter for this document" - to be
expected for Visio and Acrobat PDF files that have been loaded in the
portal. I haven't yet installed those IFilters.

"Some parts of this document cannot be accessed" - unfortunately, the
gatherer log doesn't show me an actual filename, so I don't know what's
affected.

"URL excluded due to a no-index attribute" - usually occurred with *.aspx
pages, but also with a few other entries. Again, no decipherable
information to help narrow down exactly what was being excluded.

"Restricted in file type rules" - expected for a couple of Microsoft Project
documents and some ColdFusion pages on remote web sites, since neither *.mpp
nor *.cfm are in the allowed file types for searching.

Most of the entries in the gatherer log were something like this:

Sps://vmspsweb01/site$$$category/bucketid=1/itemid=8693820d-e7df-4671-868b-5
9084059650e?MetadataOnly

How are we supposed to tell what that is? Some entries referenced a
specific file (the Microsoft Project documents excluded, for example), but
most were like the one above.

So what do you think?

Scott Lowe
Mercurion Systems, Inc.



"James Edelen [MVP]" <jj4@mvps.org> wrote in message
news:OexzYlAaDHA.1280@tk2msftngp13.phx.gbl...
> I failed to mention this in my previous post, but I would also try
turnning
> on logging of index successes (this is in the content source properties as
> well) and then try a full reindex. Make sure that your files are
actually
> getting indexed. If for some reason, they are not showing up in the
success
> index log (or failed index log) then that the gatherer is skipping them
> rather than just not indexing them properly.
>
> --
> James Edelen
> Microsoft MVP - SharePoint Portal Server
> Microsoft MVP - Windows XP Media Center
> Microsoft Associate Expert
> Expert Zone - http://www.microsoft.com/windowsxp/expertzone
> "Scott Lowe" <sloweNOSPAM@NOSPAMmercurionsystems.com> wrote in message
> news:Oe544N3ZDHA.1940@TK2MSFTNGP10.phx.gbl...
> > James,
> >
> > Thanks for the quick response. A perusal of the gatherer logs for the
> > Portal_Content index shows only a couple of errors reported:
> >
> > 0x80041201 - Object was not found
> > 0x8002802B - Element was not found
> >
> > The first error is reported for a number of items that I have
> > created--contacts lists, issues lists, and document libraries in various
> > areas and subareas of the portal site.
> >
> > So what do you think? I'm going to check the web to see if I can find
> > anything on these errors. In the meantime, any help you (or anyone
else)
> > can provide would be greatly appreciated.
> >
> > Regards,
> > Scott Lowe
> > Mercurion Systems, Inc.
> >
> >
> >
> > "James Edelen [MVP]" <jj4@mvps.org> wrote in message
> > news:O%23DRP61ZDHA.652@tk2msftngp13.phx.gbl...
> > > It defiantly should work faster than that (usually they are searchable
> in
> > 15
> > > mins). I would check the content source gatherer logs for any
> information
> > > or indication as to why they are not indexing.
> > >
> > > --
> > > James Edelen
> > > Microsoft MVP - SharePoint Portal Server
> > > Microsoft MVP - Windows XP Media Center
> > > Microsoft Associate Expert
> > > Expert Zone - http://www.microsoft.com/windowsxp/expertzone
> > > "Scott Lowe" <sloweNOSPAM@NOSPAMmercurionsystems.com> wrote in message
> > > news:e9cgZF1ZDHA.1940@TK2MSFTNGP10.phx.gbl...
> > > > Pardon me for posting a question that may have already been
> > > answered...I've
> > > > searched this newsgroup but have been unable to find a solution to
the
> > > > current problem.
> > > >
> > > > I have an installation of SPS 2003 (Beta 2 Technical Refresh) in a
> small
> > > > server farm--one server running SQL Server 2000 SP3a, a second
server
> > > > running SPS 2003 and acting as the web, search, index, and job
server.
> > > >
> > > > Within our portal, I have created a number of areas and sub-areas,
and
> > > > within one of these sub-areas I have uploaded documents (Word,
Excel,
> > and
> > > > Visio) into the Document Library for that area. (As an aside, I'm
not
> > > > pleased with the document management functionality--or lack
> thereof--in
> > > SPS
> > > > 2003 unless you install the backwards-compatible document library.
> But
> > > > that's another story.)
> > > >
> > > > What I have found is that searches on words I know to be inside one
of
> > > these
> > > > documents do not return any results. In fact, the only searches
that
> > > return
> > > > results are searches that include content from external web sites.
> > > (Which,
> > > > unbeknownst to me, are now being indexed simply because I created a
> > portal
> > > > listing that references the external web site.)
> > > >
> > > > Any suggestions? I have installed the Indexing Service on the
> > > > web/search/index server, made sure it is allowed as a web service
> > > extension
> > > > in IIS, and restarted the IIS services. That was two days ago, and
it
> > > still
> > > > doesn't work. (I have tried to be patient.)
> > > >
> > > > Thanks in advance for your help.
> > > >
> > > > Regards,
> > > > Scott Lowe
> > > > Mercurion Systems, Inc.
> > > >
> > > >
> > >
> > >
> >
> >
>
>



Re: V2 TR: Document indexing apparently not functioning by Mike

Mike
Wed Aug 27 10:06:27 CDT 2003

Wildly guessing (but with some logic behind the guess) - WSS doesn't allow
SQL searching (i.e. full-text and indexing) if you have MSDE installed. If
you did a standard WSS install (thus installing MSDE) and then later
connected to your external SQL Server, WSS would presumably think that you
were still running MSDE and would refuse to do full-text searching and
indexing.

It makes a kind of sense but what about your case ??

Mike Walsh
Helsinki
Finland
(Regretably E-mail requests for free help are ignored - please post
questions to the newsgroup(s))

"Scott Lowe" <sloweNOSPAM@NOSPAMmercurionsystems.com> wrote in message
news:%23gpxP9EbDHA.1832@TK2MSFTNGP09.phx.gbl...
> I don't know why this was the case, but upon further examination I found
> that Windows SharePoint Services was reporting that full-text searching
and
> indexing was not supported by the installed database engine. This is with
> an installation using the "small server farm" topology with one server
> running web, search, index, and job services and another server running
SQL
> 2000 SP3a.
>
> Any ideas as to why this is the case?
>
> Scott Lowe
> Mercurion Systems, Inc.
>
>
> "Scott Lowe" <sloweNOSPAM@NOSPAMmercurionsystems.com> wrote in message
> news:%23xdKZMEaDHA.1488@TK2MSFTNGP12.phx.gbl...
> > OK, after turning on logging for successes and exclusions, a review of
the
> > gatherer logs shows....well, nothing decipherable.
> >
> > All *.aspx pages were excluded, due to a default exclude content rule.
I
> > would assume this is to avoid the content of the *.aspx page (the actual
> > code) from being indexed and included during searches. The only other
> > consistent errors listed were:
> >
> > "Filter cannot be created, install a filter for this document" - to be
> > expected for Visio and Acrobat PDF files that have been loaded in the
> > portal. I haven't yet installed those IFilters.
> >
> > "Some parts of this document cannot be accessed" - unfortunately, the
> > gatherer log doesn't show me an actual filename, so I don't know what's
> > affected.
> >
> > "URL excluded due to a no-index attribute" - usually occurred with
*.aspx
> > pages, but also with a few other entries. Again, no decipherable
> > information to help narrow down exactly what was being excluded.
> >
> > "Restricted in file type rules" - expected for a couple of Microsoft
> Project
> > documents and some ColdFusion pages on remote web sites, since neither
> *.mpp
> > nor *.cfm are in the allowed file types for searching.
> >
> > Most of the entries in the gatherer log were something like this:
> >
> >
>
Sps://vmspsweb01/site$$$category/bucketid=1/itemid=8693820d-e7df-4671-868b-5
> > 9084059650e?MetadataOnly
> >
> > How are we supposed to tell what that is? Some entries referenced a
> > specific file (the Microsoft Project documents excluded, for example),
but
> > most were like the one above.
> >
> > So what do you think?
> >
> > Scott Lowe
> > Mercurion Systems, Inc.
> >
> >
> >
> > "James Edelen [MVP]" <jj4@mvps.org> wrote in message
> > news:OexzYlAaDHA.1280@tk2msftngp13.phx.gbl...
> > > I failed to mention this in my previous post, but I would also try
> > turnning
> > > on logging of index successes (this is in the content source
properties
> as
> > > well) and then try a full reindex. Make sure that your files are
> > actually
> > > getting indexed. If for some reason, they are not showing up in the
> > success
> > > index log (or failed index log) then that the gatherer is skipping
them
> > > rather than just not indexing them properly.
> > >
> > > --
> > > James Edelen
> > > Microsoft MVP - SharePoint Portal Server
> > > Microsoft MVP - Windows XP Media Center
> > > Microsoft Associate Expert
> > > Expert Zone - http://www.microsoft.com/windowsxp/expertzone
> > > "Scott Lowe" <sloweNOSPAM@NOSPAMmercurionsystems.com> wrote in message
> > > news:Oe544N3ZDHA.1940@TK2MSFTNGP10.phx.gbl...
> > > > James,
> > > >
> > > > Thanks for the quick response. A perusal of the gatherer logs for
the
> > > > Portal_Content index shows only a couple of errors reported:
> > > >
> > > > 0x80041201 - Object was not found
> > > > 0x8002802B - Element was not found
> > > >
> > > > The first error is reported for a number of items that I have
> > > > created--contacts lists, issues lists, and document libraries in
> various
> > > > areas and subareas of the portal site.
> > > >
> > > > So what do you think? I'm going to check the web to see if I can
find
> > > > anything on these errors. In the meantime, any help you (or anyone
> > else)
> > > > can provide would be greatly appreciated.
> > > >
> > > > Regards,
> > > > Scott Lowe
> > > > Mercurion Systems, Inc.
> > > >
> > > >
> > > >
> > > > "James Edelen [MVP]" <jj4@mvps.org> wrote in message
> > > > news:O%23DRP61ZDHA.652@tk2msftngp13.phx.gbl...
> > > > > It defiantly should work faster than that (usually they are
> searchable
> > > in
> > > > 15
> > > > > mins). I would check the content source gatherer logs for any
> > > information
> > > > > or indication as to why they are not indexing.
> > > > >
> > > > > --
> > > > > James Edelen
> > > > > Microsoft MVP - SharePoint Portal Server
> > > > > Microsoft MVP - Windows XP Media Center
> > > > > Microsoft Associate Expert
> > > > > Expert Zone - http://www.microsoft.com/windowsxp/expertzone
> > > > > "Scott Lowe" <sloweNOSPAM@NOSPAMmercurionsystems.com> wrote in
> message
> > > > > news:e9cgZF1ZDHA.1940@TK2MSFTNGP10.phx.gbl...
> > > > > > Pardon me for posting a question that may have already been
> > > > > answered...I've
> > > > > > searched this newsgroup but have been unable to find a solution
to
> > the
> > > > > > current problem.
> > > > > >
> > > > > > I have an installation of SPS 2003 (Beta 2 Technical Refresh) in
a
> > > small
> > > > > > server farm--one server running SQL Server 2000 SP3a, a second
> > server
> > > > > > running SPS 2003 and acting as the web, search, index, and job
> > server.
> > > > > >
> > > > > > Within our portal, I have created a number of areas and
sub-areas,
> > and
> > > > > > within one of these sub-areas I have uploaded documents (Word,
> > Excel,
> > > > and
> > > > > > Visio) into the Document Library for that area. (As an aside,
I'm
> > not
> > > > > > pleased with the document management functionality--or lack
> > > thereof--in
> > > > > SPS
> > > > > > 2003 unless you install the backwards-compatible document
library.
> > > But
> > > > > > that's another story.)
> > > > > >
> > > > > > What I have found is that searches on words I know to be inside
> one
> > of
> > > > > these
> > > > > > documents do not return any results. In fact, the only searches
> > that
> > > > > return
> > > > > > results are searches that include content from external web
sites.
> > > > > (Which,
> > > > > > unbeknownst to me, are now being indexed simply because I
created
> a
> > > > portal
> > > > > > listing that references the external web site.)
> > > > > >
> > > > > > Any suggestions? I have installed the Indexing Service on the
> > > > > > web/search/index server, made sure it is allowed as a web
service
> > > > > extension
> > > > > > in IIS, and restarted the IIS services. That was two days ago,
> and
> > it
> > > > > still
> > > > > > doesn't work. (I have tried to be patient.)
> > > > > >
> > > > > > Thanks in advance for your help.
> > > > > >
> > > > > > Regards,
> > > > > > Scott Lowe
> > > > > > Mercurion Systems, Inc.
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>



Re: V2 TR: Document indexing apparently not functioning by Michael

Michael
Thu Sep 18 00:28:42 CDT 2003

Just curious, how to solve the problem if we step into
the scenario you were talking about?

We were abel to find a word doc from Portal site, but not
from sub-site/WSS site). The word doc was stored in the
Doc Library of a sub-site/WSS site.

Thanks in advance,
Michael

>-----Original Message-----
>Wildly guessing (but with some logic behind the guess) -
WSS doesn't allow
>SQL searching (i.e. full-text and indexing) if you have
MSDE installed. If
>you did a standard WSS install (thus installing MSDE)
and then later
>connected to your external SQL Server, WSS would
presumably think that you
>were still running MSDE and would refuse to do full-text
searching and
>indexing.
>
>It makes a kind of sense but what about your case ??
>
>Mike Walsh
>Helsinki
>Finland
>(Regretably E-mail requests for free help are ignored -
please post
>questions to the newsgroup(s))
>
>"Scott Lowe" <sloweNOSPAM@NOSPAMmercurionsystems.com>
wrote in message
>news:%23gpxP9EbDHA.1832@TK2MSFTNGP09.phx.gbl...
>> I don't know why this was the case, but upon further
examination I found
>> that Windows SharePoint Services was reporting that
full-text searching
>and
>> indexing was not supported by the installed database
engine. This is with
>> an installation using the "small server farm" topology
with one server
>> running web, search, index, and job services and
another server running
>SQL
>> 2000 SP3a.
>>
>> Any ideas as to why this is the case?
>>
>> Scott Lowe
>> Mercurion Systems, Inc.
>>
>>
>> "Scott Lowe" <sloweNOSPAM@NOSPAMmercurionsystems.com>
wrote in message
>> news:%23xdKZMEaDHA.1488@TK2MSFTNGP12.phx.gbl...
>> > OK, after turning on logging for successes and
exclusions, a review of
>the
>> > gatherer logs shows....well, nothing decipherable.
>> >
>> > All *.aspx pages were excluded, due to a default
exclude content rule.
>I
>> > would assume this is to avoid the content of the
*.aspx page (the actual
>> > code) from being indexed and included during
searches. The only other
>> > consistent errors listed were:
>> >
>> > "Filter cannot be created, install a filter for this
document" - to be
>> > expected for Visio and Acrobat PDF files that have
been loaded in the
>> > portal. I haven't yet installed those IFilters.
>> >
>> > "Some parts of this document cannot be accessed" -
unfortunately, the
>> > gatherer log doesn't show me an actual filename, so
I don't know what's
>> > affected.
>> >
>> > "URL excluded due to a no-index attribute" - usually
occurred with
>*.aspx
>> > pages, but also with a few other entries. Again, no
decipherable
>> > information to help narrow down exactly what was
being excluded.
>> >
>> > "Restricted in file type rules" - expected for a
couple of Microsoft
>> Project
>> > documents and some ColdFusion pages on remote web
sites, since neither
>> *.mpp
>> > nor *.cfm are in the allowed file types for
searching.
>> >
>> > Most of the entries in the gatherer log were
something like this:
>> >
>> >
>>
>Sps://vmspsweb01/site$$$category/bucketid=1/itemid=869382
0d-e7df-4671-868b-5
>> > 9084059650e?MetadataOnly
>> >
>> > How are we supposed to tell what that is? Some
entries referenced a
>> > specific file (the Microsoft Project documents
excluded, for example),
>but
>> > most were like the one above.
>> >
>> > So what do you think?
>> >
>> > Scott Lowe
>> > Mercurion Systems, Inc.
>> >
>> >
>> >
>> > "James Edelen [MVP]" <jj4@mvps.org> wrote in message
>> > news:OexzYlAaDHA.1280@tk2msftngp13.phx.gbl...
>> > > I failed to mention this in my previous post, but
I would also try
>> > turnning
>> > > on logging of index successes (this is in the
content source
>properties
>> as
>> > > well) and then try a full reindex. Make sure
that your files are
>> > actually
>> > > getting indexed. If for some reason, they are not
showing up in the
>> > success
>> > > index log (or failed index log) then that the
gatherer is skipping
>them
>> > > rather than just not indexing them properly.
>> > >
>> > > --
>> > > James Edelen
>> > > Microsoft MVP - SharePoint Portal Server
>> > > Microsoft MVP - Windows XP Media Center
>> > > Microsoft Associate Expert
>> > > Expert Zone -
http://www.microsoft.com/windowsxp/expertzone
>> > > "Scott Lowe"
<sloweNOSPAM@NOSPAMmercurionsystems.com> wrote in message
>> > > news:Oe544N3ZDHA.1940@TK2MSFTNGP10.phx.gbl...
>> > > > James,
>> > > >
>> > > > Thanks for the quick response. A perusal of the
gatherer logs for
>the
>> > > > Portal_Content index shows only a couple of
errors reported:
>> > > >
>> > > > 0x80041201 - Object was not found
>> > > > 0x8002802B - Element was not found
>> > > >
>> > > > The first error is reported for a number of
items that I have
>> > > > created--contacts lists, issues lists, and
document libraries in
>> various
>> > > > areas and subareas of the portal site.
>> > > >
>> > > > So what do you think? I'm going to check the
web to see if I can
>find
>> > > > anything on these errors. In the meantime, any
help you (or anyone
>> > else)
>> > > > can provide would be greatly appreciated.
>> > > >
>> > > > Regards,
>> > > > Scott Lowe
>> > > > Mercurion Systems, Inc.
>> > > >
>> > > >
>> > > >
>> > > > "James Edelen [MVP]" <jj4@mvps.org> wrote in
message
>> > > > news:O%23DRP61ZDHA.652@tk2msftngp13.phx.gbl...
>> > > > > It defiantly should work faster than that
(usually they are
>> searchable
>> > > in
>> > > > 15
>> > > > > mins). I would check the content source
gatherer logs for any
>> > > information
>> > > > > or indication as to why they are not indexing.
>> > > > >
>> > > > > --
>> > > > > James Edelen
>> > > > > Microsoft MVP - SharePoint Portal Server
>> > > > > Microsoft MVP - Windows XP Media Center
>> > > > > Microsoft Associate Expert
>> > > > > Expert Zone -
http://www.microsoft.com/windowsxp/expertzone
>> > > > > "Scott Lowe"
<sloweNOSPAM@NOSPAMmercurionsystems.com> wrote in
>> message
>> > > > > news:e9cgZF1ZDHA.1940@TK2MSFTNGP10.phx.gbl...
>> > > > > > Pardon me for posting a question that may
have already been
>> > > > > answered...I've
>> > > > > > searched this newsgroup but have been unable
to find a solution
>to
>> > the
>> > > > > > current problem.
>> > > > > >
>> > > > > > I have an installation of SPS 2003 (Beta 2
Technical Refresh) in
>a
>> > > small
>> > > > > > server farm--one server running SQL Server
2000 SP3a, a second
>> > server
>> > > > > > running SPS 2003 and acting as the web,
search, index, and job
>> > server.
>> > > > > >
>> > > > > > Within our portal, I have created a number
of areas and
>sub-areas,
>> > and
>> > > > > > within one of these sub-areas I have
uploaded documents (Word,
>> > Excel,
>> > > > and
>> > > > > > Visio) into the Document Library for that
area. (As an aside,
>I'm
>> > not
>> > > > > > pleased with the document management
functionality--or lack
>> > > thereof--in
>> > > > > SPS
>> > > > > > 2003 unless you install the backwards-
compatible document
>library.
>> > > But
>> > > > > > that's another story.)
>> > > > > >
>> > > > > > What I have found is that searches on words
I know to be inside
>> one
>> > of
>> > > > > these
>> > > > > > documents do not return any results. In
fact, the only searches
>> > that
>> > > > > return
>> > > > > > results are searches that include content
from external web
>sites.
>> > > > > (Which,
>> > > > > > unbeknownst to me, are now being indexed
simply because I
>created
>> a
>> > > > portal
>> > > > > > listing that references the external web
site.)
>> > > > > >
>> > > > > > Any suggestions? I have installed the
Indexing Service on the
>> > > > > > web/search/index server, made sure it is
allowed as a web
>service
>> > > > > extension
>> > > > > > in IIS, and restarted the IIS services.
That was two days ago,
>> and
>> > it
>> > > > > still
>> > > > > > doesn't work. (I have tried to be patient.)
>> > > > > >
>> > > > > > Thanks in advance for your help.
>> > > > > >
>> > > > > > Regards,
>> > > > > > Scott Lowe
>> > > > > > Mercurion Systems, Inc.
>> > > > > >
>> > > > > >
>> > > > >
>> > > > >
>> > > >
>> > > >
>> > >
>> > >
>> >
>> >
>>
>>
>
>
>.
>

Re: V2 TR: Document indexing apparently not functioning by JED

JED
Mon Sep 22 15:26:17 CDT 2003

I am running into this exact problem. Any help would be great...
Thanks,
JED
"Michael J." <use4forums@yahoo.com> wrote in message
news:01ae01c37da5$b93b4150$a001280a@phx.gbl...
> Just curious, how to solve the problem if we step into
> the scenario you were talking about?
>
> We were abel to find a word doc from Portal site, but not
> from sub-site/WSS site). The word doc was stored in the
> Doc Library of a sub-site/WSS site.
>
> Thanks in advance,
> Michael
>
> >-----Original Message-----
> >Wildly guessing (but with some logic behind the guess) -
> WSS doesn't allow
> >SQL searching (i.e. full-text and indexing) if you have
> MSDE installed. If
> >you did a standard WSS install (thus installing MSDE)
> and then later
> >connected to your external SQL Server, WSS would
> presumably think that you
> >were still running MSDE and would refuse to do full-text
> searching and
> >indexing.
> >
> >It makes a kind of sense but what about your case ??
> >
> >Mike Walsh
> >Helsinki
> >Finland
> >(Regretably E-mail requests for free help are ignored -
> please post
> >questions to the newsgroup(s))
> >
> >"Scott Lowe" <sloweNOSPAM@NOSPAMmercurionsystems.com>
> wrote in message
> >news:%23gpxP9EbDHA.1832@TK2MSFTNGP09.phx.gbl...
> >> I don't know why this was the case, but upon further
> examination I found
> >> that Windows SharePoint Services was reporting that
> full-text searching
> >and
> >> indexing was not supported by the installed database
> engine. This is with
> >> an installation using the "small server farm" topology
> with one server
> >> running web, search, index, and job services and
> another server running
> >SQL
> >> 2000 SP3a.
> >>
> >> Any ideas as to why this is the case?
> >>
> >> Scott Lowe
> >> Mercurion Systems, Inc.
> >>
> >>
> >> "Scott Lowe" <sloweNOSPAM@NOSPAMmercurionsystems.com>
> wrote in message
> >> news:%23xdKZMEaDHA.1488@TK2MSFTNGP12.phx.gbl...
> >> > OK, after turning on logging for successes and
> exclusions, a review of
> >the
> >> > gatherer logs shows....well, nothing decipherable.
> >> >
> >> > All *.aspx pages were excluded, due to a default
> exclude content rule.
> >I
> >> > would assume this is to avoid the content of the
> *.aspx page (the actual
> >> > code) from being indexed and included during
> searches. The only other
> >> > consistent errors listed were:
> >> >
> >> > "Filter cannot be created, install a filter for this
> document" - to be
> >> > expected for Visio and Acrobat PDF files that have
> been loaded in the
> >> > portal. I haven't yet installed those IFilters.
> >> >
> >> > "Some parts of this document cannot be accessed" -
> unfortunately, the
> >> > gatherer log doesn't show me an actual filename, so
> I don't know what's
> >> > affected.
> >> >
> >> > "URL excluded due to a no-index attribute" - usually
> occurred with
> >*.aspx
> >> > pages, but also with a few other entries. Again, no
> decipherable
> >> > information to help narrow down exactly what was
> being excluded.
> >> >
> >> > "Restricted in file type rules" - expected for a
> couple of Microsoft
> >> Project
> >> > documents and some ColdFusion pages on remote web
> sites, since neither
> >> *.mpp
> >> > nor *.cfm are in the allowed file types for
> searching.
> >> >
> >> > Most of the entries in the gatherer log were
> something like this:
> >> >
> >> >
> >>
> >Sps://vmspsweb01/site$$$category/bucketid=1/itemid=869382
> 0d-e7df-4671-868b-5
> >> > 9084059650e?MetadataOnly
> >> >
> >> > How are we supposed to tell what that is? Some
> entries referenced a
> >> > specific file (the Microsoft Project documents
> excluded, for example),
> >but
> >> > most were like the one above.
> >> >
> >> > So what do you think?
> >> >
> >> > Scott Lowe
> >> > Mercurion Systems, Inc.
> >> >
> >> >
> >> >
> >> > "James Edelen [MVP]" <jj4@mvps.org> wrote in message
> >> > news:OexzYlAaDHA.1280@tk2msftngp13.phx.gbl...
> >> > > I failed to mention this in my previous post, but
> I would also try
> >> > turnning
> >> > > on logging of index successes (this is in the
> content source
> >properties
> >> as
> >> > > well) and then try a full reindex. Make sure
> that your files are
> >> > actually
> >> > > getting indexed. If for some reason, they are not
> showing up in the
> >> > success
> >> > > index log (or failed index log) then that the
> gatherer is skipping
> >them
> >> > > rather than just not indexing them properly.
> >> > >
> >> > > --
> >> > > James Edelen
> >> > > Microsoft MVP - SharePoint Portal Server
> >> > > Microsoft MVP - Windows XP Media Center
> >> > > Microsoft Associate Expert
> >> > > Expert Zone -
> http://www.microsoft.com/windowsxp/expertzone
> >> > > "Scott Lowe"
> <sloweNOSPAM@NOSPAMmercurionsystems.com> wrote in message
> >> > > news:Oe544N3ZDHA.1940@TK2MSFTNGP10.phx.gbl...
> >> > > > James,
> >> > > >
> >> > > > Thanks for the quick response. A perusal of the
> gatherer logs for
> >the
> >> > > > Portal_Content index shows only a couple of
> errors reported:
> >> > > >
> >> > > > 0x80041201 - Object was not found
> >> > > > 0x8002802B - Element was not found
> >> > > >
> >> > > > The first error is reported for a number of
> items that I have
> >> > > > created--contacts lists, issues lists, and
> document libraries in
> >> various
> >> > > > areas and subareas of the portal site.
> >> > > >
> >> > > > So what do you think? I'm going to check the
> web to see if I can
> >find
> >> > > > anything on these errors. In the meantime, any
> help you (or anyone
> >> > else)
> >> > > > can provide would be greatly appreciated.
> >> > > >
> >> > > > Regards,
> >> > > > Scott Lowe
> >> > > > Mercurion Systems, Inc.
> >> > > >
> >> > > >
> >> > > >
> >> > > > "James Edelen [MVP]" <jj4@mvps.org> wrote in
> message
> >> > > > news:O%23DRP61ZDHA.652@tk2msftngp13.phx.gbl...
> >> > > > > It defiantly should work faster than that
> (usually they are
> >> searchable
> >> > > in
> >> > > > 15
> >> > > > > mins). I would check the content source
> gatherer logs for any
> >> > > information
> >> > > > > or indication as to why they are not indexing.
> >> > > > >
> >> > > > > --
> >> > > > > James Edelen
> >> > > > > Microsoft MVP - SharePoint Portal Server
> >> > > > > Microsoft MVP - Windows XP Media Center
> >> > > > > Microsoft Associate Expert
> >> > > > > Expert Zone -
> http://www.microsoft.com/windowsxp/expertzone
> >> > > > > "Scott Lowe"
> <sloweNOSPAM@NOSPAMmercurionsystems.com> wrote in
> >> message
> >> > > > > news:e9cgZF1ZDHA.1940@TK2MSFTNGP10.phx.gbl...
> >> > > > > > Pardon me for posting a question that may
> have already been
> >> > > > > answered...I've
> >> > > > > > searched this newsgroup but have been unable
> to find a solution
> >to
> >> > the
> >> > > > > > current problem.
> >> > > > > >
> >> > > > > > I have an installation of SPS 2003 (Beta 2
> Technical Refresh) in
> >a
> >> > > small
> >> > > > > > server farm--one server running SQL Server
> 2000 SP3a, a second
> >> > server
> >> > > > > > running SPS 2003 and acting as the web,
> search, index, and job
> >> > server.
> >> > > > > >
> >> > > > > > Within our portal, I have created a number
> of areas and
> >sub-areas,
> >> > and
> >> > > > > > within one of these sub-areas I have
> uploaded documents (Word,
> >> > Excel,
> >> > > > and
> >> > > > > > Visio) into the Document Library for that
> area. (As an aside,
> >I'm
> >> > not
> >> > > > > > pleased with the document management
> functionality--or lack
> >> > > thereof--in
> >> > > > > SPS
> >> > > > > > 2003 unless you install the backwards-
> compatible document
> >library.
> >> > > But
> >> > > > > > that's another story.)
> >> > > > > >
> >> > > > > > What I have found is that searches on words
> I know to be inside
> >> one
> >> > of
> >> > > > > these
> >> > > > > > documents do not return any results. In
> fact, the only searches
> >> > that
> >> > > > > return
> >> > > > > > results are searches that include content
> from external web
> >sites.
> >> > > > > (Which,
> >> > > > > > unbeknownst to me, are now being indexed
> simply because I
> >created
> >> a
> >> > > > portal
> >> > > > > > listing that references the external web
> site.)
> >> > > > > >
> >> > > > > > Any suggestions? I have installed the
> Indexing Service on the
> >> > > > > > web/search/index server, made sure it is
> allowed as a web
> >service
> >> > > > > extension
> >> > > > > > in IIS, and restarted the IIS services.
> That was two days ago,
> >> and
> >> > it
> >> > > > > still
> >> > > > > > doesn't work. (I have tried to be patient.)
> >> > > > > >
> >> > > > > > Thanks in advance for your help.
> >> > > > > >
> >> > > > > > Regards,
> >> > > > > > Scott Lowe
> >> > > > > > Mercurion Systems, Inc.
> >> > > > > >
> >> > > > > >
> >> > > > >
> >> > > > >
> >> > > >
> >> > > >
> >> > >
> >> > >
> >> >
> >> >
> >>
> >>
> >
> >
> >.
> >