OK.  I've done some investigating.  My installation stopped at the same spot as Mihai's - Configuring Super User.

I was puzzled as well since when I look at the database after running the install, I see tables created and some are populated with install data.  I also see that the tables with the ASPNET_ prefix are owned by dbo as opposed to the rest of the tables which are owned by my database user provided by my host.

In my web.config file, I use that same database owner in both of the connection strings.  I know this is correct because I get connected to the database and create and modify objects.

I also changed the parameter for databaseOwner from 'dbo' to the same database user name provided by my host.

My host runs SQL2000 and the ASPNET_ tables are created directly inside the DNN database.  Those are the ones that are created as owned by dbo.

Since the install chokes when it's trying to configure the super user, I assume that it's trying to add data to the .net user data (ASPNET_ tables I assume) and chokes because the tables are owned by dbo and not the user you specify as databaseOwner in web.Config.

So my question is:
At what point in the install are the aspnet_ tables created and can they be created owned by the host-provided database user specified in databaseOwner?  Or is there some other parameter that I'm missing where you can specify a database username other than dbo for tasks like this?

I believe that this is definitely the problem.  After much complaining, my host granted my database user db_owner access to my database.  After that the installation ran without generating any errors.  Then I had them set the permissions back to those they give to a standard user, wiped out the db and installed again.  Sure enough, same error at the same point.  When I looked at my db, it was apparent that the install choked at the same point - trying to set up the host user in the aspnet_ tables.  Set it back to db_owner again just to make sure and it worked again.

So the point here is, I guess, that you have to check with your host to make sure that you have a database user with db_owner priveliges if you want to install or update DNN.  It's not enough to have an account that provides access to MSSQL.  You must also find out if you will be granted the appropriate permissions.

The only other alternative is to find out where in the install process the aspnet_ tables are created.  When you start out, you have a completely blank database.  When you're done, you have DNN and aspnet_ tables in there.  I would find it strange if there was no way to change this.  After all, it is possible to have an MSSQL database without a user named dbo (another username with dbo privleges).  In this case would the install fail too?  Any thoughts?