I just completed an upgrade from 3.0.13 to 3.3.7 for my company. I had a lot of tweaking to do before the site would upgrade successfully. Basically, I followed the upgrade instructions provided to us by Shaun Walker (the sticky post at the top of this forum). Since my database didn't use the "dnn_" prefix, I had to remove that from the upgrade connection string's object qualifier parameter. I also made sure that the IIS_WPG had full control of the file system. Then I kept blasting the failed installs, and repeating the upgrade (making changes as the errors dictated) until I got all the errors out. It took me about a day to complete the upgrade process, but I am still working on the Authentication module stuff. We are using the pre-core version of the Authentication module in our application, so I need to figure out how to replace our aging module with the newer core version. Other than that, I have been very happy with the process.

It looks like your issue is related to the object qualifier parameter located in the upgrade connection string in your web.config. Reflection is probably throwing an exception because it can't find a database object that matches the name of the one it is trying to execute. For example: If reflection is looking for "dnn_Users" and your actual table name is "Users", it would throw an exception because it can't find the "dnn_Users" database object. So rather than rewrite all the stored procedures and update all the table names, I elected to simply remove the "dnn_" located in the upgrade connection string's object qualifier parameter.

Make sure you cover all your bases in the web.config. READ Shaun's upgrade instructions and FOLLOW them to the T. And don't forget to make backups of your database files and website files before you start! If you do these things, you should be fine. Happy Nuking!

Cheers!