SP2 bug solved

remember the bug/issue with sp2.

after installing sp2 your MOSS installation would revert to a 180 days trial version.

today, microsoft released the solution for this problem.

Attention: Important Information on Service Pack 2

We take product quality seriously and make every effort to avoid and resolve issues that adversely impact our customers.  Unfortunately, we have recently discovered a bug with Service Pack 2 (SP2) that affects all customers that have deployed it for SharePoint Server 2007.

During the installation of SP2, a product expiration date is improperly activated. This means SharePoint will expire as though it was a trial installation 180 days after SP2 is deployed. The activation of the expiration date will not affect the normal function of SharePoint up until the expiration date passes. Furthermore, product expiration 180 days after SP2 installation will not affect customer’s data, configuration or application code but will render SharePoint inaccessible for end-users. Continue reading

Bug? When you install the 2007 Microsoft Office servers Service Pack 2, the product expiration date is activated incorrectly


During the installation of the 2007 Microsoft Office servers Service Pack 2, a product expiration date is activated incorrectly. This means that any of the products that are listed in the “Applies to” section will expire 180 days after Service Pack 2 is deployed, as if it were a trial installation. The activation of the expiration date will not affect the regular function of these products until the expiration date passes, 180 days after Service Pack 2 is deployed. If the product expires, it will not affect data, configuration, or application code. However, it will make the Office Server product inaccessible for end-users.

Office SharePoint Server Trial with Enterprise Client Access License, or a similar product, is displayed on the Convert License page.


This issue occurs because of the installation of the 2007 Microsoft Office servers Service Pack 2. All installations of this service pack will result in this issue.


To resolve this issue manually, type the product key on the Convert License Type page. To do this, follow these steps:

  1. Click Start, point to All Programs, point to Administrative Tools, and then click SharePoint 3.0 Central Administration.
  2. Click the Operations tab.
  3. Click Convert License Type.
  4. In the Enter the Product Key text box, type your product identification number, and then click OK.
  5. The License Synchronizer Job will run on all computers in the farm after a few moments. After all the computers have updated their license from the timer job, the Convert License Type page will reflect the correct license.

Value cannot be null. Parameter name: serverContext

I’ve been working with servercontect several times.

Sometimes it worked, sometimes it didn’t.
I mostly use it with Userprofiles. I think most people already saw the followin code:

SPSite currentSite = SPContext.Current.Site;
ServerContext sc = ServerContext.GetContext(currentSite);
UserProfileManager upm = new UserProfileManager(sc);

whten using this code, the above error (value …, see title) could appear.
today was such a day. I took some code from virtual development environment (with the code aboce) and placed it in my realworld development environment.

Althought the code works on the virtual dev machine, it gave me the error i didn’t want to see.

So , what was the big difference between the two: the Shared service provider.
After implementing/configuring a shared service provider, the code also worked on my real world dev machine.

So somehow the servercontect object is (strongly) related to the shared service provider !

Hope this will help other develope

Error: Export to Spreadsheet: Cannot get the list schema column proper

Tool:                WSS 3.0, MOSS 2007
Functionality:   Export to Spreadsheet on Lists
Error:                Cannot get the list schema column property from the sharepoint list
This seems to be a bug in the latest version of SharePoint package……