smithsson68@gmail.com
Feb 3, 2010
visibility 8304
star star star star star
(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

error Please login to comment.
Latest blogs
Composition Over Inheritance: Why Your Content Contract Is Not a Base Class

Inside the structural conformance pattern in SaaS CMS — from server-side inheritance to pipeline governance. A contract in Optimizely SaaS CMS is...

Vipin Banka | Sep 19, 2026

Optimizely Opti ID Integration: Why the API Key Was Missing from the DXP Management Portal

While working on an Optimizely CMS 12 Opti ID integration recently, we ran into an issue that initially appeared to be related to SSO authenticatio...

Madhu | Sep 18, 2026 |

Extending a Contract: What You Can Override

Contracts share fields across content types — but not every field setting can be overridden. Push the same contract onto several components, and CM...

Chirag Khanna | Sep 18, 2026 |

Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell

What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(),...

Stanisław Szołkowski | Sep 17, 2026 |