How to download and install the update

Important Before you install this update, make sure that the following requirements have been met:

•	Microsoft Windows Installer 2.0 Before you install this update, you must install Windows Installer 2.0 or later. For additional information about this requirement, see the "Windows Installer UpdateRequirements" section of this article.

Client update

If you installed SharePoint Team Services from Microsoft from a CD-ROM, you have the following two options:

•	Use the Microsoft Office Product Updates Web site to automatically install all the latest updates that include all available service packs and public updates.
•	Install only the Microsoft Office XP SP3 for SharePoint Team Services by following the steps that are described later in this article.

Note Microsoft recommends that you install the client update by using the Office Product Updates Web site. The Office Product Updates Web site detects your particular installation of Microsoft Office and prompts you to install exactly what you must have to make sure that your Office installation is completely up-to-date.

Office Product Updates Web site

To have the Office Product Updates Web site detect the required updates that you must install on your computer, visit the following Microsoft Web site: After detection is complete, you receive a list of recommended updates for your approval. Click Start Installation to complete the process.

Install only Office XP SP3 for SharePoint Team Services

To download and install the client update, follow these steps:

1.	Visit the following Microsoft Web site: http://www.microsoft.com/downloads/details.aspx?FamilyId=2818E9DF-79FF-49A4-89C1-CAD72FEA9B32 (http://www.microsoft.com/downloads/details.aspx?FamilyId=2818E9DF-79FF-49A4-89C1-CAD72FEA9B32)
2.	Select your language, and then click Download.
3.	Click Open to start the download and the installation of Office XP SP3 for SharePoint Team Services installation file.
4.	If you are prompted to install the update, click Yes.
5.	Click Yes to accept the License Agreement.
6.	Insert your Office XP for SharePoint Team Services CD-ROM if you are prompted to do so, and then click OK.
7.	When you receive a message that indicates the installation was successful, click OK.

Note After you install the update, you cannot remove it. To revert to an installation before the update was installed, you must remove Office XP SP3 for SharePoint Team Services, and then install it again from the original CD-ROM.

Administrative update

If you installed Office XP SP3 for SharePoint Team Services from a server location, the server administrator must update the server location with the administrative update and deploy that update to your computer.

If you are the server administrator, follow these steps to download the administrative update:

