I was curious how fixes like this one are supposed to be distributed?  Is it up to the end-user to manually fix their own stored procedure(s), etc? 

Basically - this one bug rendered my site(s) unusable from a management perspective (cannot access page settings, etc...)  - and if I did this on a "Production" site - I would have been, as a previous poster noted, REALLY freaked out...

I know this only affects the sites that have used {databaseOwner}{objectQualifier} tags.  What I find hard to believe is that with the number of release candidates for 4.5.4 (I think I saw up to 3 of them) - this wasn't discovered until it was released to production.  I found the bug within minutes of upgrading one site - so, I would just like to know what I can do to help the release process to prevent issues like this getting out to "final versions"?  This may be a specific case, but as far as a formal process - should pre-release testing include a documented step to include a site using the {databaseOwner}{objectQualifier} tags? 

Don't get me wrong - I think the DotNetNuke project is an incredible product - I'd like to see what can be done to make it even better so little things like this don't cause "major" headaches in the future.

Hi Eby,

i did the same thing which you have specified in the post. But it doesn't  works fine, still i am getting the same error (below).

A critical error has occurred. Invalid object name 'Lists'. Invalid object name 'Lists'.

Not only that after i upgraded from DNN 4.5.3 to 4.5.4, when i click the profile page in Manage Profile tab i am getting the following error. and rest of the things are working fine.

A critical error has occurred. Object reference not set to an instance of an object.

please help me out, i dont know why i am getting this error.its quite urgent.