Very odd--my site shows up fine, but when I try to log in, I get kicked back to the main page with an error up top that says:

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

I followed the directions on Mitchel Seller's blog (http://www.mitchelsellers.com/Blogs/tabid/54/articleType/ArticleView/articleId/173/Upgrading-to-DotNetNuke-480-from-4x.aspx) to the T, it upgraded with no errors, and took me to the main page.

I've tried resetting the .net app, and tried it from another machine, but to no avail.  Has anyone else ran into this?

Thanks!    -Andrew

I'm having the same trouble. I upgraded from 4.5 to 4.8. I was using LDAP for authentication, now I'm trying to use AD. Neither one is working.

It looks like it is making the call to autheticate, but it can find/set an object when it returns.

Anyone know what to do? or how to Undo this mess.

Thanks

-SP

Is the upgrade process in DotNetNuke ever going to address this issue!?  It seems that this question appears every time a new release is available.  As web.config files become more and more complex with third party information, surely there must be some sort of strategy to address this.  One of the great marketing points for DNN is that it's easy to configure, and use, but upgrading seems to be a different matter.

Best regards,

Rod