The out-of-the-box SharePoint search results web part doesn’t provide a way to get to the View Properties page for items in a document library. The search results provide a direct link to the document which will open a document in default editor registered within windows.
In the screen shot below notice that both the hyperlinked title (shown in the tool tip) and the url displayed both link to the actual document and not to the View Details page.

The goal is to generate a hyperlink that will allow the user to navigate to the properties display form for documents.

Clicking “View Properties” will take the user to the following page:

Step 1: Add a managed property for the integer ID of list items.

In order for the solution to work properly we must first create a Metadata Property Mapping for the ID of list items. SharePoint out-of-the-box does not include these identifiers in its search index.
Open the SSP
Click Search Administration
Under Queries and Results, click Metadata properties.
Click Crawled Properties:

Search for ows_id. Then edit the crawled property.

Select the checkbox at the bottom of the page to include the property in the search index:

Return to the Metadata Property Mappings screen by clicking on Metadata properties on the left side of the page.
Click New Managed Property and set the values as follows:

• Property Name: ListItemID
• Description: Numeric identifier of SharePoint List Items (i.e. documents, pictures, and custom lists).
• Type: Integer
• Add ows_id as a crawled property.

Run a full crawl of the content source

Step 2: Add the Metadata property to the search results web part

Now that the metadata property has been added to SharePoint we now need to make the property available to the search results web part. In my example I’ve added the search and search results web parts to a web part page but the same steps apply if you are editing the search results web part in the search center.
Open your search results page in edit mode.
Locate the search results web part and click Modify Shared Web Part

In the Results Query Options section, open the editor for the Selected Columns property:

Add a reference to the ListItemId property as follows:

 <Column Name="ListItemID" />

At this point the custom Metadata property we created will now be retrieved with every search query. The value will come back in the xml returned by the query servers and is just begging to be displayed somewhere on the page.

Step 3: Modify the XSL to display the hyperlink to the View Properties page.

The next step it to create a hyperlink to the View Properties page using not only the custom ListItemId Metadata property but also several other properties already available to us: url, sitename, and contentclass.

1. Click the XSL Editor button in the web part properties panel.
2. Copy the contents of the editor and paste into an XSL editor like Visual Studio .NET or any text editor.
3. Near the bottom of the XSL file paste in the following template definition just prior to the </xsl:stylesheet>tag:

<xsl:template name="DisplayViewPropertiesLink">
 <xsl:param name="itemUrl" />
 <xsl:param name="siteUrl" />
 <xsl:param name="listItemId" />
 <xsl:param name="contentclass" />
<!-- you may have issues with case, the doc lib will not matche by the substring functions, so do a translation -->
 <xsl:variable name="itemUrlLower" select="translate($itemUrl, 'ABCDEFGHIJKLMNOPQRSTUVWXYZ', 'abcdefghijklmnopqrstuvwxyz')"/>
 <xsl:variable name="siteUrlLower" select="translate($siteUrl, 'ABCDEFGHIJKLMNOPQRSTUVWXYZ', 'abcdefghijklmnopqrstuvwxyz')"/>
 <xsl:if test="$contentclass='STS_ListItem_DocumentLibrary'">
 <xsl:variable name="docLibLoc" select="substring-before(substring-after($itemUrlLower, concat($siteUrlLower, '/')), '/')" />
 <xsl:variable name="viewPropUrl" select="concat($siteUrl, '/', $docLibLoc, '/Forms/DispForm.aspx?id=', $listItemId)" />
 <xsl:text disable-output-escaping="yes">&amp;nbsp;-&amp;nbsp;</xsl:text><a href="{$viewPropUrl}">View Properties</a>
 </xsl:if>
 </xsl:template>

1. This template first checks to see if the item is part of a document library. If so, it parses out the document library name and then builds up a URL pointing to the View Properties page and outputs a hyperlink to the page.Important note: This link is hard-coded to point to the out-of-the-box View Properties page. If document libraries have custom View Properties pages, this solution will need to be modified.
2. The last step is to include a call to the new StyleSheet template. In my example, I’ve placed the call just after the rendering of the modified date:

<xsl:call-template name="DisplayString">
 <xsl:with-param name="str" select="write" />
</xsl:call-template></span>

<xsl:call-template name="DisplayViewPropertiesLink">
  <xsl:with-param name="itemUrl" select="url" />
  <xsl:with-param name="siteUrl" select="sitename" />
  <xsl:with-param name="listItemId" select="listitemid" />
  <xsl:with-param name="contentclass" select="contentclass" />
