Solution: Drop and recreate database. Replace <your login> with the user you're using to logon to the SQL, then run the script.

exec sp_addrole N'aspnet_Membership_FullAccess'
exec sp_addrolemember 'aspnet_Membership_FullAccess', '<your login>'

Now, run the installation.

It creates a role (that will be created by the setup anyway), and grants access to the dbo procedures in advance.

/Tomas

OK guys

That's completely wrong!

no one should alter tables in order to install dnn4...

I had the same error now when trying to use a fresh install, but didn't have it while upgrading from prvious versions.

This means, that the previliges were just fine, until dnn4...

This error must be fixed for next version.

What is strange here, is that I already have the 'next' version (441) - and the same error is there...

I wrote about this in the forum a time ago: There is an on going error in dnn, regarding permmisions for users that are NOT the db owners. Dnn is kinda programmed mostly for dbo's...

This attitude should change.

Thanx
Shai