smithsson68@gmail.com
Feb 3, 2010
  8124
(1 votes)

Installing multiple EPiServer CMS / Community Editions on the same server

The EPiServer CMS / Community installation packages that you download from EPiServer World are made up of a bootstrapper application (setup.exe) and a few Windows Installer (MSI) files.

One of these files, EPiServerShared.msi, is configured so that only one instance of it may be installed on a computer at the same time. Whereas all of the other MSI’s are configured for “side by side” installation.

What this means is that when EPiServerShared.msi is launched by the bootstrapper application is will check to see of there is already an existing version of it installed on the computer.

If an older version is installed then Windows Installer will replace it with the current one.

However, the problems comes when the version of EPiServerShared already installed is newer than the current one. Then you will receive an error message saying this (if you’re lucky) or if your unlucky some obscure message about a service already running. This is all correct and by design but doesn’t help you get the version of CMS or Community that you want on to the computer.

In these cases, don’t run the setup.exe bootstrapper application but instead run the individual MSI files for the relevant product, such as EPiServerCMS.msi for example.

Feb 03, 2010

Comments

Please login to comment.
Latest blogs
Promoted and Certified

What a busy week

Andy Blyth | May 1, 2026 |

Announcing new library: SettingsManager

When you run .net app, there have been a few ways to store settings. Those can be set via appSettings.json, or via Azure Portal AppService...

Quan Mai | Apr 30, 2026

From Prompting to Production: Optimizely Opal University Cohort and the Future of Agentic MarTech

Most organizations today are still playing with AI. They experiment with prompts, test ideas in isolated chats, and occasionally automate a task or...

Augusto Davalos | Apr 28, 2026

Six Compelling Reasons for Upgrading to CMS 13

Most software updates ask you to keep up. Optimizely CMS 13 asks something different — it asks whether your digital strategy is built for a world...

Muhammad Talha | Apr 28, 2026

Optimizely CMS 13 breaking changes: GetContentTypePropertyDisplayName

When upgrading from CMS 12 to 13, resolving property display names may not work as before. Here’s what changed.

Tomas Hensrud Gulla | Apr 27, 2026 |

Accelerate Optimizely DAM Adoption: Unlocking Business Value with Metadata Bulk Import

Accelerating Optimizely DAM Adoption How a Metadata-Driven Bulk Import Utility Unlocks Real Business Value Executive Summary For enterprises runnin...

Vaibhav | Apr 27, 2026