</xsl:call-template>

<xsl:call-template name="DisplayCollapsingStatusLink">

Step 4: Deploy and test

Now that the XSL StyleSheet has been modified the last step is to copy the XSL back into the web part property and save your changes. Submit a simple search for documents and verify the View Properties link appears after the date.

Special thanks to Doug Perkes  for providing this solution, and Trevor for his comment.

in these cases you can change the page title by using these tags. Add the follwing content place holder in the top of your code if not exist.

<asp:Content ContentPlaceHolderId=”PlaceHolderPageTitle” runat=”server”>

Add Title here

</asp:Content>

You can get title dynamic by add any of this tags into “PlaceHolderPageTitle”

<SharePoint:ListProperty Property=”Title” runat=”server”/>

<SharePoint:ListItemProperty Property=”Title” runat=”server”/>

<SharePoint:ProjectProperty Property=”Title” runat=”server”/>

<SharePoint:ListFormPageTitle runat=”server”/>

I found this solution here.

I didn’t want that! So after a little searching I found a solution here.

in the code view find the people and group field. You should format it as Lable and then change te value of text property to: ( in my case it was Created by)

text=”{substring-after(substring-before(substring-after(@Author, ‘ID=’), ‘&lt;’), ‘&gt;’)}”

In my case it worked !

if you copy and paste the above code, don’t forget to change the quotes and double quotes.

MMC could not create snap-in. The snap-in might not have been installed correctly.

Name: Deployment Manager

CLSID: FX:{1ac9de3e-24ae-480d-9e15-65386b76e433}

It seems that this is caused by the program either not requesting or applying elevated permissions incorrectly or not at all.

Running the Deployment Manager as an Administrator resolves this issue. To permanently fix this problem i.e not having to select Run as Administrator every time, right-click the Deployment Manager icon in the Start Menu, Select Properties, Compatibility and Tick Run this program as an administrator. Apply the changes.

I found the solution here. Thanks to Johan Pienaar.

“This operation has been canceled due to restrictions in effect on this computer. Please contact your system administrator”.

I searched and most of the solutions were for resetting default programs. Change default programs and reset IE to default . None of them did help me .

I found new solutions here.

The second solution about changing a registry key helped me. but I found the html key not in HKEY_CURRENT_USER but in

HKEY_LOCAL_MACHINE

> Software > Classes

find .htm & .html

in both change the Default String values ( in my case there were Opera.html ) to HTMLFile

save and close and after restarting outlook , links opens fine in IE.

You now that you can use a Data view to create SharePoint Forms. You choose your columns and select insert as new item and …

But there is a problem here that some validation does not work in this mode. for example DropDown or radio button required fields buttons does not validate correctly. In the other hand the good thing is that you can use your custom form action and for example commit the changes and navigate to another page.

When you use a custom web part ( Inser -> SharePoint Controls -> Custom List Form ), the good thing is that all validations work fine but you can’t redirect to another page after submitting data. The RedirectUrl property of the button also didn’t work for me. I don’t know why.

So the question is how can we have a form with complete validation and redirecting after submit ?!

I searched a lot find some solutions. I solved my problem by combining a custom form web part with a custom action button and changing in it’s code like this :

1. You use Custom List Form and Use NewItem form. Now your validation works fine and you do not need to use custom JavaScript validations.
2. to navigate to another page after submitting data don’t use the RedirectURL property of the form button.
3. Insert a Form Action button in the page and change the hide property of the previous submit button to True. Now we can use the “Navigate to page” action of the new form action button. BUT it does not validate the form correctly so you should do a little change in the code. you have access to it’s java script code.
4. the original code is like this :
   onclick=”javascript: {ddwrt:GenFireServerEvent(‘__commit’)}”
   you should change it and add this code in the middle :
   onclick=”javascript: if (!Page_ClientValidate()) return false; {ddwrt:GenFireServerEvent(‘__commit’)}”
5. for the “navigate to page” action if it didn’t work correctly. You should also change the URL in the code like this. in my case:
   onclick=”javascript: if (!Page_ClientValidate()) return false; {ddwrt:GenFireServerEvent(‘__commit;__redirect={/en/Documents/Forms/Upload.aspx}‘)}”

now save and preview your page. I did it and everything worked like a charm. GOOD LUCK !

