Current known issues with MCMS 2002 SP2 (last updated: 31.08.2006)
Currently we have a couple of known issues with MCMS 2002 SP2:
DCA complains about missing priviledges when selecting a database when SQL authentication is being used
Our current findings show that this issue is caused by the fact that the DCA now always verifies if the MCMS system account has db_datareader, db_datawriter and db_ddladmin priviledges on the SQL server - even if SQL authentication is used.
Update January 19, 2006: the hotfix for this request has been released and can be requested from Microsoft Support as KB 913400
Developer tools for VS.NET 2003 disappear after installing MCMS 2002 Service Pack 2
We are currently investigating this problem. As a workaround please change the user locale in regional options to US english.
Update February 03, 2006: the hotfix for this request has been released and can be requested from Microsoft Support as KB 914195
Developer Tools for VS.NET 2005 do not work with some regional settings
If the regional settings are different from US-english the developer tools might not work and raise the following error:
Package 'Content Managemen Server' has failed to load properly ( GUID = {639FD45D-6EC0-4060-AF7A-A1FD416A5363E} ). Please contact package vendor for assistance.
As a workaround please change the user locale in regional options to US english.
Update February 03, 2006: the hotfix for this request has been released and can be requested from Microsoft Support as KB 914195
Postbacks on Firefox and Netscape browsers do not work correct
This will only happen if the <base> tag rendering using the RobotMetaTag control has been disabled. As a workaround either enable the <base> tag rendering or (if this is not an option) add the following javascript code behind the form tag of your template:
<script language="javascript">
if (window.navigator.appName.toLowerCase().indexOf("microsoft") == -1
&& typeof __CMS_PostbackForm.onsubmit == "undefined")
{
__CMS_PostbackForm.onsubmit = null;
}
</script>
We are currently waiting for an official fix for this problem.
Update February 08, 2006: the hotfix for this request has been released and can be requested from Microsoft Support as KB 914782
Site Deployment export does not work on databases created before SP2 and moved to SQL Server 2005
This problem will occur with all databases which have been migrated from MCMS 2002 SP1a and then moved to SQL Server 2005. If you are affected by this issue please open a support case with Microsoft Support Services.
Databases created on SQL Server 2005 are not affected.
Update January 25, 2006: the hotfix for this request has been released and can be requested from Microsoft Support as KB 913401
Clearing Hyperlinks does not work after installing SP2
Before installing SP2 it was possible to clear a hyperlink by selecting the hyperlink text, clicking on the hyperlink button and clearing the URL part. After installing SP2 the hyperlink is not cleared.
The product team is currently building a fix for this. Workaround: remove the whole link and enter the text again.
Update January 26, 2006: the hotfix for this request has been released and can be requested from Microsoft Support as KB 913554
ASP.NET 2.0 Cross-Postbacks using PostBackUrl do not work on a MCMS 2002 SP2 template
Injected client side code from MCMS 2002 prevents the new cross postback feature of ASP.NET 2.0 to work correct on a MCMS template file. This behavior is by design. A workaround has been published here:
Hotfix to support VS.NET 2005 with MCMS 2002 SP2 without installing VS.NET 2003 first (new: 13.03.2006)
Requested since MCMS 2002 SP2 has been released was a possiblity to install MCMS 2002 with VS.NET 2005 without a need to install VS.NET 2003 first.
As SP2 is a service pack that only updates installed components it was necessary to install VS.NET 2003 first to ensure that the MCMS development tools could be installed with MCMS. Only this allowed the Service Pack to upgrade the developer tools to support VS.NET 2005.
For customers who did not want to do any VS.NET 2003 development or even did not have a copy of VS.NET 2003 this caused problems.
Microsoft has now released a hotfix (actually it is just a vbs script) that modifies the system in a way that allows the SP1a installer to install the developer tools for VS.NET 2003 without having VS.NET 2003 installed before. The developer tools can now be upgraded by the SP2 installer to be compatible with VS.NET 2005 as well.
The fix has been released as KB 915190.
Incorrect nrdhtml.cab file included in localized versions of SP2
The german and french version of MCMS 2002 SP2 ship with the US-english version of the nrdhtml.cab file. This can lead to US-english messages showing up in web author.
Update May 2, 2006: the hotfix for this request has been released and can be requested from Microsoft Support as KB 917509
Old version of Microsoft.ContentManagement.Common in the GAC (new: 10.05.2006)
Installing MCMS 2002 SP2 does not add the new version of the assembly Microsoft.ContentManagement.Common to the global assembly cache.
Solution: add this DLL manually to the GAC. Alternativly install a post MCMS 2002 SP2 hotfix (e.g. one in the list above). The installation of any of the above hotfixes will correctly add the DLL to the Global Assembly Cache.
Post SP2 hotfixes install an old version of the nrdhtml.cab file (new: 10.05.2006)
The installer of the above hotfixes contains a problem that causes the nrdhtml.cab file to be replaced with an old version (version 5.0.4526.0). This can cause performance problems during authoring as the cab file is downloaded for every placeholder control again and again.
Workaround: backup the original version of the nrdhtml.cab file installed when installing SP2 (version 5.0.5054.0) before installing a hotfix and then restore this file after installing the hotfix.
Update August 9, 2006: the hotfix for this request has been released and can be requested from Microsoft Support as KB 923755
