During the update, you can run into the following exception: Exception: System.Data.SqlClient.SqlException: Address Windowing Extensions (AWE) is not supported in this edition of SQL Server. Configuration option ‘show advanced options’ changed from 0 to 1. Run the RECONFIGURE statement to install. To solve the issue and be able to install the SP2 to your SharePoint Servers, you will need to disable the AWE option in the SQL server properties. If you like, you can switch it back on after the update.

Changes There are Excel files, which list all changes by the SP2 WSS SP2 Office Servers SP2 And the KB article, with more information: Description of Windows SharePoint Services 3.0 SP2 and of Windows SharePoint Services 3.0 Language Pack SP2 Description of 2007 Microsoft Office servers Service Pack 2 (SP2) and of 2007 Microsoft Office servers Language Pack Service Pack 2 (SP2) And finally the downloads… Client The 2007 Microsoft Office Suite Service Pack 2

Microsoft has released a new version of the SharePoint SDK. Go and grab it 🙂 WSS 3.0 SDK Office SharePoint Server 2007 SDK So what is new in the release? WSS Expanded documentation of backup and restore features Complete documentation of Microsoft.SharePoint.Administration.Backup New documentation of the administrative object model Revised Web Part documentation More migration support Expanded and updated reference documentation MOSS Custom Federated Search Web Part with a Credentials UI Federated Search SQL Server Connector Federated Search HTML to RSS Connector Federated Search Virtual Earth Map Connector

The SP2 will be released later this month. For SharePoint there will be various improvements and new stsadm commands. new stsadm command to scan for compatibility for SharePoint 2010 (e.g. not CAML custom fields) broader support for browsers improvements to form based authentication and much more (see link above)

The next SharePoint Server will be “Microsoft SharePoint Server 2010”. No more Office in the server product names. That will make it much easier to talk about the products. We can forget SharePoint 14. Welcome SharePoint 2010! You can read the announcement at the official SharePoint Blog. The SharePoint Services will keep the name and have many new features. What exactly these features might be, is still in the dark 🙁

How often are you asked by family members or friends “I have a problem with my computer. Can you take a look at it?” A couple of times I’ve been asked to fix a CD-Rom, which has disappeared from the explorer. In the device manager it had an error code 39. Instead of letting the other fiddle with registry settings, you can tell them to install the fix “CD drive or DVD drive is missing in Windows XP or Vista”.

The SP1 has been released. You can download it here. (Release Notes) Some changes to make the deployment easier: Slipstream – You are now able to integrate the base installation with service packs (or Hotfixes) and install in a single step. Service Pack Uninstall – You are now able to uninstall only the Service Pack (without removing the whole instance) Report Builder 2.0 Click Once capability

This post is a follow up for my post “ Get default page Url”. When you access an SPWeb through a URL in your browser, you will be redirected to the default page like home.aspx. Each SPWeb has a RootFolder. And this SPFolder has a property “WelcomePage”. This property stores the relative path to the default page like “wiki pages/home.aspx”. 1: SPContext.Current.Web.RootFolder.WelcomePage

With a Control Adapter you can customize the rendering of an attached control. Certain control methods can be overridden with custom code, to make the control behave differently. Some Control Adapters for SharePoint, which already exist: Adjusting the MOSS ROBOTS meta tag for 3rd party search engines – using a Control Adapter Modifies to be WebPartZone Adapter Replaces the tag with a tag in Webpart zones Web Slice Control adapter for MOSS 2007

The Best Practice MSDN page has some interesting hints to generate better code. In this post I write about some point of that article, provide samples and fix bugs which are in the MSDN article. Caching You should only cache thread safe objects. What’s that? This means, that you should only cache objects, which can not be changed from the outside of your code. An itemCollection (as list.Items) is changed, if another user adds an item.

For months the Webpart could be installed through a solution/feature without any problems. Then I had to change something in the code. When I tried to upgrade the solution to see the changes, the Webpart could not be added to a page anymore. The assembly is deployed to the GAC through the solution. It has been upgraded. Looking at the xml file in my solution did not show any errors.

A couple of days ago Microsoft released 10 themes for SharePoint. They provided solutions for you, so that you can build features to install and deploy the themes on your SharePoint farm. The problem with the provided themes is, that they are only meant to be installed on English SharePoint sites! The path to the images is hard coded to the English LCID. Daniel Brown has already created a solution which you can install.

As I’ve mentioned earlier, the SPD can be downloaded from Microsoft for free. All you have to do is register before you can download the SharePoint Designer. So don’t wait, and get it 🙂 Please remember, that if you modify a SharePoint page, it will be stored in the database and loose its reference to the template. This is called unghosted. Joel Oleson has written a great article about this.

By now most of you should know that there is a SharePoint Diagnostics Tool. This really is a great tool, since it scans your assemblies for memory leaks. You should also know, that there is an occasion you can create a memory leak which the tool will not recognize. 1: using (var site = new SPSite(“http://yoururl”)) <span class=lnum> 2: </span>{ 3: SPWeb web = null; <span class=lnum> 4: </span> <span class=kwrd>try</span> 5: { <span class=lnum> 6: </span> web = site.

Nach derzeitiger Planung wird die erste SharePoint Usergroup in OWL am 12. Mai ab 18h in Paderborn stattfinden. Weitere Informationen wird es hier, und auf der SharePoint Community Webseite geben. Das Treffen wird in den Räumen von Net at Work stattfinden. Eine Anfahrtsbeschreibung kann hier heruntergeladen werden: –> Anfahrtsbeschreibung Themen: Business Data Catalog Nach derzeitigem Planungsstand, werde ich einen Vortrag zum Thema BDC halten. Der Business Data Catalog erlaubt die Einbindung von Daten aus anderen Systemen.