A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More

Thomas Krantz
Jan 13, 2011
  6730
(0 votes)

CMO 2.0 and .NET 4 installation problems and solutions

When I installed CMO 2.0 on a CMS 6 site running .NET 4, I had some issues with the installer. Same problems on both my dev and production environment.

After the module installation in Deployment Center, the site does not start. Btw, why can’t I have the option to only install the necessary CMO services and application files? It’s a scary feeling to let an installer do what it wants to my production config files.

Web.config modifications

1. The installer pokes around in Web.config modifying some configSections, namely it adds some sections to system.web.extensions/scripting/webServices sectionGroup.

image

I’m not sure why but once these lines were removed I’m getting the next error.

2. The installer alters the targetFramework and set it to 3.5. I changed this back to 4.0

3. CMO adds some httphandlers that refers to a 3.5 assembly.

I needed to change this handler in order to get Live Monitor and the Thumbnail service working:

<add name="svc-Integrated" path="*.svc" verb="*" 
type="System.ServiceModel.Activation.HttpHandler, 
System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" 
resourceType="Unspecified" preCondition="integratedMode"/>

Which is located here:

image

Change it to:

<add name="svc-Integrated" path="*.svc" verb="*" type="System.ServiceModel.Activation.HttpHandler, 
System.ServiceModel.Activation, Version=4.0.0.0, Culture=neutral, 
PublicKeyToken=31bf3856ad364e35" resourceType="Unspecified" 
preCondition="integratedMode" />

KPI Settings throws an Exception

4. This is probably not a 4.0 issue but something caused by some cultureInfo thing. I don’t know.

In CMO/Campaigns/Settings you can click “KPI Settings” to configure KPI.

Iimage

This caused this one…

image

While I probably should have waited for a proper patch, I needed to get this running. So… at my own risk, I patched  C:\Program Files (x86)\EPiServer\CMS\6.0.530.\Install\Modules\CMO2.0.0.0\CMO\Units\Kpi\KpiSettingsEditor.ascx

image

I changed ValueToCompare to “0,01” with a comma instead.

App_Browsers

5. The browser or gateway element with ID “Safari1Plus” cannot be found.

image

I removed Safari.browser and Chrome.browser from the App_Browsers folder.

Done!

Jan 13, 2011

Comments

Please login to comment.
Latest blogs
A day in the life of an Optimizely OMVP: Learning Optimizely Just Got Easier: Introducing the Optimizely Learning Centre

On the back of my last post about the Opti Graph Learning Centre, I am now happy to announce a revamped interactive learning platform that makes...

Graham Carr | Jan 31, 2026

Scheduled job for deleting content types and all related content

In my previous blog post which was about getting an overview of your sites content https://world.optimizely.com/blogs/Per-Nergard/Dates/2026/1/sche...

Per Nergård (MVP) | Jan 30, 2026

Working With Applications in Optimizely CMS 13

💡 Note:  The following content has been written based on Optimizely CMS 13 Preview 2 and may not accurately reflect the final release version. As...

Mark Stott | Jan 30, 2026

Experimentation at Speed Using Optimizely Opal and Web Experimentation

If you are working in experimentation, you will know that speed matters. The quicker you can go from idea to implementation, the faster you can...

Minesh Shah (Netcel) | Jan 30, 2026