Try our conversational search powered by Generative AI!

404's on files


We have a customer who's experiencing the following problems:

In an EPiServer 6 R2 project. When running/debugging with Visual Studio 2012 and Visual Studio Development Server (Cassini) everything is OK.


But when running with IIS Express, Managed Pipeline Mode set to classic, in Visual Studio 2012 or 2013, many files served by virtual path providers gives 404. An idea is that it has something to do with virtual path providers or maybe static-file-handler. All uploaded files and the css-, js- and image-files for EPi-edit and -admin gives 404, can not be found.


Have experienced the same problem running an EPiServer CMS 6 R2 site on Windows Server 2012 R2 and IIS 8.5, Managed Pipeline Mode = Classic.

Any ideas?

May 26, 2015 9:41

As I remember, .config files in EPiServer 6R2 use IIS6 format which is quite different from IIS 8.5.
Does this post help?

Can you also check that application pool identity user has read/write permission for App_Data folder (or wherever your VPP files are stored)?

Usually when you cannot run the application, it's due to invalid web.config file, and when images / files throw 404, it's due to file permissions.

May 26, 2015 10:08

Hi (I am the customer)

Thank you for your answer.
Be aware that it is IIS Express and IIS 8.5 in CLASSIC mode (IIS 6 mode). The config files work with CASSINI, Visual Studio Development Server, that is IIS 6 mode. So if I set it to classic mode I shouldn’t have to change anything in the config-files. Or am I completely misunderstanding the CLASSIC Mode?
I know that, if I run IIS 7 or higher with Integrated mode, I have to move from:
system.web/httpHandlers -> system.webServer/handlers
system.web/httpModules -> system.webServer/modules
IIS 6, Cassini, IIS 7 (or higher) with Classic mode and IIS Express with Classic mode:
IIS 7 (or higher) with Integrated mode and IIS Express with Integrated mode:
The reason for running CLASSIC mode is temporary. I want to move over to IIS 7/IIS Express without moving over to Integrated mode yet. So I don’t have to change the config-files.
But if the only way to get it working with classic mode is to add system.webServer elements on multiple places in web.config I might as well move over to integrated mode.
A note: During the day I have got it working in IIS Express Integrated mode by moving to system.webServer-elements. But the question is for CLASSIC mode.

Can anyone confirm if I need (or not need) system.webServer elements even if I run IIS 7 or higher in CLASSIC mode?
Regards Hans

May 26, 2015 14:32
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.