.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

Windows Sharepoint Services 3 search not working getting event ids 2424 and 2436.

Posted By:      Posted Date: October 26, 2010    Points: 0   Category :SharePoint

I can login with the accounts for content and the search service on the local server.

I have the loopback reg fix.

But the crawler will not crawl.

I have deleted all search databases in sql and it I have created one from scratch and setup different accounts for the content and search service.

I downloaded and installed windows sharepoint services 3 with service pack 2 on another server and when I used the same accounts that I had on the non working sharepoint install the search worked.



View Complete Post

More Related Resource Links

Windows Sharepoint Services 3 search not working getting event ids 2424 and 2436


This the default install running on Windows 2008 64 bit.

Our content database is located on the d drive and the Sharepoint services 3 install located on the c drive.

We constantly get event ids 2424 and 2436 when the index tries to run. Which is every five minutes.

I have the loopback fix in place.

This was working fine and then it stopped working. When doing a search on sharepoint we were able to pull up some data but not the newest data.

I  deleted the search database and created a new one with a new name.

I also downloaded and installed a new install of sharepoing services 3 and used the same domain accounts for the search service and the content and the index worked when I uploaded something. I was able to do a search.

I tried running a repair on the sharepoint services 3 install and it didn't work.

I hope it is not necessary to re-install everything from scratch.


Not exactly sure why I don't get id 2424 anymore but it is not there.


event ids are listed below

Log Name:      Application
Source:        Windows SharePoint Services 3 Search
Date:          11/16/2010 11:45:02 AM
Event ID:      2436
Task Category: Gathe

Windows SharePoint Services 3 Search Event ID 2424


This error started on 29 April and I cannot get rid of it...  My search works fine, both site and people.  AD profile import works fine.  Full and incremantal crawls work as scheduled.  Just that this error keeps showing up every five minutes in one of two WFE's.  The other WFE does not receive this error


I have verified all Security Configuration/Service Accounts, verified all Services on Server/Search accounts, Stopped/Restarted all search, and verified SSP accounts.  The last thing I did was verify there was an indexer attached to the SSP...

I set the diagnostic logging to verbose and the only thing that stood out around the time of the error was

System.Data.SqlClient.SqlException: Invalid object name 'AR_CacheCounters'.

SqlError: 'Invalid object name 'AR_CacheCounters'.'    Source: '.Net SqlClient Data Provider' Number: 208 State: 1 Class: 16 Procedure: 'proc_ar_GetCacheInvalidationCountersWithCount' LineNumber: 3 Server: 'SERVER'


Any suggestions?







Office Sharepoint Server Search not working but Windows Server Search is.

I am having an annoying Issue with the Sharepoint 2007 Enterprise search functionality. I cannot get the Search Centre to work, the out of the box webparts crash the page except the Searchbox when the others are closed. The event viewer shows up numerous Errors (Office Sharepoint Server - EventID 7080) returns with and the same when trying to add a search related web part (e.g. core.results, federated etc). EventID 6398 - Timer is a regular as is 7080. Details below.

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified).

Remote connections are connected, I am not 100% on the Instance name, (how would I go about checking this?)

Also I cannot access the link to SharedServices1 - Open Shared Services Admin site (not clickable), guess it's permissions but I seem to have full site permissions, I think I need SSP-Admin to make more edits to the Search, maybe this is related :s

Both Search Servers are runnig, I have tried everything I can think of to fix this and allow the Search Centre to work.

I am running Sharepoint 2007 on SQL Server 2008.

Feature Stapling and the FeatureActivated Event in Windows SharePoint Services 3.0

You can attach (or staple) a SharePoint Feature to a site definition without modifying the original site definition. Learn about issues related to using Feature Stapling with the SPFeatureReceiver.FeatureActivated event.

Full Farm Backup Fails on Windows Sharepoint Services Search Database

I am just now starting to us central administration to backup the entire sharepoint farm.  All content backups fine except for the Search Database.  In looking through the backup log, it appears that the search database may not exist.  How can I determine if the search database actually does exist and if it does not can it be recreated?

Windows Sharepoint Services Search

I am running WSS 3.0 SP1.  It appears that my database the goes along with Windows Sharepoint Services Search no longer exists.  I have no way of restoring the database.  This is causing my complete farm backup to fail with errors.  Can Windows Sharepoint Services Search be removed completely from my Farm without affecting Sharepoint and my current applications?  I want to be able to perfrom a clean (no errors) full farm backup daily. Thanks for your help!

Why does Windows Sharepoint Services Search want access to non-sharepoint databases.


I have installed a new instance of Sharepoint 2007 and am in the process of configuring all the farm services.  At the moment the farm consists of a sharepoint box and a separate sql server.  Here is the catch.  There are already some non-sharepoint databases on the sharepoint server.  The account under which Central Administration runs has dbcreator and securityadmin privileges in the database.  The Sharepoint_Config and SharePoint_AdminContent databases were created without any issues.

When I try to start the Windows Services Search, I get an "Unknown Error."  Looking in the event viewer gives the following error "The server principal "MyServerPrincipal" is not able to access the database "MyDatabase" under the current security context."  This is true, MyServerPrincipal does not have privileges to access MyDatabase, but why should it.  MyDatabase has nothing to do with sharepoint.  

In an attempt to get past this issue, I gave MyServerPrincipal public access to MyDatabase, but that resulted in an additional error saying that it lacked INSERT privileges.  This is really worriesome.  Does anyone know why Sharepoint Search configuration would try to access the non-Sharepoint database?


