November Happy Hour will be moved to Thursday December 5th.

Magnus Rahl
Jan 27, 2009
  8631
(1 votes)

Problems installing EPiServer 4.x with newer versions of EPiServer and .NET present

This is probably old news for many of you, but I decided to put two common problems with installing EPiServer 4.x in the same blog article. The first problem is caused by the .NET framework 3.0 or newer and the second by EPiServer CMS 5 R1 or newer.

Trying to install an EPiServer 4.x (at least 4.62) site on your computer you might run into the following error message, and the installation is halted: “Failed to register ASP.NET client scripts on this side [The system cannot find the file specified]”.

The quick remedy for this, as described in this forum thread is to temporarily move the folder v3.0, v3.5 etc from C:\WINDOWS\Microsoft.NET\Framework\ (or equivalent) to another location during the installation process. The folders can be moved back when the installation is finished.

An other error message you might encounter at a later stage of the installation, when the status of the installer reads “Running assembly installer for /bin/EPiServer.SchedulerSvc.exe”, is: “Cannot install files: The installation failed, and the rollback has been performed. [The name is already in use as either a service name or a service display name]”.

To avoid this, go to add/remove programs and uninstall the EPiServer Shared component before installing the site. The EPiServer Shared component may be reinstalled afterwards from the EPiServer CMS installation package.

Jan 27, 2009

Comments

Sep 21, 2010 10:32 AM

Yes, same problems with 4.61.0.83, and same solution (you only have to rename the framework directories during the installation if you are lazy :)

Andrew Sanin
Andrew Sanin Sep 21, 2010 10:32 AM

This post helped me a lot, Thanks!!

Sep 21, 2010 10:32 AM

I have the second issue but don't have an option to remove EPiServer Shared component from add/remove programs?
/ Lee Englestone

Magnus Rahl
Magnus Rahl Sep 21, 2010 10:32 AM

A colleague had the same issue with no EPiServer Shared component in the control panel, but still having the scheduler service error message. I just installed CMS 5 R2 SP2 and have a component named "EPiServer Shared 1.1.21.0" in the control panel. So I have no clue for you, but please comment if you find a solution!

Please login to comment.
Latest blogs
Optimizely SaaS CMS + Coveo Search Page

Short on time but need a listing feature with filters, pagination, and sorting? Create a fully functional Coveo-powered search page driven by data...

Damian Smutek | Nov 21, 2024 | Syndicated blog

Optimizely SaaS CMS DAM Picker (Interim)

Simplify your Optimizely SaaS CMS workflow with the Interim DAM Picker Chrome extension. Seamlessly integrate your DAM system, streamlining asset...

Andy Blyth | Nov 21, 2024 | Syndicated blog

Optimizely CMS Roadmap

Explore Optimizely CMS's latest roadmap, packed with developer-focused updates. From SaaS speed to Visual Builder enhancements, developer tooling...

Andy Blyth | Nov 21, 2024 | Syndicated blog

Set Default Culture in Optimizely CMS 12

Take control over culture-specific operations like date and time formatting.

Tomas Hensrud Gulla | Nov 15, 2024 | Syndicated blog

I'm running Optimizely CMS on .NET 9!

It works 🎉

Tomas Hensrud Gulla | Nov 12, 2024 | Syndicated blog

Recraft's image generation with AI-Assistant for Optimizely

Recraft V3 model is outperforming all other models in the image generation space and we are happy to share: Recraft's new model is now available fo...

Luc Gosso (MVP) | Nov 8, 2024 | Syndicated blog