Archive for the ‘SharePoint’ Category

Business Data Catalog – BDC

Posted: April 5, 2010 in SharePoint

SharePoint Page Types

Posted: March 26, 2010 in SharePoint

Do you know in SharePoint there are two types of pages?

In a SharePoint site each page you see is either a ghosted page or an unghosted page.

Ghosted (Uncustomized) Pages

These are the pages stored in the severs file system but not in the database. The other important thing is these files are common to all the site collections within the SharePoint server and are generally based on the "out of the box" site definition templates. Basically they are working as template files. Ghosted pages are faster since ASP.NET parser will be used to parse them and as you might know ASP.NET parser will compile the page into an assembly on the first time it is rendered, on subsequent executions the compilation is skipped since the assembly is already there.

When ghosted pages are modified by SharePoint designer then they will become unghosted pages, and then SharePoint will start using that file in the future not the file stored in the file system. A common example for this would be the “default.master” file on the “C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\Global“.

Unghosted (Customized) Pages

These are the pages which are stored on the database. Unghosted pages are specific to the SharePoint web site the page is in. If you change these files it will not affect any other site in the same SharePoint server. Unghosted pages will be parsed by the safemode parser which will not compile the pages. The only dynamic code allowed is server-side controls that are marked safe (Safe Controls, Trusted Controls).

Why Ghosting?

This allows SharePoint to,

  • Increase it’s performance by enabling caching the main site template into memory and then apply the changes that are stored in the database for the specific file.
  • Increases security by not allowing unghosted pages to run code so an attacker who injects code will not be able to crash your server.

After installing the SharePoint Server when you try to start the search service you might end up with the following error.

An unhandled exception occurred in the user interface.Exception Information: OSearch (Administrator)


An unhandled exception occurred in the user interface.Exception Information: OSearch (UserName)

If this comes don’t panic, what you need to do is when providing the username provide it with the full domain name. For example Domain.Local\Administrator.


You can find the Microsoft knowledge base article here.

At the beginning when you try to install Microsoft Office SharePoint Server (MOSS) 2007 on Windows Server 2008 R2 it will hesitate a little. So I thought to put the steps in.

Step 1 – Download the correct Setup.

You will not be able to use your normal SharePoint Setup to install MOSS on Windows 2008 R2, if you try you will see the following message appearing continuously.

Download the required version from the following Microsoft URLs.

Windows SharePoint Services 3.0 with SP2 (x86)

Windows SharePoint Services 3.0 with SP2 (x64)

Step 2 – Install MOSS using the setup.

Installation will not have any hiccups if you downloaded the correct version.

Step 3 – Configure MOSS.

When trying to configure MOSS and if your SQL Server is running in another machine which has Windows Server 2008 R2 then you will sometimes get an error saying the SQL Server is not present.

Mainly the reason for this would be that, in your SQL Server machine the Windows Firewall is turned on. Easiest step is to turn it off, but if you are worried about your security then read the other article I have on enabling a port in Windows Server 2008 R2.

After correcting the SQL related issue then you will be able to complete the MOSS configuration wizard successfully.

If you get into any more issues contact me, I will try to help you out as I can.

Improving SharePoint Look and Feel

Posted: November 16, 2009 in SharePoint
If you are thinking whether we can improve the look and feel of the SharePoint site a perfect example is the Glu Mobile site. If you visit them at you will hardly believe that it is done by SharePoint. But the truth is it is SharePoint.
If you would like to know how they did it read the following 3 articles discussing on its design and development.

SharePoint Mobile Development

Posted: November 16, 2009 in SharePoint
If you need to create a mobile view for a SharePoint site you will soon realise that the default mobile site created by SharePoint will not take you anywhere.
With its plain look and limited features you will not be able to do anything with the default view, so to give some thing valuable to your customer you need to do some development on the default mobile site.
To get more information on getting this done visit Microsoft.
Microsoft SharePoint Server has a facility to render the site content into mobile devices as well.
In default this feature will be turned off. To enable mobile access execute the following command.
STSADM.EXE -o activatefeature -name mobilityredirect -url http://ms-sharepoint-site01/m
This will create a site under the given URL without any fancy items. It will be a plain site with only basic HTML. Whenever a mobile browser tries to access the site it will be redirected to the new mobile site.
You will be able to access the mobile sites using the URL.