This document contains installation instructions as well as other necessary information for installing Microsoft® Content Management Server (MCMS) 2002 Service Pack 1 (SP1), a maintenance release for MCMS 2002, on computers running Microsoft Windows® Server 2000, Microsoft Windows XP, or Microsoft Windows Server™ 2003.
MCMS 2002 SP1 contains hotfixes made to the MCMS 2002 product since its release, and it provides updates to the Site Manager and Site Stager applications. For a list of the hotfixes in this Service Pack and their related Knowledge Base articles, see Microsoft Knowledge Base article number 824493 at http://go.microsoft.com/fwlink/?LinkId=18357.
With the release of MCMS 2002 SP1, MCMS 2002 now supports the following software:
Note Windows Server 2003 does not support .NET Framework 1.0. With Windows Server 2003, you must use .NET Framework 1.1 which is included with Windows Server 2003. For more information, see the section Using MCMS 2002 SP1 with the .NET Framework 1.1.
The supported software listed above is not required, but if you plan to use the new software, it is recommended that you install it before you install MCMS 2002 SP1.
Important It is recommended that you print and read this entire document before you install MCMS 2002 SP1 because it contains information required for the successful installation of MCMS 2002 SP1.
This document provides information about the following:
Before you install MCMS 2002 SP1, answer the following questions:
You can install MCMS 2002 SP1 only on computers that already have MCMS 2002 installed. Use the installation instructions located at: http://go.microsoft.com/fwlink/?LinkId=9918 to install MCMS 2002.
Note the following when you install MCMS 2002:
After you install MCMS 2002, you can then install MCMS 2002 SP1. For instructions for installing MCMS 2002 SP1, see Installing MCMS 2002 SP1.
Note If you upgrade from Visual Studio .NET 2002 to Visual Studio .NET 2003 after you installed MCMS 2002, you must uninstall the MCMS 2002 developer tools before installing MCMS 2002 SP1. MCMS 2002 SP1 installs developer tools that are compatible with Visual Studio .NET 2003.
Make sure that you have the correct version of Internet Explorer installed. Use the following table to check that you have installed the required minimum Internet Explorer version for the components you intend to install on the computer.
MCMS component | Required Internet Explorer version |
---|---|
Site Manager | Internet Explorer 5.0 or later |
Content Server | Internet Explorer 6.0 or later |
Authoring Connector | Internet Explorer 5.5 or later |
Web Author | Internet Explorer 5.0 or later |
By default, Internet Information Services (IIS) 6.0 is not installed when you install Microsoft® Windows Server™ 2003. You must ensure that the following IIS 6.0 components, which are included with Windows Server 2003, are installed before you install MCMS 2002 or MCMS 2002 SP1:
Important You must use Add or Remove Programs to install the required IIS 6.0 components. If you configure the components with the IIS Web Server Extensions wizard, you must use Add/Remove Programs to remove the components and add them again.
It is recommended that you install Windows Server 2003 before you install MCMS 2002. If you plan to upgrade your operating system to Windows Server 2003, and MCMS 2002 is already installed on your computer, it is recommended that you remove MCMS 2002 before upgrading to Windows Server 2003.
If you must upgrade to Windows Server 2003 without removing MCMS 2002, you will need to modify your MCMS 2002 installation before you install MCMS 2002 SP1. See Upgrading Your Operating System to Windows Server 2003 for instructions.
For information about issues with Windows Server 2003, see Known Issues with MCMS 2002 SP1 on Windows Server 2003.
If you maintain a Web farm for MCMS 2002, install MCMS 2002 SP1 on each of the servers in the farm.
MCMS 2002 SP1 includes an upgrade of the MCMS Site Manager and Site Stager. This upgrade eliminates the need for Microsoft® virtual machine (Microsoft VM) which is no longer widely available.
The MCMS 2002 SP1 version of Site Manager and Site Stager provides improved performance over the Site Manager and Site Stager installed with MCMS 2002, and the downloadable updated Site Manager.
If you want to upgrade Site Manager or Site Stager at the same time you install MCMS 2002 SP1, you must install Site Manager and Site Stager from the MCMS 2002 CD before upgrading to the updated MCMS 2002 SP1 version. Otherwise, you can use Add or Remove Programs to install the MCMS 2002 SP1 Site Manager or Site Stager after you install MCMS 2002 SP1. For information about installing MCMS components after installing MCMS 2002 SP1, see Installing MCMS Components After Installing MCMS 2002 SP1.
Additionally, when you install MCMS 2002 SP1 on your MCMS 2002 servers, you must also upgrade every Site Manager or Site Stager that you use to connect to those servers.
If you installed the downloadable upgraded Site Manager, which did not require Microsoft VM, you must uninstall it, install the Site Manager from the MCMS 2002 CD, and then install MCMS 2002 SP1.
For information on installing Site Manager and Site Stager from the MCMS 2002 CD without Microsoft VM, see Installing Site Manager or Site Stager Without Microsoft VM.
You must have the Visual J#® .NET Redistributable Package installed before upgrading Site Manager or Site Stager with MCMS 2002 SP1.
The version of the Microsoft J# .NET Redistributable Package that you need for your MCMS 2002 SP1 deployment depends on the version of .NET Framework that you have installed. .NET Framework is installed on your computer when you install Windows 2003, Visual Studio .NET 2002, or Visual Studio .NET 2003. It is also available for download.
If you do not have .NET Framework installed, it is available for download:
To determine which version of the J# Redistributable Package you need, and to view download instructions, see Which version of the J# Redistributable Package do you need to install?.
MCMS 2002 SP1 works with both .NET Framework 1.0 and .NET Framework 1.1. Use the following table to determine the version that is most likely available on your computer. Note that you may have both versions, or you may have downloaded a version other than the default.
If you have this installed | You most likely have this version of .NET Framework installed |
---|---|
Visual Studio .NET 2002 | .NET Framework 1.0 |
Visual Studio .NET 2003 | .NET Framework 1.1 |
Visual Studio .NET 2002 upgraded to Visual Studio .NET 2003 | .NET Framework 1.0 and .NET Framework 1.1 |
Windows Server 2003 | .NET Framework 1.1 |
Windows Server 2003 with Visual Studio .NET 2002 | .NET Framework 1.0 and .NET Framework 1.1 |
Note Windows Server 2003 does not support .NET Framework 1.0, although .NET Framework 1.0 may be installed on a Windows Server 2003 system. With Windows Server 2003, you must use .NET Framework 1.1 which is included with Windows Server 2003. For more information, see the section Using MCMS 2002 SP1 with the .NET Framework 1.1.
It is recommended that you check your computer for the version of .NET Framework installed.
For information about which version of the J# Redistributable Package you need, and download instructions, see Which version of the J# Redistributable Package do you need to install?.
For information on installing Site Manager and Site Stager with the Visual J# .NET Redistributable Package from the MCMS 2002 CD, or if you don’t have Microsoft VM, see Installing Site Manager or Site Stager Without Microsoft VM.
You cannot install MCMS 2002 SP1 Site Manager or Site Stager if you do not have the J# .NET Redistributable Package installed.
You must install the appropriate version of the J# .NET Redistributable Package for each version of .NET Framework you are using:
For information about which version of .NET Framework you have installed, see Will you be using Site Manager or Site Stager?.
For information on installing Site Manager and Site Stager with the Visual J# .NET Redistributable Package, see Installing Site Manager or Site Stager Without Microsoft VM.
If you are currently using, or plan to use Microsoft Content Integration Pack 2.0, you must install it before installing MCMS 2002 SP1. If you install Content Integration Pack 2.0 after installing MCMS 2002 SP1, you must reinstall MCMS 2002 SP1.
Important Content Integration Pack 2.0 has customized Web Author files. Save these files before installing MCMS 2002 SP1. Restore these files only after installing MCMS 2002 SP1.
Note MCMS 2002 SP1 does not enable Content Integration Pack 2.0 to work with Windows Server 2003.
It is strongly recommended that you back-up the following before you install MCMS 2002 SP1:
Note During SP1 installation, any previous customizations that you made to the Web Author will be overwritten. Therefore, you should back up these files before installing SP1 and then restore them after installation. SP1 automatically backs up the IIS_NR and IIS_CMS directories. The files from the SP1 backup are found at <MCMS base directory>\SP1 Backup\IIS_NR and <MCMS base directory>\SP1 Backup\IIS_CMS. Note that SP1 does not back up the IIS_NR_RO or the IIS_NR_RO_ASP directories. You must back up those files manually. Migrated MCMS 2001 directories. For more information about migrated files, see Files That Have Been Migrated From MCMS 2001 to MCMS 2002 Must Be Updated After Uninstalling SP1.
As with any update of your system, backing up the system is a recommended operations procedure.
Note You may be prompted to restart your computer after installing MCMS2002 SP1.
The Site Manager and Site Stager applications that shipped with MCMS 2002 required Microsoft virtual machine (Microsoft VM), which is not part of some versions of Windows® Server 2000 and Windows XP, or Windows Server™ 2003, and is no longer widely available from other sources.
If your operating system does not include Microsoft VM, you must install the Microsoft J#® .NET Redistributable Package first, then install MCMS 2002 SP1. For information about installing the J# .NET Redistributable Package, see Which version of the J# .NET Redistributable Package do you need to install?.
If you want to install the MCMS 2002 SP1 upgrade to Site Manager or Site Stager when you install MCMS 2002 SP1, you must first install Site Manager or Site Stager from the MCMS 2002 CD, and then install MCMS 2002 SP1.
If you want to install the MCMS 2002 SP1 upgraded Site Manager or Site Stager without installing these components from the MCMS 2002 CD, you will have to use Add or Remove Programs to install them from the MCMS 2002 SP1 after you have installed MCMS 2002 SP1. For information about installing MCMS components after installing MCMS 2002 SP1, see Installing MCMS Components After Installing MCMS 2002 SP1.
The following procedures describe how to install Site Manager or Site Stager on a computer without Microsoft VM.
To install only Site Manager on computers
msiexec /i "Microsoft Content Management Server.msi" PASS_SITEMGR_PREREQUISITE="Yes"
To install only Site Stager on computers without Microsoft VM
msiexec /i "Microsoft Content Management Server.msi" PASS_SITESTAGER_PREREQUISITE="Yes"
It is recommended that you uninstall MCMS 2002 before upgrading your operating system to Microsoft® Windows Server™ 2003. After you install Windows Server 2003, you can reinstall MCMS 2002 and then install MCMS 2002 SP1. For instructions on installing MCMS 2002 SP1, see Installing MCMS 2002 SP1.
However, if you decide to upgrade to Windows Server 2003 without uninstalling MCMS, you will need to do the following before you install MCMS 2002 SP1:
After you upgrade your computer to Windows Server 2003, the World Wide Web (WWW) publishing service may become disabled. This condition prevents the Site Manager and the Server Configuration Application (SCA) from operating. You must restart this service to use these components.
To restart the WWW Publishing Service
After you upgrade to Windows Server 2003, the SP1 installation cannot detect if server side includes are properly installed. To ensure that they are installed correctly, you must uninstall and reinstall them.
To uninstall server side includes
To reinstall server side includes
In Windows Server 2003, you can now configure the maximum amount of data for resource uploading within IIS, but the default limit is too low for MCMS resources. The following procedure sets the limit to approximately 50 megabytes (MB) for MCMS resources.
Note You must follow this procedure for each Web site that is configured as an MCMS Web entry point.
To increase the allowed resource size
Format | Location of the IIS InstanceID |
---|---|
ServerBindings=
"IP:Port:HostHeader" and SecureBindings= "IP:Port:HostHeader" |
In the metabase.xml file, search for the ServerBindings or SecureBindings strings. If the string appears as ServerBindings=IP:Port:HostHeader or SecureBindings=IP:Port:HostHeader, and the IP:Port:HostHeader matches the Web site IP, the port, and HostHeader that is entered in the SCA, then the IIS InstanceID for the Web site is in the location property of the <IIsWebServer ...> tag, which is in the form /LM/W3SVC/xxx. For example:
<IIsWebServer Location ="/LM/W3SVC/1256" DefaultDoc="Default.htm,Default.asp, iisstart.asp,Default.aspx" ServerBindings=":80:" ServerComment="Default Web Site" > </IIsWebServer> In this example, the IIS InstanceID is 1256. Note If the IP Address in IIS and the SCA is All Unassigned then the IP field is blank. |
Name=ServerBindings and/or Name=SecureBindings | In the metabase.xml file, search for the ServerBinding or SecureBinding strings. If the strings appear as Name=ServerBindings or Name=SecureBindings, then they are located in a <Custom> tag. Also in this custom tag is a value property in the form of Value=IP:Port:HostHeader. If the IP:Port:HostHeader matches the Web site IP, the port, and HostHeader that is entered in the SCA, then the IIS InstanceID for the Web site is in the location property of the <IIsWebServer ...> tag, which is in the form /LM/W3SVC/xxx. For example:
<IIsWebServer Location ="/LM/W3SVC/1987" AppPoolId="DefaultAppPool" DefaultDoc="Default.htm,Default.asp, iisstart.asp,Default.aspx" ServerComment="Default Web Site" > <Custom Name="SecureBindings" ID="2021" Value=":443:" /> <Custom Name="ServerBindings" ID="1023" Value=":80:" /> </IIsWebServer> In this example, the IIS InstanceID is 1987 Note If the IP Address in IIS and the SCA is All Unassigned then the IP field is blank. |
<IIsWebDirectory Location ="/LM/W3SVC/<InstanceID>/ROOT/NR/System/ResUpload" AppFriendlyName="ResUpload" AppIsolated="2" AppRoot="/LM/W3SVC/<InstanceId>/Root/NR/System/ResUpload" AspMaxRequestEntityAllowed="51200000" > </IIsWebDirectory>
In Windows Server 2003, you can now configure the maximum amount of data for resource uploading within IIS, but the default limit is too low for MCMS site deployment. The following procedure sets the limit to approximately 4 gigabytes (GB) for site deployment.
Note You must follow this procedure for each Web site that is configured as an MCMS Web entry point.
To increase the size of the SDO files
Format | Location of the IIS InstanceID |
---|---|
ServerBindings=
"IP:Port:HostHeader" and SecureBindings= "IP:Port:HostHeader" |
In the metabase.xml file, search for the ServerBindings or SecureBindings strings. If the string appears as ServerBindings=IP:Port:HostHeader or SecureBindings=IP:Port:HostHeader, and the IP:Port:HostHeader matches the Web site IP, the port, and HostHeader that is entered in the SCA, then the IIS InstanceID for the Web site is in the location property of the <IIsWebServer ...> tag, which is in the form /LM/W3SVC/xxx. For example:
<IIsWebServer Location ="/LM/W3SVC/1256" DefaultDoc="Default.htm,Default.asp, iisstart.asp,Default.aspx" ServerBindings=":80:" ServerComment="Default Web Site" > </IIsWebServer> In this example, the IIS InstanceID is 1256. Note If the IP Address in IIS and the SCA is All Unassigned then the IP field is blank. |
Name=ServerBindings and/or Name=SecureBindings | In the metabase.xml file search for the ServerBinding or SecureBinding strings. If the strings appear as Name=ServerBindings or Name=SecureBindings, then they are located in a <Custom> tag. Also in this custom tag is a value property in the form of Value=IP:Port:HostHeader. If the IP:Port:HostHeader matches the Web site IP, the port, and HostHeader that is entered in the SCA, then the IIS InstanceID for the Web site is in the location property of the <IIsWebServer ...> tag, which is in the form /LM/W3SVC/xxx. For example (see the bolded items below):
<IIsWebServer Location ="/LM/W3SVC/1987" AppPoolId="DefaultAppPool" DefaultDoc="Default.htm,Default.asp, iisstart.asp,Default.aspx" ServerComment="Default Web Site" > <Custom Name="SecureBindings" ID="2021" Value=":443:" /> <Custom Name="ServerBindings" ID="1023" Value=":80:" /> </IIsWebServer> In this example, the IIS InstanceID is 1987 Note If the IP Address in IIS and the SCA is All Unassigned then the IP field is blank. |
<IIsWebDirectory Location ="/LM/W3SVC/<InstanceID>/ROOT/NR/System/SDUpload" AppFriendlyName="ResUpload" AppIsolated="2" AppRoot="/LM/W3SVC/<InstanceId>/Root/NR/System/SDUpload" AspMaxRequestEntityAllowed="51200000" > </IIsWebDirectory>
When you installed MCMS 2002, it was originally configured to run under Windows Server 2000 and Internet Information Services (IIS) 5.0. After you upgrade to IIS 6.0, you must reinitialize MCMS to run under Windows Server 2003 and IIS 6.0.
These instructions explain how to install Microsoft® Content Management Server (MCMS) 2002 Service Pack 1 (SP1) if you are running Microsoft Windows® Server 2000, Windows XP, or Windows Server™ 2003. It is recommended that you read the topic Before You Install MCMS 2002 SP1 before you begin the installation of MCMS 2002 SP1.
If you installed Windows Server 2003 before you installed MCMS 2002, you can install MCMS 2002 SP1 just as you would for computers with Windows Server 2002 or Windows XP installed.
Important If you installed Windows Server 2003 after you installed MCMS 2002, you must make several modifications before you install MCMS 2002 SP1. For instructions for modifying your MCMS 2002 installation to work on Windows Server 2003, see Upgrading Your Operating System to Windows 2003.
Note If you installed the developers tools with MCMS 2002 and have installed Microsoft® Visual Studio® .NET 2003, you must remove the developer tools from the computer using Add/Remove Programs before you install MCMS 2002 SP1, unless Visual Studio .NET 2002 is also installed.
To download and install MCMS 2002 SP1
Page | Action |
---|---|
Welcome | Click Next. |
License Agreement | To accept the terms of the license agreement, click I accept the terms in the license agreement, and then click Next. |
SP1 Installation | This page lists the MCMS 2002 components that will be upgraded. Click Next. |
SP1 Installation | Select the optional components that you want to install. For example, if you installed Visual Studio .NET 2003, select Developer Tools for Visual Studio .NET 2003, and then click Next.
Accept the default location where the components will be installed, or select Change to change this location. |
Ready to Install SP1 | Click Install.
Note Installation takes a few minutes. |
Installation of MCMS 2002 SP1 Complete | Click Launch DCA to configure the database. You must run the Database Configuration Application (DCA) to configure your MCMS databases for MCMS 2002 SP1. |
Note You may be prompted to restart your computer after installing MCMS 2002 SP1. Troubleshooting tip: You must install Site Manager or Site Stager from the MCMS 2002 CD in order to upgrade them with MCMS 2002 SP1. You must install the Microsoft J#® .NET Redistributable Package and install the MCMS 2002 CD version before upgrading Site Manager or Site Stager with MCMS 2002 SP1.
For information about installing the J# .NET Redistributable Package, see Which version of the J# .NET Redistributable Package do you need to install?.
For more information about installing Site Manager and Site Stager, see the section Installing MCMS Components After Installing MCMS 2002 SP1.
After you have installed MCMS 2002 SP1, you can use the Add/Remove Programs feature in the control panel to install additional MCMS components.
To install additional MCMS components after MCMS 2002 SP1 is installed
You must install Authoring Connector Service Pack 1 (SP1) on all computers that have Authoring Connector installed.
To download and install Authoring Connector SP1
The MCMS 2002 Authoring Connector Language Pack for SP1 contains the client and server files that provide local versions of MCMS 2002 Authoring Connector for Microsoft Word 2002. The languages provided are Simplified Chinese, Traditional Chinese, Dutch, English, French, German, Italian, Japanese, Korean, Portuguese (Brazil), Spanish, and Swedish.
This language pack should be installed on all client computers that require these languages after you install Authoring Connector SP1. The language pack must also be installed on all servers that these client computers connect to.
To download and install Authoring Connector Language Pack for SP1
Before you uninstall MCMS 2002 SP1, it is recommended that you back up the following:
Note During MCMS 2002 SP1 installation, any customizations you previously made to the Web Author will be overwritten. You should back up these files before installing MCMS 2002 SP1 and then restore them after installation. MCMS 2002 SP1 will back up the IIS_NR and IIS_CMS directories. The files from the MCMS 2002 SP1 backup can be found at <MCMS base directory>\SP1 Backup\IIS_NR and <MCMS base directory>\SP1 Backup\IIS_CMS. MCMS 2002 SP1 does not back up the IIS_NR_RO or the IIS_NR_RO_ASP directories. You must back those up manually. Migrated MCMS 2001 directories (see Files That Have Been Migrated From MCMS 2001 to MCMS 2002 Must Be Updated After Uninstalling MCMS 2002 SP1 for more information about migrated files).
As with any update of your system, this step is a recommended operations procedure. Also, review the section Known Issues with Uninstalling MCMS 2002 SP1 before uninstalling MCMS 2002 SP1.
Note If you uninstall MCMS 2002 SP1, you must manually re-add the hotfixes that you manually applied before or after the MCMS 2002 SP1 installation.
Note If you have Content Integration Pack 2.0 installed and you uninstall MCMS 2002 SP1, you must reinstall Content Integration Pack. For information about installing Content Integration Pack 2.0, see Do you have Content Integration Pack 2.0 installed?.
Use the Add/Remove Programs option in the Control Panel to uninstall MCMS 2002 SP1.
Note MCMS 2002 SP1 will take a few minutes to uninstall.
Use the information in this section to troubleshoot MCMS 2002 SP1.
This section contains:
The following are known issues in this MCMS 2002 SP1 release:
Background processing is implemented as a SQL Server Agent Job. You may have modified the starting step in the background processing job (for instance, to enable deletion of expired postings). MCMS 2002 SP1 resets the background processing starting step, so if you customized the background processing before you installed MCMS 2002 SP1, you must reset it after applying MCMS 2002 SP1. See "Using MCMS Background Cleanup" in MCMS 2002 Help for more information about background processing.
If you are using Microsoft SQL Server™ 2000 SP3, the Database Configuration Application (DCA) and the Server Configuration Application (SCA) may not recognize a database user and its database rights. This is a i known SQL Server issue. For more information, see Knowledge Base article 305711 at http://go.microsoft.com/fwlink/?LinkId=18411.
To solve this issue you must define the MCMS system account in SQL Server for the MCMS system account user, and add the database user to the MCMS system database role.
To define the MCMS system account in SQL Server
To add the database user to the MCMS system database role
When some computers are restarted, the following messages may appear in the Event Log:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7022
Description:
The Simple Mail Transport Protocol (SMTP) service hung on starting.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7022
Description:
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 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.
Visual Studio .NET 2002 is used to build Web applications based on .NET Framework Version 1.0. When these applications are deployed, the target machines must have .NET Framework 1.0 (or .NET Framework 1.1) installed in order for these applications to run. Note that you can only run .NET Framework 1.0 applications on Windows Server 2003 using .NET Framework 1.1 because .NET Framework 1.0 is not supported on Windows Server 2003.
Visual Studio .NET 2003 is used to build Web applications based on .NET Framework 1.1. When these applications are deployed, the target machines must have .NET Framework 1.1 installed in order for these applications to run. See the section Using MCMS 2002 SP1 with .NET Framework 1.1 for more information.
.NET Framework 1.1 has a new attribute (validateRequest) that is not compatible with .NET Framework 1.0. See the Knowledge Base article 821343 at http://go.microsoft.com/fwlink/?LinkId=18386 for more information.
If you target your MCMS Web application and MCMS 2002 to use .NET Framework 1.1, then the validateRequest attribute must be added (and set to false) in one of the following:
Note This attribute is not compatible with ASP.NET 1.0. If you move your MCMS Web application Web.config files (or the MCMS 2002 Web.config files) to a computer running ASP.NET 1.0 then neither your MCMS Web application nor MCMS 2002 will work properly until this attribute is removed.
To set request validation to false for all applications on your computer
<configuration> <system.web> <pages validateRequest="false" /> </system.web> </configuration>
To set request validation to false for your MCMS Web application and all MCMS internal applications
<configuration> <system.web> <pages validateRequest="false" /> </system.web> </configuration>
To disable request validation for all MCMS internal applications
<configuration> <system.web> <pages validateRequest="false" /> </system.web> </configuration>
In Windows Server 2003 (and Windows Server 2000 SP4), the account which the ASP.NET process runs under must have impersonation privileges. By default, this account is the local ASPNET user. If this account does not have impersonation privileges, then you must manually assign impersonation privileges to the appropriate account.
To assign impersonation privileges
This section contains information about known issues with MCMS 2002 SP1 on Windows Server 2003.
This section contains:
When you try to install the developer tools in Visual Studio .NET 2002 on Windows Server 2003 you may receive the following error message: "Unable to pre-create directory for profile files." For more information about this error message, including a workaround, see the Knowledge Base article 320930 at http://go.microsoft.com/fwlink/?LinkID=18359.
In Windows Server 2003, the Internet Explorer Internet zone has a high security level setting. The default console in MCMS may not work because this setting prevents the JavaScript file that supports the Switch To Edit Site link from being downloaded.
You must add the MCMS Web site to the Trusted Sites in Windows Server 2003.
To add the MCMS Web site to Trusted Sites
If you manually stop the AESecurityService in Windows Server 2003 and attempt to access your MCMS Web site, the AESecurityService may not automatically restart and your MCMS Web site will not be available. AESecurityService must be manually restarted.
To manually restart the AESecurityService
You may be unable to create a Web application in Visual Studio .NET 2002 if you are using Windows Server 2003. Visual Studio .NET creates .tmp files, but Internet Information Services (IIS) 6.0 in Windows Server 2003 is not configured for this file type. This is a known issue with Visual Studio .NET 2002 and Windows Server 2003. For more information about this, including a workaround, see Knowledge Base article 327283 at http://go.microsoft.com/fwlink/?LinkId=18383.
When deploying a site in Windows Server 2003, the following error message may appear: "The remote server returned an error: (404) Not Found." This occurs because the ASPNET user does not have permission to access the site deployment directory on Windows Server 2003.
To grant the ASPNET user access to the site deployment directory
The following error message may appear when you are importing data in Windows Server 2003: "An underlying connection was closed. An unexpected error occurred." This may occur when you are importing a large amount of data, because IIS will time out. You can modify the connection time in IIS.
To increase the timeout connection in IIS
This section contains the following known issues when uninstalling MCMS 2002 SP1:
If you have Visual Studio .NET running when you attempt to uninstall MCMS 2002 SP1, you may receive the following error message: "Package Microsoft Content Management Server has failed to load properly."
To fix this, you must reinstall MCMS 2002 SP1, close Visual Studio .NET, and then uninstall MCMS 2002 SP1.
The process of migrating from MCMS 2001 to MCMS 2002 creates templates and resources on the file system in the directories listed below.
Important If you migrated from MCMS 2001 to MCMS 2002 you must back up the files listed below before you uninstall MCMS 2002 SP1, and then restore them when you are finished uninstalling MCMS 2002 SP1.
MCMS uses this directory to create resource directories and files.
After you replace these files, you must also restore the Access Control Lists (ACL) for each object because only administrators will have read and write access to these directories. You must grant read/write access to those users who need to access these files. (For example, template designers need access to these files.)
When your MCMS site is accessed, resources are downloaded and internally cached by Internet Explorer. When you uninstall MCMS 2002 SP1 the resources on the server revert back to the previous version, but Internet Explorer may still contain MCMS2002 SP1 resources. Therefore, when the site is accessed again, Internet Explorer may run a combination of MCMS 2002 SP1 and MCMS 2002 script files, and a scripting error can occur as a result.
To work around this issue, wait for Internet Explorer to empty its cache, or manually empty the client cache in the temporary Internet folder.
To empty the temporary Internet folder
This section outlines new features included with MCMS 2002 SP1.
This section contains:
Some characters allowed in MCMS 2002 placeholder names, query strings, and custom property names may expose your MCMS Web site to cross-scripting issues. MCMS 2002 SP1 removes this exposure by restricting the allowable characters for these properties.
If your MCMS Web site uses placeholder or custom property definitions with characters not allowed by MCMS 2002 SP1, you must change those definitions.
Note If your MCMS Web site uses query strings with characters not allowed by MCMS 2002 SP1, you must redo the query strings or add them into the Web.config file so they can be accepted my MCMS. See the section Adding Valid Characters to Query String Contents for more information.
Valid characters are listed in the following table:
Characters | Hex Code | Notes |
---|---|---|
All Unicode alphabetic letters | ||
All Unicode decimal digits | ||
All Unicode whitespace | ||
! | 0x21 | Exclamation |
$ | 0x24 | Dollar sign |
( | 0x28 | Left parenthesis |
) | 0x29 | Right parenthesis |
* | 0x2A | Asterisk |
, | 0x2C | Comma |
- | 0x2D | Hyphen (minus) |
. | 0x2E | Full stop |
: | 0x3A | Colon |
; | 0x3B | Semicolon |
= | 0x3D | Equal sign |
? | 0x3F | Question mark |
@ | 0x40 | Commercial at |
[ | 0x5B | Left square bracket |
] | 0x5D | Right square bracket |
^ | 0x5E | Circumflex accent |
_ | 0x5F | Underscore |
` | 0x60 | Grave accent |
{ | 0x7B | Left curly bracket |
} | 0x7D | Right curly bracket |
~ | 0x7E | Tilde |
With MCMS 2002 SP1, query strings are now validated (see the section Changes to Allowed Characters in Placeholder Names, Query Strings, and Custom Property Names). Your MCMS Web application may use characters in the query string that are no longer allowed. However, you can add them to your application using the following procedure.
Note Adding new characters can make your application vulnerable to cross-site scripting issues.
To add additional valid characters
<appSettings> <add key="WebAuthor.CustomValidCharacters" value="/> </appSettings>
You can configure the Web Author to display resources in tree view, list view, or both (the default) when you select resources. You can set the view that you want the Web Author to display.
To configure the resource view
<appSettings> <!—Choose "TreeView" or "ListView" or "Both" for WebAuthor.ResourceGalleryView <add key="WebAuthor.ResourceGalleryView" value="Both" /> </appSettings>
MCMS 2002 SP1 adds the following new APIs to MCMS:
Gets a value indicating whether the current user has sufficient rights to use this Resource for authoring a Posting.
[Visual Basic] Public ReadOnly Property CanUseForAuthoring As Boolean [C#] public bool CanUseForAuthoring {get;} [C++] public: __property bool get_CanUseForAuthoring();
Returns true if the user has sufficient rights to use this resource for authoring a Posting; false otherwise.
This property is included primarily for providing a visual indication of which resources a user has sufficient rights to use in authoring a posting.
A user has rights to use a resource for authoring a posting if at least one of the following conditions is true:
This property indicates whether a user has sufficient rights to use this object for authoring, independently of the current mode. This means that even though an object can only be modified in the Update mode, this method will return true regardless of the Mode, as long as the User has sufficient rights to use the object in the Update mode. This behavior is useful for generating a visual indication of whether the current user could use a particular object after switching to the Update mode, regardless of the current mode.
This property indicates whether the current user has sufficient rights to use an object only at the point in time when it is called. An attempt to use an object can still fail if, for example, the rights associated with the current user are changed between the time that this property is checked and the time that the method using the object is called. Therefore, calls to the method using the object should be enclosed in appropriate try...catch blocks.
This property cannot be read for any object that has been deleted and for which the deletion has been committed by calling CommitAll.
This property is false for historical revisions of an object.
Platforms: Microsoft Windows 2000 Server SP2, Microsoft Windows 2000 Advanced Server SP2, Windows XP Professional SP1 (development server only)
.NET Framework Security:
Resource Class | Resource Members | Microsoft.ContentManagement.Publishing Namespace
Filters Resource objects out of the collection based on the CanUseForAuthoring property.
[Visual Basic] Overloads Public Sub FilterByCanUseForAuthoring()
[C#] public void FilterByCanUseForAuthoring();
[C++] public: void FilterByCanUseForAuthoring();
[Visual Basic] Overloads Public Sub FilterByCanUseForAuthoring(System.Boolean)
[C#] public void FilterByCanUseForAuthoring(System.Boolean);
[C++] public: void FilterByCanUseForAuthoring(System.Boolean);
ResourceCollection Class | ResourceCollection Members | Microsoft.ContentManagement.Publishing Namespace
Filters Resource objects out of the collection based on the CanUseForAuthoring property.
[Visual Basic] Overloads Public Sub FilterByCanUseForAuthoring() [C#] public void FilterByCanUseForAuthoring(); [C++] public: void FilterByCanUseForAuthoring();
Resource objects with a CanUseForAuthoring property value that is equal to true are kept in the collection. All other resources are removed.
Platforms: Microsoft Windows 2000 Server SP2, Microsoft Windows 2000 Advanced Server SP2, Windows XP Professional SP1 (development server only)
.NET Framework Security:
ResourceCollection Class | ResourceCollection Members | Microsoft.ContentManagement.Publishing Namespace | ResourceCollection.FilterByCanUseForAuthoring Overload List
Filters Resource objects out of the collection based on the CanUseForAuthoring property.
[Visual Basic] Overloads Public Sub FilterByCanUseForAuthoring( _ ByVal isInclusive As Boolean _ ) [C#] public void FilterByCanUseForAuthoring( bool isInclusive ); [C++] public: void FilterByCanUseForAuthoring( bool isInclusive );
If isInclusive is true, Resource objects with a CanUseForAuthoring property value that is equal to true are kept in the collection. All other resources are removed.
If isInclusive is false, Resource objects with a CanUseForAuthoring property value that is equal to false are kept in the collection. All other resources are removed.
Platforms: Microsoft Windows 2000 Server SP2, Microsoft Windows 2000 Advanced Server SP2, Windows XP Professional SP1 (development server only)
.NET Framework Security:
ResourceCollection Class | ResourceCollection Members | Microsoft.ContentManagement.Publishing Namespace | ResourceCollection.FilterByCanUseForAuthoring Overload List
Gets a value indicating whether the current user has sufficient rights to use this template for authoring a posting.
[Visual Basic] Public ReadOnly Property CanUseForAuthoring As Boolean [C#] public bool CanUseForAuthoring {get;} [C++] public: __property bool get_CanUseForAuthoring();
Returns true if the user has sufficient rights to use this template for authoring a Posting; false otherwise.
This property is included primarily for providing a visual indication of which resources a user has sufficient rights to use for authoring a posting.
A user has rights to use a template for authoring a posting if at least one of the following conditions is true:
This property indicates whether a user has sufficient rights to use this object for authoring, independent of the current Mode. This means that even though an object can only be modified in the Update mode, this method will return true regardless of the Mode as long as the User has sufficient rights to use the object in the Update mode. This behavior is useful for generating a visual indication of whether the current user could use a particular object after switching to the Update mode, regardless of the current mode.
This property indicates whether the current User has sufficient rights to use an object only at the point in time when it is called. An attempt to use an object can still fail if, for example, the rights associated with the current User are changed between the time that this property is checked and the time that the method using the object is called. Therefore, calls to the method using the object should be enclosed in appropriate try...catch blocks.
This property cannot be read for any object that has been deleted and for which the deletion has been committed by calling CommitAll.
This property is false for historical revisions of an object.
Platforms: Microsoft Windows 2000 Server SP2, Microsoft Windows 2000 Advanced Server SP2, Windows XP Professional SP1 (development server only)
.NET Framework Security:
Template Class | Template Members | Microsoft.ContentManagement.Publishing Namespace
Filters Template objects out of the collection based on the CanUseForAuthoring property.
[Visual Basic] Overloads Public Sub FilterByCanUseForAuthoring()
[C#] public void FilterByCanUseForAuthoring();
[C++] public: void FilterByCanUseForAuthoring();
[Visual Basic] Overloads Public Sub FilterByCanUseForAuthoring(System.Boolean)
[C#] public void FilterByCanUseForAuthoring(System.Boolean);
[C++] public: void FilterByCanUseForAuthoring(System.Boolean);
TemplateCollection Class | TemplateCollection Members | Microsoft.ContentManagement.Publishing Namespace
Filters Template objects out of the collection based on the CanUseForAuthoring property.
[Visual Basic] Overloads Public Sub FilterByCanUseForAuthoring() [C#] public void FilterByCanUseForAuthoring(); [C++] public: void FilterByCanUseForAuthoring();
Template objects with a CanUseForAuthoring property value that is equal to true are kept in the collection. All other templates are removed.
Platforms: Microsoft Windows 2000 Server SP2, Microsoft Windows 2000 Advanced Server SP2, Windows XP Professional SP1 (development server only)
.NET Framework Security:
TemplateCollection Class | TemplateCollection Members | Microsoft.ContentManagement.Publishing Namespace | TemplateCollection.FilterByCanUseForAuthoring Overload List
Filters Template objects out of the collection based on the CanUseForAuthoring property.
[Visual Basic] Overloads Public Sub FilterByCanUseForAuthoring( _ ByVal isInclusive As Boolean _ ) [C#] public void FilterByCanUseForAuthoring( bool isInclusive ); [C++] public: void FilterByCanUseForAuthoring( bool isInclusive );
If isInclusive is true, Template objects with a CanUseForAuthoring property value that is equal to true are kept in the collection. All other templates are removed.
If isInclusive is false, Template objects with a CanUseForAuthoring property value that is equal to false are kept in the collection. All other templates are removed.
Platforms: Microsoft Windows 2000 Server SP2, Microsoft Windows 2000 Advanced Server SP2, Windows XP Professional SP1 (development server only)
.NET Framework Security:
TemplateCollection Class | TemplateCollection Members | Microsoft.ContentManagement.Publishing Namespace | TemplateCollection.FilterByCanUseForAuthoring Overload List
======================================================
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, Visual J#, Visual Studio, 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.