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

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

Managed Properties in the Advanced Search page of Sharepoint Server 2007

Posted By:      Posted Date: April 10, 2011    Points: 0   Category :C#

Hi all,

I want to search a custom field in a SharePoint list by using the Advanced Search page. I followed this post http://interdata.cl/?p=368 and i was able to find all metadata properties without any blank.  For example, I´ve created columns called "Baseline", or "Milestone" and it works properly, but for example, "Document Code" doesn´t works.


The field shows up correctly in the Advanced Search properties, but whenever I do a search trying to specify my custom property I 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.".

if I look at the Managed property in Central administration, it tells me "Number of objects with this property: more than 350", so the data is mapped correctly to the property.


Thanks in advance,



View Complete Post

More Related Resource Links

Search Customization and Development Options in SharePoint Server 2007

Examine the powerful platform of SharePoint Server 2007 search for the end user and developer. Learn about the built-in Web Parts for search and writing search queries for your applications.

Video: Coding a Long-Running Operation Page in SharePoint Server 2007 or Windows SharePoint Services

Watch this visual how-to video as you learn to write code to mimic the default long-running operations page (the "spinning wheel") in SharePoint Server 2007 or Windows SharePoint Services 3.0. (Length: 7:56)

Coding a Long-Running Operation Page in SharePoint Server 2007 or Windows SharePoint Services 3.0 (V

Watch the video and explore code as you learn how to write code to mimic the default long-running operations page (the "spinning wheel") in SharePoint Server 2007 or Windows SharePoint Services 3.0.

Using managed metadata properties to drive SharePoint search

I would like to advance search box to offer option to select managed metadata for the search. Basically I need one more search element to the advanced search options. I have SharePoint 2010 Enterprise Server Farm and currently out of box search available. How to do it?Kenny_I

How to Make Properties Search Work in the Advanced Search page?


I work in SharePoint 2007. I have created "Advanced Search" page. It is the standard advanced search page and is created by choosing "search center" option when you "create site" in site settings.

The top part of this advanced search page has fields to enter search terms. This will search full text of documents. This part works.

Bottom part of the search page includes properties search. I know how to add or change those properties in the list. It is done through XML file which can be found in "Edit Page", "modify the web part", and it is in properties.

I have added a new property in this XML file but it does not appear in the drop-down list in the search page. I know that this property must exist and data has to be populated in at least one record for this property to show up in the drop-down list. This has been done and still the added property does not show up in the drop-down list in the search page.

What else do I need to do to make properties search work?


Thank you very much in advance for your help.

Bad URL on search results page - sharepoint 2007


Hi All,

I have a strange problem.

I am using sharepoint 2007 with the infrastructure update.

I have a production sharepoint 2007 farm, and a test sharepoint 2007 farm.  Both farms are pretty much the same.  Each has two WFE's, and a database server.  There is a production database server and a test database server. They are crawling different content databases, but the test content database is a copy of the production content database.    The only difference is that the production farm has a DNS record and different AAMs to correspond to this DNS entry (farmname.company.org)

Both have the same search scopes set up, there are about 5 that point to lists, and about 5 that point to document libraries.  When I do a search within one of the document library search scopes in both prod and dev, I get back identical results, but In production, when I hover over the the document title in the results, the URL in the bottom status bar looks like this: "http://myserver/MySite//Forms/DispForm.aspx?ID=32" (note the missing document library name)
While in test the URL looks like this:
"http://myserver/MySite/MyLibrary/Forms/DispForm.aspx?ID=32" (this is correct and works.)

I don't know if this is relevant info but I recently had to rebuild the production environme

Advanced Basics: Setting Word Document Properties the Office 2007 Way


The last time I wrote this column (March 2006), I shared an application that allows you to update all the Microsoft® Word documents in a folder and its subfolders. Each time the application finds a document in the specified path, it updates the document properties to match those you specified in the application.

Ken Getz

MSDN Magazine June 2006

SharePoint Portal Server 2001: Search and Access Disparate Data Repositories in Your Enterprise


The knowledge worker is greatly empowered if she is able to access information across the enterprise from a central access point. With the SharePoint Portal Server 2001 Search Service you can catalogue information stored in Exchange public folders, on the Web, in the file system, and even in Lotus Notes databases. This article discusses the use of ActiveX Data Objects and the Web-based Distributed Authoring and Versioning protocol for creating search solutions based on SharePoint Portal Server 2001.

Kayode Dada

MSDN Magazine April 2002

Ingest google Search Index into Sharepoint 2007


Hi Folks

 I am wondering  if there is a way to ingest google search index into SharePoint index such that when people search via SharePoint they see the Google results too… incorporated/federated inline with the SP results (not as a separate "box" ).

We have Google search in our environment and also share-point search. Share-point search for sharepoint site but Google search is for all other environments. Now i am thinking if we ingest the Google search index into share-point then may be its great deal to provide user a platform to search everything on one place.




i am at entry level administrator

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

Sharepoint 2007 Document Search and Highlight in Office 2007 and PDF


We will be implementing Document Search (DOC, DOCX, PDF, TIFF, PPT, PPTX, XLS, XLSX) for one of our customers. We were evaluating a few MOSS 2007 based solutions, and happened to visit your site.  What we intend to achieve are the following functionalities:


a.       User should be able to search through 1000s of documents which are in a Sharepoint Document Library

b.      The documents could be in English, International Languages.

c.       Each document is 70-100 pages, and therefore it is important that the Search Results show the relevant pages on which the Search Text appears (Get Highlighted) within each document . Clicking on the link will take the user to the right page.

d.      The additional requirement is Synonym search. So, I can search for

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.

Advanced Search page no found



Currently when a user attempts to conduct an advance search they recieve a page not found message. When I tried to conduct a search myself I was able to enter in my search term, but the search results came up as page not found. On closer inpection I noticed that it is droping part of the URL.


http://sitesp.ca/sites/PETL-EPFT/searchcenter/Pages/Advanced.aspx becomes http://sitesp.ca/sites/PETL/searchcenter/Pages/Advanced.aspx

Has anyone seen this before? Any help would be greatly appreaciated.


SharePoint 2007 - Consolidating everything as feature into WSP [Content Type, Page Layout, Pages, Ma


Hello –


Overview – We are building a Mobile Web Site using SharePoint 2007. The big screen site has been already built and we need to integrate the mobile site into same site collection of big screen –


·         The Mobile site will use the existing content types of existing big screen site

·         We will build a new custom Master page

Sharepoint 2007 - Wiki site - New Pages Not Inheriting Custom Master Page


I am working on a SP site (MOSS not WSS) which is heavily customised away from the OOTB layout. I need to create a Wiki site, which was going well - I've created a master page which displays the miniconsole (this was not visible with our customised layout), and made it the default master page for the site. This has been applied to the two standard pages that come with the Wiki site, however when a new page is created, it seems to inherit the default.master, rather than my custom master page - thus not showing the miniconsole.

When I have created a new page, I am able to use SharePoint Designer to attach my custom master page to it, which works perfectly, however this will not be a viable option going forward as end-users create their new wiki pages.

How can I get the new pages to inherit my master page when they are created?


SharePoint 2007 Central Admin - blank page, isapimodule error in IIS


I've got a Windows 2008 SP2 server runing x64.

When i try to access the SharePoint Central Admin site, I just get a blank page. No errors in the Windows logs, nothing showing up in the SharePoint logs. The IIS log shows a 500 error.

I enabled Failed Request Tracing for the 500 status code, which gives me the following information:

ModuleName IsapiModule

Notification 128

HttpStatus 500

HttpReason Internal Server Error

HttpSubStatus 0

ErrorCode 2147942593


Deploying custom Web Parts on SharePoint 2007 production server

I would like to develop a custom SharePoint 2007 Web Part for a client. Currently I'm using Visual Studio to deploy my solution to a test environment (since it's a SharePoint Project I choose just Build -> Deploy from the menu). What are the appropriate steps to deploy it to the production server?

I'd like keep it simple and safe (i.e. use the principle of least privilege). Therefore (if possible) avoid using stsadm, achieve this through web interface, or avoid using administrative rights.

Also, can I specify the scope of my Web Part, i.e. choose on which Web Application or Site Collection will it be installed?
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