New post-SP2 KBs for SPS, WSS, & CMS posted.

SharePoint Portal Server SP 2 (Released 10/18)                           Most important KB articles for SP 2KB 887623 Description of Microsoft Office SharePoint Portal Server 2003 Service Pack 2KB 906337 Issues that are fixed in SharePoint Portal Server 2003 by SharePoint Portal Server 2003 Service Pack 2KB 907763 SPS requires ASP.NET 1.1 (although there was some initial confusion, the product team has clarified that SPS SP 2 and earlier must run on ASP.NET 1.1 – ASP.NET 2.0 is not supported for SPS virtual servers)KB 907308 How to address the case where SPS SP 2 does not updated the databases during service pack installation (Top support issue for SPS SP 2 and KB has been updated with more information based on research from our escalation engineers)KB 905229 How to update an evaluation version to SPS RTM if SPS if SPS SP 1 or SPS SP 2 has been installed on it.  (Updated KB article to be published soon)   Pending issue to be updated in KB 905854:  SharePoint Portal Server 2003 install on x64 fails if there is too much memory (4GB) on the server.  When this is the case, SPS SP 2 installer displays an OK button and silently fails.  A workaround that we are testing that seems to be working is to use the following switch in boot.ini to effectively reduce the memory to 1GB: /burnmemory=5054. Windows SharePoint Services SP 2 (Released 9/27) Most important KB articles for SP 2KB 906336 WSS SP 2 KB article listing all of the fixes KB 875358  Guidance for deploying WSS SP 2 including the new SP 2 version numberKB 841216  Steps for manually upgrading in case the databases do not get updated Pending issue that may require a KB article:  THAI and HEBREW web language template packs cannot be updated to SP 2 version.  When you attempt to update the THAI or HEBREW web language template pack to SP 2 version the update silently fails.  There may be other problems with these templates that we don’t know about especially when running on ASP.NET 2.0.  Another problem that might occur is if you installed the THAI or HEBREW template packs and then try to install another language template pack SharePoint reports the following error: “Setup has detected Pre-Release or trial versions of Windows SharePoint Services products on this computer.  Pre-release versions must be removed before setup can continue” For a few days the incorrect version of these two language template packs were made available on the download center.  A number of customers may have downloaded these incorrect web language template packs.  The solution is to uninstall the incorrect version and install the republished version,   KB 909455 Document library event handlers that use object model code without explicit impersonation fail with the “Cannot complete this action” error message after Windows SharePoint Services Service Pack 2 is installed Pending KB article (number not available yet): An error occurs creating an SPS area after WSS SP 2 is installed.  When you attempt to create a new area in SharePoint Portal Server 2003 after applying Windows SharePoint Services Service Pack 2 you receive the following error message:

“An error has occurred in the portal site. Contact the portal site administrator for assistance.”

This can happen if the file timestamps on the SharePoint SQL script files is incorrect. These files are located in <drive>:\Program Files\Common Files\Microsoft Shared\web server extensions\60\TEMPLATE\SQL. Because the timestamps are incorrect WSS SP 2 did not update these files and subsequently the stored procedures for the content databases were not updated.  To work around the issue do the following:

1. Remove the *.SQL files in location <drive>:\Program Files\Common Files\Microsoft Shared\web server extensions\60\TEMPLATE\SQL.
2. Go to Add/Remove Programs, Windows SharePoint Services, Repair/Reinstall.
3. Select ‘Detect and Repair errors in Microsoft Windows Sharepoint Services 2.0 installation’.
4. After repair completes you will need to force an upgrade so the stored procedures on the content databases are updated.

To do this, follow these steps:

1. Click Start, click Run, type cmd in the Open box, and then click OK.
2. At the command prompt, type the following lines, and then press ENTER after each line:
cd /d %commonprogramfiles%\Microsoft Shared\Web Server Extensions\60\Bin stsadm -o upgrade -forceupgrade

