Archive for the ‘Search Server Express 2008’ Category

Fixing SharePoint Search Server 2008: The content index is corrupt

February 16, 2010

Another Search Server 2008 arm-wrestle.

Client was getting “Content index on Portal_Content could not be initialized. Error The content index is corrupt” in the Application event log. The full crawl was stuck in the “Crawling” state and would not stop. I tried stopping the crawl, but it again got stuck in the “Stopping” stage and would never go idle. Numerous service and machine resets also didn’t work.

I needed to reset the index content via the following:

1. Navigate to the Search Administration page
2. On the left-hand menu select “Reset all crawled content”
3. Tick “Deactivate search alerts during reset”
4. Click “Reset Now” and wait for it to complete. Your search admin page should now say zero documents in the search index
5. Start a full content crawl

Check the status page to make sure it is working.
5. Take a deep breath and

SharePoint Search Server 2008 Shared Services Provider Limitation

February 16, 2010

Search Server 2008 Standard Edition and Search Server 2008 Express Edition are only allowed one Shared Services Provider. If you want more, you need to upgrade to MOSS 2007 or SharePoint 2010. This is because both editions are limited to one server.

Having problems with an SSP on Search Server Express 2008 and thought I’d just create a new one, but no, it can’t be that simple can it… ūüôā

Search Administration Completed Crawls Shows Zero Success

August 24, 2008

This is partly related to a previous post¬†on “Sharepoint Search Stops Working With Event Id 2436“.¬† If you are diagnosing why no results are being returned, one place to check is the Shared Services Central Admin consol, in particular the “Recently completed crawls”.¬† The number in “Success” may be zero, indicating an issue with your search.

A little bit of background – Search Server automatically deletes links to documents if it can’t “find” them after three days.¬† This is to cater for server downtime of indexed content i.e. a file server is offlinen for 24 hours.¬† It is more efficient for search server to “hold on” to the indexed content, rather than remove it immediately and have to reindex it later on.¬† The unfortunate side-affect is that you might not find out that content is unavailable for three days, but we’ll assume you are keeping a close eye on all your servers ūüôā

So, if you have zero items in your crawled content, there are several things to check:

  1. Check that your crawl account has access to the crawled content.  Try logging on with that same account and seeing if you can get to your data.
  2. Check the SharePoint crawl log for issues.  Note that you can use filters to narrow down your error results.
  3. Check the event log for errors, like the one above.
  4. Check the SharePoint log for errors.

On some occasions I have had to do a full content crawl after I have fixed the underlying issue.

SharePoint Search Stops Working with Event ID 2436

July 29, 2008

My Search Server does not like me… search has stopped working *again*.¬† Another mysterious error in the event log each time a search is attempted (either incremental or full):

Event Type: Warning
Event Source: Office Server Search
Event Category: Gatherer
Event ID: 2436
Date:  29/07/2008
Time:  2:19:11 PM
User:  N/A
Computer: [deleted]
Description:
The start address <http://deleted> cannot be crawled.

Context: Application ‘SharedServicesProvider’, Catalog ‘Portal_Content’

Details:
 The parameter is incorrect.   (0x80070057)

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

and:

Event Type: Error
Event Source: Office Server Search
Event Category: Gatherer
Event ID: 2424
Date:  29/07/2008
Time:  2:19:11 PM
User:  N/A
Computer: [deleted]
Description:
The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.

Context: Application ‘SharedServicesProvider’, Catalog ‘Portal_Content’

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

I tried the following:

  1. Start a full crawl on the content source – FAIL
  2. Ensure the search services for Windows SharePoint Services Search and Office SharePoint¬†Server Search used the same search account using Central Admin/Operations/Services on Server (they didn’t before) then start a full crawl – FAIL
  3. Reset all crawled content via Search Admin and full crawl – FAIL
  4. Stop and start the Office SharePoint Server Search service – SUCCESS

This seems to have fixed the issue for now, but I’m concerned that I will just keep having the same problem ever couple of days.¬† My automated full crawl happens every night at 3am, so I’ll just have to keep an eye on the search logs I guess…

UPDATE: Unfortunately, Search Server has failed again ūüė¶¬† I have received the same problem and the same error.¬† Some more info: the catalog size is about 60,000 documents, and it does seem to occur on my nightly crawl at 3am.¬† As soon as that happens, subsequent crawls fail and after 3 days, all content disappears.¬† Guess I’ll have to open a support incident.

 

UPDATE2: At last!  After some exhaustive work with an MS Support Engineer, it seems that Search Server Express 2008 is having problems when more than one crawl is occurring on different content sources.  We have two sharepoint sites, and search server is set up to crawl both.  My main site is crawled every 10 minutes, and the second site every 30 minutes on incremental crawls.  Therefore they overlapped, and the second site was always failing its crawl.  I have since turned off the incremental (not needed Рnow only has once per day at midnight) and the errors dried up.  Hopefully this is the end of it!

According to the MS doco, you “may experience problems” if you server hardware is not powerful enough to support multiple content crawls at the same time.¬† Problem experienced – check!¬† I am not sure if this is a bug in Microsoft Search Server Express 2008, but I haven’t got any event log errors at all since turning off the secondary site content crawl.¬† Let’s hope that the end of it!

