Last night I had the occasion to upgrade a site from DNN v 04.00.02 to 04.05.05. Although the upgrade appeared to have gone fine, I discovered I was not able to add a module (happened to be Media module) to a page without generating an SQL object invalid error in the log for the table "DNN_DNN_Roles". Further investigation found that in both stored proceedures GetRole and GetRoleByName defined in the 04.00.04.SqlDataProvider script, the FROM clause was coded as  "{objectQualifier}{objectQualifer}Roles" rather than the correct {databaseOwner}{objectQualifier}Roles". This error was apparently first introduced in this script in DNN version 04.05.02 or 04.05.03.  and has been carried forward in versions 04.05.04 and 04.05.05.

Manually correcting the two sprocs in the database fixed the problem. I then checked to see if the issue had been reported in Gemini and finally found it in the non-public core issue tracker. It has been corrected for the next DNN release.

As I could not find mention of the issue here on the forums. I am posting this incase others who are using a non-blank objectQualifier and upgrading from a version prior to DNN 4.5.2.  That will teach me not to skip framework upgrades!

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner