• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2561
  • Last Modified:

Sharepoint Search WSS3.0 Not Working

Hi,

I'm running Share point wss3.0 I cannot figure out how to get the search to work.

Its a single server environment (apart from the email server)
 
I've tried several different things with no avail. I shall detail where I am up to currently. Sorry for the long winded-ness but I want to be as accurate as possible!

When I tried to run a search you get the error message:
Your search cannot be completed because of a service error. Try your search again or contact your administrator for more information.

In "Central Administration > Operations > Services on Server > Windows SharePoint Services Search Service Settings" I have:
Service account = a domina admin account with sql access to the content and the search database.
Content Access Account = service account set up specifically for this it is only a member of the domain user group. in sql SharePoint has added its own membership to this account.

In the search Database =  "sql-Server"
Database name = WSS_Search_2_sql-Server     (This used to be without the 2 but I made a change along the way and it put the 2 in)
Authentication = Windows Authentication
Indexing Schedule = Hourly between 53 and 59 mins past the hour

The status of the search Service is Started.

at 53 mins past the hour I get 2 events recorded:
Log Name:      Application
Source:        Windows SharePoint Services 3
Date:          01/03/2011 15:53:00
Event ID:      5586
Task Category: Database
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SQL-01
Description:
Unknown SQL Exception 2812 occured. Additional error information from SQL Server is included below.

Could not find stored procedure 'dbo.proc_MSS_GetConfigurationProperty'.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows SharePoint Services 3" />
    <EventID Qualifiers="0">5586</EventID>
    <Level>2</Level>
    <Task>484</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-03-01T15:53:00.000000000Z" />
    <EventRecordID>38674</EventRecordID>
    <Channel>Application</Channel>
    <Computer> SQL-01</Computer>
    <Security />
  </System>
  <EventData>
    <Data>2812</Data>
    <Data>Could not find stored procedure 'dbo.proc_MSS_GetConfigurationProperty'.</Data>
  </EventData>
</Event>

AND

Log Name:      Application
Source:        Windows SharePoint Services 3
Date:          01/03/2011 15:53:00
Event ID:      6398
Task Category: Timer
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SQL-01
Description:
The Execute method of job definition Microsoft.SharePoint.Search.Administration.SPSearchJobDefinition (ID f6717ca0-f994-40e3-aa06-6150df1f92fc) threw an exception. More information is included below.

Could not find stored procedure 'dbo.proc_MSS_GetConfigurationProperty'.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows SharePoint Services 3" />
    <EventID Qualifiers="0">6398</EventID>
    <Level>2</Level>
    <Task>964</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-03-01T15:53:00.000000000Z" />
    <EventRecordID>38675</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SQL-01</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Microsoft.SharePoint.Search.Administration.SPSearchJobDefinition</Data>
    <Data>f6717ca0-f994-40e3-aa06-6150df1f92fc</Data>
    <Data>Could not find stored procedure 'dbo.proc_MSS_GetConfigurationProperty'.</Data>
  </EventData>
</Event>

I have also done this: http://jopx.blogspot.com/2007/08/solving-sharepoint-site-not-assigned-to.html 

I've also done this:
Use the following command to force upgrade.
1. Open a command prompt (start, run, cmd)
2. Change directory to <system drive>\program files\common files\microsoft
shared\web server extensions\12\bin
3. Run the command without quotes "psconfig -cmd upgrade -inplace b2b"
finally stop the  windows sharepoint search and start it again.
It will ask you to create a new database.
From
http://social.msdn.microsoft.com/Forums/eu/tfsgeneral/thread/dcbd6d9b-0adc-4b76-a25c-17471748e3a0



Then I got
 
Your search cannot be completed because this site is not assigned to an indexer. Contact your administrator for more information
Did this:
http://www.eggheadcafe.com/software/aspnet/30321277/search-function-not-working-site-is-not-assigned-to-an-indexer.aspx

And now I don’t get any errors but it doesn’t find anything. (I changed the Crawl time to 20 past the hour)

The only thing I get is at the time of the crawl I get this event in the event log:
Log Name:      Application
Source:        Windows SharePoint Services 3 Search
Date:          02/03/2011 09:20:58
Event ID:      2436
Task Category: Gatherer
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      SQL-01
Description:
The start address <sts3://SQL-01/contentdbid={73bc0b74-a3a3-490d-9202-e0a3f62b01b9}> cannot be crawled.

