Microsoft KB Archive/936867

= Description of the Windows SharePoint Services 3.0 hotfix package: May 8, 2007 =

Article ID: 936867

Article Last Modified on 11/15/2007

-

APPLIES TO


 * Microsoft Windows SharePoint Services 3.0

-



SUMMARY
This article describes the Microsoft Windows SharePoint Services 3.0 issues that are fixed in the Windows SharePoint Services 3.0 hotfix package that is dated May 8, 2007.

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.



List of issues fixed
This hotfix package fixes the following issues:  

937038 Error message when you try to connect to a site in a Windows SharePoint Services 3.0 site collection: &quot;HTTP 500 - Internal server error&quot;

 

935958 Error message when you try to connect to a site in a Windows SharePoint Services 3.0 site collection after you configure a document library to inherit permissions: &quot;HTTP 500 - Internal server error&quot;



This hotfix package fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:  A crawl occurs on a server that is running Windows SharePoint Services 3.0. Additionally, incremental crawls may occur periodically during the crawl. Intermittently, the crawl may stop responding (hang), and the following status message may be displayed on the Search Settings page:

Computing Ranking

 You remove users from the site collection for Microsoft Office SharePoint Server 2007. Then, you run a Microsoft Office SharePoint Server 2007 deployment job. After you update the page, the Status column for the deployment job shows a status of Failed. Additionally, when you click the Failed status link, you receive the following error message:

User cannot be found.

at Microsoft.SharePoint.SPUserCollection.GetByID(Int32 id)

at Microsoft.SharePoint.SPWeb.get_Author

at Microsoft.SharePoint.Deployment.WebSerializer.GetDataFromObjectModel(Object obj, SerializationInfo info, StreamingContext context)

at Microsoft.SharePoint.Deployment.DeploymentSerializationSurrogate.GetObjectData(Object obj, SerializationInfo info, StreamingContext context)

at Microsoft.SharePoint.Deployment.XmlFormatter.SerializeObject(Object obj, ISerializationSurrogate surrogate, String elementName, Boolean bNeedEnvelope)

at Microsoft.SharePoint.Deployment.XmlFormatter.Serialize(Stream serializationStream, Object topLevelObject)

at Microsoft.SharePoint.Deployment.ObjectSerializer.Serialize(DeploymentObject deployObject, Stream serializationStream)

at Microsoft.SharePoint.Deployment.SPExport.SerializeObjects

at Microsoft.SharePoint.Deployment.SPExport.Run

 You upload documents to a document library on a server that is running Windows SharePoint Services 3.0 and Microsoft Forefront Security for SharePoint. In Central Administration, you click to clear the Scan documents on download check box on the Antivirus page. You click to select the Scan documents on download check box, and then you click OK. When you open the Application event log, you find the following error message:

Source: Windows SharePoint Server

Type: Error

User: N/A

Date:

Time:

Computer:

Category: General

Event ID: 26424

Description: The description for Event ID ( 26424 ) in Source ( Windows SharePoint Services 3 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE=flagto retrieve this description; see Help and Support for details. The following information is part of the event: #960012: Finished loading antivirus scanner. Error -2147024890

 When you search for content on a server that is running SharePoint Server 2007, the search unexpectedly times out.

</li> You use a relative path in a link that is inside a Web Part. The Web Part is contained on a Web page on a server that is running Windows SharePoint Services 3.0. When you click OK to close the Web Part Properties dialog box, you notice the following error message on the Web page in the location of the Web Part:

Error (File Not Found)

Additionally, the relative path of the link in the Web Part is removed if you edit the Web Part again.

</li> You create a user account in a Windows SharePoint Services 3.0 site. If you click to clear the option to send the new user an e-mail message after you create the user's account, an e-mail message that contains the user name and password is sent unexpectedly to the user.

</li> You run an incremental deployment job on a server that is running Windows SharePoint Services 3.0. After you update the page, the Status column for the incremental deployment job shows a status of Failed. Additionally, when you click the Failed status link, you receive the following error message:

Violation of PRIMARY KEY constraint 'PK__#ExportObjects____22355A14'. Cannot insert duplicate key in object 'dbo.#ExportObjects'. The statement has been terminated.

at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)

at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)

at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)

at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)

at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)

at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)

at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)

at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)

at System.Data.SqlClient.SqlCommand.ExecuteNonQuery

at Microsoft.SharePoint.Utilities.SqlSession.ExecuteNonQuery(SqlCommand command)

at Microsoft.SharePoint.Deployment.SPExport.CalculateObjectDependencies(Boolean linksOnly)

at Microsoft.SharePoint.Deployment.SPExport.FollowLinks

at Microsoft.SharePoint.Deployment.SPExport.CalculateObjectsToExport

at Microsoft.SharePoint.Deployment.SPExport.Run

</li> You export a document from a document library on a server that is running Windows SharePoint Services 3.0. If the document contains a version history, the content of the Modified By field is lost when the document is imported back into the document library.

</li> As the number of documents in a document library increases on a server that is running Windows SharePoint Services 3.0, the lag time between the initiation of a crawl and the actual beginning of the crawl increases.

</li></ul>

<div class="moreinformation_section">

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

Prerequisites
There are no prerequisites for installing this hotfix.

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

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

Registry information
To use one of the hotfixes in this package, you do not have to make any changes to the registry.

Pre-installation information
Before you apply this hotfix, we recommend that you disable the antivirus settings in Windows SharePoint Services 3.0 on all front-end Web servers. To do this, follow these steps:
 * 1) On the Operations page, click Antivirus in the Security Configuration section.
 * 2) In the Antivirus Settings section, click to clear the following check boxes, and then click OK:
 * 3) * Scan documents on upload
 * 4) * Scan documents on download
 * 5) * Allow users to download

Post-installation information
After you apply this hotfix, follow these steps: <ol> Run the SharePoint Products and Technologies Configuration Wizard. To do this, click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Products and Technologies Configuration Wizard.</li> Enable the antivirus services on all front-end Web servers by using the same values as were previously configured. To enable the antivirus settings in Windows SharePoint Services 3.0, follow these steps: <ol style="list-style-type: lower-alpha;"> On the Operations page, click Antivirus in the Security Configuration section.</li> In the Antivirus Settings section, click to select the following check boxes as appropriate for your situation, and then click OK:  Scan documents on upload</li> Scan documents on download</li> Allow users to download</li></ul> </li></ol> </li></ol>

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 are listed in this article.

32-bit hotfix package
The global version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. The dates and the 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

Microsoft Windows Installer .msp file information

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

64-bit hotfix package
The global version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. The dates and the 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

Microsoft Windows Installer .msp file information

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

Additional notes  For more information about how to install this hotfix, see the Readme.txt file that is included in the hotfix package.</li> For more information about software update terminology, 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

</li></ul>

Additional query words: wss3 wss30 wss3.0

Keywords: kberrmsg kbbug kbfix kbqfe kbpubtypekc kbhotfixrollup kbexpertiseinter kbhotfixserver kbwss30postrtm KB936867

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.