New hotfixes for WSS and MOSS (SharePoint 2007)

And not a moment too soon! We rolled out the infrastructure update to a client just recently to resolve an issue they were having where emails coming into an email-enabled document library were not triggering a workflow. As most people know, the Infrastructure Update breaks Alternate Access Mappings when using Load-balancing or Proxies… so if you use them, you then need to install at least the next hotfix rollup that came out after it.

So that was the plan… and all was going swimmingly until we looked at the workflow and realised that they were all failing – it appears as though the October and December hotfixes introduced an issue where updates to user columns failed when running through SharePoint Designer workflow. It’s like playing Whack-a-mole.

Anyway, the new hotfixes have just been released and they fix a lot of outstanding issues – they can be found here for WSS – http://support.microsoft.com/kb/961750 – and here for MOSS – http://support.microsoft.com/kb/961749. I can’t find the hotfix rollup yet, so until they are published, these should ideally be deployed on farms that already have the December releases.

**UPDATE** – The Rollups for February have been released, as announced on Todd Klindt’s blog – http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?List=56f96349%2D3bb6%2D4087%2D94f4%2D7f95ff4ca81f&ID=111 – get them here (WSS3) and here (MOSS 2007)

**UPDATE** – Joerg Sinemus has updated his blog with the information required to roll these out. Until the uber-patches are released, you need to be at least running SP1, however there are no other prerequisites as per his article… having said that, other people have had problems if they do not yet have the infrastructure update installed and they try to install a hotfix pack released after the Infrastructure Update was released.


The big or “uber” packages are not yet available. CAPES (Customer and Partner Engineering Services team in Microsoft) is still working on these so please stay tuned. If you need to immediately install the Feb Hotfix update please read & follow the checklist.

 Checklist to install Feb CU:

– Preqs are WSS and MOSS Global SP1 and all language specific SP1
– Install WSS Global 961750 (Feb Hotfix pack WSS)
– For each language including the installed one install language specific WSS 967703
– Install MOSS Global 961749 (Feb Hotfix Pack MOSS)
– For each language including the installed one install language specific MOSS 961754
– Run psconfig -cmd upgrade -inplace b2b –force


