I am a module developer and am trying to test it in a DNN site where the 'run as db owner' option was UNCHECKED during the DNN installation, but I have been unable to install DNN in this configuration. Everything I try results in SQL errors. I spent quite a bit of time searching, but everything I find suggests to make sure the option is checked. I understand that, but I need to test with it unchecked, since I want to verify that my use of the {databaseOwner} replacement token in my SQL scripts is working as expected.
Things I have tried:
* Specify the 'sa' account during installation, with various tweaks such as creating an 'sa' schema with maximum permissions.
* Creating a new SQL login, adding it to the sysadmin server role and the db_owner database role, with various tweaks such as creating a schema with maximum permissions.
In other words, I am trying to minimize any chance for a permission-related error.
These are the error messages I get (which vary depending on how I tweak the permissions):
"System.Data.SqlClient.SqlException (0x80131904): Cannot find the object 'GetTabPanes', because it does not exist or you do not have permission."
"Installing Database - Version 05.00.00...FAILURE 400 - The stored procedure 'dbo.UpdateDatabaseVersionAndName' doesn't exist."
"System.Data.SqlClient.SqlException (0x80131904): Table 'EventLog' already has a primary key defined on it."
I believe this last error may be a bug, so I created a
bug report.
Can anyone provide some info on installing with the 'run as db owner' option UNCHECKED?
Cheers,
Roger