Archive for September, 2009

Add Web Server role before installing SharePoint

September 21, 2009 1 comment

The Web Server role should be added to the server prior to installing SharePoint otherwise slipstreamed updates are not deployed correctly on Windows 2008 R2.


Having followed the instructions listed on TechNet for a Windows 2008 deployment using a slipstreamed installation source, the following error was encountered when attempting to create a Publishing site collection:

The Office SharePoint Server Standard Web application features feature must be activated at the web application level before this feature can be activated.

Looking at the version number reported by Central Administration and that shown for Microsoft.SharePoint.Portal.dll it was clear that the SP2 update had not been correctly applied; the dll was reporting the original version number whereas Central Administration reported the correct version number for SP2.

This was confirmed when running the stand-alone SP2 update packages; the update package for WSS 3.0 claimed that the update had already been applied but the Office SharePoint Server update package did not detect that SP2 had already been applied. Re-applying the SP2 update for Office SharePoint Server fixed the problem quoted above.

To prevent this from happening in the first place, add the Web Server role before installing SharePoint and the updates will be applied correctly.

For more information refer to the answer given in this TechNet post: Error trying to activate Publishing Infrastructure


SharePoint Database Sizing – a request for information

September 2, 2009 Leave a comment

When planning a deployment, one of the fundamental issues that needs to be addressed is providing sufficient capacity to accommodate the anticipated growth of the SharePoint environment. Microsoft provides some detail on best practices for capacity planning and management for SharePoint, mostly focussed on content or search database sizing and the effect upon performance.

Information on the size of SharePoint configuration databases is however decidedly thin on the ground. The second of the TechNet articles linked above lists the configuration database as being around 1.5 GB in size and states that the “configuration database will generally not grow past this size” although this is “not a hard limit”.

So this begs the question: just how large can the configuration database get? And how about the other supporting databases such as the Central Admininstration (SharePoint_AdminContent) and SSP database (SharedServices1_DB)?

And for the answer to this I’m turning to you good readers. Please vote to indicate the size of your configuration and other supporting databases so that we can all benefit from being better able to plan for the growth of SharePoint. If you have some interesting findings you’d like to share, please leave a comment.