The Engineer is doing some additional research to try and find out why this causes Search Server to drop out its content.¬† My¬† hunch is that there is some randomness for which content crawl occurs first.¬† For example – if the secondary site crawl occurs first, it would stop the first crawl from working.¬† If that happened a couple of times, then search server might think the primary site is gone, and happily delete all the indexed content.¬† Just a guess though…

Disk Quotas cause SharePoint Search Site Data Web Service to Fail

July 13, 2008

More fun with Microsoft Search Server Express 2008 Рthis time with crawling content and disk quotas.  My Search installation was failing each day with the following event log entry:

Event Type: Information
Event Source: Ntfs
Event Category: Disk
Event ID: 36
Date:  11/07/2008
Time:  2:59:43 AM
User:  <Search Service account name Рdeleted>
Computer: <computer name Рdeleted>
Description:
A user hit their quota threshold on volume C:.

The user that was hitting its quota?  My Search Service account!  My setup was as follows:
C: drive, 13 Gb free, program files, Disk Quotas enabled
E: drive, 40 Gb free, index files and SharePoint databases, Disk Quotas disabled
I have a full crawl that occurs at 3am each day.¬† At about 2:58am each day a System Event entry was added to the log as above, and consequently the crawl would fail.¬† Worse than that, all future incremental crawls would also fail!¬† Because SharePoint Search automatically deletes content it can’t locate after three attempts (such as when a file is deleted under normal conditions) it removes the index entry.¬† So every index entry was being deleted, and I had zero content in my index.¬† No content, no results.¬† Drat.
The solution was to remove the Disk Quota requirements for my search service account only.  You can do this via:
1. Open Windows Explorer
2. Right-click on the Drive and select properties
3. Click the tab “Disk Quotas”
4. Remove the disk quota requirements for the search service account
After making this change, I no longer get any event log errors and my search stops falling over every day.

Microsoft Search Server Express 2008 Causes Lots of Event Log Error 1000 Entries

July 9, 2008

I am working with a client who has Microsoft Small Business Server 2003, with a Windows SharePoint Server 3.0 Extranet.  We wanted to upgrade their searching functionality so we installed Microsoft Search Server Express 2008, which worked a treat.  For one day.  Then it stopped working.  I emptied the index and did a full scheduled index, and the same thing happened Рworked for one day, then broken again.  My Application event log was filled with the following event log errors:

Event Type: Error
Event Source: Windows SharePoint Services 2.0
Event Category: None
Event ID: 1000
Date:  9/07/2008
Time:  9:02:57 PM
User:  N/A
Computer: AHA001
Description:
#30002: Error 5 opening registry key “SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\Secure\ConfigDb”.

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

Event Type: Error
Event Source: Windows SharePoint Services 2.0
Event Category: None
Event ID: 1000
Date:  9/07/2008
Time:  9:02:57 PM
User:  N/A
Computer: AHA001
Description:
   (#5: Access is denied.)

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

and by “filled”, I mean 10 of these events every 5 seconds!¬† After messing around for a couple of hours, I pushed this straight to Microsoft support.¬† Give it to the experts to sort out (especially on a Production site – bwaaaaark bwaaaark chicken!).

The reply from MS support was to create a new Shared Services Provider – good enough for me!¬† I tried to delete the existing Shared Services Provider, but of course you are only allowed one in WSS 3.0 so it wouldn’t let me delete the SSP.¬† Cue STSADM.exe with the command:

stsadm -o deletessp -title <SSP Name> -force

and then I was free to create a new SSP via the web interface.  It automatically added all my existing WSS 3.0 sites to the list of sites sharing services, and I could successfully start a crawl on the content I wanted.

However, the event log errors remained… hmmmm…. the Event Source says “Windows SharePoint Services 2.0”, that doesn’t look right!¬† Obviously left over from previous install – I have WSS 3.0 and MS Search Server, heck I don’t need that!¬† After carefully backing up my databases (backup your backups, then backup your backups of backups…) I checked the web for uninstalling WSS 2.0 from an SBS server, didn’t find anything bad, followed the instructions here:

http://support.microsoft.com/default.aspx/kb/829114

and went bravely ahead.¬† Uninstallation successful, but oh-oh… where’s my WSS 3.0 sites!¬† Databases still there, IIS manager says the sites are there, but going to the sites gives me a whole load of nothing!¬† Uh-oh, here comes that sinking feeling…

So I head for the “SharePoint Products and Technologies Wizard” and start that up.¬† Hmmmm, no I don’t want to disconnect from my server farm… yes I like that admin site where it is, yes I do have existing content and I don’t want to remove it… so it does it’s job, steps 1-8 completed, and welcome back admin site!¬† Hello existing WSS sites!¬† And goodbye errors every 5 seconds!!!

So… my initial thoughts are that upgrading from WSS 2.0 to WSS 3.0 and then to Search Server Express 2008 causes some issue with the WSS 2.0 site… I had to uninstall WSS 2.0, and then re-run the SharePoint config wizard to restore everything to its rightful place.¬† I could then do a full crawl, and get results back from my search.¬† Huzzah!