Issues that are fixed in Windows SharePoint Services by Windows SharePoint Services Service Pack 2

Article translations Article translations
Article ID: 906336 - View products that this article applies to.
Expand all | Collapse all

On This Page

SUMMARY

Microsoft has released a service pack for Microsoft Windows SharePoint Services that contains fixes for Microsoft Windows SharePoint Services.

INTRODUCTION

Microsoft Windows SharePoint Services Service Pack 2 (SP2) provides the latest updates to Windows SharePoint Services. Windows SharePoint Services SP2 contains security enhancements, stability improvements, performance improvements, and new feature functionality. Some of the fixes that are included with Windows SharePoint Services SP2 were previously released in Windows SharePoint Services Service Pack 1 (SP1) or in separate updates. Windows SharePoint Services SP2 combines the previously released fixes into one update.

For more information about Windows SharePoint Services 2.0 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
887624 Description of Windows SharePoint Services 2.0 Service Pack 2

MORE INFORMATION

Issues that the service pack fixes

Issues that were previously documented in the Microsoft Knowledge Base

Windows SharePoint Services SP2 fixes the issues that are described in the following hotfix packages:
867811 Description of the Windows SharePoint Services post-Service Pack 1 hotfix package: September 16, 2004
840317 Description of the Windows SharePoint Services post-Service Pack 1 hotfix package: September 20, 2004
886676 Description of the Windows SharePoint Services post-Service Pack 1 hotfix package: October 12, 2004
887810 Description of the Windows SharePoint Services post-Service Pack 1 Hotfix Package: October 19, 2004
888505 Description of the Windows SharePoint Services post-Service Pack 1 hotfix package: November 13, 2004
889385 Description of the Windows SharePoint Services post-Service Pack 1 hotfix package: November 19, 2004
890201 Description of the Windows SharePoint Services post-Service Pack 1 hotfix package: November 25, 2004
890630 Description of the Windows SharePoint Services post-Service Pack 1 hotfix package: December 3, 2004
890930 Description of the Windows SharePoint Services post-Service Pack 1 hotfix package: December 14, 2004
891512 Description of the Windows SharePoint Services post-Service Pack 1 hotfix package: December 18, 2004
892295 Users who are members of the local Administrators group have access to all the content in your Windows SharePoint Services Web sites
892557 Description of the Windows SharePoint Services post-Service Pack 1 hotfix package: January 27, 2005
894258 Description of the Windows SharePoint Services post-Service Pack 1 hotfix package: February 17, 2005
894375 Description of the Windows SharePoint Services post-Service Pack 1 hotfix package: March 11, 2005
894376 Description of the Windows SharePoint Services post-Service Pack 1 hotfix package: February 21, 2005
894681 Description of the Windows SharePoint Services post-Service Pack 1 hotfix package: February 25, 2005
895184 Description of the Windows SharePoint Services post-Service Pack 1 hotfix package: March 1, 2005
895185 Description of the Windows SharePoint Services post-Service Pack 1 hotfix package: March 4, 2005
896349 Description of the Windows SharePoint Services post-Service Pack 1 hotfix package: March 29, 2005
896670 Description of the Windows SharePoint Services post-Service Pack 1 hotfix package: April 04, 2005
890861 Description of the Windows SharePoint Services post-Service Pack 1 hotfix package: April 14, 2005
897329 Description of the Windows SharePoint Services post-Service Pack 1 hotfix package: April 22, 2005
Windows SharePoint Services SP2 fixes the following issues that were previously documented in the Microsoft Knowledge Base:
830342 You receive a "Soap:Server Exception of Type Microsoft.SharePoint.SoapServer.SoapServerException" message when you try to edit a portal by using FrontPage 2003 or when you try to export a Web part
826787 New links are not visible on your Windows SharePoint Services Web site
827930 Error messages when you delete or rename large folders or sites in Windows SharePoint Services
888946 You cannot use a Web browser to access a document library after you delete the document library Forms folder in Windows SharePoint Services
892403 Users can still add content to a Web site in Windows SharePoint Services even after the storage quota limit for the Web site collection has been reached

Issues that were not previously documented in the Microsoft Knowledge Base

Windows SharePoint Services SP2 also fixes the following issues that were not previously documented in the Microsoft Knowledge Base.

The right ALT key does not function correctly in the rich text editor control of the Content Editor Web Part
When you try to type certain international characters in the rich text editor control of the Content Editor Web Part, the right ALT key does not function correctly. The right ALT key functions as CTRL+ALT.


You cannot enable the full-text search feature on the SearchAdmin.aspx page
On the SearchAdmin.aspx page, you click to select the Enable full-text search and index component check box, and then you click OK. After several minutes, you receive an error message that is similar to the following:
Error

Thread was being aborted.


