I'm installing DNN for the first time today, version is 4.3.4.
I'm hitting the same issue as this thread:
http://dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/107/threadid/65644/scope/posts/Default.aspx

I tracked down the issue to be that the install fails if I use a "db_owner" account but succeeds if I just logon as sa. This is of course a bad practice and so in my opinion this is a DNN bug. db_owner role of the DNN database should be entirely sufficient, or at the very least the install doc needs to state otherwise ;)

I verified the failure and repro cases twice each.
Repro follows.

My test environment is a seperate web server and database server. Both are running Windows MCE.

On database server:
-Right-click Security, choose Create Login.
--create login 'dnn' with a password
---set default database to DotNetNuke
---uncheck enforce password policy
--click User Mapping in left hand pane
---click Map checkbox for DotNetNuke database
---click db_owner role in lower pane for DotNetNuke database
--click OK to create the new user account

On web server:
-copy release.config to web.config and edit with settings
--comment Sql Express SiteSqlServer values for connectionStrings and appSettings sections
--uncomment Sql 2000/2005 SiteSqlServer values for connectionStrings and appSettings sections
--fill in uid/pwd values for both occurrences of the connection strings
--set correct servername for both occurrences of the connection strings
-net start w3svc, browse to /default.aspx

I see two sql exceptions from dnn in the eventlog that it cannot find dbo.GetPortals. I verified that the sp does exist in the DNN database, and I see a few successful calls to it in my sql profiler trace.


Thanks,
Adrian