...
>I just realised that I'd been looking in the wrong place. I had been
> altering the settings on the shared services search. I've now found
> where I can alter the content access accounts for "Windows SharePoint
> Services 3 Search" so I have tried using both my own account and
> another content one which have known good access to the central
> administration site and neither has fixed the error.
> I can't find where I can change the content sources for that search,
> so I'm still getting the errors. I've tried stopping the service and
> restarting (creating new databases etc.) but that didn't work.
> Any suggestions?
> On 10 May, 14:43, "Daniel Bugday" <itkons@gmail.com> wrote:
>> Have you tryied using another account for the crawl?
>> You could also check if something changed in the crawl content config.
>> /Daniel Bugday
>> <st3p@gmail.com> wrote in message
>> news:1178797969.631752.213540@e65g2000hsc.googlegroups.com...
>> > Yesterday I changed the URLS for my Shared Services and Central
>> > Administration sites on the MOSS2007 server so that they were not
>> > using Port Numbers and instead were using host headers. I altered the
>> > Alternate Access Mappings and everything seems fine when actually
>> > visiting the pages using the new URLs created for them.
>> > Everything that is except search. I now get the following error in
>> > eventviewer as search cannot crawl the central administration site:
>> > ---------
>> > The start address <sts3://centraladmin/contentdbid={b82597d0-f36e-4e7a-
>> > bda7-8c1a49452d51}> cannot be crawled.
>> > Context: Application 'Search index file on the search server', Catalog
>> > 'Search'
>> > Details:
>> > Access is denied. Check that the Default Content Access Account has
>> > access to this content, or add a crawl rule to crawl this content.
>> > (0x80041205)
>> > For more information, see Help and Support Center at
>> >http://go.microsoft.com/fwlink/events.asp.
>> > --------------
>> > I've added the default content access account to the centraladmin site
>> > as a reader, but that's not solved it. I tried to add "sts3://
>> > centraladmin/" in to the start address in the config for the search
>> > but it doesn't like it.
>> > Does anyone have any suggestions as to what might be wrong? Should
>> > search even be crawling the central administration pages at all?- Hide
>> > quoted text -
>>
On 11 May, 18:35, "Daniel Bugday" <itkons
@gmail.com> wrote:
> Do you have anything in the log (Eventviewer)?
> /Daniel Bugday
> <st3p@gmail.com> wrote in message
> news:1178889081.427878.147960@l77g2000hsb.googlegroups.com...
> >I just realised that I'd been looking in the wrong place. I had been
> > altering the settings on the shared services search. I've now found
> > where I can alter the content access accounts for "Windows SharePoint
> > Services 3 Search" so I have tried using both my own account and
> > another content one which have known good access to the central
> > administration site and neither has fixed the error.
> > I can't find where I can change the content sources for that search,
> > so I'm still getting the errors. I've tried stopping the service and
> > restarting (creating new databases etc.) but that didn't work.
> > Any suggestions?
> > On 10 May, 14:43, "Daniel Bugday" <itkons@gmail.com> wrote:
> >> Have you tryied using another account for the crawl?
> >> You could also check if something changed in the crawl content config.
> >> /Daniel Bugday
> >> <st3p@gmail.com> wrote in message
> >>news:1178797969.631752.213540@e65g2000hsc.googlegroups.com...
> >> > Yesterday I changed the URLS for my Shared Services and Central
> >> > Administration sites on the MOSS2007 server so that they were not
> >> > using Port Numbers and instead were using host headers. I altered the
> >> > Alternate Access Mappings and everything seems fine when actually
> >> > visiting the pages using the new URLs created for them.
> >> > Everything that is except search. I now get the following error in
> >> > eventviewer as search cannot crawl the central administration site:
> >> > ---------
> >> > The start address <sts3://centraladmin/contentdbid={b82597d0-f36e-4e7a-
> >> > bda7-8c1a49452d51}> cannot be crawled.
> >> > Context: Application 'Search index file on the search server', Catalog
> >> > 'Search'
> >> > Details:
> >> > Access is denied. Check that the Default Content Access Account has
> >> > access to this content, or add a crawl rule to crawl this content.
> >> > (0x80041205)
> >> > For more information, see Help and Support Center at
> >> >http://go.microsoft.com/fwlink/events.asp.
> >> > --------------
> >> > I've added the default content access account to the centraladmin site
> >> > as a reader, but that's not solved it. I tried to add "sts3://
> >> > centraladmin/" in to the start address in the config for the search
> >> > but it doesn't like it.
> >> > Does anyone have any suggestions as to what might be wrong? Should
> >> > search even be crawling the central administration pages at all?- Hide
> >> > quoted text -
> >> - Hide quoted text -
>
The start address <sts3://centraladmin/contentdbid={b82597d0-f36e-4e7a-
bda7-8c1a49452d51}> cannot be crawled.
Context: Application 'Search index file on the search server', Catalog
'Search'
Details:
Access is denied. Check that the Default Content Access Account has
access to this content, or add a crawl rule to crawl this content.
(0x80041205)
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
That's the full text from the event logs. Happens every 5 minutes as
that's how often the crawl is taking place. I really don't think the
search needs to crawl central admin, but I have no idea how to exclude
it. I did have a look through the registry and found that sts3://
centraladmin etc. in a key, but when I delete the key it just adds it
back in again and throws up the error.