We're not in a position to upgrade DNN just yet but would like to move from SQL 2014 to 2019 on the database side. After restoring the database and "fixing" the logins, I can connect with SQLCMD using the SQL credentials and run a query but DNN is having an issue. I am the DBA and know next to nothing about DNN other than updating the server name in the web.config file.
We're getting this error:
Exception information: Exception type: NullReferenceException Exception message: Object reference not set to an instance of an object. at DotNetNuke.HttpModules.OutputCaching.OutputCacheModule.OnResolveRequestCache(Object sender, EventArgs e) at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step) at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Any thoughts or suggestions would be helpful.
Thanks
Make sure there's an entry in the PortalAlias table with the domain/URL you're using to access the site.
PortalAlias
Well, that seems to be the issue. I was restoring a production db back up to create the test system db on the new sql server and the URL of the test server was not in the portalalias table there. My resolution was to backup our existing test system (which has the correct URLs) and restore it to the new server. Worked like a champ. Now, to find a "how to create a test system" document.
Thanks for the quick and very helpful response!
jmt
These Forums are dedicated to the discussion of DNN Platform.
For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:
Awesome! Simply post in the forums using the link below and we'll get you started.