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

Comments (39)

  1. William Cornwill says:

    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.

  2. Euan says:

    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.

  3. stan says:

    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!

  4. Gaetan says:

    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!

  5. Stefan_Gossner says:

    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

  6. Anonymous says:

    Clearing Hyperlinks does not work after installing SP2

    Before installing SP2 it was possible to clear…

  7. Jason M says:

    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.

  8. Ian says:

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

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

  9. Stefan_Gossner says:

    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

  10. Stefan_Gossner says:

    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

  11. Anonymous says:

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

    This…

  12. Anonymous says:

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

  13. Erik Hedblom says:

    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

  14. Stefan_Gossner says:

    Hi Erik,

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

    Cheers,

    Stefan

  15. MJ says:

    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: XYZDOMAINCMSXYZ

    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: XYZDOMAINXYZXYZ

    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?

  16. Andy Allan says:

    Hi Stephan,

    I think you remember Justin Drerup? He has left us for other pastures…we do miss him.

    Anyway we are having a problem after installing SP2 for MCMS.

    We use panels on some of our forms. The path changes when we click on a next button to the

    /Templates/path.aspx rather than the /Channels/Posting paths…as it should be.

    E.g.

    FirstPanel Second Panel Third Panel

    /PostBrochure/BrochureRequest/ /PostBrochure/BrochureRequest/ /PostBrochure/BrochureRequest/

    SP2

    /PostBrochure/BrochureRequest/ /Templates/NGW/Forms/BrochureRequest.aspx?NRMODE= /Templates/NGW/Forms/BrochureRequest.aspx?NRMODE=

    Do you have a fix for this one. Is there a hotfix out for this?

    We are running .Net 1.1, on SQL 2000 servers using Visual Studio 2003. It is not viable for us to update to .Net 2.0 just yet.

    I see SP2 spits out a new bunch of javascript…maybe there is a way of stopping this?

    E.g.

    <!– Generated by Microsoft.ContentManagement.WebControls.Console to reset form.action –>

    ……

    I see maybe you have a fix but that is only for .Net 2.0 users.

    ASP.NET 2.0 Cross-Postbacks using PostBackUrl do not work on a MCMS 2002 SP2 templates"?

    Any comments/help appreciated.

    Thanks,

    Andy

  17. Brian Danberry says:

    After installing MCMS SP2, I get the following JavaScript error "null is null or not an object", when I open the Edit hyperlink Dialog.  Also all of the fields in the dialog box are undefined. This is a Multiple Hyperlink Placeholder from which we got the code from Stefan’s book.  When you remove SP2 it works.  Anyone else experience this?  Any fixes or work arounds?  Thanks

  18. Miguel Hern&#225;ndez says:

    Hi Stefan,

    After migrating from SQL 2000 to SQL 2005 a CMS2002 database (before, the CMS2002 SP2 has been installed), we have encountered the reported error “Field not found: Microsoft.ContentManagement.WebAuthor.TemplateGalleriesBrowse.ViewAsList” when we try to create a new page. On edition mode, this has no occurred.

    We’ve revised the past threads and have read about the installation of a modified WebauthorExtension from your own and then, recompiling the solution and clear the ASP.NET temporary file folder.

    The problem is: where do we find that extension?

    Sorry for any inconvience.

    Regards,

    Miguel

  19. Stefan Goßner says:

    Hi Miguel,

    it is at the usual place at GotDotNet:

    http://www.gotdotnet.com/Community/UserSamples/Details.aspx?SampleGuid=DD7F32CC-7543-4026-B858-69CC4A25EF99

    But usually the problem occur because of outdated content in the "temporary internet files" folder in your .NET framework installation directory. E.g. for .NET 1.1:

    C:WINDOWSMicrosoft.NETFrameworkv1.1.4322Temporary ASP.NET Files

    Please clear this folder and check if this solve the problem.

    Cheers,

    Stefan

  20. mikehardeman says:

    I’m not sure if anyone has had this problem.

    Because the Database Configuration Application would not recognize SQL Server 2005 Express as a "post-SQL Server 2000" version, I installed SQL Server 2005, Developer edition on my machine.  Before I did this, I removed SQL Server 2005 Express.

    When I launch the DCA (the latest one), it still assumes that the old SQL Server 2005 Express server is the default one, and does not recognize the new SQL Server 2005 server.  I’ve tried all combinations of SQL and Trusted Connection credentials, and it does not see the new database.

    I even tried uninstalling and re-installing MCMS 2002 SP2 on the machine, thinking that it might be holding the old server name in a registry entry, but that produces the same results.

    Any ideas how to fix this so that MCMS SP2 DCA can see the new database server?

    Thanks,

    MH

  21. mikehardeman says:

    FYI, I solved the problem described in the previous post.  As another MCMS post, by another developer, had hinted to, the way to solve this problem is to uninstall both SP2 and SP1A.  Only after you do this and reinstall both versions, should you again try to configure your database.

    Again, this was an attempt to configure with a SQL Server 2005 Express database that failed, followed by installing SQL Server 2005 Developer Edition.  With the new database installed, the DCA would refuse to acknowledge the new database and kept trying to default to the SQL Express database, which had been de-installed.

    Removing both CMS service packs and re-installing solved the issue.  I was then able to see my new database in the DCA setup wizard.

    MH

  22. Akader says:

    after i installed MCMS SP2 my arabic content inside the placeholders displays like : &#1608;&#1586;&#1610;&#1585; …

    the cause is from the new "nrdhtml.cab" installed on the client PCs.

    any help???

  23. francescobramato says:

    Hi Stephan,

    installing MSCMS 2002 SP1a, i receive this error message: "Need Microsoft Visual J# .NET Redistributable Package 3.0 (required by Site Manager, Site Stager)".

    I cant install SP2 without sp1a.

    Visual J# .NET Redistributable Package 3.0 doesnt exists. In other forums, i’ve read to uninstall the 3.0 version.

    So, i uninstalled it, rebooted, but nothing. Issue still exists.

    Any idea?

  24. Stefan Goßner says:

    Hi Francesco,

    you have to uninstall .NET framework 3.0.

    MCMS cannot be installed if .NET 3.0 is installed.

    Cheers,

    Stefan

  25. francescobramato says:

    First installation of .net 3.0 came from automatic updates, and uninstalling it installation procedure of sp1a was still finding the 3.0 installed.

    So, i have reinstalled .net 3.0 from redistrutable package and uninstalled it. At that time, installation procedure of sp1a didnt find the presence of .net 3.0

    The issue is on uninstallation of .NET 3.0 installed from automatic updateswindows update that doesnt uninstall it correctly (maybe some registry keys)

  26. kapil says:

    plz give a solution for the above mentioned problem by francesco..m facing the same problem

  27. Stefan Goßner says:

    Hi Francesco,

    I haven’t seen this before but if your steps helped: thanks for sharing.

    Cheers,

    Stefan

  28. Frederic Ponchaut says:

    I’ve got the same issue (framework 3.0).

    Our dev laptop are currently installed with VS2008 SQL2005.

    I can install MCMS (seems working but need more check), but i can’t install sitemanager & site stager (require J# 3.5 – does not exist)

    I can’t remove VS2008 & .net3.5 (after the reboot, an corporate update software check that my computer is not uptodate and reinstall the framework)

    We absolutly need to be able to setup MCMS on this machine (a migration to MOSS is planned but in a few month)

    Is there a workaround to be able to setup the site manager (manual setup, registry change, …)

    please help us…

  29. Stefan Goßner says:

    Hi Frederic,

    no workaround. You have to uninstall all .NET framework versions higher than 2.0 to install MCMS.

    Afterwards you can install .NET framework 3.5 again and create a config file for Site Manager to use .NET 2.0.

    Cheers,

    Stefan

  30. Frederic Ponchaut says:

    Stefan,

    I’ve had the same issue as  francesco.

    the framework 3.0 is not completly removed from my computer and MCMS setup request the J# 3.0.

    So i’ve to reinstall the framework from the redistibuable package, uninstall again, install mcms and install .net 3.0 again.

  31. Frederic Ponchaut says:

    One more thing…

    what do I have to with the config file to ensure that SiteManager use the 2.0?

    Frederic

  32. Stefan Goßner says:

    Hi Frederic,

    something like this:

    NRClient.exe.config:

    <?xml version ="1.0"?>

    <configuration>

      <startup>

         <requiredRuntime version="v2.0.50727" safemode="true"/>

         <supportedRuntime version="v2.0.50727" safemode="true"/>

      </startup>

    </configuration>

  33. ankit5 says:

    Hi

    I have a Authoring Website and it works fine on my machine but when the

    Authors are authoring the site the HTML Editor keeps on prompting them to

    Install the Web Author tool for like 5-6 times and then It finally installs,

    they have been doing the authoring earlier and ActiveX was installed on theri

    machines so why it keeps on prompting to install, can any body suggest a

    solution to this.

  34. Stefan Goßner says:

    Hi Ankit,

    that means that the version of the Active X control installed and the version expected in the javascript code sent from the server is different.

    Cheers,

    Stefan

  35. ankit5 says:

    Hi Stefan,

    Thanks for the reply, I checked and found that there is a difference in the Size of NRDHTML.cab development server and on the Production box and since the CMS Virtual Directory is being pointed to the Production Box IIS_CMS Directory in Program Files of Production Box, so do I need to check any JavaScript to make sure the Version of HTML Editor?

  36. Stefan Goßner says:

    Hi Ankit,

    on the page that prompts use View Source in IE and search for the object tag for the editor. It will contain a version number.

    Compare this version with the nrdhtml.dll inside the NRDHTML.cab file.

    These versions have to match.

    Cheers,

    Stefan