Take the community feedback survey now.

smithsson68@gmail.com
Mar 30, 2011
  4065
(0 votes)

Deployment Center “New Site Wizard” crashes on Windows 7 SP1 & Windows Server 2008 R2 SP1

The current version of the EPiServer Deployment Center has a bug which only shows itself on Windows 7 SP1 and Windows Server 2008 R2 SP1.

The problem occurs when you launch the “Install site and SQL Server database” or “Install site without database” scripts and then on the 1st wizard page you choose an existing web site in the Site Name dropdown box and enter a name in the Application Name dropdown box (i.e. to create a sub-application):

image

When you click on the Next button you will probably find that Deployment Center crashes. This is caused by some sloppy coding by us which was tolerated on previous versions of Windows but alas no more.

To fix this problem you should download CMS 6 R2 from EPiServer World (this should be available from Monday 4th April 2011) and install the EPiServerShared.msi. This will install the latest Deployment Center and shared EPiServer CMS Windows Services which are all backwards compatible with previous versions of CMS.

Mar 30, 2011

Comments

Please login to comment.
Latest blogs
A day in the life of an Optimizely OMVP - Introducing the beta of Opti Graph Extensions add-on

Introducing Opti Graph Extensions: Enhanced Search Management for Optimizely CMS I am excited to announce the beta release of **Opti Graph...

Graham Carr | Sep 15, 2025

Content modeling for beginners

  Introduction Learning by Doing – Optimizely Build Series  is a YouTube series where I am building  a fictional  website called  TasteTrail , food...

Ratish | Sep 14, 2025 |

A day in the life of an Optimizely OMVP - Enhancing Search Relevance with Optimizely Graph: Synonyms and Pinned Results

When building search experiences for modern digital platforms, relevance is everything. Users expect search to understand their intent, even when...

Graham Carr | Sep 14, 2025

Optimizely CMS and HTML validation message: Trailing slash on void elements has no effect and interacts badly with unquoted attribute values.

When using the W3C Markup Validation Service, some annoying information messages pop up because Optimizely CMS adds the trailing slash to...

Tomas Hensrud Gulla | Sep 14, 2025 |