Last Modified: November 6, 2003
This Readme contains late-breaking information about Microsoft® Content Management Server (MCMS) 2002 with SP1a.
Important Before you install MCMS 2002 with SP1a, it is recommended that you review this Readme.
This Readme contains a list of known issues.
When you upgrade from MCMS 2002 SP1 to the Enterprise edition, you may get an error message that says "The following applications should be closed before continuing the installation," but the message does not list any applications.
Ignore this message and continue with the installation.
If you run the Repair option from the Add/Remove component of the Control Panel to repair your MCMS 2002 with SP1a installation, the Server Configuration Application (SCA) shortcut may not appear on the Start menu.
You can manually add the shortcut by navigating to <install drive>:\Program Files\Internet Explorer\IEXPLORE.EXE http://<computer name>:<port>\NRConfig.
Modifying MCMS 2002 with SP1a from Add/Remove Programs after you've already installed it takes a few minutes. You must wait until the computer's resources are available to do another task.
If you only installed the Web downloadable MCMS Site Manager and upgrade to MCMS 2002 with SP1a then you may receive an error message that says, "Microsoft Content Management Server 2002 installation not found. The patching process will now exit."
Install any MCMS component from the MCMS 2002 CD and install MCMS 2002 with SP1a again.
You cannot click Cancel at the end of a MCMS with SP1a installation.
You must complete the installation and then from the Control Panel, use Add/Remove Program to uninstall the product.
If you upgraded Microsoft Windows® Server 2000 to Microsoft Windows Server™ 2003 then, during installation of MCMS 2002 with SP1a, you may get the following error messages: "The feature you are trying to use is on a network resource that is unavailable ..." or "Click OK to try again or enter an alternative path to a folder containing the installation package 'netfx.msi.'"
For information on how to resolve this issue, go to Knowledge Base article 320474 at http://go.microsoft.com/fwlink/?LinkId=20931.
If you upgraded Microsoft Windows Server 2000 to Windows Server 2003, MCMS 2002 with SP1a sites may no longer work.
When you upgraded your operating system, IIS 6.0 was configured to run in IIS 5.0 Isolation mode. You must reconfigure IIS 6.0 to run in native mode:
If your site is not working on Windows Server 2003 (Japanese version) and an error code 500 in the IIS log appears, go to Knowledge Base article 827640 at http://go.microsoft.com/fwlink/?LinkId=21087 for information on how to resolve this issue.
When you upgraded Microsoft Windows Server 2000 to Windows Server 2003, .NET Framework was also upgraded (to Version 1.1). Site Manager uses the Visual J# .NET Redistributable Package and the version of this redistributable must match the latest version of the .NET Framework.
You must install the appropriate version of the J# .NET Redistributable Package for the latest version of .NET Framework you have installed:
If you are running an older version of the MSIB 2.1 installer, you may get a warning that says MCMS 2002 does not meet the pre-requisite for MSIB 2.1.
You can ignore this error message or get an updated version of MSIB 2.1 at: http://go.microsoft.com/fwlink/?LinkId=9517.
If you installed the MS03-032 security update on Windows XP and you go to an ASP.NET page, you may get an error message that says "Server Application Unavailable." See the Knowledge Base article 827641 at http://go.microsoft.com/fwlink/?LinkId=20932 for more information.
It is not recommended to install MCMS 2002 with SP1a on a domain controller. See the following Knowledge Base articles 315158 and 824308 at http://go.microsoft.com/fwlink/?LinkId=20933 and http://go.microsoft.com/fwlink/?LinkId=20934 for more information.
Important Content Integration Pack 2.0 has customized Web Author files. You must save these files before installing MCMS 2002 with SP1a. Restore these files only after installing SP1a. The files are located in:
If you install Microsoft Content Management Server Content Integration Pack 2.0 after you install MCMS 2002 with SP1a, you must run the repair option in MCMS 2002 with SP1a. This ensures the Content Integration Pack 2.0 files are compatible with MCMS 2002 with SP1a files.
To run the repair option:
Note SP1a does not enable Content Integration Pack 2.0 to work with Windows 2003.
If you install a MCMS sample site on a read-only entry point you cannot use the Server Configuration Application (SCA) to change the entry point to a read/write entry point.
You must uninstall and then re-install the sample site to change the read-only entry point to a read/write entry point in the SCA.
You cannot install MCMS 2002 in a folder with a name that contains GB18030 characters.
The installation folder name can only contain ASCII characters.
Some characters may not display correctly in the ToolTips. To display these characters, you must set the font manually.
To manually set the font
If you use non-ASCII characters in your Site Stager script, the string appears incorrectly. To resolve this, do not use non-ASCII characters in your Site Stager script.
If you use non-ASCII characters, the WebControl Microsoft.ContentManagement.WebControls.RobotMetaTag returns an incorrect server name. MCMS does not support non-ASCII characters in the domain name. You must only use ASCII characters in the domain name.
You cannot log on to MCMS 2002 if you use non-ASCII characters in your domain name. MCMS does not support non-ASCII characters in the domain in host headers since the Internet, in particular DNS servers, does not support non-ASCII characters in domain names. You must only use ASCII text in the domain name.
If you use non-ASCII characters in server name, the Site Deployment reports generates script errors. MCMS does not support non-ASCII characters in the domain name. You can only use ASCII characters in the domain name.
The following message appears in the Event Log when some computers are restarted.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7022
The Simple Mail Transport Protocol (SMTP) service hung on starting.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7022
The World Wide Web Publishing Service hung on starting.
This error is the result of a slow initialization of the tracing services that MCMS uses during Internet Information Services (IIS) initialization. This slow initialization appears to the Service Control Manager as a hung service; however, later in the Event Log these services do successfully start. No workaround is required.
The MCMS 2002 with SP1a upgrade installer does not allow you to specify a target directory that is different from the directory for other MCMS components. If you install Site Manager to a custom directory then when you run the upgrade installer it will install it to the default directory. In addition original shortcuts and other share files may not be removed.
You must manually remove any obsolete shortcuts.
MCMS 2002 with SP1a does not support Microsoft Internet Explorer 5.5 on Windows ME.
If you try to run the DCA you may get an error message that says "Patch table has invalid data. Cannot determine migration path." This happens because the MCMS 2002 or MCMS 2002 SP1 Database Configuration Application (DCA) is not compatible with an MCMS 2002 with SP1a database. These versions of the DCA cannot connect to MCMS 2002 with SP1a databases.
Replace the MCMS 2002 SP1 file _dca.ini, with the MCMS 2002 with SP1a file _dca.ini, which is located in the folder \server\setup files\sql install. Refer to Knowledge Base article 831316 "Cannot run CMS 2002 SP1 DCA against a CMS 2002 SP1A database" located at http://go.microsoft.com/fwlink/?LinkId=20935.
After you install MCMS 2002, a Microsoft SQL Server™ background processing job is created (see "Using MCMS Background Cleanup" in the MCMS 2002 Help for more information on background processing). When you use the DCA to reconnect to an existing database in MCMS 2002 with SP1a, any changes you made to the starting job number is reset.
Using the SQL Server sa login, especially with the no password option selected is a known security risk and is not recommended. See the SQL Server documentation for more information on how to configure a secure user name and password.
If you uninstall one of the sample sites (for example, Woodgrove.ASP), but leave the other sample site (for example, Woodgrove.NET) and then uninstall MCMS 2002, the remaining sample site does not work. If you then try to uninstall the remaining sample site, you may get an error message that says "Unable to find Content Management Server Key, Installation failed." When you click OK another error message says "Fatal error during installation."
Reinstall MCMS with SP1a to view the sample site or uninstall it.
Information in this document, including URL and other Internet Web site references, is subject to change without notice. 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.
© 2003 Microsoft Corporation. All rights reserved.
Microsoft, MS-DOS, Windows, Windows NT, and Windows Server 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.