Microsoft KB Archive/918421

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 18:30, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Article ID: 918421

Article Last Modified on 11/15/2007



APPLIES TO

  • Microsoft Windows SharePoint Services 2.0




SUMMARY

Microsoft has released the Windows SharePoint Services 2.0 package for Microsoft Windows SharePoint Services 2.0.

This article describes the following items about the hotfix package:


  • The issues that the hotfix package fixes.
  • The prerequisites for installing the hotfix package.
  • Whether you must restart the computer after you install the hotfix package.
  • Whether the hotfix package is replaced by any other hotfix package.
  • Whether you must make any registry changes.
  • The files that the hotfix package contains.


INTRODUCTION

This article describes the Microsoft Windows SharePoint Services 2.0 issues that are fixed in the hotfix package that is dated May 23, 2006.

Issues that the hotfix package fixes

This hotfix package fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:

  • Garbage characters appear at the start of display names of certain users in Windows SharePoint Services 2.0 when Windows SharePoint Services 2.0 is deployed in an Active Directory Federation Services (ADFS) environment

    Consider the following scenario. You deploy Windows SharePoint Services 2.0 in an ADFS environment. After a user who is a member of the ADFS account partner accesses Windows SharePoint Services 2.0, garbage characters appear at the start of the display name of that user in Windows SharePoint Services 2.0fter a user adds new content such as a list item to Windows SharePoint Services 2.0. For example, the display name of a user may resemble the following:

    %$#*\UserName@DomainName.com

  • Data in a document is removed after you check in a document to a document library

    You check out a document that is stored in a folder in a document library. Then you check in the document. When you view the document, the document no longer contains any data. The size of the document is changed to 0 (zero) bytes.

    This issue occurs if the name of the folder that stores the document is changed when the document is checked out.
  • A site owner receives an "HTTP 404 - File not found" error message when the site owner clicks a URL in an e-mail message that is generated by the Site Use Confirmation and Auto-Deletion feature

    Consider the following scenario. You install Windows SharePoint Services 2.0 in scalable hosting mode. You configure the Site Use Confirmation and Auto-Deletion feature in Windows SharePoint Services 2.0 to automatically send e-mail messages to site owners to confirm whether Windows SharePoint Services 2.0 sites are still being used. A site owner uses Microsoft Outlook Web Access to open the e-mail message. When the site owner clicks a URL in the e-mail message, the site owner receives an error message that resembles the following:

    HTTP 404 - File not found

    This issue occurs because the URLs in the e-mail message contain an additional forward slash (/) character.


MORE INFORMATION

Service pack information

This problem was first corrected in Windows SharePoint Services 2.0 Service Pack 3.To resolve this problem, obtain the latest service pack for Windows SharePoint Services 2.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

906795 How to obtain the latest service pack for Windows SharePoint Services 2.0


Hotfix information

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

The following list contains prerequisites for the hotfix package:

  • The full-file version of this hotfix is also the administrative version of this hotfix. You can install this version of the hotfix on a computer that is running Windows SharePoint Services 2.0 Service Pack 2 or Windows SharePoint Services 2.0 Service Pack 1. However, we have tested this hotfix more extensively on Windows SharePoint Services 2.0 Service Pack 2 than we have on Windows SharePoint Services 2.0 Service Pack 1. If you install this hotfix on a computer that is running Windows SharePoint Services 2.0 Service Pack 1, some file conflicts might occur. We support this configuration, but we do not recommend this configuration.

Restart information

You do not have to restart your computer after you apply this .

Hotfix replacement information

This hotfix is not replaced by any later hotfix.

Registry information

You do not have to create any registry keys or modify any registry keys to use any hotfixes that this package contains.

Hotfix file information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that this article lists.

The global version of this hotfix uses a Microsoft Windows Installer package to install the hotfix. The dates and times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Download information

File name File version File size Date Time
Wss2003-kb918421-glb.exe 11.0.8027.0 3,576,128 23-May-2006 16:55

Microsoft Windows Installer .msp file information

File name File version File size Date Time
Sts.msp Not applicable 3,870,208 23-May-2006 16:54

After the hotfix package is installed, the global version of this hotfix package has the file attributes, or a later version of the file attributes, that are listed in the following table.

File name File version File size Date Time
Mdspsppt.dll 11.0.8010.0 80,632 20-Jan-2006 21:50
Mdspxmlu.dll 11.0.6467.0 80,632 28-Jan-2005 22:06
Onetutil.dll 11.0.8027.0 1,411,856 22-May-2006 22:52
Owssvr.dll 11.0.8027.0 2,239,248 22-May-2006 22:56
Sqmsto.dll 11.0.8004.0 2,288,328 06-Dec-2005 21:45
Sqmstoup.dll 11.0.8004.0 2,222,792 06-Dec-2005 21:45
Store.sql Not applicable 1,158,756 30-Nov-2005 09:34
Storeup.sql Not applicable 1,125,263 30-Nov-2005 09:34
Stsadm.exe 11.0.6551.0 154,312 25-Mar-2005 21:39
Stsap.dll 11.0.8000.0 244,480 22-Oct-2005 22:36
Stslib.dll 11.0.8000.0 97,008 22-Oct-2005 22:36
Stsom.dll 11.0.8027.0 1,477,416 22-May-2006 22:56
Stssoap.dll 11.0.8012.0 199,368 03-Feb-2006 14:21
Stswel.dll 11.0.8027.0 1,063,696 22-May-2006 22:56

Notes

  • For more information about how to install this hotfix, see the Readme.txt file that is included in the hotfix package.

For more information about the terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates



Additional query words: wss link WSSv2

Keywords: kbwsssp3fix kberrmsg kbwsspresp3fix kbexpertiseinter kbfix kbqfe kbhotfixrollup kbhotfixserver KB918421