Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
AI OnAI Off
EPiServer 4.61, Windows Vista and IIS 7.0
This is another recommendation about this issue from one of our partners @ Ottoboni Group Kalle Ljung. I have done these steps myself and have no trouble today between Vista and EPiServer. :)
1. Install .NET Framework 1.1
2. In the Control Panel, Programs & Features, install:
- IIS 6 Management Compatibility
- IIS 6 Management ConsoleIIS 6 Metabase and
- IIS 6 configuration compatibility
3. Make sure the site runs .NET 2.0 after the install of .NET 1.1
4. Install EPiServer Manager
5. Shut down User Account Control (UAC), otherwise you get Access denied when you list the websites.
6. Install EPiServer with .NET 2.0 templates according to the instruction on www.episerver.com
7. Point 404 side to /Util/NotFound.aspx and change "Error Responses" to "Custom errorpages" under "Edit Feature Settings...", these settings are not found under "Error Pages" for the EPiServer website.
8. Make sure that the site uses "Classic .NET AppPool", if this does not exist, create a new application pool wiht settings: .NET Framework version: 2.0, Manged pipline mode: Classic
When I tried EPiServer i Manged pipline mode: Integrated så började w3wp.exe process started loading the CPU 100%.
It seems that IIS does not handle URL with + chars, this means that the tree in Edit shows wrong pictures that refers to: Util/images/ExplorerTree/T+.gif
A problem is that they have changed the handling of error pages in IIS7 ad to get "FriendlyURL" to work you need to turn on the errorhandling even if you run it locally. This means that you DON´T se the error message generated from .NET but a ”nicer” page. So the solution is not to use FriendlyURL when you develop.
Case:75325
I actually solved the issue with the + in url.
I had to do some system changes by inserting
#15206
Mar 30, 2007 8:50
I would suggest against disabling UAC, especially since it does not seem to interfere with EPiServer operations at any time later.
Instead open your Episerver Manager folder (probably C:\Program Files\EPiServer Manager) and in the file property of EPiServerManager.exe set it's privilege level to run as administrator.
#15207
Apr 03, 2007 8:38
The requested page cannot be accessed because the related configuration data for the page is invalid.Then you will need to grant access to the local "Network Service" account to the EPiServer root directory. NOTE: Due to Vista's UAC the permissions will NOT inherit automatically to the Web.Config (or indeed License.config) file as would be expected - You may need to set the permissions on the *.Config files after setting the permissions on the root, along with granting modify access to the Web.Config. 2. IIS 7.0 and Application Pools The next issue I encountered was to do with Application Pool Modes. IIS 7.0 runs its Application Pools in a different manner (Managed Pipeline Mode can be "Classic" (old) or the new "Integrated") from previous versions, and hence running a default EPiServer site with the new (Integrated Managed Pipeline) Application Pool type will cause the following error:Description: This application is running in an application pool that uses the Integrated .NET mode. This is the preferred mode for running ASP.NET applications on the current and future version of IIS.The exception message prompts you to either change the AppPool to classic mode, or to Upgrade the App to work with the new Integrated Mode AppPools. I upgraded the EPiServer to use the new AppPool by issuing the following command (given to you in the exception message body) from an administrative command prompt:%systemroot%\system32\inetsrv\APPCMD.EXE migrate config "EPiServer460Test/"This sounds intrusive, but all it is really doing is moving therunAllManagedModulesForAllRequests="true"to the