Or am I more likely to be abducted by aliens? Well, if you installed MOSS Service Pack 2 from a download before the 29th July 2009 your production MOSS Farm could stop working in the future. This is explained in Microsoft KB 971620 and in this Microsoft blog post.

In summary, initial releases of SP2 was configured as a trial version, and unless re-installed, MOSS features will stop working 180 days after you installed SP2. The value “180″ is reported in the KB, but this value seems to be different in practice.

To determine if your MOSS Farm is at risk you can:

• Run Central Administration.
• Select Operations.
• Select Convert license type in the “Upgrade and Migration” section.

The description of “Current License” will show if you installed SP2 with the trial version problem:

You can also determine when the trial version will expire:

• Run Central Administration
• Select Application Management.
• Select Check services enabled in this farm in the “Office SharePoint Server Shared Services” section.

A warning will be displayed if you’re running the trial version:

KB 971620 contains a link to a hotfix to correct this issue. This hotfix may require you to reboot the server. Before testing if the fix was applied correctly, issue an IISRESET before running Central Administration.

Thanks to Tim at Cork County Council for pointing out this issue.

In this post I explained how to determine if your SharePoint installation is service packed, and to what level. However, the situation is a little more complex since your MOSS 2007 farm will be running Microsoft SharePoint Services 3.0 and MOSS on top.

When using Central Administration / Operations / Servers In Farm to report the version number you’re seeing the Windows SharePoint Services 3.0 version number. This will be updated when you run the Windows SharePoint Services (WSS) service pack update.

So how do you find which service pack for MOSS you’re running with? One way is to find the version number of the Microsoft.Office.Server assembly from the Windows GAC (Global Assembly Cache). To do this:

• Run the Windows Explorer.
• Navigate to \Windows\Assembly.
• Right-click the file Microsoft.Office.Server and select Properties.
• Click the Version tab.
• Take a note of the “File Version”:

Here are the version numbers for the main MOSS services packs using this technique:

Version numbers from the Microsoft.Office.Server assembly do not follow exactly those for the WSS reported version number, but there is a close correlation.

In this blog post I describe a problem whereby document libraries having multiple content types use the default content type when documents are saved regardless of the selected content type.

Well, thanks to Kevin at Dublin City Council, (that’s Dublin, Ireland) here’s a solution to this problem. It’s all to do with how you define the template for the content type using “Advanced Settings” for a content type:

First, if you “Upload a new document template” the problem described above does not occur. The correct content type will always be selected regardless of how many content types there are associated with the document library. However, your document template is not under version control and becomes more difficult to update using this option.

I normally use the “Enter the URL of an existing document template” and add the URL to a document library containing content type templates (let’s call it “Content Type Templates Library”). That way, if the content type template is updated in this document library the new version will immediately be used. This is the situation where the wrong content type will be selected.

To solve the problem (and this is where Kevin comes in), you need to associate the content types with the “Content Type Templates Library”. The documents representing the content type templates need to have the content type they are being used in. Let me give an example:

Say you’ve got two content types: “CT1″ and “CT2″ and these use document templates called “DT1.doc” and “DT2.doc” respectively. The documents “DT1.doc” and “DT2.doc” are stored in a document library called “Content Type Templates Library”. Now, you need to associate content types “CT1″ and “CT2″ with “Content Type Templates Library”. Further, “DT1.doc” must use “CT1″ and “DT2.doc” must use “CT2″.

Once this has been setup, the content types “CT1″ and “CT2″ can be associated with a document library in which users will create documents. Now, new documents created by users will have the correct content type associated with them.

The “My SharePoint Sites” links facility is designed to provide quick and easy access to all sites to which you are member:

This facility is very well described in the blog post Overview of My SharePoint Sites and how the data is populated by Jerry Orman.

Sites in which you are a member are included in the list. What does “member” mean? In the simple case, it means that you belong to the group
designated as the “members” group for the site.

When you create a site and choose unique permissions you can specify a new group for site members. You can also change the “Members of this site” group through “Setup Groups for this Site” or create another members group:

Now, what’s strange is that it is the group “Project N Members” that is deemed to be a “members” group when it is created as a “Members of this Site” group and regardless of how and where it is used in the future.

Therefore, if you use this dialog to select another group that was not created as a “Members of this Site” (say “Project N Visitors”), the site will not appear in the “My SharePoint Sites” list.

Conversely, if you select “Project N Members” as the “Visitors to this Site”, the site will appear in the “My SharePoints Sites” list.

