I am not sure I have ever had the joy of a nice, clean DNN install. And once again I've run up against a error on a fresh installation.

My current site runs on DotNetNuke Community Edition version 6.x. I want to move to 7.0 (DNN Platform) on a completely clean WS 2008 R2 installation. Having installed the OS, installed the ASP.Net and made sure the OS is fully patched with the latest updates, I then installed DNN Platform using WebMatrix. With a couple of minor exceptions (I created a new application, through the Web Matrix wizard), I accepted all defaults. The WebMatrix part ran without error and reported the successful installation of the DNN platform. However, when the site is subsequently launched  (InstallWizard.aspx is launched) I receive the following error:

HTTP Error 500.21 - Internal Server Error

Handler "PageHandlerFactory-Integrated" has a bad module "ManagedPipelineHandler" in its module list

As far as I know, I haven't done anything weird here - completely clean, "simple" installation. It's pretty frustrating.

I'd appreciate any pointers.

Mark

Yes on both counts - .Net Framework 4.0 installed and the app pool is using it.

What frustrates me about the DNN Platform install (and has done with DotNetNuke forever) is that this initial installation should be so straightforward. While I appreciate the suggestion, the idea that the installer wouldn't take care of this as a simple dependency seems weird to me, for such a mature platform. I basically want to run an installer and have a basic DNN web site run.

There always seems to be some "gotcha". This time around I went out of my way to create a fresh VM, with ASP.Net installed and run WebMatrix. I can't think of how I could possible have made it more straightforward. And yet it fails.

Pretty frustrating.

Mark

Thanks Matthias. I added these permissions at the file level, with no luck. I am not sure how/where to set permissions on IIS

handlers.

Also, is this sort of low-level permission configuration expected and necessary on a plain vanilla installation of the DNN Platform through WebMatrix? I see no reference to this in the docs or pages I read to get to the WebMatrix installer. My expectation is that a WebMatrix installation should leave me in a functional state after installation is complete, without having to set permissions at the file level, let alone the IIS Handler level. Is that an unreasonable expectation? As I hinted at the start of this thread, I have never understood why DNN always seems to have these little hurdles and I wonder how many curious users take a look and give up. I don't have that luxury but would hope that the most straightforward of installations on a completely fresh OS installation should not involve setting permissions manually.

Two cents.

Thanks.

Mark