Pending issue that may warrant a KB article:  SQL Server 2005 running as a domain account runs with Kerberos Authentication.  If the domain account SQL is running as is not registered as an SPN then SharePoint will not be able to connect to it to create databases (whether or not WSS is configured to use Kerberos).  A workaround is to run SQL Server as Local System. ASP.NET 2.0 and SQL Server 2005         An updated WSS Administration Guide with instructions for using ASP.NET 2.0 and SQL 2005 will be released soon.  I don’t have a date yet exactly when it will get posted but you can check the date on  When it shows greater than 10/7/2005 then the new version is posted. Microsoft Content Management Server 2002 SP2 is Available as of 11/8 Direct link to Download: Download details: Content Management Server 2002 Service Pack 2 (SP2) SP2 Additions:       ·         Support for ASP.NET 2.0 (.NET Framework 2.0)      ·         Support for Visual Studio 2005      ·         Support for SQL 2005 (Yukon)      ·         Support for running on 64-bit machines in 32-bit emulation mode Related KBs

  • 894691 – A list of the bugs that are fixed in Content Management Server 2002 Service Pack 2 (live)
  • 906142 – How to obtain the latest Microsoft Content Management Server 2002 service pack (live)
  • 906145 – Content Management Server 2002 Service Pack 2 installation information (not live as of 1PM PDT on 11/8)
  • 984691 – Description of the Content Management Server 2002 Service Pack 2 (not live as of 1PM PDT on 11/8
Supportability issue for CMS SP2:  CMS SP2 does not install the Developer Tools.  Developer Tools must be installed from SP1a, which doesn’t support Visual Studio 2005.  This has some interesting implications for customers and support.  For example, if a customer has installed Content Management Server 2002 SP2 on a machine without Developer Tools or Visual Studio installed, and they wish to install Developer Tools, they will need to take the following steps: 1.      Uninstall MCMS 2002 SP22.      Install Visual Studio 2003 (or Visual Studio 2002)3.      Run “Change/Remove” from Add/Remove Programs on MCMS 2002 SP1a (Using the SP1a CD to access required files)4.      Change the existing installation, and select Developer Tools as the feature to add5.      Re-install MCMS 2002 SP2 It should be noted that this essentially means that in order to use Visual Studio 2005 with MCMS 2002 SP2, customers must have at some point installed Developer Tools on Visual Studio 2003 (or Visual Studio 2002).  MCMS 2002 SP2 does update existing Developer Tools installations to support Visual Studio 2005.  See KB 906145 for more information. Supportability update for Database OrphansCurrently PSS has a number of support cases opened where we have orphans in the databases.  WSS took two fixes in SP 2 to prevent orphans from being created but those fixes do not retroactively clean orphans from the database.  The most common orphan is where there is an entry for a site in the sites table of the configuration database but no corresponding site entry in the content database sites table.  The product team is developing a solution where you can run an stsadm.exe command to detect and clean orphans.  The common issue we see is that a customer cannot restore an stsasdm backup because of orphaned entries.  The work for this is under way and we don’t have an estimate yet when it will be ready. Newly published content:Every month new content is published and made available on Office Online.  This is a great place to keep up to date with new content released by the product teams.         SharePoint Portal Server,         Windows SharePoint Services,  

84 thoughts on “New post-SP2 KBs for SPS, WSS, & CMS posted.”

  1. Thanks for an excellent summary of potential post-SP2 problems! In particular, the “Pending KB article (number not available yet): An error occurs creating an SPS area after WSS SP 2 is installed.” We were having a similar problem when creating a portal site. It kept failing at 42% when trying to set an alert property. It turns out that the SQL scripts problem that prevents SPS areas from being created also caused our error! (We had copied the 60\TEMPLATES folder from another computer that only had SP1 installed, which messed up the SQL files.) The repair solution above worked perfectly. Thanks!

  2. Scommettevo che avete speso molto tempo lavorare al luogo. Ha valso la pena di fare;)[URL=] famose [/URL]

Leave a Reply

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