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, 2008.
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 packages.
951249
(http://support.microsoft.com/kb/951249/
)
You do not receive search alerts when you use the FullTextSqlQuery object to perform a full-text search of a server that is running SharePoint Server 2007
This hotfix package also fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:
Consider the following scenario:
On a Windows SharePoint Services 3.0 site, you set the regional settings of the site and the format of the currency to a locale. This locale uses a comma (,) as a decimal symbol and uses a period (.) as the digit grouping symbol for the currency format.
For example, if you select Germany as the locale, the currency is displayed in the following format:
123.456.789,00 €
In a document library on the site, you create a new document that is based on a custom document content type. This custom document content type contains a Currency type column.
You open the document in a Microsoft Office application on a client computer that uses the same locale as the Windows SharePoint Services 3.0 site.
In the Document Properties pane of the document, you enter a number that has a comma in the Currency field. Then, you save the changes to the document.
You examine the properties of the document from the document library.
In this scenario, the value of the Currency property is displayed incorrectly as a number that does not have a comma.
For example, when the locale is set to Germany, "100,99" is displayed incorrectly as "10.099,00" in Microsoft Word.
The calendar cannot show all items when you click the link. This condition indicates that one more item exists for that day.
Consider the following scenario:
On a Windows SharePoint Services 3.0 site, you create a new discussion item on a discussion board.
The subject of the discussion item ends with a double-byte space character.
When you search this discussion item on the discussion board, you receive a link that points to the discussion item.
You click the link to open the discussion item.
In this scenario, you receive the following error message:
Page not found
Note This issue does not occur if the subject of the discussion item ends with a single-byte space character.
You have a Windows SharePoint Services 3.0 site that contains lots of items and that takes a long time to back up. When you try to make a backup of the site, the backup operation stops unexpectedly at the seventeenth hour.
Consider the following scenario:
In Microsoft Office SharePoint Designer 2007, you create a workflow that is attached to a list in a Windows SharePoint Services 3.0 site.
The Windows SharePoint Services server uses a localized version of Microsoft Office SharePoint Server 2007 that displays the time in 24-hour mode.
For example, the time is usually displayed in 24-hour mode in the German version of SharePoint Server 2007.
The workflow contains a field that uses "Date and Time" as the Information type. The value of this field is displayed in the "Date and Time" format.
You try to create a workflow for a list item on the Windows SharePoint Services site.
In this scenario, the Date and Time field in the initiation page contains no AM and PM symbols. The hours in the Date and Time field range from 1 to 12 instead of from 1 to 24. Therefore, you cannot distinguish 1:00 AM from 1:00 PM.
You have a Windows SharePoint Services 3.0 site that uses the Lightweight Directory Access Protocol (LDAP) role provider as the user authentication provider. In this case, the e-mail messages that are configured to be sent to the user groups cannot be received.
Consider the following scenario:
You enable advanced usage analysis processing in a Shared Services Provider (SSP) in SharePoint Server 2007.
You set the regional and languages options on the server to "Thai."
You open a site that uses the SSP and then connect to the site usage report or to the site collection usage report.
In this scenario, no site usage data is displayed.
On a Windows SharePoint Services 3.0 site, you move a meeting workspace for a recurring meeting from a source subsite to a destination subsite. Then, you change the recurrence of the meeting on the source subsite.
When you do this, you receive the following error message:
Changes to the event were saved, but they could not be communicated to the Meeting Workspace associated with the event. For more information, contact the server administrator.
Then, you try to access the meeting workspace for one of the new dates for the recurring meeting. When you do this, you receive the following error message:
The meeting occurrence you are trying to access does not exist within the Meeting Workspace. Please select a valid date and try again.
On a Windows SharePoint Services 3.0 site, you create a recurring meeting workspace. Then, you use the Stsadm tool to export and then to import the meeting workspace when some meetings are opened. When you do this, some duplicate meeting entries are added.
Consider the following scenario:
On a server that is running Windows SharePoint Services 3.0, you create a Windows SharePoint Services site.
The time zone that you set on the server differs from the time zone that you set on the site.
You subscribe to a Really Simple Syndication (RSS) feed from a discussion list on the site.
On a client computer, you access the RSS feed by using Windows Internet Explorer or any other RSS feed reader.
In this scenario, the published time of the RSS feed is calculated incorrectly.
On a Windows SharePoint Services 3.0 site, a discussion topic can be created unexpectedly without any input in the body of the topic.
When you search a file by using a path property that contains more than 64 characters, many files may be returned.
This issue occurs because the search value is truncated to 64 characters.
Consider the following scenario:
You add a document library Web Part and a list Web Part to the home page of a Windows SharePoint Services site.
You edit the document library Web Part to include rows in the list.
You set the items to be grouped by a column in the List view.
You click a file in the document library to show the corresponding items in the list.
In this scenario, an incorrect number of items is shown in the list.
A customer has to implement some business logic synchronously when a major version of a document is being checked in. However, no property can be used to indicate that the customer is checking in a major version.
Consider the following scenario:
You move folders around document libraries in SharePoint Server 2007 programmatically or by using the Explorer view.
You perform several incremental crawls.
In this scenario, search results may be displayed incorrectly for the folder. Additionally, if you click some results that point to old locations, you may receive the following error message:
404 Not Found
You set the toolbar type for a Web Part to No Toolbar. When you do this, the custom views for the list in the Web Part are no longer available in any view list.
You configure the document library in a Web application to accept incoming e-mail attachments. When you do this, the e-mail attachments can be added to the document library.
However, the incoming e-mail attachments cannot be added to the document library after you disable any of the following user rights for the Web application in Windows SharePoint Services 3.0:
Create Subsites
ManageWebSite
ViewPages
Open
ManagePermissions
BrowseDirectories
UseRemoteInterfaces
In Windows SharePoint Services 3.0, you create a Web application on a port, and then you extend the same Web application on another port. Then, you add the content to the Web.config file by using the Web Config object model (SPWebConfigModification). When you do this, the content is added to both the primary and extended Web applications as expected.
However, if you remove the content from the Web.config file by using the Web Config object model, the content is removed only from the primary Web application.
On a Windows SharePoint Services site, a content type for a document library matches the following criteria:
The content type has lots of "Single line of text" columns and "Hyperlink or Picture" columns.
The last column for the content type is a "Hyperlink or Picture" column.
When you open the document library, you may receive the following error message:
Cannot complete this action
You enable the Definition Extraction feature in SharePoint Server 2007. When you search for some words in SharePoint Server 2007, you may receive the following error message:
Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Windows SharePoint Services-compatible HTML editor such as Microsoft Office SharePoint Designer. If the problem persists, contact your Web server administrator.
For example, if you search for "Abbott," you may receive the error message.
Consider the following scenario:
You set one of the site collections to be Read-only.
You perform an incremental crawl for the content database.
You search the changes that you made on a site collection.
In this scenario, the changes are not displayed in the search results.
A user who has Contributor permissions to a Windows SharePoint Services site tries to upload a document to the site. When this occurs, the user may receive the following error message:
Access Denied
This issue occurs when the title of the document contains one of the following characters:
#
%
&
*
:
<
>
?
/
{
|
}
"
On a Windows SharePoint Services 3.0 site, you customize a page by modifying a list view Web part. When you try to save the modification, you receive the following error message:
404 not found
You apply hotfix 950484 to resolve this problem. After you do this, you create a standard view for the list and then delete the standard view. When you do this, you receive the following error message:
HTTP 404
For more information about hotfix 950484, click the following article number to view the article in the Microsoft Knowledge Base:
950484
(http://support.microsoft.com/kb/950484/
)
Description of the Windows SharePoint Services 3.0 hotfix package: March 27, 2008
Additionally, this hotfix introduces a design change to enable users to download infected files when a download scan that is performed by using antivirus software is disabled.
This section describes a known issue that occurs after you apply the hotfix.
Symptoms
You add a custom list as a Web Part on the home page of a Windows SharePoint Services site. Then, you try to edit the current view of the custom list by clicking Edit the current view. When you do this, the Create View page is opened.
However, you expect the Edit View page to be opened.
Workaround
To work around this issue, edit the list view before you add the custom list to a Web Part on the home page of the Windows SharePoint Services site. To do this, follow these steps:
Remove the Web Part that contains the custom list from the home page.
Open the custom list, and then click Modify this View.
On the Edit View page, make the changes that you want, and then click OK.
Re-add the custom list to a Web Part on the home page.
A supported hotfix is 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 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.
Prerequisites
To apply this hotfix package, you must have Windows SharePoint Services 3.0 installed.
Restart requirement
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.
Registry information
To use one of the hotfixes in this package, you do not have to make any changes to the registry.
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.
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.
Windows SharePoint Services 3.0, 32-bit versions
Download information
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Wss-kb952288-fullfile-x86-glb.exe
12.0.6300.5000
23,334,616
05-May-2008
05:43
x86
Microsoft Windows Installer .msp file information
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Sts.msp
Not applicable
23,565,824
01-May-2008
16:35
Not applicable
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:
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:
Back to the top
