Stefan Goßner

Senior Escalation Engineer for SharePoint (WSS, SPS, MOSS, SP2010) and MCMS

Blogs

Current known issues with MCMS 2002 SP2 (last updated: 31.08.2006)

  • Comments 39
  • Likes

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

Comments
  • After installing SQL Server 2005 (which also installed .NET Framework 2.0), I recieved the following error message when trying to login to Site Manager:

    "The Microsoft Content Management Server proxy component is not correctly installed."

    I found that this is because the J# redistributable package installed is v1.1 (for framework 1.1). I downloaded and installed the new J# redistributable package v2.0 from http://msdn.microsoft.com/netframework/downloads/updates/default.aspx and all is again well with Site Manager.

  • I cant say I am feeling particularly confident in MCMS SP2 as yet.

    All the confidence in the world with your support Stefan. Just not the patch.

  • Hi Stefan,

    concerning 'Clearing Hyperlinks does not work after installing SP2': it is not necessary to remove the whole text. You can simply put the cursor at the end of the hyperlinked text and then press 'backspace' once: the hyperlink is removed and the text remains!

  • Hi Stefan,
    Thanks for your usefull info. I am experiencing the problem you highighted when trying to connect to a db using SQL Login instead of trusted authentication. I have tried many things without luck nor success. In fact I am glad to hear that it's a bug and that I am not going nuts :-)
    Do have any idea when the hotfix should be released and where to get it as soon as it is available???
    Thanks again and all the best!

  • Hi Gaetan,

    the hotfix is currently in testing and should be released very soon.
    There will not be a public download. You need to open a support case with Microsoft and request the hotfix.
    I would suggest to open the support case now to ensure that you get the hotfix as soon as it is released.

    Cheers,
    Stefan

  • Clearing Hyperlinks does not work after installing SP2
    Before installing SP2 it was possible to clear...

  • After installing SP2 creating new content throws a server error: "Field not found: Microsoft.ContentManagement.WebAuthor.TemplateGalleriesBrowse.ViewAsList".  

    It appears to be an issue only related to viewing template galleries.  Editing existing content (which doesn't require viewing template galleries) is not affected.

  • I still see the following error even after installing J# redistributable 2.0.

    The Microsoft Content Management Server proxy component is not correctly installed.

  • Hi Ian,

    this will happen if the J# redistributable for the .net framework version used by SiteManager is not available or not correctly installed.
    So this is not a MCMS problem but a problem with the J# runtime (parts of SiteManager are written in J#).

    Cheers,
    Stefan

  • Hi Jason,

    did you install my WebauthorExtension? Then you need to install the latest version of my extension. The old version will throw this error after installing SP2.

    Cheers,
    Stefan

  • Site Deployment export does not work on databases created before SP2 and moved to SQL Server 2005
    This...

  • DCA complains about missing priviledges when selecting a database when SQL authentication is being used...

  • Hi, thanx for some good services. I have not found the KB 914195 as you write about. Is it the wrong number?

    That is for the locale VS fix

    thanx

    /Erik

  • Hi Erik,

    no this is the correct hotfix number. The KB article has not yet been released.

    Cheers,
    Stefan

  • I am thinking about rolling back MCMS 2002 SP2.  

    After the upgrade, I was no longer able to do Export/Import programatically...

    Here is the code I run to do the Export (something published by (Stefan_Gossner a while back):

    Public Shared Sub Export()
           Dim MSCMSRoot As String = AppSettings("MSCMSRoot")
           Dim TimeIntervalInMin As String = AppSettings("TimeIntervalInMin")
           Dim AdminPass As String = AppSettings("AdminPass")
           Dim cmsDeployExport As SITEDEPLOYSERVERLib.CmsDeployExport
           cmsDeployExport = New CmsDeployExportClass()
           cmsDeployExport.AuthenticateAsUser(CMSUser, AdminPass)
           'cmsDeployExport.AuthenticateAsCurrentUser()

           Dim strPackageName As String = "C:\deploy.sdo"

           If Not AppSettings("ExportFile") Is Nothing Then
               If AppSettings("ExportFile") <> "" Then
                   strPackageName = AppSettings("ExportFile")
               End If
           End If

           Dim cmsDeployExportOptions As SITEDEPLOYSERVERLib.CmsDeployExportOptions
           cmsDeployExportOptions = cmsDeployExport.Options
           cmsDeployExportOptions.IncludeCreatedBy = 1
           cmsDeployExportOptions.IncludeRightsGroups = 1 'CMS_EXPORT_RIGHTS_GROUPS_NONE

           Dim strReportUrl As String = cmsDeployExport.Export(strPackageName, TimeIntervalInMin, "") '14400 for 48 hours
           System.Console.WriteLine(strReportUrl)
           'Process.Start("iexplore.exe", MSCMSRoot + strReportUrl)
       End Sub


    This is what I get:

    Event Type:       Error
    Event Source:    ExceptionManagerPublishedException
    Event Category: None
    Event ID:           0
    Date:                5/5/2006
    Time:                10:18:00 AM
    User:                N/A
    Computer:         OWSRC
    Description:

    General Information
    *********************************************
    Additional Info:
    ExceptionManager.MachineName: OWXYZ
    ExceptionManager.TimeStamp: 5/5/2006 10:18:00 AM
    ExceptionManager.FullName: Microsoft.ApplicationBlocks.ExceptionManagement, Version=1.0.1446.17805, Culture=neutral, PublicKeyToken=null
    ExceptionManager.AppDomainName: XYZExportScript.exe
    ExceptionManager.ThreadIdentity:
    ExceptionManager.WindowsIdentity: XYZDOMAIN\CMSXYZ

    1) Exception Information
    *********************************************
    Exception Type: System.Runtime.InteropServices.COMException
    ErrorCode: -2147352567
    Message: There was an error generating the XML document.
    TargetSite: System.String Export(System.String, Int32, System.String)
    HelpLink: NULL
    Source: System.Xml

    StackTrace Information
    *********************************************
      at SITEDEPLOYSERVERLib.CmsDeployExportClass.Export(String strPackageFilename, Int32 lTimeIntervalInMin, String strParentChannel)
      at XYZExportScript.CmsExport.Export()
      at XYZExportScript.CmsExport.Main(String[] args)


    I am now working with Microsoft, but they do not have a solution for me as of yet…  They had me change the SITEDEPLOYSERVERLib (Copy Local = True) to Microsoft.ContentManagement.Interop.NRSiteDeployServer (Copy Local = False) instead.  

    Here is the error I now get after that change:

    Event Type:       Error
    Event Source:    ExceptionManagerPublishedException
    Event Category: None
    Event ID:           0
    Date:                5/5/2006
    Time:                12:20:31 PM
    User:                N/A
    Computer:         OWSRC
    Description:

    General Information
    *********************************************
    Additional Info:
    ExceptionManager.MachineName: OWXYZ
    ExceptionManager.TimeStamp: 5/5/2006 12:20:31 PM
    ExceptionManager.FullName: Microsoft.ApplicationBlocks.ExceptionManagement, Version=1.0.2316.19322, Culture=neutral, PublicKeyToken=null
    ExceptionManager.AppDomainName: XYZExportScript.exe
    ExceptionManager.ThreadIdentity:
    ExceptionManager.WindowsIdentity: XYZDOMAIN\XYZXYZ

    1) Exception Information
    *********************************************
    Exception Type: System.Runtime.InteropServices.COMException
    ErrorCode: -2147221164
    Message: COM object with CLSID {CA0752B3-021C-4F99-82E3-2C0F19C5E953} is either not valid or not registered.
    TargetSite: Void Export()
    HelpLink: NULL
    Source: XYZExportScript

    Does anyone have a step by step on how to do the SP2 uninstall?

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
Raw Html Fix