You cannot delete a Web Part assembly in the Bin folder
After you delete a Web Part assembly in the Bin folder, you can still access the Web Part that corresponds to the Web Part assembly without any errors. When you delete the Web Part assembly, Windows SharePoint Services continues to load the Web Part assembly. Windows SharePoint Services does this by retrieving the copy of the Web Part assembly from the cache that is owned by the application pool identity.


Memory leaks may occur because Windows SharePoint Services cannot unload temporary application domains
When one of the following actions occurs, Windows SharePoint Services creates a temporary application domain to help you load Web Part assemblies from the Bin folder:
  • You visit a Windows SharePoint Services Web site that has a static IP address.
  • You visit a Windows SharePoint Services Web site through the host header of the Web site.
However, Windows SharePoint Services cannot unload temporary application domains. Therefore, memory leaks may occur.


Windows SharePoint Services cannot correctly load Web Part assemblies when you visit a Windows SharePoint Services Web site through the host header of the Web site
When you visit a Windows SharePoint Services Web site through the host header of the Web site, Windows SharePoint Services cannot correctly load Web Part assemblies. If another Web site on the Web server also uses port 80, Windows SharePoint Services tries to load Web Part assemblies from an incorrect application domain.


After you upload a document in Explorer view, you may find that the document has two versions in the version history
After you enable the Document Versions feature and then upload a document in Explorer view, you may find that the document has two versions in the version history.


You cannot restore a Windows SharePoint Services Web site when the number of sites reaches the warning limit
You expect that you can restore a Windows SharePoint Services Web site until the number of sites reaches the maximum limit. The maximum limit is specified in Maximum number of sites that can be created in this database. However, you cannot restore a Web site when the number of sites reaches the warning limit. The warning limit is specified in Number of sites before a warning event is generated. When you try to restore a Web site and the number of sites reaches the warning limit, you receive the following error message:
The content databases in this cluster have exceeded the warning Web site count.

Either change the content database Web site capacity settings or add more content databases.


An entry for the Web site is added in the configuration database of Windows SharePoint Services when the Web site restore operation fails
When the Windows SharePoint Services Web site restore operation fails, an entry for that Web site is added in the configuration database of Windows SharePoint Services. Because the Web site does not actually exist, the entry prevents you from creating or restoring sites that have the site name that was used in the restore operation.


The restore operation may produce an orphan Web site
After you perform a restore operation, you cannot access the restored Web site. Additionally, you cannot delete the restored Web site.


The Group by feature does not work correctly when you try to sort a column that contains half-width characters and full-width characters
You may see duplicate items in a Web page when the following conditions are true:
  • You mix half-width characters and full-width characters in a column.
  • You use the Group by feature to sort this column.
For example, if a Web page contains four items, you may see eight items in the Web page.


All the Web Parts display errors on the content page of a Windows SharePoint Services page even though an error occurs in only one Web Part
If an error occurs in one Web Part, all the Web Parts display errors on the content page of a Windows SharePoint Services page.


You cannot open the UserInfo table in Microsoft Office Access 2003
You use the Import From Windows SharePoint Services Wizard to import Windows SharePoint Services lists into an Access 2003 database as linked tables. If you open the linked tables and then try to open the UserInfo table, you may receive an error message that is similar to the following:
The Microsoft Jet database engine could not find the object ''. Make sure the object exists and that you spell its name and the path name correctly.
This issue occurs because the Windows SharePoint Services indexed sequential access method (ISAM) enables only 10 open cursors for each table.


You receive many errors and permissions problems when the Web site language ID is different from the locale ID
When the Web site language ID is different from the locale ID, you receive many errors and permissions problems.


The appearance of the pawn icon was changed
The pawn icon that indicates presence status was changed from the Messenger-style icon to a circle.

Error signature details

When you use Windows SharePoint Services, you may receive an error message that is similar to the following:
Microsoft Windows SharePoint Services has encountered a problem and needs to close. We are sorry for the inconvenience.

To see what data this error report contains, click here.
When you view the data in the error report, the error report contains an error signature that is similar to one of the following error signatures.
Collapse this tableExpand this table
Application nameApplication versionModule nameModule versionOffset
W3wp.exe6.0.3790.0Owssvr.dll11.0.6358.000175901
Iexplore.exe6.0.2800.1106Owsclt.dll11.0.5606.00003263e
W3wp.exe6.0.3790.0Stswel.dll11.0.5530.00007bf5f
W3wp.exe6.0.3790.0Fpencode.dll2003.1100.5510.000001608
W3wp.exe6.0.3790.0Stswel.dll11.0.5530.00002b563
Additionally, other program versions, module versions, and offsets are possible.

REFERENCES

To obtain Windows SharePoint Services Administrator's Guide, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyID=a637eff6-8224-4b19-a6a4-3e33fa13d230

Properties

Article ID: 906336 - Last Review: November 30, 2005 - Revision: 4.2
APPLIES TO
  • Microsoft Windows SharePoint Services 2.0
Keywords: 
kbfix kbupdate kbtshoot KB906336

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com