Note that when editing a group you do not get an opportunity to set the “Is Member” flag. However, if you look at the “Groups” table in the content SQL Server database you’ll find a “flags” column. A value of “0″ means the group is a “Members” group, and “1″ for other groups:

Please note I’m only showing the SQL Server Database table for illustration. Please do not modify the table contents directly.

Here’s some additional information to this post about this subject.

An alternative to our solution for while loops in SharePoint Designer workflows have been previously proposed based on setting a workflow to start when an item is changed. This gets over the problem of how to get a workflow to restart itself (which we do with the “Restart This Workflow” action). You can find a description of how to do this here: http://sharepointmagazine.net/technical/development/the-dog-ate-my-task-use-sharepoint-designer-to-email-daily-task-reminders

However, the technique of a workflow restarting itself when an item changes will not work with SP2. Take a look at this Microsoft post:

http://blogs.msdn.com/sharepointdesigner/archive/2009/07/13/service-pack-2-prevents-an-on-change-workflow-from-starting-itself.aspx

In SP2 a workflow cannot restart itself recursively, and so this will break stateful workflows written in this way. Seems strange that Microsoft would introduce a breaking change when using these techniques have been well documented.

Amongst several significant limitations with SharePoint Designer workflows, perhaps the most important is the lack of looping. Therefore, expressing processes like “while not approved, rework” becomes difficult.

We have published a paper that describes how to implement while loops by emulating stateful workflows in Microsoft SharePoint Designer. You can download the paper here (PDF, Oct 2009). The technique uses our “Restart this workflow” custom action, which is part of our “Custom Activity Pack” which can be downloaded here for free.

Our Custom Activity Pack contains actions that can be installed for use in Microsoft SharePoint Designer workflows. The latest version includes an action for sending documents and items to a Records Center site collection directly from your workflows.

The Custom Activity Pack is free and can be downloaded from our web site at http://www.nickgrattan.net/Downloads.aspx.

Other custom actions in this pack include:

• Start Workflow – Start another workflow for the item or document and return.
• Call Workflow – Start another workflow and wait until that workflow has completed.
• Halt Workflow – Halt another workflow executing against the item or document.
• Restart This Workflow – great for implementing stateful workflows in SharePoint Designer
• Is Workflow Running – check if another workflow is running against the item or document.

Here is the entire list of actions:

To improve the quality of metadata associated with documents it is advisable to make columns required:

When applied to “Choice” types, the first choice from the list is automatically selected. Thus the user is not forced to make a choice, and the likelyhood is that the correct value will not be selected.

To circumvent this problem you can set a calculated default value that sets an empty string as the default value. This is an equal sign followed by two double quotes:

Now, when a new item using this field is presented to the user a blank item is selected. If the item is added without supplying a value an error is presented:

Update Oct 30 2009: Here’s a solution to this problem.

There are many cases where you may want to have multiple content types associated with libraries. For example, a document library may be created for all documents do with a project. You may have different content types for project specifications, project plans etc. This can be easily done and is well documents. This results in multiple items displaying on the “New” menu, each of which can have different document templates and different meta data columns:

Now, when the user selects New + Content Type 2 the document template for Content Type 2 will be downloaded. So far, so good. Remember, though, that the document has not yet been created in the document library.

Once the document has been authored, the user will now save the document back to the document library, say with the name “document1.docx”. This is the point at which SharePoint suffers from amnesia. It has no idea that this document was created by the user selecting New + Content Type 2, and so when the document is saved SharePoint will use the default content type, which is “Content Type 1″ in this case.

In many situations, this does not matter. However, when the content types have different meta data associated with them, or different workflows or policies, the document will have the wrong processing applied. This can have serious problems, especially when documents are passed to records management.

This problem can be mitigated to an extent by having required meta data fields – in this case the user will be prompted by the client application to provide values, and at this stage the user will have an opportunity to select the content type. Alternatively, separate document libraries will be required for each of the different content types – but this compromises your taxonomy.

You can find the current version number for MOSS 2007 through Central Administration:

• Run Central Administration.
• Click the Operations tab.
• Click Servers in farm under the “Topology and Services” section.

This shows the version number for the farm and each individual server in the farm:

Here are the version numbers for various MOSS 2007 service packs:

For a full list of version numbers, including interim builds see here.

Update: 5 Nov 2009: See here for how to find MOSS 2007 and Windows SharePoint Services version numbers.