That's it.

1. Unpacked files and installed VS2005 template.

2. Created SQL Server 2003 database and user as specified in tutorial.

3. Created a DNN web site from VS2005, pointing to C:\DotNetNuke (tried other dirs...).

4. Created a new Virtual Directory in IIS 5.1, pointing to C:\DotNetNuke, using .NET 2.0.

5. Configured all that web.config stuff and so on.

6. Yeah, no "prefix" was specified for database names...

7. CTRL+F5. It built and installation info started to draw in the browser.

8 Finished with:

00:01:49.867 - Executing Additional Scripts:
00:01:49.888 -   Creating Portal: DotNetNuke
00:01:50.909 -   Error: Invalid object name 'vw_Users'.
00:01:50.919 -   Portal failed to install:
00:01:50.919 - Installing Optional Resources:

Installation Complete

Checked database. There is no such vw_Users table. There is a vw_aspnet_users table instead.

It tried to find the error. I was unable to do it, but I found a funny (inofensive?) error in 03.02.03.SqlDataProvider script file:

if exists (select * from dbo.sysobjects where id = object_id(N'{databaseOwner}[{objectQualifier}vw_Users]') and OBJECTPROPERTY(id, N'IsView') = 1)

drop procedure {databaseOwner}[{objectQualifier}vw_Users]

GO

My Users table already contains AffiliateID column.

So, the problem is not there.

I think the problem has to do witn vw_Users view creation. Because code is referring this view, and it doesn't exist.

Seems obvious it is not being created by the installation scripts. I wonder if there are more database objects in this situation.