Same error here ("CanDeleteSkin" error on Skins page), no sign of the SP in the freshly installed DNN database (SQL05). 

I'm guessing this is a problem with {objectQualifier}, since a second fresh installation DOES have "CanDeleteSkin" SP and doesn't have an {objectQualifier} specified in "web.config", whereas the problem installation does.

Note that {objectQualifier} is fairly commonly used, since "development.config" (recommended for shared host installations) uses it.

Am I right in thinking there was a recent switch to bulk importing the DB schema up to the last major version number, then upgrading the final few steps through SQL scripts?  Lending support to this theory is the fact that GetFoldersByUser SP *does* exist in the problem installation, BUT it is definitely an older version, not the v4.1.1 version.

So much for "stablisation" release v4.1.1 - the DB scripts don't work and they forgot a bunch of DLLs from "bin"!

 

as far as I see, the objectqualifier is in place at this part of the script, please check the associated .log file for issues during upgrade and post any error listed, so we can check it.

Please accept, that this is a volunteer project and everyplace where people work, ther might occur issues (this might even happen to you).

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN

Thanks for all the replies:  this is the first chance I have had to check the forum since my last post and for some reason, the forum notifications don't seem to be working.

The install completed without any errors.  i actually deleted all the table, views and stored procedures and re-installed after I got this error the first time.    Both connections strings match.  The DatabaseOwner is set to "dbo" and the objectqualifier is "".  There are no install errors in the log files, but there is one error that seems to appear regularly.

 I can try an install with the DatabaseOwnerset to "".