when I do double-click on error to show the details
“Problems with this web page might prevent it from displayed properly or functioning properly.”
Detail Part shows:
“Line: 1935
Char: 4
Error: Library not Registered.
Code: 0
URL:http://server/pages/default.aspx

a small search was enough to find the problem and how to solve it.

Just open one office program and Run Office Diagnostic.

for example : Word 2007

  Office button -> Word Options -> Resources -> Diagnose

BUT in the production server you may not want to install visual studio . so how can you use this tool ?

1. In the server where you have VS 2005 installed, from VS create a new simple web site which you want to Administer. It can be a simple web site, the main idea is that we want to use WSAT to create user in the production server.
2. I am using File System to create the website and have called it CreateSQLUsers . ( Location : C:\Inetpub\wwwroot\CreateSQLUsers )
3. Click on the ASP.NET Configuration button in your Solution Explorer’s toolbox or Website menu.
   We will need the URL soon (in my case, it is… http://localhost:1347/asp.netwebadminfiles/default.aspx?applicationPhysicalPath=C:\Inetpub\wwwroot\CreateSQLUsers\&applicationUrl=/CreateSQLUsers)
4. Copy the contents of created web site to a folder in production server. ( I used the same path both in development and production server as C:\Inetpub\wwwroot\CreateSQLUser )
5. Now, go to your production server, Open IIS console.
6. Right Click on Web Sites -> New -> Web Site . Create a new web site and point it to the location where your website files is copied. ( C:\Inetpub\wwwroot\CreateSQLUser ) in my case site name is : SimpleSite on port : 200
7. Right-Click on your Web Site and New -> Virtual Directory, Click on Next, give an Alias (WebSiteAdmin) and click Next
   In the Directory text box browse to… “C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ASP.NETWebAdminFiles” and click Next, Next and Finish.
8. Right-click on WebSiteAdmin and hit properties, Click on the “ASP.NET” Tab and check ASP.NET Version as 2.0.50727 and click Ok.
9. Right-Click on WebSiteAdmin and hit properties. In the “Virtual Directory” Tab if in the “Application name” section there’s no application, Click Create.
10. Open an instance of Internet Explorer and in the Address Bar Paste the URL from the development environment… and do some changes like this :
    http://SimpleSite:200/WebSiteAdmin/default.aspx?applicationPhysicalPath=C:\Inetpub\wwwroot\CreateSQLUsers\&applicationUrl=/CreateSQLUsers
11. You should be able to see ASP.NET Web Site Administration Tool (You can bookmark this so that you don’t have to remember that string)

As you can see, we have changed the site name and port number and changed asp.netwebadminfiles to our application WebSiteAdmin.

***

NOTE :

If you encounter this error :

An error was encountered. Please return to the previous page and try again. “

System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. Parameter name: site at System.Web.Configuration.WebConfigurationHost.InitForConfiguration….

Here is reason and how to resolve :

The page responsible for opening the web.config file of the ASP.NET web application you specify is located in your ASP.NETWebAdminFiles folder, i.e. C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ASP.NETWebAdminFiles\. Then look for App_Code\WebAdminPage.cs. This much we know from the error.

On line 344 or 345 it is trying to open the configuration according to the application path you have specified in the querystring: return WebConfigurationManager.OpenMappedWebConfiguration(fileMap, path);

However, this OpenMappedWebConfiguration method has two more optional parameters, the first of which is SITE – the one we are getting the error about. So I added a third parameter to this function: return WebConfigurationManager.OpenMappedWebConfiguration(fileMap, path, “SimpleSite“); This works as a charm!!

***

The above solution was found here . also Thanks to Magician comment.

1.       From your search center, go to the Advanced Search Page
2.       Click Site Actions->Edit Page
3.       On the “Advanced Search Box” web part, click edit -> Modify Shared Web Part
4.       Expand the Properties tab
5.       In the “Properties” textbox, find <Option Name=”AllowOpContains” Value=”False”/> under root the node. If it does not exist, create it.
6.       Change value from “False” to “True” and click OK
7.       Click “Publish” to publish the page

Resources :

1. Ron Grzywacz’s Blog
2. Brendan Griffin

    private static void ClearList(SPList listToClear)

    {

        int initialItemCount = listToClear.Items.Count;

         for (int counter = 0; counter < initialItemCount; counter++)

        {

            // Always delete the list item at index 0

            SPListItem listItemToClear = listToClear.Items[0];

            listItemToClear.Delete();

        }

        listToClear.Update();

    }