Microsoft KB Archive/867811

= Description of the Windows SharePoint Services post-Service Pack 1 hotfix package: September 16, 2004 =

Article ID: 867811

Article Last Modified on 11/15/2007

-

APPLIES TO


 * Microsoft Windows SharePoint Services 2.0

-





SUMMARY
''Microsoft has released the Microsoft Windows SharePoint Services post-Service Pack 1 hotfix package for Microsoft Windows SharePoint Services. This article describes the following items about the hotfix package:''


 * Issues that the hotfix package fixes
 * Prerequisites for installing the hotfix package
 * Whether you must restart your 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 to use one or more of the hotfixes in the package
 * The files that the hotfix package contains



Article contents

 * INTRODUCTION
 * Issues that the hotfix package fixes
 * MORE INFORMATION
 * Hotfix information
 * Prerequisites
 * Restart information
 * Hotfix replacement information
 * Registry information
 * Hotfix file information
 * REFERENCES



INTRODUCTION
This article describes the Microsoft Windows SharePoint Services issues that are fixed in the Windows SharePoint Services post-Service Pack 1 hotfix package that is dated September 16, 2004.

back to the top

Issues that the hotfix package fixes
This hotfix package fixes the following issues that were not previously documented in a Microsoft Knowledge Base article.  ==== You receive a &quot;List does not exist&quot; error message ====

When you try to open a Web page from a subsite in Windows SharePoint Services, you receive the following error message:

Error

List does not exist

The page you selected contains a list that does not exist. It may have been deleted by another user. Click &quot;Home&quot; at the top of the page to return to your Web site.

This problem occurs when the following conditions are true:  The subsite contains a custom list. The custom list was created in another subsite in Windows SharePoint Services.  ==== &quot;System.OutOfMemoryException&quot; exception in the W3wp.exe process in Windows SharePoint Services ====

When you try to open a Web page in Windows SharePoint Services, you receive the following error message:

Unable to connect

If you click Refresh on the View menu in Microsoft Internet Explorer after the Worker process (W3wp.exe) in Microsoft Internet Information Services (IIS) recycles, the Web page is displayed as expected.

An error that is similar to the following is logged in the application event log :

Event Type: Error

Event Source: Windows SharePoint Services 2.0

Event Category: None

Event ID: 1000

Description:

Faulting application w3wp.exe, version 6.0.3790.0, stamp 3e8000e6, faulting module owssvr.dll, version 11.0.5530.0, stamp 3f28c94c, debug? 0, fault address 0x0017354a.

This problem occurs because a null pointer reference causes the Worker process (W3wp.exe) to stop (crash).  ==== Worker process recycles when you change a recurring meeting request in Windows SharePoint Services ====

When you change the date or time of a recurring meeting request, and then you click Send Update, an error that is similar to the following is logged in the application event log:

Event Type: Error

Event Source: Windows SharePoint Services 2.0

Event Category: None

Event ID: 1000

Description:

Faulting application w3wp.exe, version 6.0.3790.0, stamp 3e8000e6, faulting module onetutil.dll, version 11.0.5530.0, stamp 3f295664, debug? 0, fault address 0x000a8021. The problem occurs because of a null pointer reference that causes the Worker process (W3wp.exe) to stop (crash). </li> ==== Deadlock condition may occur when you call SPFileCollection.Delete and SPListItem.Update at the same time in Windows SharePoint Services ====

When you call the SPFileCollection.Delete method and the SPListItem.Update method at the same time in Windows SharePoint Services, a deadlock condition may occur in Microsoft SQL Server 2000.

This problem may occur when you use threads and do not serialize the calls to each method.

Note You may experience slow performance in Windows SharePoint Services when the deadlock condition occurs in SQL Server 2000. </li> ==== &quot;The page cannot be found&quot; error message if the path of the document is more than 128 characters in Windows SharePoint Services ====

When you try to open an old version of a document in a document library in Windows SharePoint Services, you receive the following error message:

The page cannot be found

The page you are looking for might have been removed, had its name changed, or is temporarily unavailable.

The problem occurs when the path of the document is more than 128 characters long. For example, consider the following scenario: <ol> You create a folder in a document library. The folder name is 70 characters long.</li> Within this folder, you create another folder. This new folder also has a name that is 70 characters long. The total length of the path is now more than 140 characters.</li> You upload a document in to the newly created folder.</li> You make a revision to the document</li> When you try to retrieve the previous version in the document history, you receive the error message.</li></ol>

Note After you apply this hotfix, the maximum character length supported is increased to 256 characters. </li> ==== Incorrect error codes are returned from SPFileCollection.Delete and SPFileCollection.Update in Windows SharePoint Services ====

When your Microsoft Windows SharePoint Services application calls either the SPFileCollection.Delete method or the SPFileCollection.Update method, incorrect result codes may be returned. Therefore, you cannot write code that reacts correctly to the result code that is returned in Windows SharePoint Services. </li></ul>

back to the top

<div class="moreinformation_section">

Service pack information
This problem was first corrected in Windows SharePoint Services Service Pack 2.

To resolve this problem, obtain the latest service pack for Windows SharePoint Services. 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

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:

http://go.microsoft.com/?linkid=6294451

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:

http://support.microsoft.com/contactus/?ws=support

back to the top

Prerequisites
The following list contains prerequisites for the hotfix package:  This hotfix is a post-Windows SharePoint Services Service Pack 1 (SP1) hotfix. To install the hotfix, you must have Windows SharePoint Services SP1 installed. For more information about Windows SharePoint Services SP1, click the following article number to view the article in the Microsoft Knowledge Base:

841876 Description of Windows SharePoint Services Service Pack 1

</li></ul>

back to the top

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

back to the top

Hotfix replacement information
This hotfix is not replaced by any later hotfix.

back to the top

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

back to the top

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

The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it 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.

The following is the download information. <pre class="fixed_text">  Date         Time   Version            Size    File name --  30-Aug-2004  22:46  5.0.2919.6304   3,305,504  Office2003-kb867811-glb.exe

The following is the Microsoft Windows Installer .msp file information. <pre class="fixed_text">  Date         Time   Version            Size    File name --  27-Aug-2004  20:05                  3,200,000  Stsff.msp 26-Aug-2004 22:11                    421,376  Stsop.msp

After the hotfix is installed, the global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. <pre class="fixed_text">  Date         Time   Version            Size    File name --  18-Aug-2004  06:10  11.0.6400.0     1,410,248  Onetutil.dll 18-Aug-2004 05:56  11.0.6400.0     2,218,688  Owssvr.dll 13-Aug-2004 06:03                  1,111,049  Store.sql 13-Aug-2004 06:03                  1,077,217  Storeup.sql 18-Aug-2004 06:17  11.0.6400.0       137,920  Stsadm.exe 18-Aug-2004 06:15  11.0.6400.0        92,912  Stslib.dll 18-Aug-2004 06:25  11.0.6400.0     1,501,920  Stsom.dll 18-Aug-2004 06:17  11.0.6400.0     1,051,328  Stswel.dll

Additional notes:  For additional information about installing this hotfix, see the STS_Readme.txt file that is included in the hotfix package.</li> For additional information about the differences between the two .msp files, see the &quot;Strategies for Updating Office 2003 Installations&quot; topic. To see this topic, visit the following Microsoft Web site:

http://www.microsoft.com/office/ork/updates/patch_o2k3.htm

</li></ul>

back to the top

<div class="references_section">