Thanks a lot.

how to add a Event Handling in Windows SharePoint Services


Hi all,

   how to add a Event Handling In Share Point  for particular document library or list.

    actually i saw one article for restrict the deletion  i tried that article,

   i created one class library in that i added one class and two xml files(elements.xml and    feature.xml).

Code are give Below.


class file

using System;
using System.Collections.Generic;
using System.Text;
using Microsoft.SharePoint;

namespace EventHandlerExample1
  public class CancelAnnouncementDeleteHandler : SPItemEventReceiver
    public override void ItemDeleting(SPItemEventProperties properties)
      string HandledMessage = ("Announcements can not be deleted from this list");
      properties.ErrorMessage = HandledMessage;
      properties.Cancel = true;





<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">

Event Error 3351 Windows SharePoint Services 3



I have been fighting this error on my WFE/APP Server for the last two weeks and I have followed the guidance from Microsoft but the fix did not help; the error is still there.  I have also researched a fix on the Internet but could not find anything other than the Microsoft fix.  Every morning between 12:45AM and 1:25AM I receive 11 of event ID 3351 errors on my WFE/App server.  While on my DB server I receive five Error 18456.  Every morning same time 7 days a week.

Any suggestions on how to fix the error? 

We have made no know changes to the MOSS configuration.


Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Database
Event ID: 3351
Date:  3/6/2008
Time:  12:45:30 AM
User:  N/A
Computer: SERVER
SQL database login failed. Additional error information from SQL Server is included below.

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

In the SQL Server Logs I receive Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT:  IP ADD

Getting Started with Windows SharePoint Services

Of all of the capabilities of SharePoint, I thought I would start with the most basic installation - as a corporate intranet. It is likely that we will need to discuss some of the elements of SharePoint as we go along, so this also gives us the opportunity to review these elements for future reference.

Before going into too much detail, I would like to point out that you can try the core SharePoint framework (known as Windows SharePoint Services or WSS) for free. On Microsoft's Web site you can download a trial version of Virtual PC 2004 (VPC). Using VPC, you can install the Windows 2003 Evaluation Kit and the WSS add-on. This combination will give you 45 days to evaluate the setup.

Building a Searchable Phone Directory with Windows SharePoint Services

I want to continue to build out the intranet site we've started in our previous articles. A standard item in every intranet is a staff/employee list. Most companies implementing Windows SharePoint Services (WSS) are large enough to have a database that contains all employees. We will use the aggregation features of SharePoint to include data from this database into our intranet.

New Features in Windows SharePoint Services 3.0

Windows SharePoint Services 3.0 (WSS 3.0) is the next version of WSS 2.0, released on 2007, and Microsoft Office SharePoint Server 2007 (MOSS 2007) is built on top of this. Windows SharePoint Services 3.0 takes full advantage of Microsoft ASP.NET 2.0 and the core Microsoft .NET 2.0 runtime. WSS 3.0 offers a lot of new features and programmability support. I have consolidated a list of new features and enhancements in the below section:

Take Control: Use SharePoint to Manage Your Windows Services


In this article, we show you how to integrate a Windows Services-based solution with SharePoint. The results enable you to provision, start, stop, and remove service instances through SharePoint 3.0 Central Administration.

Pav Cherny

MSDN Magazine April 2009

SharePoint: Add a Recycle Bin to Windows SharePoint Services for Easy Document Recovery


Windows SharePoint Services helps improve collaboration and workflow while protecting documents and intellectual property. But one feature is conspicuously missing - an easy way to back up and restore deleted files from document libraries. In this article, the authors take advantage of the extensibility of WSS and its server-side and client-side object models to build a restore feature that works like the Recycle Bin in Windows Explorer.

Maxim V. Karpov and Eric Schoonover

MSDN Magazine February 2005

Web Parts: Use Windows SharePoint Services as a Platform for Building Collaborative Apps, Part 2


Microsoft Office SharePoint Portal Server 2003, which is part of the Office System, lets you create and manage virtual servers, site collections, sites, workspaces, and users. You can also use the Windows SharePoint Services object model to design and implement user-targeted applications. In the second part of a two part series, the authors take a look at the WSS and SPS object models, Web Part Page anatomy, creating and deploying Web Parts, and Web Part security. They also discuss Web Part infrastructure and how to create custom Web Parts.

Jason Masterman and Ted Pattison

MSDN Magazine August 2004

SharePoint: Use Windows SharePoint Services as a Platform for Building Collaborative Applications


In this article the authors provide an in-depth examination of the architecture of SharePoint products and technologies: WSS and SPS. WSS provides the foundation for creating collaborative Web sites that support customization and personalization and SPS complements WSS by playing the role of a content aggregator. This article explains how.

Jason Masterman and Ted Pattison

MSDN Magazine July 2004

Sharepoint 2007 Search Not Working


I am pulling my hair out guys. I have tried everything i could find from this site and all other sites but have not been successful. No matter what i do I cannot get the search to work. We are using SharePoint 2007 and the search had been fine but our security team performed some patches and now I’m stuck with a dead search feature.

Any help would be immensely appreciated.

Things I have tried but did not resolve the problem:

1. Check all accounts and passwords

2. Run the SharePoint Products and Technologies Configuration Wizard

3. Reboot server reset IIS

4. Try to rebuild the index but that also fails

5. Check the Content Access Account

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend