November 2001
Microsoft Corporation. All rights reserved.
=====================================================
Thank you for using Microsoft® SharePoint Portal Server 2001 Service Pack (SP) 1. This README file contains important late-breaking information that may not be included in online Help.
Note: This document includes only new issues and changes since the original release. Topics discussed in the original README that are still relevant are not included. For more information, see the original README on the product CD.
=====================================================
When you insert the SharePoint Portal Server CD into your CD-ROM drive, the Start page runs automatically. This page includes links to:
=====================================================
This README file is divided into the following sections:
=====================================================
=====================================================
SharePoint Portal Server SP 1 includes several bug fixes and improvements to general stability. It also includes the following features:
SharePoint Portal Server SP 1 introduces two levels of performance optimization in the dashboard site. Neither optimization is on by default, so dashboard performance remains unchanged after you install SharePoint Portal Server SP 1. A workspace coordinator can invoke the optimizations individually for each dashboard.
Gaining the most performance benefit from the optimizations requires some changes to the settings of the content and Web Part of each dashboard.
For more information about the new optimizations, see "Dashboard Performance Considerations," on the SharePoint Portal Server SP 1 CD at Support\Documentation\newportalperf.doc.
Additional Information about SharePoint Portal Server SP 1
The list of the fixes contained in this service pack is in Microsoft Knowledge Base article Q310460. Each fix listed in Q310460 has a link to a Knowledge Base article describing the problem addressed by the fix. You can locate these articles at http://search.support.microsoft.com/kb/c.asp.
To find articles about SharePoint Portal Server SP 1 fixes in the Knowledge Base:
QFE Fixes
If you received a QFE fix after October 30, 2001, the fix is not included in SP 1. Please contact your primary support provider about QFE fixes against SP 1.
=====================================================
=====================================================
Operating System | Server Support | Client Support | Browser Support (for dashboard site/Web access) only) |
Microsoft® Windows® 95 | No | No | Yes |
Microsoft Windows 98 | No | Yes (limited)* | Yes |
Microsoft Windows NT® 4 (SP6a) | No | Yes (limited)* | Yes |
Microsoft Windows 2000 Professional | No | Yes | Yes |
Microsoft Windows 2000 Server/Advanced Server | Yes (requires SP1) | Yes | Yes |
Microsoft Windows 2000 Datacenter Server | No | No | Yes |
Microsoft Windows Millennium Edition | No | Yes (limited)* | Yes |
Microsoft Windows XP | No | Yes | Yes |
Systems with Microsoft Internet Explorer 5.0 or Higher | Yes | Yes | Yes |
Systems with Microsoft Office XP | Yes | Yes | Yes |
Supported Browsers (dashboard site/Web access only):
Important User's Help includes requirements for accessing the dashboard with UNIX or Macintosh Operating Systems. These platforms are not supported for this version of SharePoint Portal Server.
*Note Windows 98, Windows Millennium Edition, and Windows NT 4.x computers do not support coordinator functions such as scheduling updates and configuring content sources, tasks performed using Microsoft Management Console (MMC), or Web views.
Windows 98 users who upgrade to Windows XP may encounter problems with previously installed client components for SharePoint Portal Server. This problem may occur when you install the client components separately, rather than as part of Office XP. This occurs with the client components for both SharePoint Portal Server and SharePoint Portal Server SP 1. To repair the problem, after installing the operating system, reinstall the client components for SharePoint portal Server SP1.
To provide improved handling of East Asian Uniform Resource Locators (URLs), SharePoint Portal Server SP 1 updates the dashboard site files in all existing workspaces and for all workspaces created after installation of the service pack.
After SharePoint Portal Server SP 1 has been installed on the SharePoint Portal Server computer, the dashboard site is no longer accessible using Internet Explorer 4.x. Internet Explorer users who need to access a SharePoint Portal Server dashboard site after installation of SharePoint Portal Server SP 1 on the server must use Internet Explorer 5.0 or a later version of Internet Explorer.
When installing SharePoint Portal Server Pack 1, the following message may appear:
Setup cannot overwrite the file "D:\Program Files\Common Files\Microsoft Shared\CDO\cdoex.dll". This file is currently being used by another application. Please shut down your other application and try again. Choosing "Continue" copies the file but requires a reboot at the end of setup to complete the installation.
This message is expected whenever other active applications are using Charset (CDO). Continuing to install, and rebooting the server after the installation has completed, succeeds.
If you have a Web site other than the default Web site that uses the computers IP address on port 80 without a host header, you receive an error message when attempting to use the MMC or to create a workspace following installation. This message is "Unable to open the SharePoint Portal Server named '<servername>'.
To determine if this is the cause of the error, check the following for each Web site:
To correct this problem, perform any one of the following steps:
Note Before performing any of the following steps, you should be familiar with how that step affects any other applications or users for this computer.
Installation of SharePoint Portal Server SP 1 overwrites customized dashboard site files. During installation, SharePoint Portal Server backs up the existing dashboard site files by copying them to http://server/workspace/portal/portal.backup for each workspace on the SharePoint Portal Server computer. These files retain the same folder and file structure as in the original http://server/workspace/portal folder.
However, attempting to restore these files by simply copying them back to the original location reverses improvements made to dashboard site performance in SharePoint Portal Server SP 1. You must customize the new dashboard files again, using the backup copies as a reference.
For more information on customizing the dashboard site and delivering the best performance, see Using Management in Dashboard Site Help.
=====================================================
=====================================================
Subscription notifications and approval e-mails sent by SharePoint Portal Server use UTF-8 encoding by default. Mail clients that cannot read UTF-8 are unable to read these notifications. To address this limitation, encoding of subscription notifications is now configurable. To select a different encoding, change the value for the EmailContentCharset registry key.
To change the value for the EmailContentCharset registry key:
CAUTION Incorrectly editing the registry may severely damage your system. Back up the current version of the registry before making any changes. You should also back up any valued data on the computer.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SharePoint Portal Server
When you first send a subscription notification from the server, SharePoint Portal Server creates the EmailContentCharset key. If it is not present, you can add it or send a notification to create the key. It is set to UTF-8 by default.
You can find a list of values for different encodings the CDO documentation in Microsoft Developer Network (MSDN) at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cdosys/html/_cdosys_ibodypart_charset.asp. This is not a comprehensive list.
Based on interviews with customers, Microsoft has learned that customers plan to install Microsoft Exchange 2000 Server and SharePoint Portal Server on separate computers. Typically, customers do not run other server applications on their mailbox servers because of the mission-critical nature of corporate messaging systems.
As a result, Microsoft does not recommend or support using both Exchange 2000 Server and SharePoint Portal Server on a single computer. The coexistence of Exchange 2000 Server and SharePoint Portal Server on a single computer can have a negative effect on your mission-critical messaging infrastructure. However, Microsoft does encourage customers to use the services and data from Exchange 2000 Server and SharePoint Portal Server together in their collaborative solutions and to run the server applications on separate computers.
Some of the potential issues with running Exchange 2000 and SharePoint Portal Server on the same computer include the following:
=====================================================
=====================================================
There are no new naming restrictions issues for SharePoint Portal Server SP 1.
=====================================================
=====================================================
The SharePoint Team Services protocol handler is a Microsoft Search component that allows SharePoint Portal Server computers to search SharePoint Team Services computers and create an index of their content.
CAUTION Documents stored on a server running SharePoint Team Services from Microsoft that are included in an index on a server running SharePoint Portal Server appear in search results even if a user does not have permission for the documents location. The Search summary will make visible the document properties and the first few lines of content. However, normal permissions apply to opening the actual document. To correct this behavior, upgrade your installation of SharePoint Team Services with Office XP Service Pack 1.
You can add a SharePoint Team Web site as you add any other file share, with some additional steps.
By default, the SharePoint Team Services Protocol Handler uses the default content access account specified during SharePoint Portal Server Setup to create and crawl indexes. Alternatively, you can specify another account to create and crawl indexes by using site path rules. In either case, the account must have SharePoint Team Services administrator privileges on the SharePoint Team Web site for that content source.
When you create a SharePoint Team Web site, SharePoint Team Services creates a local group account for that site. The account has SharePoint Team Services administrator privileges, and every member of the group is a member of the SharePoint Team Services administrator role for that site.
When you create a SharePoint Team Web site on a server, SharePoint Team Services adds the BUILTIN\Administrators group for the server to the SharePoint Team Services administrator role. This allows any user in the local administrators group to manage the SharePoint Team Services site completely.
SharePoint Portal Server cannot expand local groups. Because of this, even if the account used to create and crawl the SharePoint Team Web site is a member of the BUILTIN\Administrators group, SharePoint Portal Server cannot determine whether that account is a member of the SharePoint Team Services administrator role. If the BUILTIN\Administrators group is the only member of the SharePoint Team Services administrator role, and there is no site path rule specifying a user account with appropriate privileges, attempts to create or crawl the index fail.
To ensure that an index is crawled without failing:
When setting up your SharePoint Portal Server computer, use this account as the default content access account. Alternatively, create a site path rule for the sites content source that specifies the use of this account when crawling that content source.
To add a SharePoint Team Web site as a content source:
STS://site_name
Note that site_name can correspond to the server name or the name of a site on that server.
CAUTION If you do not clear the Start creating an index check box, the SharePoint Team Services content source does not work properly.
STS://site_name/*
Note that site_name can correspond to the server name or the name of a site on that server.
Note If the default account does not have administrator privileges and you do not complete this step, updates of the index for this content source fail.
If the SharePoint Team Web site that you are adding as a content source includes lists, there is an additional consideration.
By default, list content for SharePoint Team Services appears in search results for lists as a whole. If the search term appears multiple times in a single list, there are not multiple search results for that list. Each list is displayed only once.
If you want search to return a result for every instance of an item in each list, or if you want to exclude lists from the index entirely, you must add a DWORD value in the Windows Registry Editor for each workspace with list content.
To change how list content for SharePoint Team Services is included in indexes and search results:
CAUTION Incorrectly editing the registry may severely damage your system. Back up the current version of the registry before making any changes. You should also back up any valued data on the computer.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\CatalogNames\SharePointPortalServer\workspace_name.
DWORD value | How list content appears in search results |
0 | List content is not included in the index at all, and does not appear in search results. |
1 | List content is included for lists as a whole, rather than for each instance of an item in each list. Each list appears once in the search results no matter how many items in the list match the search terms. This is the same as the default behavior after installing SharePoint Portal Server SP1, before the DWORD value is added. |
2 | All list items in all lists are included in the index. Every item matching the search terms appears in the search results. This is the only value that will make items in secured SharePoint Team Services lists searchable, but using this value will greatly expand the number of items in search results. |
You must update the index after making this change, or search results continue to appear as they did previously.
When creating or building an index for a SharePoint Team Web site, SharePoint Portal Server detects list security and caches the information. If the SharePoint Team Web site administrator changes security on a SharePoint Team Services list, these changes do not appear in SharePoint Portal Server search results until the cache is refreshed. The cache is automatically refreshed when its scheduled expiration time is reached, or when MSSearch restarts. To reflect security changes in SharePoint Portal Server search results immediately, stop and restart MSSearch, then rebuild the index for the SharePoint Team Web site.
SharePoint Team Services does not allow a user without the proper rights to view items on the SharePoint Team Web site, even if the items are visible in SharePoint Portal Server search results.
Unlike other content sources, advanced searches for an exact author name will fail to match items added to the index from SharePoint Team Web sites unless specified in the form domain\username. Searches for local items and items from other content sources remain unchanged.
The IFilter for Microsoft Office documents does not report the locale when including properties in the index. SharePoint Portal Server uses the locale of the computer creating the index instead of the locale of the computer where each document is stored. As a result, searches on properties such as Title Contains <non-English term> may not return the expected results.
=====================================================
=====================================================
In the previous release of SharePoint Portal Server, users who wanted to open a document for editing from the dashboard site were required to locate the document separately using Web folders and open it there.
SharePoint Portal Server SP 1 modifies the summary Web Part in the dashboard site to allow users to open the Web folder for a document directly from the dashboard site, avoiding the need to find the specific location of the document.
After installing the service pack, SharePoint Portal Server adds an Open in Web Folder link to the Folder Information Web Part at the top of the home page of the dashboard site. The link is displayed right next to Add a Document as one of the available options. You must still install the client components for SharePoint Portal Server.
The original release of SharePoint Portal Server used canonicalized UTF-8 to encode URLs to documents in the dashboard site that included double-byte character set (DBCS) characterssuch as those in East Asian languages. Canonicalized UTF-8 uses 9 bytes to store DBCS characters that are only one or two bytes in Unicode.
When users performed a document management task such as check in, check out, or publish, the URL of the document appended to the URL for the browser address. For DBCS file or folder names, the length of the file or folder name in the URL for the browser address after conversion could be up to nine times longer than the original file or folder name of the document.
This exposed an issue with Internet Explorer that prevents a user from opening Microsoft Office documents from the dashboard site when the file name portion of the URL exceeds 255 bytes. There was also an issue with exceeding the system limit of 2K in memory for the URL as a whole. This was particularly an issue when the folder depth of the document was high, because those folders have longer URLs. Effectively, this limited potential folder depth in the workspace.
For SharePoint Portal Server SP 1, the URL encoding uses non-canonicalized Unicode instead of canonicalized UTF-8. This represents the URL in the same number of characters, so that the URL of the document does not easily exceed the URL length limit. SharePoint Portal Server SP 1 also handles browser navigation differently, avoiding an additional doubling of the size of the URL. This also allows users to perform document management tasks in folders that are close to the browser URL length limit.
When checking in or publishing documents to the dashboard site, Publishing and Knowledge Management Collaboration Data Objects (PKMCDO) creates a zero-byte file, and then writes the content to the Web Storage System as a text stream.
When trying to check in or publish an .EML message, the Web Storage System attempts to validate the .EML message format as soon as the message is created. Because the .EML message is zero bytes during this validation, the attempt to add the file to the Web Storage System fails. This results in the following error message:
An error occurred while processing your request. Please contact your system administrator for this server.
If you are checking in or publishing documents programmatically using PKMCDO, you may get the following error:
Object or data matching the name, range, or selection criteria was not found within the scope of this operation.
This problem occurs whenever PKMCDO is used. SharePoint Portal Server uses PKMCDO when publishing and checking in documents using the dashboard site, and PKMCDO can be used directly in custom applications by calling its APIs. It does not occur when checking in or publishing documents from Web Folders in Windows Explorer, which does not use PKMCDO.
Software developers using PKMCDO can work around this issue by renaming the file with an .xxx extension, writing the contents in the text stream, and then renaming the file back to an .eml extension.
The Minimize and Close buttons may appear on new Web Parts, though these buttons do not function as expected. To avoid this, clear the following check boxes when creating new Web Parts:
You can also clear these check boxes after creating the Web Part.
To remove the Minimize and Close buttons after creating a Web Part:
To speed up performance of the dashboard site, it is recommended that you enable full-page caching for each dashboard used in your site. To enable full page caching, you must first run Portalperf.vbs, and then set the cache setting for all Web Parts to All Users from the Web Part Settings page. This allows Web Parts to be stored in the cache, so that the dashboard site loads more quickly.
Note that dashboards such as Categories and Document Library have multiple views that do not work properly if you enable full-page caching. This setting is most appropriate for the Home dashboard.
For more information on improving dashboard site performance, see "Dashboard Performance Considerations," on the SharePoint Portal Server SP 1 CD at Support\Documentation\newportalperf.doc.
Users running Windows XP on their client computer can copy categories from the Category folder of the workspace to their client computer. If the categories are extensive enough, this can cause the client computer to stop responding. This is not possible with Windows 2000 and Windows 98, and should not be possible with Windows XP. Future service packs will not support the ability to copy categories to the client computer.
=====================================================
=====================================================
There are no new documentation issues for SharePoint Portal Server SP 1.
=====================================================
=====================================================
Information in this document, including URL and other Internet Web site references, is subject to change without notice and is provided for informational purposes only. The entire risk of the use or results of the use of this document remains with the user, and Microsoft Corporation makes no warranties, either express or implied. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
® 2000-2001 Microsoft Corporation. All rights reserved.
Microsoft, MS-DOS, Windows, Windows NT, and SharePoint are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.