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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ..."Upgrading DotNetNuke" page repeats after upgrade 4.4.0 to 4.4.1"Upgrading DotNetNuke" page repeats after upgrade 4.4.0 to 4.4.1
Previous
 
Next
New Post
2/6/2007 10:04 PM
 

On WH4L I used their canned install script to successfully create a DNN 4.4.0 instance on my remote site. A few days later DNN 4.4.1 was released so I used the 4.4.1 StarterKit to create a DNN 4.4.1 instance on my local machine (using VS 2005). I then FTP'd the resulting DNN 4.4.1 directories from my local machine to the remote site. My subsequent visit to the remote site's home page tripped the expected "/Install/Install.aspx?mode=Install" change to execute and I received the hoped-for "Upgrade Complete" info that included the following:

CURRENT ASSEMBLY VERSION: 04.04.01

CURRENT DATABASE VERSION: 04.04.00

and when I clicked on the "CLICK HERE TO ACCESS YOUR PORTAL" link everything appeared fine with the upgraded remote site. I also exercised various pages on the remote site successfully.

The problem is that upon a subsequent visit this evening to the remote site the same "/Install/Install.aspx?mode=Install" page reappeared and the remote site apparantly reran the upgrade script.  It now seems that whenever the remote DNN site is restarted - either indirectly or directly (by clicking on RESTART APPLICATION on the Host Settings screen) - this causes the same "/Install/Install.aspx?mode=Install" screen to reappear along with the same "Upgrade Complete" info to appear as before.

How do I eliminate the need for this "/Install/Install.aspx?mode=Install" screen to keep reappearing?

Frozen North

 

 
New Post
2/7/2007 9:05 PM
 

Progress made:

Given that each time my remote DNN restarted it triggered the "/Install/Install.aspx?mode=Install" screen to reappear, and assuming that the 4.4.1 files that I had previously FTP'd were correct then I guessed that whenever DNN is restarted it first checks somewhere to see if there is a discrepancy between the HTML files and some version bit in the database. Inspecting the database I found a table cleverly named "dbo.Version" (doh) containing a single row whose columns were as follows:

VersionID=1, Major=4, Minor=4,Build=0

Hence, since my HTML was 4.4.1 then the startup logic invoked after an application restart (maybe every time?) must compare the HTML and database versions and - if a discrepency exists - initiates the "/Install/Install.aspx?mode=Install" screen to process. I tested this theory by changing the aforementioned value of Build from Build=0 to Build=1 and then restarted DNN, and this time the "/Install/Install.aspx?mode=Install" screen did NOT reappear and the site performed normally. (I double-checked this theory by changing the Build value back to 0 and again the "/Install/Install.aspx?mode=Install" screen again reappeared after a DNN restart).

So, my upgraded 4.4.1 system now seems intact but my new question is:

...why didn't the "/Install/Install.aspx?mode=Install" logic not update the "dbo.Version" table with the new Build value? Is my database now truly OK after upgrading my HTML from 4.4.0 to 4.4.1?

 

 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ..."Upgrading DotNetNuke" page repeats after upgrade 4.4.0 to 4.4.1"Upgrading DotNetNuke" page repeats after upgrade 4.4.0 to 4.4.1


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