Re: wss 3.0 Search is Killing Me
- From: "eastcoasttech" <tomd@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 1 May 2008 14:52:52 -0400
ok i've screwed around for about a week on this and finally have a
fix...(not really what i want to do but it works)
thanks to this
http://davidschrag.com/schlog/168/fixing-event-2424-after-installing-wss-30
I used the admin account for both and i was instanly in business!
"eastcoasttech" <tomd@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:eBT16G6qIHA.2292@xxxxxxxxxxxxxxxxxxxxxxx
Hello, I'm encountering the same thing on my installation. I upgraded my
2.0 installation and ever since my search no longer works. Search returns
no results or errors.
I'm running on server 2003 SP2 (for both servers) IIS & Search server is
on one box and SQL 2000 SP4 on a second database server.
no proxy of any type.
Any suggestions would be appreciated.
i also get the occasional Event ID 2436
"Mike" <angelove@xxxxxxxxxxxxxxxx> wrote in message
news:AF915A28-7422-42F2-8E6A-9C5EAF8B88A6@xxxxxxxxxxxxxxxx
After further tinkering; i'm convinced the problem is with AAM.
I've read Troy Starr's Blog on AAM but just don't get it.
I don't have a proxy service and every article I read on AAM seems to be
wrtten for big systems that use a Proxy Server.
--
Information Technology Consultant
"Mike" wrote:
I'v been Searching three weeks for answers and I've worked through every
solution I can Google, yet I still I can't get sharepoint Search to
function.
I got it to work for a few hours once. but that's it. The only error
message I get from the sharepoint server's log is the Gatherer Event
2436
Warning shown below.
Event Type: Warning
Event Source: Windows SharePoint Services 3 Search
Event Category: Gatherer
Event ID: 2436
Computer: GSPSERVER
Description: The start address
<sts3://mikeangelo.com/contentdbid={71521041-4199-4488-9019-a078f6e03c4e}>
cannot be crawled.
Context: Application 'Search index file on the search server', Catalog
'Search'
Details: The object was not found. (0x80041201)
That 's it, a contentdbid can't be crawled and an object can't be found.
How does one decypher such a warning? It makes no sense to me.
Please, Can anyone offer some guidance? All I can think of doing is
reformat, reinstall, and restore (again for the 3rd time).
--
Information Technology Consultant
.
- References:
- Re: wss 3.0 Search is Killing Me
- From: eastcoasttech
- Re: wss 3.0 Search is Killing Me
- Prev by Date: Connect to Outlook" option does not appear in Sharepoint 2003 or 2007
- Next by Date: Re: wss 3.0 Search is Killing Me
- Previous by thread: Re: wss 3.0 Search is Killing Me
- Next by thread: Re: wss 3.0 Search is Killing Me
- Index(es):
Relevant Pages
|