This article describes the Windows SharePoint Services 3.0 issues that are fixed in the Windows SharePoint Services 3.0 hotfix package that is dated April 28, 2009.
Issues that this hotfix package fixes
Excel 2003 workbooks that contain cells that have large comments are not filtered. Therefore, legacy Index service, Microsoft Office SharePoint Server (MOSS), or Desktop search cannot search on the content in the large comments.
When you try to publish a page after the application pool has been running for two or more hours, publishing takes 30 minutes or longer. This is a performance issue.
When you create a document in a document library, you enter a date and time value for the newly created document in SharePoint. When you save the changes, the date and time value is changed to include daylight saving time (DST). You expect the date and time value to remain as entered.
Dates from Spanish-localized lists are rendered incorrectly in DataForm Web parts in SharePoint Designer.
When you programmatically export or import a list that contains a custom lookup field, the export process or the import process generates an exception that resembles the following message:
System.ArgumentOutOfRangeException was unhandled
If a site collection is very large, an attempt to delete the site collection from a Web application fails. This causes the stsadm -o mergecontentdbs command to fail when you try to move site collections from one content database to another. Therefore, both the source content database and the destination content database contain orphaned copies of the site collection. SharePoint cannot access orphaned site collections. This issue is resolved by adding an optional -gradualdelete parameter to the stsadm -o deletesite command. If this parameter is present, SharePoint marks the site collection as deleted to prevent further access while a SharePoint Timer job gradually deletes the data in the site collection. After you install the hotfix package that this article describes, the stsadm -o mergecontentdbs command uses this gradual delete functionality by default.
When you try to attach a content database, the operation fails because of process interruption. When this problem occurs, the database is left in an unworkable state in which the content database can neither be fully attached nor detached.
You create a site that contains two Web parts by using SharePoint Designer. The Web parts are connected so that when you select a day in the left Web part, the details of that day appear in the right Web part. However, SharePoint provides the wrong date as a parameter to the Web part connection between the date views. Therefore, the wrong details appear in the right Web part.
The SPAlert.Filter property cannot set or get a filter value that conatins more than 511 characters.
When you add columns to a content type, the InfoPath document information panel (DIP) must be updated as well. However, if the column is one of a certain set of built-in columns, the DIP cannot be updated.
You cannot create an audit history to discover the roles that a user has had or to see any changes in those roles. You can determine what roles are currently assigned to the user. You can also determine the time that a specific action occurred. However, you cannot determine what roles have been changed. This problem occurs because several false audits are tracked at the time that the change occurs. Therefore, SharePoint cannot create a history. After the user's role is changed for the second time, you can only determine when the role was changed. You cannot determine what the earlier role was.
The Form Web part causes rendering problems on all Web parts on the page as soon as the Form Web part is connected to a document library where the user does not have permissions.
Note Not only the Form Web part, but also any provider Web part that supports multiple connections can cause this issue.
You cannot send meeting requests to a SharePoint calendar from a user whose display name contains a special character, such as an umlaut. The meetings are not created in the SharePoint calendar during incoming e-mail processing. Instead, an error is logged. Outlook can open the calendar without errors. Additionally, Exchange Server 2003 and Exchange Server 2007 can process the calendar e-mail without errors.
When you try to create a Gantt View for all decision items from all meeting instances in a Decision Meeting workspace, only the decision items from currently selected meeting instances appear in the Gantt View.
Data in lookup columns that contain multiple values is lost after you move site collections to a new content database by using the stsadm -o mergecontentdbs command.
Pages may contain links to the wrong location after you perform a SharePoint farm restoration or after you attach a content database.
Search Security trimming needs about 100 seconds for 6000 results when Forms-based Authentication (FBA) is used. However, the search needs less than 2 seconds for 6000 results when Microsoft Windows NT LAN Manager (NTLM) is used.
Memory leaks occur when you upload an InfoPath form. This problem occurs if the form contains two or more rows in a repeating table, and the selected file in the repeating table is connected to a WSS column by one of the following functions:
You browse a "Grouped by" enabled view with the Show filter choices option enabled. When you click to expand the "Grouped by" items, you receive a "RENDER FAILED" error message.
When you move folders in a SharePoint list by using the object model, the ItemCount value for the list is not correctly increased. This causes the object model to return incorrect numbers of items.
In a document library that contains two folders, you delete one folder. Then, you rename the second folder by using the name of the deleted folder. When you perform an incremental content deployment, the incremental content deployment fails. Additionally, you receive the following error message:
Cannot rename "D1" to "C1": destination already exists.
When you click Connect to discussion boardfrom a WSS alert in an Outlook 2007 instance that is connected to an Exchange 2003 server, you receive the following sync error message:
You manipulate custom properties for documents in a document library. When you use code to read or to write the SPListItem.Properties property bag, data loss for date fields occurs. The data loss occurs only when you call the SPListItem.Update()/SystemUpdate after the property bag read operation or write operation.
After a content deployment, the Content Query Web part is empty under Meeting and events. This issue occurs because the Content Query Web part's source list is changed from "/Meetings" to "/default.htm/Meetings".
After you install the hotfix package that this article describes, the CheckEffectivePermissions API is added to Windows SharePoint Services 3.0.
When you use incremental deployment to deploy a site that contains lookup fields from Farm 1 to Farm 2, and then from Farm 2 to Farm 3, the lookup fields do not appear on Farm 3. The lookup fields appear on Farm 2. The deployment job from Farm 2 to Farm 3 succeeds. However, a warning appears that says that the list that is related to the lookup field cannot be found.
You create a Discussion Board list. You add a new post in the list, and then you insert an image at the end of the new post. After you save the post, the image does not appear at the end of the new post. If you click Show Quoted Messages, you can see the image.
When you set the least critical event to report in the Event log to ERROR, and you set the least critical event to report to the trace log to MEDIUM, the following messages are logged in the Unified Logging Service (ULS) logs:
Preserving template record with size…
Deleting template record with size…
However, you only expect these ULS messages to appear if the logging level for General is set to Verbose.
After you clear a value of a list column, you receive an e-mail alert from SharePoint, and you find that the value of the list column is still there. However, you may expect the value of the list column to be formatted with strike-through in the e-mail alert.
When a list contains a calculated date column that is referenced by the calendar view, you receive an unhandled exception when you browse the the calendar view.
When you use Internet Explorer 8 at speeds under 180 kbps to browse the Default.apsx page in a SharePoint site, you receive a JaveScript error. If you refresh the page, the problem does not occur.
You set Windows SharePoint Services 3.0 to send alert e-mails when documents in the document libraries are changed. However, alert e-mails are not sent on on filtered views of document libraries.
An unmanaged memory leak occurs when you add large volumes of Office 2007 files to a SharePoint document library through the SharePoint object model. This problem occurs with .docx files, with .xlsx files, with.pptx files, and with other files.
When you browse Explorer view in the document library by using Internet Explorer 7 from a Windows Vista client, you receive the following error message:
Internet Explorer cannot display the webpage.
When you try to un-publish a document in the document library, and your permissions are set to Item Level, you receive an "Access denied" error message.
When you save an InfoPath 2007 form that has a value that contains percent (%) and double-byte character set (DBCS) characters, the value is not promoted to a list column in Windows SharePoint Service 3.0.
967568 If users update content on the site while you are backing up a SharePoint site collection, the backup file may become corrupted
968172 After you change the Task content type for a SharePoint site collection, you cannot synchronize task items on a newly created Task list
969231 After you install the hotfix package that is described in Microsoft Knowledge Base article 952288, the Site Collection Usage Summary page is broken
970143 You cannot run an incremental content deployment job if a list is deleted and a new list is created that has the same name as the deleted list in Windows SharePoint Services 3.0
970109 A draft version of content that was written in a content editor Web Part is unexpectedly published on the destination site after content is deployed in Windows SharePoint Services 3.0
Issues that this hotfix together with hotfix 968859 fix
To resolve the following issues, you have to install both hotfix 968857 and hotfix 968859. For more information about hotfix 968859, click the following article number to view the article in the Microsoft Knowledge Base:
968859 Description of the Microsoft Office SharePoint Server 2007 hotfix package (Coreserver.msp): April 30, 2009
970155 Error message when you run a full crawl on Business Data Catalog (BDC) data source in Office SharePoint Server 2007: "0X80040E14"
970113 A discussion board item does not index when a crawl is run against the site if the subject contains a period (.)
970003 The filter daemon process crashes when Office SharePoint Server 2007 crawls Office 2007 documents
970108 By default, if you use the CONTAINS Predicate, the search terms in the CONTAINS predicate are hit-highlighted
970010 The thesaurus is not applied when you perform a search after you type text in the "All of these words" text box or in the "The exact phrase" text box in SharePoint Server 2007
968845 Office SharePoint Server 2007 cannot index Office SharePoint Server 2003 portal listings
969401 Search term variants are not highlighted in the search results if you enable search term stemming in Office SharePoint Server 2007
969103 The System.IO.PathTooLong exception occurs when you issue a public "DataSet QueryEx(string queryXml)" method that includes "HitHighlightedSummary" in your Windows SharePoint 3.0-based application
Issue that this hotfix together with hotfix 969414 fix
To resolve the following issue, you have to install both hotfix 968857 and hotfix 969414. For more information about hotfix 969414, click the following article number to view the article in the Microsoft Knowledge Base:
969414 Description of the InfoPath 2007 hotfix package (Ifswfe.msp): April 30, 2009
969215 When you save an InfoPath 2007 form that has a value that contains a percent sign and double-byte character set (DBCS) characters, the value is not promoted to a list column in Windows SharePoint Service 3.0 as expected
Known issues for this package
After you install this package on Japanese versions of Windows SharePoint Server, the Drop-down menu may be expanded to a wider size than expected. This is only a menu experiance issue and has no impact on menu function. Microsoft has confirmed that this is a Windows SharePoint Server product issue that applies to this hotfix package. Microsoft is working on this issue.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problems that are described in this article. Apply this hotfix only to systems that are experiencing the problems described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
To install this hotfix, you must have Windows SharePoint Services 3.0 Service Pack 1 installed. For more information949582, click the following article number to view the article in the Microsoft Knowledge Base:
949583 How to obtain the latest service pack for Windows SharePoint Services 3.0
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
To use one of the hotfixes in this package, you do not have to make any changes to the registry.
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.
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.
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: