Here's what I'm getting:

I looked in the object browser for info to fill this in, could not find a type, etc. for the InstallWizard.aspx handler.  Chris Hammond has a post from 2009 about making sure the zip file doesn't have a "Blocked" on it.  I use Winrar, it didn't.  But I had some adventures getting this far.

It does mean my DB in Sql Server is set up and the connection strings worked!

I need to make a handler -- what's the resource that tells how to do this?

Erik,

We're on an earlier version of IIS, 7.5.  Here's what I see.  ASP.Net is installed.

This may or may not be a clue, here are the Handler Mappings for the New Install:

Here are the Handler Mappings for the production installation, note no scroll bar in the above shot.  There are several pages of mappings in this shot:

Something didn't happen someplace.  Of note is the LogoffHandler* which does live in the working site and this entry in the web config of the new install was throwing an error.  I had to add a <clear /> tag above it because it was throwing a duplicate key error.

So ... have we got something throwing loads of duplicate key errors?  Here's the shot of the web config I put in another post.  Look at the number of <remove name= ... > tags that had to be installed.

This smacks of a *simple* answer ... like maybe I have a jacked install and need to start over?  DNN is definitely not this hard.

Anyhow, here's a bit more input.  Somewhere ... the penny will drop.

Thanks,

Mike

Cathal,

The install was done by our ISP.  This is the 10th or so site I've added, along with 9 prior DNN and/or FTP sites.  Trust me, .Net is installed.  And other sites which needed to be upgraded from 4.9 to 6.2 some time ago upgraded just fine.

I hesitate to re-register the .net version with IIS what with the production site also on this machine.  If I do that, it can affect the other sites, right?

I can double check with the ISP team that upgraded our server in 2012 and make certain they did install IIS first and then the .net version but I'm sure they knew to do this.  Again, if that were the issue it would have reared its head in 2012 ... I think I'm right anyhow.

Enlighten me if I've missed anything.

Thanks,

Mike