Microsoft Office Online
Sign in to My Office Online (What's this?) | Sign in

 
 
Products
Search
Search
 
Check for updates: (c) Microsoft
Microsoft Update
 
Warning: You are viewing this page with an unsupported Web browser. This Web site works best with Microsoft Internet Explorer 6.0 or later, Firefox 1.5, or Netscape Navigator 8.0 or later. Learn more about supported browsers.
Email this linkEmail this link Printer-Friendly VersionPrinter-Friendly Version
Microsoft Windows SharePoint Services 3.0 Known Issues/ReadMe

Windows SharePoint Services

Issue Type Question or Issue Answer

Readme Software Requirements

Current Readme contains references to:

A computer running Microsoft Windows Server 2003 (Standard, Enterprise, or Datacenter) with Service Pack 1 (SP1), Microsoft Windows Workflow Foundation Runtime Components Beta 2.2 (Build 3807.7), and Microsoft .NET Framework 2.0. Instructions for installing the Windows Workflow Foundation Beta 2.2 and Microsoft .NET Framework 2.0 are provided later in this section.

References should read as:

A computer running Microsoft Windows Server 2003 (Standard, Enterprise, or Datacenter) with Service Pack 1 (SP1), Microsoft Windows Workflow Foundation Runtime Components Beta 2.2 (Build 4302.2), and Microsoft .NET Framework 2.0. The computer must be configured as a Web server running Microsoft Internet Information Services (IIS) in IIS 6.0 worker process isolation mode. The computer must be using the NTFS file system.

 Note   You cannot install Windows SharePoint Services 3.0 as a standalone server on Windows Server 2003, Web Edition.

Upgrade - Shared Services

After upgrading pre-B2TR builds to B2TR or RTM, the links to SSPs in the central administration navigation control takes user to OLD farm.

Run the following stsadm command:

stsadm -o activatefeature -name OssNavigation -url <SSP admin site url>

Delete Web Application

A Central Administration user tries to delete a Web application and gets this error message:

This operation uses the SharePoint Administration service (spadmin), which could not be contacted. If the service is stopped or disabled, start it and try the operation again.

However, the admin service is running.

Delete Web application requires box administrator privileges. When a central admin user who is not a box admin tries this function, the call to the admin service fails with the wrong error message.

Setup

During the installation of Windows SharePoint Services, you get the following error in the configuration wizard:

This access control list is not in canonical form and therefore cannot be modified.

This issue will occur if you are using Sysinternal's Newsid utility to reset the SID of the machine or image.

To work around this issue do the following:

  1. Uninstall Windows SharePoint Services.
  2. Join the server to a workgroup.
  3. Remove the machine account from domain.
  4. Run sysprep from Windows Support Tool's deploy.cab.
  5. Reboot and rejoin the domain.
  6. Install Windows SharePoint Services.

The alternative solution is to rebuild the server from scratch and not use NewSID or other imaging solutions.

Setup

Hardware and software requirements and deployment instructions for Windows SharePoint Services 3.0

For deployment information and requirements, consult the deployment web site at:

http://go.microsoft.com/fwlink/?LinkId=73952.

For further information, visit the Windows SharePoint Services 3.0 web site at:

http://go.microsoft.com/fwlink/?LinkId=73953.

Upgrade/Migration

InfoPath forms may not function properly while a Windows SharePoint Services gradual upgrade is in progress, or after content has been moved from one server to another.

InfoPath form templates contain fully-qualified URLs to some resources, such as data connections to SharePoint lists. If the URL to one of these resources changes, InfoPath will no longer be able to access that resource.

The Server Upgrade and Migration Tool for Microsoft Office InfoPath, available on the Microsoft.com download center, will allow the administrator of a SharePoint farm to update Form templates and other InfoPath collateral on the farm with a new server URL so that these forms continue to work as expected.

Content Deployment

When creating a content deployment path which replicates a site collection to another site collection within the same farm, but on another managed path, the following error occurs:

Value does not fall within the expected range.

The workaround is as follows:

Stsadm -o deactivatefeature -name deployment -url <URL>

Stsadm -o deactivatefeature -name migration -url <URL>

Stsadm -o activatefeature -name deployment -url <URL>

Stsadm -o activatefeature -name migration -url <URL>

Document Conversions

Document Conversions Launcher Service is always in "starting" state (specifically when trying to enable the Launcher Service on more than one Server in the farm).

The Document Conversions Launcher Service Admin UI is not functional for any Launcher that will run on a server that is not hosting the Central Administration web application. The UI will never reflect current state in this configuration.

WORKAROUND:

To enable the Launcher Service you must specify the necessary Launcher information that the UI normally provides. This is done by updating two values in a registry key located on the machine on which you are trying to run the Launcher service. This includes the location of the Load Balancer and the Port to use for the connection.

Key:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\LauncherSettings]"LoadBalancerUrl"="http://server:port/HtmlTrLoadBalancer""Port"=dword:port

LoadBalancerUrl:

This is the full URL to the .NET Remoting channel that the Load Balancer opens. The scheme should be http://[please specify Load Balancer server]:[please specify Load Balancer port]/HtmlTrLoadBalancer and ensure they are accurate.

Port:

This is the port that the launcher service will open for incoming .NET Remoting requests to do Conversions, e.g. "8082".

After changing either of these settings (initially or if future machines are added and require settings changes), you must stop and start the Launcher service (Office Document Conversions Launcher Service) in the Services control panel (Start|Control Panel|Administrative Tools|Services). The services should be set to Enabled and set to start automatically (Automatic) if not so already.Any future changes to the Load Balancer settings will require updating the Launcher settings on each machine to reflect those changes. The services will also have to be stopped and then started again to pick up the new changes once updated.

Top of Page Top of Page
Printer-Friendly VersionPrinter-Friendly Version