smithsson68@gmail.com
Jan 28, 2011
  7013
(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

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