Installing CMO on server


Hey guys,

how do I go about installing EPiServer CMO on a test/prod server? The problem is that the database tables and content related to CMO doesn't get created. I've done a manual export of all tables (31...) but as the saying goes, I've got a bad feeling about this... perhaps there's another more 2016-ish way?



Feb 22, 2016 14:38

Do you get any nice errors? database user got access rights to create tables? What version of CMS?

Feb 22, 2016 19:22

Hey Daniel,

the problem is no tables are created when I move the latest code from the dev environment to the test environment. So I get a table-not-found error of sorts. I solved it by manually exporting CMO tables and table content, via SQL Management Studio, from the development database and then creating the tables in the test environment. It seems to work but feels abit sktechy to be honest.

The CMS (and also Commerce if I'm correct) auto-updates the database if it's missing/wrong version, and I was hoping for something like that.

Edited, Feb 22, 2016 20:08

Hi, I can sadly tell you there is no easy way to install it on an site that is already in procudtion. You will actually need to install everything with deployment center. But you can trick Deployment Center to install it on your site even if it is not a cms 7.5 website anymore.

The only thing the you get with nuget is actully an update so that it will work with CMS 9. First you need to install a couple of services and such on the server. Then you need the correct tables in the db and you also need to have a lot of settings in your web.config to make it work. Best way as I said is to use Deployment Center on either an empty cms 7.5 website and then copy settings to your site or trick DC to install it on your CMS 9 environment.

The following steps should allow you to manually install CMO on an 8.x site. The general process is to

“trick” deployment center into thinking your site is 7.5, use Deployment Center’s CMO installation

option to install database tables and do some setup, and then update to the current version via nuget /

Package Manager. While we’ve been able to do this without issues, it is strongly recommended to back

up your files before doing this.

1. If it doesn’t exist already, add the following to the <episerver> section of the web.config:

<episerver xmlns="http://EPiServer.Configuration.EPiServerSection">



<site siteId="YOUR_SITENAME_HERE" />

2. Backup the episerver.dll file in the site’s \bin directory (eg. rename to episerver.dll.original).

3. Copy the episerver.dll file from a CMS 7.5 site to the site’s \bin directory. NOTE: the file can

either be copied from an existing site, or from the Deployment Center installation folders; for

example, on my machine the CMS 7.5 dll can be found at:

4. Run Deployment Center. Select the site (the list is populated via IIS site list), and choose the

option to install CMO:

C:\Program Files (x86)\EPiServer\CMS\7.5.394.2\bin\episerver.dll

“Install EPiServer 7.5 CMO (CMS 7.5.394.2)”

a. Live Monitor can be unselected, and installed separately per the section “Installing Live

Monitor from scratch” here:


b. The CMO installation via Deployment Center should complete successfully.1

5. Replace the DLL in the site’s \bin folder with the original 8.x version that you backed up


6. Remove the items you added to the web.config in step 1 above.

7. Run the following commands in Package Console:

Install-Package EPiServer.CMO

Wait for everything to finish; it may take a few minutes. If you get a message about the

database version being out of sync, the following command will update that:


8. If you receive any assembly redirects errors:

a. Add assembly redirects (version 7.5.394.2) per:


At this point CMO installation should be complete; you should be able to access the CMO configuration

page and use the feature (eg. create and start an A/B test, and view the results).

Feb 22, 2016 22:30
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.