smithsson68@gmail.com
Jan 28, 2011
visibility 7181
star star star star star star
(3 votes)

“Error - EPiServerFramework installation directory was not found” when deploying a CMS 6 site

A few people have experienced this problem which is caused by the EPiServerFramework.msi not installing properly.

We have identified that the EPiServerFramework.msi does not install properly when the setup.exe for the EPiServer product is executed from a zip file.

So the fix is, unzip the package first to your local hard disk, then execute the setup.exe. If you find yourself in this state already you should be able to just execute the EPiServerFramework.msi file on it’s own.

Happy deploying!

Jan 28, 2011

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 |