Context: Application 'Search index file on the search server', Catalog 'Search'

Details:
      The object was not found.   (0x80041201)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows SharePoint Services 3 Search" />
    <EventID Qualifiers="32768">2436</EventID>
    <Level>3</Level>
    <Task>3</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-03-02T09:20:58.000000000Z" />
    <EventRecordID>38790</EventRecordID>
    <Channel>Application</Channel>
    <Computer> SQL-01 </Computer>
    <Security />
  </System>
  <EventData>
    <Data>

Context: Application 'Search index file on the search server', Catalog 'Search'

Details:
      The object was not found.   (0x80041201)</Data>
    <Data>sts3:// sql-01/contentdbid={73bc0b74-a3a3-490d-9202-e0a3f62b01b9}</Data>
  </EventData>
</Event>

I’ve left it overnight to see if it does crawl a bit more or does work, but I’m getting the same thing this morning. Please help!


0
QuadrisIT
Asked:
QuadrisIT
  • 5
1 Solution
 
Rahul AgarwalTeam LeaderCommented:
Have you tried stopping all search services and then restarting them (identifying a new database name)?
0
 
navdeepmadanCommented:
1) Give the content access acount to  read only permission to content databases.
2) Switch on SQL-trace and check on permission issues.
3) Give permission on sharepoint configuration database

 or you can make it a SQL-server administrator some time.

if you are using windows 2008 server or windows 2003 server, please disable the loopback property.

http://blogs.technet.com/b/sharepointcomic/archive/2009/02/25/event-id-2436-sharepoint-search-error.aspx
0
 
QuadrisITAuthor Commented:
agarwalrahul, yes I have. Thats why in the search database its got  _2_ in the middle of it.

navdeepmadan, I am using windows 2003 server I've disabled the loopback policy. I've made the reg edit and shall let it re-boot over night (its a live server so cant do it now). I'll let you know how it goes tomorrow.

I dont fancy making the content access account sql server admin because it says explicit instructions not to:
For proper search functionality and information security, do not use an administrator account, and do not use accounts that can modify content.

0
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
QuadrisITAuthor Commented:
So the latest with this is its still broken.

I've got this error:
Log Name:      Application
Source:        Windows SharePoint Services 3 Search
Date:          04/03/2011 08:28:01
Event ID:      2436
Task Category: Gatherer
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      SQL-01.Red.local
Description:
The start address <sts3://sql-01/contentdbid={73bc0b74-a3a3-490d-9202-e0a3f62b01b9}> cannot be crawled.

Context: Application 'Search index file on the search server', Catalog 'Search'

Details:
      The object was not found.   (0x80041201)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows SharePoint Services 3 Search" />
    <EventID Qualifiers="32768">2436</EventID>
    <Level>3</Level>
    <Task>3</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-03-04T08:28:01.000000000Z" />
    <EventRecordID>39493</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SQL-01.Red.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>

Context: Application 'Search index file on the search server', Catalog 'Search'

Details:
      The object was not found.   (0x80041201)</Data>
    <Data>sts3://sql-01/contentdbid={73bc0b74-a3a3-490d-9202-e0a3f62b01b9}</Data>
  </EventData>
</Event>

That content bid number relates to the main content database, so it looks to me as if the mani content database cant be trawled.

any ideas?
0
 
QuadrisITAuthor Commented:
Alternate Access Mappings!
http://vspug.com/mcotw/2007/01/20/wssv3-search-small-business-server-amp-dns/

Basically, in the error message I was getting there is the line OBJECT not found sts3://MY-SQL-BOX/...

as it turned out I couldn't browse to http://MY-SQL-BOX

I resolved it by going to IIS and sticking a new binding in that said
type: http  
Ip Address: All Unassigned
Port: 80
Hontname: Blank

Kicked off the full content crawl by
"C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN\stsadm.exe -o spsearch -action fullcrawlstart"

Gave it 10 mins to crawl and searches started to return results!
0
 
QuadrisITAuthor Commented:
.
0
 
QuadrisITAuthor Commented:
Thanks for the help
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now