Hi

I'm new to DotNetNuke and can't find a quick answer to this problem, apologies if it's been answered before.

I watched and followed the installation video tutorial and managed to get a site working locally on my home PC (Win7, IIS7.5, SQL Server Express) but have problems when trying to install to my webhost.

I removed to security from  the downloaded .zip install package and extracted all files.
Uploaded the extracted files to wwwroot of my webhost.
Created a new empty database on their SQL Server 2008 server and a user with access to that database (though I'm not able to set that user as owner)
I've assigned read and write permissions to wwwroot and all child objects to Network Service and my site's URL account
Connected to the site with my browser and initiated the installation.
The site reports all permissions are fine, I choose the typical installation option and select SQL server, give the server and database name, choose SQL Server login and give the correct username and password. Deselect run as dbowner. All works fine at this point.

The next page starts to create the 5.0.0 database but fails within a few moments saying to check a log file.
The file it mentions does not exist, though many different tables have been created in the database so I know that the connection and initial scripts are working.

I have tried deleting this database, recreating another empty database and selected different options at the relevant part of the install wizard, but all of them fail in the same way - leaving dbowner checked doesn't help, deleting and recreating the SQL server user doesn't help.

If anyone has any suggestions I would really appreciate it.

Thanks in advance!

Do not de-select the option to run as dbowner ... you need dbowner privileges.

You can check with your host but typically when you are given a database and a user to connect to the db, that user is granted the db_owner privileges. That is safe from the host's perspective because although you are getting a high degree of permissions, they are isolated to this particular database and are not able to affect the SQL Server itself or other databases on that server.

Since you are creating, dropping and modifying database objects when running the DNN sql scripts during installation, db owner privilges are required.

The file in question should be located on disk under Providers/DataProviders/SQLDataProvider. Not there?

---

pmgerholdt