SharePoint Updates

Current Build: 12.0.0.6510.5001 (June 2009 CU)

Important Information about SP2:
(SP2 Trial Hotfix: http://support.microsoft.com/kb/971620/en-us)

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.

Source

What to install:

The SharePoint Product Group releases cumulative updates every two month.
The initial release is language specific, so you have to install the update for all language (including the installation language).
After some time, the PG releases so called Uber Updates, which include all languages. I will add them here as soon as they are released.

  1. WSS 3 SP2 (KB 953338)
  2. MOSS 2007 SP2 (KB 953334)
  3. MOSS 2007 SP2 Trial Hotfix (KB 971620)
  4. WSS 3 June CU (KB 971538)
  5. MOSS 2007 June 2009 CU, Dlc.msp (KB972569)
  6. MOSS 2007 June 2009 CU, Coreserver.msp (KB 970948)
  7. MOSS 2007 June 2009 CU, Coreservermui-en-us.msp, language specific (KB 970947)
  8. MOSS 2007 June 2009 CU, Lpsrvmui-en-us.msp, language specific (KB 972562)
  9. MOSS 2007 June 2009 CU, Ifswfe.msp (KB 972564)

Installation prerequisites / order:

  • For the June 2009 CU you have to have SP2 installed.
  • To have the newest files you have to install both SP2 and June 2009 CU.

Changes:

(Latest update on top)

Important Changes in June 2009 CU (my opinion):

WSS 3:

  • You are using a computer that is in a different time zone than the computer that is running the SharePoint Web application. If you submit content for approval, or if you check in a shared draft, the start date of the SharePoint document changes.
  • When you click Send To, and then click Other Location to send a document in a Document Library, you receive the following error message: Copying to the destination did not complete successfully.
  • When you try to do a search in a SharePoint site, the scope "This List: Name of list, doclib etc." for a particular listis missing. This issue occurs because you are using the Extended Web Applications and the Alternative Access Mapping (AAM) settings.
  • In an extranet deployment scenario in SharePoint, the URLs to access SharePoint internally and the URLs to access SharePoint externally are different. You access the SharePoint externally, you visit a page that contains a list view Web part, you edit the list view Web part, and then you click the Edit current view link. However, when you click Cancel to go back to the previous page, you receive a "file not found" error message. Additionally, when you examine the URL in the Internet Explorer address bar, it displays an internal URL.
  • Workflows do not recognize users from the Membership Provider in the SharePoint Designer when Forms-based Authentication (FBA) is enabled.
  • You use the "Site Warning Level" and the "Maximum number of Sites" settings on a content database to control how to create sites in a database. However, when you add a content database by using Central Administration or the stsadm -o addcontentdb command, if the value that you specify in WarningSiteCount or the value that you specify in MaximumSiteCount is less than or equal to the current number of sites in the content database, the values that you specified are not used. Instead, the following values are set:
    WarningSiteCount = CurrentSiteCount + 500
    MaximumSiteCount = CurrentSiteCount + 1000
  • You move a sub-site to a new location, and then you delete its earlier parent site. In this case, the incremental deployment job fails, and your receive the following error message: Error deleting Web site "/ParentSite/SubSite". You can’t delete a site that has subsites.
  • When a SharePoint user creates a circular loop between lookup columns, if you click one of the lists that contain lookup columns, this action will cause 100% CPU usage on the SharePoint server. To work around this issue, you have to perform an application pool recycle.
  • You use multi-value lookup values in a SharePoint list. However, you notice that some documents in the SharePoint list are unpublished. The multiple value lookup values in the AllUserDataJunctions table are still present and flagged as current version documents and are not marked to be deleted. Therefore, multiple value lookup values become orphans. In this case, if you use the stsadm -o export command, the export phase of the content deployment will fail.
  • In the issue tracking list, you can open and save an attachment successfully for the first time, but when you try to save the attachment again, you receive the following error message: The Internet Address <URL> is not valid.
  • You create immediate alerts and scheduled alerts on document libraries at the library level. You receive an initial E-mail indicates that a message alert is created. However, you cannot receive alerts for all the documents. This issue occurs in Contributor and Reader when major and minor versioning is enabled on the document library.

MOSS 2007:

  • In Microsoft Office SharePoint Server 2007, you start an out-of-the-box approval workflow and set a due date. As soon as the due date passes, you edit the workflow and then delete the due date. Immediately a task overdue e-mail is sent out to the approvers with the original due date. The approvers continue to receive a task overdue e-mail (referencing the original due date) weekly until the workflow is canceled, a future due date is set or the workflow is approved
  • If you enable binary large object caching on a site collection intermittently you receive "File not found" errors when you open already cached files during the BLOBCache automatic background cleanup procedure. After you install this update, the probability of "File not found" errors caused by this race condition is minimal.
  • A search alert is added to inform you of any new results for a particular query term. However, after crawling a content source that contains many changed or new documents by using that query term, you find that the resulting alert e-mail only contains results for 10 of these newly crawled documents. You are never notified of the other documents.

Important Changes in April 2009 CU (my opinion):

WSS 3:

MOSS 2007:

  • Content deployment for a large site collection may stay in the export phrase for several days without finishing. This issue occurs when the size of the site collection is larger than 10 GB.
  • Navigation Links are deleted if a user who does not have permissions to see all navigation links modifies the navigation.
  • After a reghost operation (Reghost.aspx) on a publishing Web, all files that have been customized at least once will have a hardcoded size of 200 bytes in the alldocs table after these files are restored to the original versions. This causes Blobcache to save only the first 200 bytes of the affected files to the cache. This behavior causes invalid images, .css files, and corrupt .js files served to visitors.The Blobcache reset is not enough. You must modify the files to have the correct size information in the alldocs table.
  • You backup Microsoft Office SharePoint Server (MOSS) 2007 content database through SQL Server Then, you upgrade to MOSS 2007 SP1. When you restore the content database by using the stsadm -o addcontentdb command, data loss may occur.
  • Users that have comma (,) in the display name cannot be imported in the Active Directory Resource setup.
    When you create a non-English Search Center site collection, search scopes are missing. Additionally, a dropdown list does not appear. Only the "this site" string appears. For example, this issue occurs in a French Search Center site collection.

Important Changes in SP2 (my opinion):

WSS 3:

  • Confusing errors may be displayed after a database is marked as read-only.
  • Pages may display errors when served from 64-bit servers.
  • Large files may be changed unexpectedly after the files are checked out and then checked in.
  • After a site reaches its quota, the site becomes inaccessible.
  • Alerts may not be sent correctly on certain installation languages.
  • Importing a site fails when the site that is being imported contains a subsite that has features that are activated.
  • The SharePoint timer service may stop working on 64-bit servers.
  • 32-bit systems may perform badly in low memory conditions.

MOSS 2007:

  • Variations will continue to spawn copies of a page that has been moved out of the variations hierarchy if the root of that hierarchy is not the root of the domain (for example, http://contoso/sites/marketing).
  • When you configure a Site Collection cache profile with "Browser" for the "Vary by HTTP header" option, different cached versions of the site are not actually created for each browser heading.
  • Activating the "Office SharePoint Server Publishing Infrastructure" feature causes an Access Denied error for Site Collection administrators.
  • A user may select to open a snapshot of the workbook from the Excel Web Access Web Part when a workbook is published as a list of items to Excel Services. The snapshot is not correctly generated you may see a 500 internal error displayed.
  • During an incremental crawl, the crawler might encounter URLs with missing slashes in the URL. The crawler will fail to index these URLs because of the invalid URL. Post-SP2, the crawler identifies such URLs as being incorrect and re-creates the correct URL.
  • Any crawl immediately following a crawl that was stopped by the administrator is forced to be a full crawl. For example, if crawl "n" (incremental or full) on content source "xyz" is stopped by the administrator, the search system will force crawl "n+1" on content source "xyz" to be a full crawl.
  • When performing a backup of a search application, sometimes the operation for pausing the search application fails. In this case, the backup of the search index cannot continue. In that case, the SSP backup is virtually useless. Pre-SP2, the process of backing up the search database will continue. Post-SP2, the failure to pause the search application during a backup process will also result in failure of backing up the search databases, and the search databases will be marked with the same error as the search index component.
  • This problem occurs when an antivirus program or some other program is actively reading the index table file while the search process is trying to  read the index table file at the same time. This causes an index corruption and there is no way in the product to recover the index, and a catalog reset followed by a full recrawl of all content must be performed.
  • In SP2, there is an upgrade checker which will help customers who want to upgrade from MOSS 2007 SP2 to MOSS 14.
  • While crawling host header sites, the search crawler treats each host header site as a Web application and causes each URL to be indexed multiple times. This increases the size of the index and the database. Post-SP2, the crawler treats each host header site as a site collection, which results in each URL being indexed once.
  • The Czech language may be missing for the Search Word Breaker.
  • "This issue occurs in the following situations:
    1.  While the indexer is crawling content, a query server is restarted for patches, an operating system upgrade, a power outage, or other reasons. After the query server comes back up, there may be a corrupt index file if a merge had been ongoing at the time. The query server will serve queries, but crawling will not be able to continue, and the query server will need to be reinitialized with the index from the indexer.
    2.  While the indexer is crawling content, the indexer is restarted. After it comes back up, there is a corrupt index file.
    In each of these cases there is no way in the product to recover the index, and a catalog reset followed by a full recrawl of all content must be performed."
    Indexing a .docx file sent as an attachment to an e-mail causes the .docx iFilter to enter an infinite loop, resulting in high CPU usage.
  • "Pre-SP2, an access violation will occur when you use Windows Server 2003 SP1 in the following cases:
    1. When filtering an .html or .txt attachment in a .msg file
    2. When filtering an .html or .txt file in a .zip file"
  • If the admin stops a full crawl of any SharePoint repository, the crawler loses the ability to process changes using the change log in the next incremental crawl. If the admin were to do another incremental crawl at this point, there is very high probability that some changes would be missed by the crawler.
  • When the indexer service has problems like registry corruption or there are network connection issues, the user always sees the same "Search service is …offline"  error message on one of the following four pages: Search administration, SearchServiceInstanceSettings, SearchSSPSettings, and ManageSearchService.  Post-SP2, the error messages have been updated to be more meaningful and actionable.
  • The index gets corrupted when a shadow or a master merge is interrupted in the very late stages of the merge.
  • If a power outage causes the storage system to shut down before Windows can flush the index file to disk, the index file may be the correct size when the storage system comes back up again, but the index file is filled with zeros. The index is then considered corrupt, and crawling cannot continue until that query server is completely reinitialized with a full fresh index.
    new site collection created with the same name as a deleted site collection will not be crawled by a search.
  • SP2 fixes an issue in which PSConfig fails while upgrading farms with a pre-created Search database.

General information concerning SharePoint updates:

Be Sociable, Share!

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>