Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...DNN Platform (o...DNN Platform (o...Migrated Website Redirects to Install WizardMigrated Website Redirects to Install Wizard
Previous
 
Next
New Post
8/23/2018 8:05 PM
 

It's not very often I get stumped on DNN, but I've run into a very curious issue with a website I've migrated to my local machine.  This is a fresh backup too, taken directly from a working production website moments before I tried to restore it locally.  No matter what I've tried so far, it keeps redirecting to the installation wizard.  I've literally migrated thousands of DNN websites, so this is really interesting to me.

This is normally a database issue, but so far, I don't see anything to confirm this for me this time.

Just to get it out of the way, I've already:

  • Created and verified that the database exists and that the expected data is in the database.
  • Created and verified that the DB user can log in and view tables, as well as execute stored procedures, using SSMS and LINQPad.
  • Added the new portal alias to the HOST file, IIS website, and the PortalAlias table.
  • Ensured that the connection string is pointing at the correct database instance and table.
  • Verified that the correct permissions are applied to the website folder.
  • Turned on custom errors and switched to debug compilation mode.

I don't see anything useful in the Log4Net event log either.  The following are the errors that are logged when I view the website, in order.

  • DotNetNuke.Web.Common.Internal.DotNetNukeHttpApplication - System.Web.HttpException (0x80004005): The file '/Install/InstallWizard.aspx' does not exist.
  • DotNetNuke.Services.Exceptions.Exceptions - System.Data.SqlClient.SqlException (0x80131904): Could not find stored procedure 'dbo.GetPackages'.
  • DotNetNuke.Services.Exceptions.Exceptions - System.Data.SqlClient.SqlException (0x80131904): Could not find stored procedure 'dbo.GetHostSettings'.
  • DotNetNuke.Services.Exceptions.Exceptions - System.Exception: Failed to execute initialization task DnnSharp.Common.InitCommonDlls.Tasks.FixResourceManifests ---> System.ArgumentNullException: Value cannot be null.
  • DotNetNuke.Services.Exceptions.Exceptions - System.Exception: Failed to execute initialization task DnnSharp.Common.InitCommonDlls.Tasks.SetupPersistentCacheScheduler ---> System.Data.SqlClient.SqlException: Could not find stored procedure 'dbo.GetSchedule'.

Every time I attempt to view the website, I'm instantly redirected to the InstallWizard.aspx page, but it doesn't exist of course, since this is an existing website and I'm not attempting to upgrade it.


Will Strohl

Upendo Ventures Upendo Ventures
DNN experts since 2003
Official provider of the Hotcakes Commerce Cloud and SLA support
 
New Post
8/23/2018 8:08 PM
 
Oh... I'm not sure if it makes any difference, but the original database was SQL 2014 and the local one I restored to is 2016. This hasn't mattered in the past though.

Will Strohl

Upendo Ventures Upendo Ventures
DNN experts since 2003
Official provider of the Hotcakes Commerce Cloud and SLA support
 
New Post
8/23/2018 8:18 PM
 
Have you checked the web.config to make sure the upgrade flag has not been set?

Also, can you confirm the .NET Framework matches where it came from?

What happens when debug="false"?


nvisionative, Inc.
Corporate Website  |  Facebook Page  |  Twitter Page
 
New Post
8/23/2018 8:25 PM
 
Thanks for your help, David. I literally just resolved the issue. This specific website has two different databases it requires in order to run. One is DNN, of course, and the other is for a third-party app integration. The database names are almost identical, so I kept not noticing that the DNN connection string was actually pointing at the other database.

Ugh... Rookie mistake! :D

Will Strohl

Upendo Ventures Upendo Ventures
DNN experts since 2003
Official provider of the Hotcakes Commerce Cloud and SLA support
 
New Post
8/23/2018 9:20 PM
 
So glad you figured it out! Been there, done that. So easy to overlook the "simple things". :)


nvisionative, Inc.
Corporate Website  |  Facebook Page  |  Twitter Page
 
Previous
 
Next
HomeHomeDevelopment and...Development and...DNN Platform (o...DNN Platform (o...Migrated Website Redirects to Install WizardMigrated Website Redirects to Install Wizard


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out