Microsoft Windows SharePoint Services 2.0 Readme File

Microsoft Windows SharePoint Services 2.0 Readme File

© 2003 Microsoft Corporation. All rights reserved.

This document provides late-breaking information about Windows SharePoint Services from Microsoft.

How to use this document

To view the Readme file on the screen, maximize the browser window. To print the Readme file, click the Print button on the toolbar.

Contents

On servers upgraded from Windows 2000 Server to Windows 2003 Server, verify that FrontPage 2002 Server Extensions are not running on port 80

Make sure Read and Run Scripts permissions are enabled in IIS before extending virtual servers

Internet Explorer Enhanced Security Configuration issues

Security issue: Source code for Web Part Pages can be viewed when placed in a document library

Temporary files may be left on server disk

Lack of permissions for application pool account can cause Web Parts to not display on home page

Using Windows SharePoint Services and Universal Description, Discovery, and Integration on the same virtual server

On servers upgraded from Windows 2000 Server to Windows 2003 Server, verify that FrontPage 2002 Server Extensions are not running on port 80

If you are installing Windows SharePoint Services with the default options (you are not using remotesql=yes), verify that FrontPage 2002 Server Extensions from Microsoft are not installed and running on the virtual server on port 80 before you install. (If you upgraded from Windows 2000 to Windows Server 2003, FrontPage 2002 Server Extensions were installed by default to port 80.)

If you want to preserve the content from your FrontPage 2002 Server Extensions-based site, use the Microsoft SharePoint Migration tool (smigrate.exe) to migrate the content to your new Windows SharePoint Services-based site before uninstalling. Note that you can run Windows SharePoint Services and FrontPage 2002 Server Extensions on the same server. For information on using the SharePoint Migration Tool or running Windows SharePoint Services and FrontPage 2002 Server Extensions on the same server, see the Windows SharePoint Services Administrator's Guide at http://www.microsoft.com/SharePoint/Assistance.

To remove FrontPage 2002 Server Extensions from the default virtual server:

  1. Click Start, and then click Run.
  2. In the Run window, type cmd, and then click OK.
  3. Change to the directory where FrontPage 2002 Server Extensions are installed. For example:

    cd ..\..\program files\common files\microsoft shared\web server extensions\50\bin

  4. Type the owsadm.exe command to uninstall FrontPage 2002 Server Extensions:

    owsadm.exe -o fulluninstall -p <port number>

    Where <port number> represents the port number used by the virtual server running FrontPage 2002 Server Extensions.

Make sure Read and Run Scripts permissions are enabled in IIS before extending virtual servers

With Windows Server 2003 Service Pack 1, there is a change to default site permissions turned on by the Web Site Creation Wizard in Internet Information Services (IIS). When creating a new site that you intend to run with Windows SharePoint Services, on the Web Site Access Permissions screen, make sure that both Read and Run Scripts (such as ASP) permissions are turned on.

Note   Turning on the Run Scripts (such as ASP) option allows script files on the site to run. Script files can contain malicious code or be vulnerable to attacks from outside users. When creating sites in IIS, do not turn on the Run Scripts (such as ASP) option unless the site is running Windows SharePoint Services or has script files from a trusted source.

Internet Explorer Enhanced Security Configuration issues

By default, Windows Server 2003 installs with Internet Explorer Enhanced Security Configuration enabled. These settings limit the types of content that a user at the server can view using Microsoft Internet Explorer, except for sites listed in the Local intranet and Trusted sites zones. These settings cause Windows SharePoint Services to not function correctly when browsing or managing the site locally.

Note  Internet Explorer Enhanced Security Configuration does not affect remote users viewing content on the server— it only affects users running Internet Explorer on the server computer itself.

To browse or manage Windows SharePoint Services from the server, either remove Internet Explorer Enhanced Security Configuration by using Add or Remove Programs in Control Panel, or add the URLs of all virtual servers that are hosted by the server to the Internet Explorer Local intranet zone. To add a Web site to this security zone:

  1. Browse to a site hosted by the server that you want to add to the Local intranet list.
  2. On the Tools menu, click Internet Options.
  3. Click the Security tab, and then click the Local Intranet zone.
  4. Click Sites.
  5. Click Advanced.
  6. Enter the URL of the site hosted by the server, and then click Add.

Security issue: Source code for Web Part Pages can be viewed when placed in a document library

The source code of Web Part Pages is visible to members of the Contributor site group (or any user with the Edit Items right) when a Web Part Page is stored in a document library. This means that users with these permissions can read sensitive information stored in Web Parts such as user names and passwords. This affects both embedded and dynamic Web Parts, because it is possible for contributors to edit pages from a document library by using a Windows SharePoint Services-compatible Web page editor such as Microsoft Office FrontPage 2003.

Temporary files may be left on server disk

When users navigate to a SharePoint site, temporary files are left on the Web server's hard disk. Over time, these temporary files will take up more and more server disk space. To resolve this problem, download and install the update for Windows Server 2003 from the Windows update site. For more information, search for article 824629 in the Microsoft Knowledge Base at http://support.microsoft.com.

Lack of permissions for application pool account can cause Web Parts to not display on home page

If the account used for authenticating the application pool for Windows SharePoint Services does not have read and write permissions to the directory that Windows uses for temporary files, Web Parts may not display properly. When this occurs, the following error message appears: 

Web Part Error: One of the properties of the Web Part has an 
incorrect format. Windows SharePoint Services cannot deserialize 

the Web Part. Check the format of the properties and try again.

Typically, this problem occurs when the Windows directory for temporary files is set to something other than the default location (%systemroot%\temp -- usually c:\windows\temp). To resolve this problem, give the account permissions to the directory for temporary files.

  1. Locate the system temporary directory.
  2. Go to the directories listed for TEMP and TMP.
  3. Right-click on the folder for the temporary directory, and then click Sharing and Security.
  4. On the Security tab, verify that the application pool account for the content virtual server has Read and Write permissions in each of the directories.

For information about configuring the application pool account, see the Windows SharePoint Services Administrator's Guide at http://www.microsoft.com/SharePoint/Assistance.

Using Windows SharePoint Services and Universal Description, Discovery, and Integration on the same virtual server

If you are using Windows SharePoint Services and Microsoft Windows Server 2003 Universal Description, Discovery, and Integration (UDDI) service on the same virtual server, you must modify the UDDI web.config file by inserting the line <trust level="Full" originUrl=""/> immediately before the line </system.web>. The web.config file is located in the %\inetpub\uddi\webroot directory.