Welcome to MSDN Blogs Sign in | Join | Help

Top 3 issues and workarounds for Search in SharePoint 2007 Beta 2 Tech Refresh

1. Before running the B2TR Patch, you must stop and disable the SharePoint Search Service

 

For Windows SharePoint Services 3.0:

Before starting the installation, ensure that you have stopped the “Windows SharePoint Services Search” service on *all* search servers from the “Services on Server” page in Central Administration. Failure to stop the service will cause search not to work on the upgraded farm. For more information see the B2TR Installation documentation at http://blogs.msdn.com/sharepoint/archive/2006/09/12/750127.aspx.

 

For Microsoft Office SharePoint Server 2007:

Before starting the installation, ensure that you have disabled and stopped the “Office SharePoint Server Search” service from the Service Control Manager on *all* the servers in the farm. Failure to disable and stop the service might cause you to lose the crawled data and require an index reset to recover. For more information, see the B2TR Installation documentation at http://blogs.msdn.com/sharepoint/archive/2006/09/12/750127.aspx. For other known issues related to MOSS 2007 Search beta, go to the readme file at http://officebeta.iponet.net/search/redir.aspx?assetid=FX101667211033&QueryID=TIFAYFpTT0&respos=7&rt=2.

 

2. Configuring the propagation share

 

After upgrading from Beta 2 to B2TR, or after creating a new SSP, or after adding a new query server to a farm, if your Office SharePoint Server farm includes separate Indexing and Query servers, the shared folder for search index propagation must be reconfigured. For each query server (a server running the Office SharePoint Server Search service, and is configured to "serve search queries" only), run the command "stsadm.exe -o osearch propagationlocation <location>" where <location> is the desired file system path for the search index files.

 

After configuring the propagation share, if you see an error on the checkfarmservices.aspx page, this is likely a false alarm.

 

Additionally, when doing a backup/restore, the propagation share must be configured once again to enable propagation. This is the same procedure as the paragraph above. There is no action for backup.  Only after certain types of restores would the command have to be run.  After the following events, the propagation share would need to be reconfigured:

·         Restore a backup of a farm to new servers.  The admin will have to run the STSAdm command on each query server in the restored farm.

·         Restore a backup of the farm to the same servers, but after the operating system has been reinstalled. The admin will have to run the STSAdm command on each query server in the restored farm.

 

3. When using a MOSS 2007 Indexer to crawl content that resides on a SharePoint Portal Server 2003 server

 

You have to do two full crawls of the repository to get the correct metadata into the MOSS Search system.

 

 

Sage Kitamorn

Program Manager, SharePoint Search

Published Wednesday, October 11, 2006 4:53 AM by sptblog
Filed under: ,

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

# re: Top 3 issues and workarounds for Search in SharePoint 2007 Beta 2 Tech Refresh

Hi, I have tried to install Sharepoint Server 2007 several times.

It worked once and I was able to get Excel Services up, running and spread sheets deployed.

I start fresh. I have Virtual Server RC2, installing Windows 2003 SP1, WF runtime  components 2.2, Sql Server 2005 on a separate box. I have gone through several steps to add the guest to the domain, enable ASP 2.0 through IIS admin.

Now when I run the Sharepoint install it fails during setup with ‘OSERVER setup did not complete…’.

Is there an A-Z install procedure you can point me too?

Thank you

Doug Finke

dfinke@lab49.com

Wednesday, October 11, 2006 8:44 AM by Doug Finke

# Search Resources

I wanted to get all the Admin Search links all in one place... I realize it's not that impressive, but

Wednesday, October 11, 2006 2:33 PM by Joel Oleson's SharePoint Land

# re: Top 3 issues and workarounds for Search in SharePoint 2007 Beta 2 Tech Refresh

Hi Sage, does search work with forms Authentication and a CustomMembershipProvider in WSS 3?  Will it?  It is very important for us to support Search with our Custom Provider, and return results appropriate to the authenticated (or Anonymous) user.  We've posted our experiences with Forms Auth in the URL above.

Also, how do we prevent the indexer from searching attachments?  We use an XML attachment for a feature.  Is there anything we can do to keep it out of the search results?

Thanks

Thursday, October 12, 2006 2:31 PM by Nathan and Rajiv's Dev Center

# re: Top 3 issues and workarounds for Search in SharePoint 2007 Beta 2 Tech Refresh

Nathan and Rajiv-

I discussed your forms auth issue with my colleague Avi.  He has posted a reply directly to your blog.

There is no feature in Search in MOSS 2007 to disallow the indexing of attachments.  However, you may be able to leverage a different feature to achieve the desired effect.  

The file types list (Shared Services Administration > Search Settings > File Types) defines which file extensions are included when indexing.  To keep a particular file type out of the index, remove it from this list.  