1.	In Microsoft Windows Explorer, create a new folder on drive C, and then name the folder kb833845.
2.	The following file is available for download from the Microsoft Download Center: Download the English version of the Office XP Service Pack 3 (SP3) for SharePoint Team Services package now. (http://download.microsoft.com/download/0/1/b/01b7f0a8-8649-4a60-9f25-1198d48a989c/stssp3-kb833845-fullfile-enu.exe) Release Date: March 9, 2004 For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base: 119591 (http://support.microsoft.com/kb/119591/) How to Obtain Microsoft Support Files from Online Services Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file. Note To obtain a localized version of the Office XP SP3 for SharePoint Team Services, visit the following Microsoft Web site: http://www.microsoft.com/office/ork/updates/xp/StsSP3.htm (http://www.microsoft.com/office/ork/updates/xp/StsSP3.htm)
3.	Click Save, and then save the Office XP Service Pack 3 (SP3) for SharePoint Team Services installation file to the C:\kb833845 folder.
4.	Click Start, and then click Run.
5.	In the Open box, type cmd, and then click OK.
6.	At the command prompt, type the following lines, and then press ENTER after each line: cd\kb833845 Ows10Sp3-kb833845-fullfile-language version.exe /c /t:c:\kb833845 Notelanguage version is the language identifier of the installation file that you downloaded previously. For example: cd\kb833845 Ows10Sp3-kb833845-fullfile-enu.exe /c /t:c:\kb833845
7.	Click Yes to accept the License Agreement.
8.	At the command prompt, type exit, and then press ENTER to quit the command prompt.
9.	If you are familiar with the procedure for updating your administrative installation, click Start, and then click Run. Type the following command in the Open box msiexec /a AdminPath\MSI File /p C:\kb833845\MSP File SHORTFILENAMES=TRUE where Admin Path is the path of your administrative installation point for Office XP for SharePoint Team Services (for example, C:\STS2002), MSI File is the .msi database package for Office XP for SharePoint Team Services , and MSP File is the name of the administrative update. Note You can append /qb+ to the command line so that the Office XP for SharePoint Team Services Administrative Installation dialog box and the End User License Agreement dialog box do not appear.
10.	To deploy the update to the client workstations, click Start, and then click Run. Type the following command in the Open box msiexec /i AdminPath\MSI File REINSTALL=Feature List REINSTALLMODE=vomu where Admin Path is the path of your administrative installation point for Office XP for SharePoint Team Services (for example, C:\STS2002), MSI File is the MSI database package for Office XP for SharePoint Team Services, and FeatureList is the list of feature names (case sensitive) that have to be reinstalled for the update. To install all features, you can use REINSTALL=ALL, or you can install the following features: FPHtmlAdmin,FPSE,FPSELangSupport,Complete

For additional information about how to update your administrative installation and deploy to client workstations, click the following article number to view the article in the Microsoft Knowledge Base: This article contains standard instructions for installing an administrative public update. You can also see the following article in the Microsoft Office Resource Kit:

Back to the top

How to determine whether the update is installed

The update contains updated versions of the following files:

   Date         Time   Version      Size       File name
   -------------------------------------------------------
   09-Oct-2003  02:48                  18,051  Adduser.htm
   13-Oct-2003  20:02  10.0.6308.0     27,192  Admin.dll        
   13-Oct-2003  20:02  10.0.6308.0     27,192  Author.dll       
   13-Oct-2003  20:03  10.0.6308.0    105,016  Cfgwiz.exe       
   13-Oct-2003  20:03  10.0.6308.0    141,888  Fp5amsft.dll     
   12-Jun-2002  19:07  10.0.4205.0     36,424  Fp5areg.dll      
   13-Oct-2003  20:10  10.0.6308.0    944,696  Fp5autl.dll      
   13-Oct-2003  20:03  10.0.6308.0     47,672  Fp5avnb.dll      
   19-Nov-2003  02:11  10.0.6417.0  1,378,832  Fp5awel.dll      
   13-Oct-2003  20:02  10.0.6308.0     27,200  Fpadmdll.dll     
   09-Oct-2003  02:34                 119,728  Fpext.msg
   13-Oct-2003  20:04  10.0.6308.0    399,928  Fpmmc.dll        
   09-Oct-2003  02:48                  33,185  Genset.htm
   13-Oct-2003  20:02  10.0.6308.0     27,192  Owsadm.exe       
   03-Dec-2003  22:57  10.0.6501.0    834,056  Owssvr.dll       
   13-Oct-2003  20:04  10.0.6308.0    346,688  Owstimer.exe     
   13-Oct-2003  20:02  10.0.6308.0     27,192  Shtml.dll 

To determine the version of Microsoft Office XP for SharePoint Team Services that is installed on your computer, follow these steps.
Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

1.	Click Start, and then click Search.
2.	In the Search Results pane, click All files and folders under Search Companion.
3.	In the All or part of the file name box, type the file name of a file that is listed in the previous installed list, and then click Search.
4.	In the list of files, right-click the found file, and then click Properties.
5.	On the Version tab, determine the version of SharePoint Team Services that is installed on your computer.

Note If Office XP SP3 for SharePoint Team Services is already installed on your computer, you receive the following error message when you try to install Office XP SP3 for SharePoint Team Services:

Back to the top

Windows Installer Update Requirements

To install the update that is described in this article requires Windows Installer 2.0 or later. Both Microsoft Windows XP and Microsoft Windows 2000 Service Pack 3 (SP3) include Windows Installer 2.0 or later. To install the latest version of the Windows Installer, visit one of the following Microsoft Web sites.

Windows Installer for Microsoft Windows 98, and Microsoft Windows Millennium Edition (Me): Windows Installer for Microsoft Windows NT 4.0 and Windows 2000:

Back to the top

List of issues that are fixed by the update

The Office XP Service SP3 for SharePoint Team Services includes the following earlier released updates:The Office XP SP3 for SharePoint Team Services fixes the issues that are described in the following Microsoft Knowledge Base articles:

The Office XP SP3 for SharePoint Team Services fixes the following issues that were previously not documented in the Microsoft Knowledge Base:

You receive the "Root Web not found" error message when you try to create a subweb under an unextended virtual folder

When you try to create a subweb under an unextended virtual folder, you receive the following error message:

You receive an HTTP 404 error message when you click Help on the Server Extensions 2002 tab

When you click Help on the Server Extensions 2002 tab (right-click your server in Internet Information Services (IIS) Manager, and then click Properties), you receive the following error message:

The server extensions are not changed to "prohibited" in IIS Manager after you remove Microsoft FrontPage Server Extensions 2002

After you remove Microsoft FrontPage Server Extensions 2002, the server extensions are not changed to "prohibited" in Internet Information Services (IIS) Manager.

A log entry is not created in the application event log for an Indexing Service error message

When an Indexing Service error message occurs, a log entry is not created in the application event log.

You receive an Access Violation error message on virtual directory in IIS Manager

When you right-click a virtual directory or click Action on the menu bar in Internet Information Services (IIS) Manager, you may receive an Access Violation error message.

A .vb file causes a compilation error message when you open a Web site in FrontPage 2002

When you open your Web site in FrontPage 2002 that contains a .vb file in the code directory, you receive an error message that is similar to the following:

The SearchCatalogName registry key is added for new subwebs

If you install a new version of the FrontPage Server Extensions 2002 and do not upgrade your root Web, the SearchCatalogName registry key is added to the registry for any new subwebs that you may create.

You receive a "Server busy" error message when you publish to a different Windows .NET server

If you open your Web from a UNC location and then publish the Web site to a different Windows .NET server, the publishing may time-out, and you receive the following error message:

You cannot add a role after you move a Web site

If you move your Web site and then install and upgrade your new Web site with FrontPage Server Extensions 2002, you receive the following error message when you try to add a role:

The New Document button in the shared documents library does not open a new document

When you click New Document in the Shared Documents document library of your SharePoint Team Services site, nothing happens. This problem may occur when your shared document library does not contain a default (pre-specified) template.

Back to the top