Thursday, February 18, 2010

SharePoint List Fixed Header

The following script from

Gives the possiblity to fix the list header for large lists.

I modified the script from Kjell-Sverre Jerijærvi to adapt to the screen height.

Please change the src link to the jQuery file and the list QUID. Both are marked with grey.



src="Link to jquery.js"


<style type="text/css">


.DataGridFixedHeader { position: relative; top: expression (this.offsetParent.scrollTop);}



<script type="text/javascript">


var $table = $("TABLE[ID^='{BFD03356-0ACF-4950-9C6C-D772A31E3E46}']:first",



$table.wrap("<DIV style='OVERFLOW: auto; HEIGHT: " + (screen.height-400) + "px'></DIV>"); <!--FROZEN HEADER ROW--> $("", $table).addClass("DataGridFixedHeader");



Tuesday, February 16, 2010

SharePoint 2007 Limit/Guidelines

Here are some guideline for site objects

Site object

Guidelines for acceptable performance


Scope of impact when performance degrades

Site collection

50,000 per content database

Total farm throughput degrades as the number of site collections increases.


Site collection

150,000 per Web application

This limit is theoretical, and is dependent largely upon:

Performance of the database server on which the configuration database resides.

Performance of the Web servers in the farm.

Network bandwidth between the Web servers and the database server.

This is not a hard limit, and assumes a single database server. Your environment may not be able to host this many site collections per Web application. Distributing content databases across additional database servers can increase the effective limit of the number of site collections per Web application. You should perform testing to determine the actual effective limit in your environment.


Web site

250,000 per site collection

You can create a very large total number of Web sites by nesting the subsites. For example, 100 sites, each with 1000 subsites, is 100,000 Web sites. The maximum recommended number of sites and subsites is 125 sites with 2,000 subsites each, for a total of 250,000 sites.

Site collection


2,000 per Web site

The interface for enumerating subsites of a given Web site does not perform well as the number of subsites surpasses 2,000.

Site view


5 million per library

You can create very large document libraries by nesting folders, using standard views and site hierarchy. This value may vary depending on how documents and folders are organized, and by the type and size of documents stored.



2,000 per view

Testing indicates a reduction in performance beyond two thousand items. Using indexing on a flat folder view can improve performance.

List view

Document file size

50MB (2GB max*)

File save performance is proportional to the size of the file. The default maximum is 50 MB. This maximum is enforced by the system, but you can change it to any value up to 2 GB.

Library, file save performance


2,000 per Web site

Testing indicates a reduction in list view performance beyond two thousand entries. For more information about large lists, see White paper: Working with large lists in Office SharePoint Server 2007.

List view

Field type

256 per list

This is not a hard limit, but you might experience list view performance degradation as the number of field types in a list increases.

List view


2,000 per document library

This is not a hard limit, but you might experience library and list view performance degradation as the number of columns in a document library or list increases.

Library and list view


4,096 per list


Web Part

50 per page

This figure is an estimate based on simple Web Parts. The complexity of the Web Parts dictates how many Web Parts can be used on a page before performance is affected.


Managed path

20 per Web application

20 managed paths is a soft limit. Managed paths are cached on the Web server, and CPU resources are used to process incoming requests against the managed path list. You should test for performance before exceeding 20 managed paths in a single Web application.

Web application

Here are some guideline for search objects:

Search object

Guidelines for acceptable performance


Search indexes

One per SSP

Office SharePoint Server 2007 supports one content index per SSP. Given that we recommend a maximum of 20 SSPs per farm, a maximum of 20 content indexes is supported.

Maximum of 20 per farm

Note that an SSP can be associated with only one index server and one content index. However, an index server can be associated with multiple SSPs and have a content index for each SSP.

Indexed documents

50,000,000 per content index

Office SharePoint Server 2007 supports 50 million documents per index server. This could be divided up into multiple content indexes based on the number of SSPs associated with an index server.

Content sources

500 per SSP*

This is a hard limit enforced by the system.

Start Addresses

500 per content source*

This is a hard limit enforced by the system.


1,000,000 per SSP

This is the tested limit.


200 per site

This is a recommended limit per site. We recommend a maximum of 100 scope rules per scope.

Display groups

25 per site

These are used for a grouped display of scopes through the user interface.

Crawl rules

10,000 per SSP

We recommend a maximum 10,000 crawl rules irrespective of type.


15,000 per site

We recommend a maximum of 10 Best Bets and five synonyms per keyword.

Crawled properties

500,000 per SSP

These are properties that are discovered during a crawl.

Managed properties

100,000 per SSP

These are properties used by the search system in queries. Crawled properties are mapped to managed properties. We recommend a maximum of 100 mappings per managed property.

Authoritative pages

200 per relevance level

This is the maximum number of sites in each of the four relevance levels.

Results removal


This is the maximum recommended number of URLs that should be removed from the system in one operation.

Crawl logs


Number of individual log entries in the crawl log.

Some architecture guidelines:

Logical architecture object

Guidelines for acceptable performance


Shared Services Provider (SSP)

3 per farm (20 per farm maximum)



5* per farm

The number of zones defined for a farm is hard coded to 5.

Web application

99 per SSP

This limit includes the number of Web applications on child farms consuming resources on this SSP.

Internet Information Services (IIS) application pool

8 per Web server

Maximum number is determined by hardware capabilities.

Site collection

50,000 per Web application


Content database

100 per Web application


Site collection

50,000 per database



Monday, February 15, 2010

SharePoint Group Membership for specific site

I you want to get a list of all groups and the members in a site collection you can use this sql script.

Replace the SITE GUID with the guid of site collection for which you want this list


tp_title AS [User name],

tp_Email as [Mail address],

Title as [SharePoint group]



INNER JOIN UserInfo ON GroupMembership.MemberID=UserInfo.tp_ID and GroupMembership.SiteID=UserInfo.tp_SiteID

INNER JOIN Groups ON GroupMembership.GroupID=Groups.ID and GroupMembership.SiteID=Groups.SiteId


GroupMembership.SiteID='SITE GUID'

Friday, February 12, 2010

Office programs open documents in read-only

When you open a Microsoft Office 2003 or a 2007 Microsoft Office document in Microsoft Internet Explorer, the document opens with read-only permissions, and you cannot make changes to the document.

Source <>

    This problem can be solved depending on the office version with a registry key unter HKEY_Current_User

  • For Office XP
    HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Common\Internet\OpenDocumentsReadWriteWhileBrowsing = 1
  • For Office 2003
    HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Common\Internet\OpenDocumentsReadWriteWhileBrowsing = 1
  • For the 2007 Office system
    HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Common\Internet\OpenDocumentsReadWriteWhileBrowsing = 1
  • Browse to the key KEY_CURRENT_USER\Software\Microsoft\Office\12.0\Common\Internet


    Create a new dword


    Enter the name of the dword Value "OpenDocumentsReadWriteWhileBrowsing"


    Enter the value 1 to activate this feature.

Use you own local CSS file without admin rights

    For example if you want to change on a site or site collection some CSS format

    Like in this example the link color:

    Save this CSS setting in a file on the SharePoint site


    Upload the file to SharePoint DocLib


    Go to the site settings


    Click on "Master page"


    Choose your MyCSS.css file for an alternate CSS. And activate if needed the reset all subsites option


    All CSS format with are in the MyCSS.css file will be active.

    The "Master page" menu is only visible if the publishing feature is activated.

Beta Office 2010 Tool: Compatibility Inspector available

Brief Description

The Compatibility Inspector compares existing (legacy) code against the Microsoft Office 2010 object model to identify possible code issues.

Edit Mode for ASPX Pages

All aspx pages in SharePoint not located in the layouts directory can

be modified (edit) by extending the url


With the command &contents=1 it is possible to delete webpart from a page.

Create a WebPartPage with no navigation

    Create WebPart Page



    And configure web parts


    Download the WebPart Page


    Upload the blank.master


    Edit the ASPX File

    Change the MasterPageFile from

    "~masterurl/default.master" to


    Upload the modified ASPX file


    CheckIn to master version to get rid of the error message




InfoPath form in a WebPart

How to create a embedded InfoPath form in a normal web part page or site. This is how it can look like:


Change the web.config of the web application and add this line in the section <SafeControls>

<SafeControl Assembly="Microsoft.Office.InfoPath.Server, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c" Namespace="Microsoft.Office.InfoPath.Server.Controls" TypeName="*" Safe="True" />

Go to the site where you want to show the InfoPath forms and activate the site settings


Click on Web Parts


Click on New


Activate the InfoPath XmlFormView Assembly


And click on Populate Gallery

Now you can create a new site or web part page. The following example shows how to do this with webpart pages. Please keep in mind to use the link http://url/site?contents=1 to remove/deactivate the XmlFormView WebPart.


Create a new Page


Type the Title, URL an choose a Web Part Page layout to create. Open the Page and edit


Add a web Part


Add the XmlFormView WebPart


The WebPart is not configured. Press close


This is the result. This web part is not going to work. We need to add an other one but first disable this one.

In the page library select the webpart page and edit the properties



Click on "Open Web Part Page in maintenance view"


Select the web part and click on close

Go back to edit the web part page and add a web part


Select the XmlFormView web part again. This time you get the following message


Now modify the web part


Open the Data Binding properties


You need to have a deployed InfoPath form (see XsnLocation) and you also need a library to store the edited forms (SaveLocation). Please create them before

e.g. http://alegri-intranet/sites/site0001/FormServerTemplates/Project.xsn

e.g. http://alegri-intranet/sites/site0001/Project%20Status

Press Apply


Now we need to delete the fist web part. Edit the page in the page library



Click on "Open Web Part Page in maintenance view"


Select the right web part and click on delete

That's it.

Broken web parts

If you added a web part and can not access your site/page anymore


if you closed the web part but you want to delete the web part

type after the site/page URL the parameter ?contents=1

With this maintenance page you can delete/show, hide web part.

WepPart Page with Quicklaunch

  1. Create a webpart page in SharePoint
  2. Download the ASPX File (with the “Send To” command)
  3. Edit the ASPX file with a editor
  4. Find this lines:

<asp:Content ContentPlaceHolderId="PlaceHolderPageImage" runat="server"></asp:Content>

<asp:Content ContentPlaceHolderId="PlaceHolderLeftNavBar" runat="server"></asp:Content>

<asp:Content ContentPlaceHolderId="PlaceHolderNavSpacer" runat="server"></asp:Content>

  1. Delete this lines
  2. Upload the ASPX file

    It's working.

    To use this webpart page you can create a content type and bind this content type to a doc lib.

Sunday, February 7, 2010

Missing inclusion operators in Advanced Search

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


<root xmlns:xsi="">   

<Option Name="AllowOpContains" Value="True"/>


SharePoint Monitoring

This list shows possible events/problems which can/should be monitored


Backup failed due to timer job failure

The second stage Recycle Bin has reached 90% capacity

Backup failed due to insufficient permissions

Cannot connect to SQL Server

SQL Server database is full

Insufficient disk space

Index is corrupt

SQL Server Database Error


SharePoint Administration service is disabled

Failed to create a SharePoint site


Cannot connect to SMTP host

An error occurred while communicating with the SMTP server

Cannot resolve name of the outbound SMTP server


The Windows SharePoint Services Timer service is not running

Shared Service Provider

Enabling features failed on some sites

Administration site for the Shared Service Provider is missing

Enabling features on existing sites failed

The Office SharePoint Server Search is not running


The location specified for the disk-based cache is no longer accessible

The disk-based cache exceeded the specified limit

Cannot initialize disk-based cache because the specified location is inaccessable


A site copy operation has failed, leaving the site structure in an unusual state

A site move operation has failed, leaving the site structure in an unusual state

A site deletion operation has failed, leaving the site structure in an unusual state

Excel Services

Excel Calculation Services is not running locally

Workbook disk cache is full

Maximum memory configured for Excel Calculation Services has been exceeded

Excel Calculation Services not available

Workbook disk cache cannot be created

Memory Allocation Failed


InfoPath Forms Services calculations exceeded the maximum limit

InfoPath Forms Services user has exceeded the maximum number of actions per postback

SQL Server

Database out of space

SQL Server Database Error

Insufficient disk space


Index is corrupt

Crawler exception

Propagation failed to communicate with a query server

Query server removed from rotation

Hide New.gif


    stsadm.exe -o setproperty  -pn days-to-show-new-icon -pv X -url http://webapplication

    X means

    0 = No new.gif any more

    2 = Show the gif for two days

More then one Application.master in one farm

Make a copy of the layouts folder


Configure the virtual directories (_layouts) in IIS


Change the local path to the copy of layouts

This actions must be done on all SharePoint servers.

This describes one way. An other way is the usage of http modules to redirect to a application.master copy.

Saturday, February 6, 2010

Disable SharePoint Designer

Edit ONET.XML in Site Definition

<?xml version="1.0" encoding="utf-8"?>

<Project Title="$Resources:onet_TeamWebSite;" Revision="2" ListDir="$Resources:core,lists_Folder;" xmlns:ows="Microsoft SharePoint" DisableWebDesignFeatures="wdfopensite">

Add this Property


Hide Column in View/Edit Mode

This example shows how to configure a hidden column



No Hide possible

To Hide columns it is necessary to enable content type management for this list/library



Click on Content Type which is providing the column


Click on the Column you want to hide


The views keep on showing the "hidden" columns


It is not shown in the view or Edit Mode



With Nintex it is possible to change this hidden columns