Hi all.

I recently upgraded a site from 4.3 to 4.9 and although the upgrade appears to have gone smoothly, I'm looking into a couple of complaints regarding some styles being lost and difficulty creating new pages in the manner they did before.

I have a test instance that is a clone of the production instance. I know tha t I need to adjust the values in the PortalAlias table to make the app see the test instance, as well as resetting the site (I do this by changing the web.config insubstantially and saving it).

Without making those changes, when I try to load the test site, it redirects to the main site, and shows on that page an error message:

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

After I make the change to the PortalAlias table and reset the site, the browser stays on the test site, however it doesn't display the skin for the site and instead shows the DNN logo and a general error message:

DotNetNuke Error: - Version 04.09.03   An error has occurred. An error has occurred.

Return to Site

I've tried to locate any sort of error logging in the tables with no success. Is there a flag somewhere that I can turn on more verbose error reporting?

I'd run it from localhost, however the webserver is configured with multiple sites and my IIS admin skills are light enough that I don't know how to do a localhost and have it display that particular site.

I've been chasing this around for about a week now with no success. Any help or direction would be a huge help. Thanks!

Bob

The website and database are on the same server and the connection string uses localhost to connect to the database. We have not observed any change in the behavior of the production site.

When we originally started the upgrade process, we had a functional clone of the production site, version 4.3, and did the site upgrade there. When we had that process ironed out, we took down the production site and did the upgrade with no apparent issue. We subsequently found that there a few discrepancies in the appearance and operation of the site that the client wanted resolved. This is what led to the cloning of the production site, now version 4.9, to the test.

Just to be safe, is there a way to check the production site to see that the version numbers are good? I'm not in a position where I can access the site right now; it will have to wait until later, but is there a table on the database and a page on the site that will tell me what version the site thinks it is? Thanks.