List of issues resolved is as follows:WSS


  • When you decline a recurring meeting request from the meeting workspace, the e-mail message that is sent by the SharePoint server is not recognized by Microsoft Office Outlook 2007 as a meeting declination. Therefore, Outlook does not update the meeting attendee status to "Declined."
  • You migrate discussion boards from Windows SharePoint Services 2.0 to Windows SharePoint Services 3.0. Discussion boards work fine after that. However, if you export and import a discussion board into another Windows SharePoint Services 3.0 site, the thread relationship is broken, and all entries appear in one list.
  • Content deployment target site permissions that are not inherited can be removed.
  • The entries for e-mail-enabled lists are being deleted from the EmailEnabledLists table in the configuration database. When this issue occurs, incoming e-mail messages for these lists are not delivered. Therefore, the e-mail messages are deleted, and errors are logged for "Unkown alias."
  • If you have a list that has more than 500 unique scope IDs and if the Content Approval option is enabled, duplicated items may appear in the default view of this list.
  • In a Windows SharePoint Services 3.0 site, alerts for All day Calendar events do not show the correct start and end time in alert e-mail messages.
  • When you try to modify group membership of the built-in groups of site collections, you may receive a "System.UnauthorizedAccessException" exception. For example, this issue may occur when you try to add a new user to a built-in group. Built-in groups include visitors, owners, members, and so on.
  • If you use the SharePoint Content Migration API to export large sites, the performance is poor.
  • You create a new page in the source variation by using a customized page layout that has calculated columns. However, when you try to allow the variation engine to propagate the new page to the other variation label Web sites, it fails.
  • When you move through a specific blog category page, you cannot move to the Next page of blog entries. By default, the paging is set to 10 items per page. However, when you move to the next page in a category, a "There are no posts in this category" message is displayed. This message is incorrect. Paging in the All Posts area works as expected.
  • Before an incremental content deployment, you activate and then deactivate the feature that creates content types on both the source site and the destination site. During the incremental deployment, the content type delete operation fails, and the content deployment stops with an error message.
  • All meetings that you view under a meeting workspace display folder numbers instead of document names.
  • You create a versioned page, and you create a major version and a minor version. When you delete the versioned page and try to export the document library, it fails.
  • If you have an orphan site collection, the XML produced by the stsadm -o enumsites command is not well formed, as shown in the following example.

    <Sites Count="3"> 
    <Site Url="http://webapp/" ... /> 
    <Site Error="Error message">  
    <Site Url="http://webapp/..." ... /> 
    </Site>

    The last tag is missing an "s." It should be </Sites>. Also, the <site Error …> tag is not correctly closed.

  • After you install update 957691, you cannot set a user type column from the workflow when you create a new list item.
  • If you programmatically run the SPListItem.SystemUpdate(bool) method on a document library, the latest check-in comment will be removed.
  • If you add a Site Columns choice type that has a slash (/) in the column name to a document library, you cannot change the value of it on a SharePoint site. However, you can change the value by opening the document in Microsoft Word, editing the property, and saving it back to the document library.
  • When you build an application to control a document library, the SPFolder.CopyTo() method does not increase the List.ItemCount number, this will cause inconsistency in the list.
  • The Microsoft PKM Search Filter Daemon (Mssdmn.exe) crashes every 15 seconds when crawled using certificate authentication.
  • When you try to back up the Shared Search index, it always fails, and you receive the following error message in the backup log:

    [30/9/2008 2:11:46]: Verbose: Starting object: Shared Search Index. [30/9/2008 3:12:17]: Error: Object Shared Search Index failed in event OnBackupComplete. For more information, see the error log located in the backup directory. WebException: The current operation timed-out after 3600 seconds [30/9/2008 3:12:17]: Debug: at Microsoft.Office.Server.Search.Administration.CatalogPauseTimeout.WaitAndThrowIfTimeout() at Microsoft.Office.Server.Search.Administration.SearchApi.CatalogResumeCrawl(GathererPauseReason reason) at Microsoft.Office.Server.Search.Administration.SearchSharedApplication.Microsoft.SharePoint.Administration.Backup.IBackupRestore.OnBackupComplete(Object sender, SPBackupInformation args) [30/9/2008 3:12:17]: Verbose: Starting object: SharedServices_Default_Search.

  • When you search on a SharePoint site, the performance may sometimes be slow.
  • Search results are not security trimmed for anonymous users who access the sites that have the lockdown feature activated.

    MOSS


    • The UserProfileChangeService service does not report user deletions.
    • If blob caching is enabled for a Web site, you cannot download files whose size is more than 32 megabytes (MB) from that Web site.
    • When you open a SharePoint Search site by using SharePoint Designer, the W3wp.exe process crashes.
    • You create a new page based on the "(Welcome Page) Welcome page with summary links" page layout. You add a new link to the Summary Links Web part, and you use a URL that starts with "mms://". However, the newly added link is an empty link.
    • You convert a Word document (.docx) to a Web page on a SharePoint site. However, the multi level numbering is incorrect. For example, 1.1 may be displayed as 0.1.
    • When you use spelling check in a Spanish site, it fails and you may receive the following error message:

      Spell checking is not available for the default language. Choose one of the following languages and click OK to continue spelling, or click Cancel to stop.

    • A Shared Services Timer job opens handles for each task, but the job does not close the handles. Because the type is set to manual reset for these handles, the garbage collector cannot clean them up. Therefore, a handle leak occurs in the Owstimer.exe process.
    • You have a Word document (.docx) that has Track Changes enabled. You convert the Word document to a Web page on a SharePoint site. However, deleted words are displayed in the conversion results as unhidden text.
    • If you disable the Show Subsites option on the navigation settings page and repeatedly visit a subsite, you see high latency and low throughput.
    • The variation engine cannot restore destination page properties if the page contains a Content Query Web part.
    • When you set a publishing time for a page in SharePoint, the publishing time may shift incorrectly if the time zone is not Coordinated Universal Time (UTC). This behavior occurs for the end time too.
    • If you input Date type cells in Excel 2007 files, the XLSX Filter extracts them as numbers.
    • A Variation Page propagation job cannot transfer updated content to target labels if the page has a comma in the URL. This is because the Variation engine cannot find propagated pages that have a comma in the URL.
    • The Business Data List Web part is not using the Regional Settings collation when it sorts the data.
    • When you build an application to control a document library, the SPFolder.CopyTo() API does not increase the List.ItemCount number. This behavior causes inconsistency in the List.
    • The Microsoft PKM Search Filter Daemon (Mssdmn.exe) crashes every 15 seconds when crawled using certificate authentication.
    • When you back up the Shared Search index, it always fails, and you may receive the following error message in the backup log:

      [30/9/2008 2:11:46]: Verbose: Starting object: Shared Search Index. [30/9/2008 3:12:17]: Error: Object Shared Search Index failed in event OnBackupComplete. For more information, see the error log located in the backup directory. WebException: The current operation timed-out after 3600 seconds [30/9/2008 3:12:17]: Debug: at Microsoft.Office.Server.Search.Administration.CatalogPauseTimeout.WaitAndThrowIfTimeout() at Microsoft.Office.Server.Search.Administration.SearchApi.CatalogResumeCrawl(GathererPauseReason reason) at Microsoft.Office.Server.Search.Administration.SearchSharedApplication.Microsoft.SharePoint.Administration.Backup.IBackupRestore.OnBackupComplete(Object sender, SPBackupInformation args) [30/9/2008 3:12:17]: Verbose: Starting object: SharedServices_Default_Search.

    • When you search on a SharePoint site, the performance may be slow.
    • Search results are not properly security trimmed for anonymous users who access the SharePoint sites that have the Lockdown feature activated.

    This release also includes fixes that are described in the following Microsoft Knowledge Base articles:

  • Advertisements

    About Brad Saide

    I'm a SharePoint consultant. I'm also slowly going bald, seem to have a permanent spare tyre around my waist and enjoy socialising with friends over a beer or 10. The last 2 may possibly be related. Started working with SharePoint when the first version was in limited beta release (participated in the Technology Adoption Program while at Woolworths) and have been committed to the adoption of the technology as a business enabler ever since.
    This entry was posted in Uncategorized. Bookmark the permalink.

    Leave a Reply

    Fill in your details below or click an icon to log in:

    WordPress.com Logo

    You are commenting using your WordPress.com account. Log Out / Change )

    Twitter picture

    You are commenting using your Twitter account. Log Out / Change )

    Facebook photo

    You are commenting using your Facebook account. Log Out / Change )

    Google+ photo

    You are commenting using your Google+ account. Log Out / Change )

    Connecting to %s