I have just found that when trying to install with SQL 2005 on a web service that you need to the following lines so that they look like below

<authentication mode="Forms">

      <forms name=".DOTNETNUKE" protection="All" timeout="60" cookieless="UseCookies"/>
    </authentication>

    <!---->
            <identity impersonate="true"/>
            <!--
            <authentication mode="Windows">
            </authentication>


I hope that helps!

I had performed an install while my database user (specified in both connection strings and set as databaseOwner in web.config) and the install ran.  My host then set my db user back to their default permissions (they won't allow me to keep a db user with db_owner privleges).

After that, when I log in as host, I get the following error:

A critical error has occurred. EXECUTE permission denied on object 'aspnet_CheckSchemaVersion', database '[my database name]', owner 'dbo'.

So it's not just during the installation process that your database user is required to be dbo.

The combination of this Full Trust issue as well as the db_owner issue makes it impossible to run DNN 4.4 in my shared hosting environment.  Is anyone actually running DNN 4.4 in a shared host environment similar to mine and mahai's?

I'd prefer to not have to switch hosts just for this.  They provide everything that I need for many differrent types of sites (.net 2.0, mssql2000, unique application pools per domain) as well as multiple domains in the same account.  This worked out quite well for me up until 4.3 (when I started encountering impersonation-related issues as well).  I have not been able to use my host for DNN since then.

Is DNN heading in a direction where it's abondoning support for multiple domain shared hosts or is there a potential solution to this?