If your xml files have a .xml extension, and want to index other xml files, consider using a unique extension for the files you intend to exclude.

Sage Kitamorn

Program Manager, SharePoint Search

Friday, October 13, 2006 5:19 PM by Sage Kitamorn

# re: Top 3 issues and workarounds for Search in SharePoint 2007 Beta 2 Tech Refresh

We are still having issues installing SharePoint Server 2007 and SharePoint Services 3.0, and based on the comments and emails I have received others are to. We first installed Windows Server 2003 R2 Standard x64 Edition, I than sent the roles on the server to just Application Server (IIS). All in all we could see SharePoint Server, we had some issues when we went to my site in which we just had a page not found. We than added the roles Domain Controller (Active Directory), DNS Server, DHCP Server and Remote access / VPN server.

I am now getting the following Server Error in ‘/’ Application

Security Exception

Description: The application attempted to perform an operation not allowed by the security policy. To grant the application please contact your system administrator or change the application’s trust level in the configuration file.

Exception Details: System.Security.SecurityException: Request registry access is not allowed.

Source Error:

An unhandled exception was generated during the exception of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[SecurityException: Request registry access is not allowed.]Microsoft.Win32.RegistryKey.OpenSubKey (String name, Boolean writable) +385Microsoft.Win32.Registry, GetValue (string keyname. String ValueName, Object defaultValue0 =62Microsoft.Office.InfoPath.Server.Runtime.<>c_DisplayClass1.<DeterminePremiumSku>b_0() +124Microsoft.Office.Server.Security.SecurityContext.RunAsProcess (CodeToRunElevated secureCode) +309Microsoft.Office.InfoPath.Server.Runtime.FormServer.SeterminePremiumSku () +142Microsoft.Office.InfoPath.Server.Runtime.FormServer..cctor () +31

Version Information: Microsoft .NET Framework Version:2.050727.42; ASP.NET Version: 2.0.50727.42

Sunday, October 15, 2006 10:58 AM by Kevin Tunis

# re: Top 3 issues and workarounds for Search in SharePoint 2007 Beta 2 Tech Refresh

Justa  quick question... I am trying to get search working on MOSS 2007 and I keep getting Acess Denied errors when I try to do a crawl of my site collection. The reason for this, I suspect, is tat when you enter the URL of the site collection that I want to crawl it simply redirects you, or the crawler, to the My Site page. For example, http://portal/ will redirect to http://portal/personal/jshepherd/default.aspx when what I want to crawl is http://portal/sites/<site>/Pages/default.aspx. If anyone has any idea how to get around this it would be greatly appreciated.

Thanks!

Joe

Monday, October 16, 2006 10:19 AM by Joe Shepherd

# re: Top 3 issues and workarounds for Search in SharePoint 2007 Beta 2 Tech Refresh

Thanks for the tip on excluding file extensions from the search results, Sage.  I think your suggestion will work well for our needs.

As for WSS Search with Forms Authentication, we did find some success with Avi's help.  Unfortunately, we receive the error "Your search cannot be completed because of a service error. Try your search again or contact your administrator for more information."  when anonymous in a Forms Authentication zone.  After logging in under forms authentication, search works as expected.

We will post a step-by-step guide on our blog soon.

Thanks,

Nathan and Rajiv

Monday, October 16, 2006 5:50 PM by Nathan and Rajiv

# re: Top 3 issues and workarounds for Search in SharePoint 2007 Beta 2 Tech Refresh

Sage,

Our findings have been posted to our blog.  We are still unable to see search results for anonymous users in the Forms Authentication zone.  We were also unable to get Avi's suggestion to work with NTLM in the Default zone, although reversing the zones worked for authenticated users.  

Please review with Avi and let us know what you think (and if we're doing something wrong).  Are we missing something?

Thanks,

Nathan and Rajiv

Tuesday, October 17, 2006 12:48 PM by Nathan and Rajiv

# re: Top 3 issues and workarounds for Search in SharePoint 2007 Beta 2 Tech Refresh

Sage,

With your assistance and Avi's response, we now have search working under forms auth for authenticated users.  Unfortunately, we still cannot search anonymous content under forms (as mentioned in our previous comment). We've posted details on our findings, as well as a step by step guide to forms search setup to our blog (http://www.sharepointblogs.com/nrdev/default.aspx).  Is there a way to support anonymous search?  Thank you.

Nathan and Rajiv

Wednesday, October 18, 2006 9:44 AM by Nathan and Rajiv

# re: Top 3 issues and workarounds for Search in SharePoint 2007 Beta 2 Tech Refresh

Hi Sage,

We're having some problems with duplication when the crawler indexes pages that do a "301" redirect (301 Moved Permanently). Basically the indexer does not work in this case as it would be expected from a search engine, because it indexes with the original Url (in the search results) and not the redirected one (which is the new Permanent Url for the requested page).

To further explain this situation, consider a Url such as http://mydomain/oldPage.aspx which no longer exsists because it has been moved to http://mydomain/newPage.aspx. However there are still some documents (which cannot always be updated because of various company business rules and politics), that still point to the old Url. So to handle this correctly, if the http://mydomain/oldPage.aspx is requested, a 301 redirect is performed (i.e. with status of MOVED PERMANENTLY) to the new Url (http://mydomain/newPage.aspx). From my evaluations of different search engines, when they request the old page but are redirected to the new page, the index only contains the NEW URL (since they know the page has moved permanently). However in my test with SPS Search 2007 (and 2003), the index contains 2 entries, one for the old url (because some documents are still referencing the old url) and one for the new url (since the new site structure includes the new Url). Logically the index should only contain the new Url. I know that SPS Search 2007 has duplicate collapsing, but that's not an acceptable solution for us. Is this a bug or has this been done by design? Is there a workaround for this?

Thank You.

K-Kyc

Thursday, October 19, 2006 11:16 AM by K-Kyc

# re: Top 3 issues and workarounds for Search in SharePoint 2007 Beta 2 Tech Refresh

Hello all. I have B2TR installed for Project Server 2007. Installation went without error as I followed the docs and notes. Two questions from the shared services admin I select project server and get the following error:

http://projectvpc/ssp/admin/_layouts/managepwa.aspx

ERROR

'The Project Application Service doesn't exist or is stopped. Start the Project Applicatons Service.'

Why am I getting this error and how to find/restart the Project Applications Service?

Thanks.

Friday, October 20, 2006 12:02 AM by Chad Smith

# re: Top 3 issues and workarounds for Search in SharePoint 2007 Beta 2 Tech Refresh

I can't get the search service to crawl the content. Using WSS 3.0 on a single box with SQL Server. The Gatherer produces event 2424 at each indexing cycle with the following text:

"The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.

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

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

I'm using the service account for content, which I can log into the SQL Server DB with outside of WSS.

Ideas?

Thanks,

Wes

Tuesday, October 31, 2006 1:21 PM by Wes W

# re: Top 3 issues and workarounds for Search in SharePoint 2007 Beta 2 Tech Refresh

when I click on a site from the manage project web access sites I get a lovely Error "an unexpected error has occured".  This happens for every site under my project web access virtual directories in the farm.  Now I am running MOSS 2007 and project server 2007 on the same box, but MOSS seems fine I can create site with out any problems

Tuesday, December 19, 2006 4:55 PM by James

# re: Top 3 issues and workarounds for Search in SharePoint 2007 Beta 2 Tech Refresh

I have the exact same error message that only seems to happen on a particular production environment.

I've checked, double checked, and triple checked all the permissions to make sure that's not a problem.

Seems noone has a solution to this one.

Tuesday, August 21, 2007 11:10 AM by Bryan

# re: Top 3 issues and workarounds for Search in SharePoint 2007 Beta 2 Tech Refresh

See: http://groups.google.com/group/microsoft.public.sharepoint.setup_and_administration/browse_thread/thread/b7eac47f95c90472/e162242250a73bc1%23e162242250a73bc1

Thursday, August 23, 2007 3:15 PM by Megan

# re: Top 3 issues and workarounds for Search in SharePoint 2007 Beta 2 Tech Refresh

I receive this except the search appears to work fine.  What do you say?

Event Type: Error

Event Source: Windows SharePoint Services 3 Search

Event Category: Gatherer

Event ID: 2424

Date: 8/27/2007

Time: 10:35:01 AM

User: N/A

Computer: CHI01MOSS

Description:

The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.

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

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

Monday, August 27, 2007 11:54 AM by Zune Today

# re: Top 3 issues and workarounds for Search in SharePoint 2007 Beta 2 Tech Refresh

Please can anyone help me resolving this:

The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.

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

The start address <sts3://systemd:29153/contentdbid={0977e461-48ca-4701-b975-c4d1a02aca01}> cannot be crawled.

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

Wednesday, April 02, 2008 5:00 AM by Prashanthspark

# re: Top 3 issues and workarounds for Search in SharePoint 2007 Beta 2 Tech Refresh

Hi,

I have been fighting with this issue for quite some time.

Every morning my search does not work.

I delete the sql database, rebuild the index, and it starts to work, however the next day, it will only show this error:

Your search cannot be completed because of a service error. Try your search again or contact your administrator for more information.

Sunday, September 28, 2008 7:07 PM by Edward Meshuris

Leave a Comment

(required) 
required 
(required) 
 
Page view tracker