Re: SBS 08, Event ID 2436 Windows SharePoint Services 3 Search
- From: Duder <Duder.3pvinb@xxxxxxxxxxxxx>
- Date: Mon, 30 Mar 2009 23:09:28 +0530
Sherry Jia from SBSC newsgroup offers this as a reply to this issue:
I would like to explain that this warning may occur if you are using a
FQDN
host header to crawl the site and did not setup the proper Alternate
Access
Mappings, the authentication way is set as Basic or the service account
does not have enough permission.
To troubleshoot the issue, I recommend we follow the steps below:
Suggestion 1: Disable the loopback check as below KB article.
http://support.microsoft.com/kb/896861
Suggestion 2: Check if you are using the same account as the identities
for
all the application pools in IIS and as well the services below:
a. Windows SharePoint Services Search
b. Windows SharePoint Services Timer
Suggestion 3: Check if the account has local Admin rights, DB Owner and
Security Admin on SQL Server and site Admin rights.
Suggestion 4: Check to see if you are using the Basic authentication
for
the site URL http://portal.domain.com.
If yes, change it to the Windows Authentication + NTLM. Then, do an
IISRESET.
Suggestion 5: Check to see if you have used AAM (Alternate Access
Mapping).
If not, you need to edit the AAM by removing the existing user site
(ex:
http://portal.domain.com from the default URL to Custom and type in
http://servername);
Then, run the stsadm -o execadmsvcjobs;
Stop and restart the timer service.
If the suggestions above don't help, please help us collect the
following
information for further research:
1. Has the problem ever worked? If so, what has changed?
2. Is there any problem when you try to do the search in WSS 3.0? If
there
is any error message, please take a screen shot and attach it to your
reply
or send it to us.
3. Check if the http://servername can be resolved.
4. Please first zip and then send us the trace logs located at
%ProgramFiles%\Common Files\Microsoft Shared\web server
extensions\12\LOGS.
5. Please also send us the Application Event log for further research.
My
email address is potcdata@xxxxxxxxxxxxx with subject: 43411000- Search
stopped working on SBS 2008.
6. Have you enabled the proxy settings in IE?
I'm interested in your opinion on #3 Chad. My logs show SQL
informational messages regarding access failure to sql. I wonder if we
need to add the above rights to the 2 accounts we made? If so I'll need
to find instructions on adding those.
The only other sbs 08 log errors i get are 10016 dcom's which I know
the fix for and occasional print spooler ones which SBSC has a fix for.
Overall I'm liking sbs 2008. Duder
--
Duder
------------------------------------------------------------------------
Duder's Profile: http://forums.techarena.in/members/86106.htm
View this thread: http://forums.techarena.in/small-business-server/1150530.htm
http://forums.techarena.in
.
- Follow-Ups:
- References:
- SBS 08, Event ID 2436 Windows SharePoint Services 3 Search
- From: Leythos
- Re: SBS 08, Event ID 2436 Windows SharePoint Services 3 Search
- From: Chad A. Gross
- Re: SBS 08, Event ID 2436 Windows SharePoint Services 3 Search
- From: Leythos
- Re: SBS 08, Event ID 2436 Windows SharePoint Services 3 Search
- From: Duder
- Re: SBS 08, Event ID 2436 Windows SharePoint Services 3 Search
- From: Chad A. Gross
- Re: SBS 08, Event ID 2436 Windows SharePoint Services 3 Search
- From: Leythos
- SBS 08, Event ID 2436 Windows SharePoint Services 3 Search
- Prev by Date: Re: SBS 08, Event ID 2436 Windows SharePoint Services 3 Search
- Next by Date: Re: what's gonna happen if the 75 user limit is exceeded?
- Previous by thread: Re: SBS 08, Event ID 2436 Windows SharePoint Services 3 Search
- Next by thread: Re: SBS 08, Event ID 2436 Windows SharePoint Services 3 Search
- Index(es):
Relevant Pages
|