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 ...Install 4.8 ..... Seemingly so close, yet ......Install 4.8 ..... Seemingly so close, yet ......
Previous
 
Next
New Post
2/20/2008 6:29 AM
 

Inspired by Mitch Sellers very helpful blog for installing DNN 4.8.0 on a remote host, I have given updating a trial 4.5.5 installation hosted with CrystalTech to 4.8.0 an attempt today.

Initially I tried updating the test 4.5.5 site hosted with CT. There was no need to backup the db given it was only a test; fortunately I made a copy of the sites web.config file. This proved very handy as it enabled me to copy the SQL connection strings into the new web.config file unzipped from the 4.8.0 Install package.

After competing a very lengthy ftp process and mucking around with the web.config file I was able to get the entire installation to run successfully. Success!

Well so I thought – the portal was created and scripts successfully executed (as indicated below), and so I went with great expectation to the link: Click Here To Access Your Portal Only to RECEIVE a DREADED 403 ERROR PAGE:

This error (HTTP 403 Forbidden) means that Internet Explorer was able to connect to the website, but it does not have permission to view the webpage.

I experimented with the web.config file permissions and recreated the SQL dbs on numerous occasions; and adventurously (given my limited abilities) tried changing the encryptions and related that were provided with the web.config file, saved from the original 4.5.5 file. Alas, whilst the installation still ran successfully similar error messages were produced.

I now have no other option but record the sorrowful tale of my day in this forum in the hope that someone might be so merciful as to offer a suggestion to end my suffering – death is currently not an option.

NB: I failed an installation – or partially executed an install using the old dnn 4.5.5 db – will this affect the dnn 4.8 files I had updated to my server i.e. does a failed installation necessitate a new lengthy file update via ftp. I hope not – the previous update took me half a day.

Afterthought – is there an alternative way to access the portal that has been created? A way in which I can manipulate the permissions?

Installation Status Report

00:00:00.031 - Installing Version: 4.4.0
00:00:00.031 -   Executing Script: DotNetNuke.SetUp.SqlDataProvider 
Success
00:00:00.093 -   Executing Script: DotNetNuke.Schema.SqlDataProvider 
Success
00:00:03.984 -   Executing Script: DotNetNuke.Data.SqlDataProvider 
Success
00:00:05.375 - Installing MemberRole Provider:
00:00:05.390 -   Executing Script: InstallCommon
00:00:06.031 -   Executing Script: InstallMembership
00:00:06.562 -   Executing Script: InstallProfile
00:00:06.781 -   Executing Script: InstallRoles
00:00:07.265 - Upgrading to Version: 4.8.0
00:00:07.296 -   Executing Script: 04.04.01.SqlDataProvider 
Success
00:00:07.531 -   Executing Script: 04.05.00.SqlDataProvider 
Success
00:00:08.562 -   Executing Script: 04.05.01.SqlDataProvider 
Success
00:00:08.703 -   Executing Script: 04.05.02.SqlDataProvider 
Success
00:00:09.062 -   Executing Script: 04.05.03.SqlDataProvider 
Success
00:00:09.156 -   Executing Script: 04.05.04.SqlDataProvider 
Success
00:00:09.234 -   Executing Script: 04.05.05.SqlDataProvider 
Success
00:00:09.265 -   Executing Script: 04.06.00.SqlDataProvider 
Success
00:00:10.078 -   Executing Script: 04.06.01.SqlDataProvider 
Success
00:00:10.093 -   Executing Script: 04.06.02.SqlDataProvider 
Success
00:00:10.093 -   Executing Script: 04.07.00.SqlDataProvider 
Success
00:00:10.343 -   Executing Script: 04.08.00.SqlDataProvider 
Success
00:00:10.484 - Performing General Upgrades
00:00:11.203 - Loading Host Settings:
00:00:11.343 - Configuring SuperUser:
00:00:11.531 - Synchronizing Host Files:
00:00:11.687 - Installing Modules:
00:00:11.703 - Executing Additional Scripts:
00:00:11.718 -   Creating Portal: My Website
00:00:14.375 -   
Successfully Installed Portal 0:
00:00:14.375 - Installing Optional Resources:

 

 
New Post
2/20/2008 7:27 PM
 

Well I tried another complete reinstall via ftp this morning same result - successfully runs installation however when go to access the portal receive the following error msg:

This error (HTTP 403 Forbidden) means that Internet Explorer was able to connect to the website, but it does not have permission to view the webpage.

Looks like I will being changing to host who offers 4.8.

 
New Post
2/21/2008 10:48 AM
 

Sorry to hear that you have been encountering issues with the upgrade.

From the looks of the message that you displayed in your first post there was a problem with the SQL connection as it did an INSTALL and not an upgrade.

Most likely the issue that was occuring was due to an incorrect portal alias there are a few options that mgiht cause that, such as a trailing / in the alias.

If you are looking at switching hosting providers, or are looking for some help with getting the install/upgrade going, check out the link in my signature to 3Essentials and feel free to e-mail me at msellers@iowacomputergurus.com with any questions.


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
2/21/2008 7:08 PM
 

Mitch

Thanks for your response.

To clarify I initially attempted an upgrade using the 4.5.5 version. Errors were encountered executing the script associted with the schema. I assumed this was some issue with a difference in the underlying db structure - so wiped the db created from the installation of 4.5.5 from my host and installed a new db. Then ran a fresh install using 4.8 Install. So this explains why there is no upgrade message in the output I posted above.

I too though that it was a problem with a portal alias. So went into the host to see if I cud delete, insert or update the portal alias - unfortunately CT does not offer a Plesk desk type option to view the db table. To write an Update SQL  when you cant see the db table with its column headings etc  is difficult - whilst I am capable with SQL, I might as well be blindfolded at the terminal if I cant get some hints on the table structure and its fields. Well after numerous failed attempts I hoisted the white flag on this one.

You wudnt per chance know the correct SQL statement to update a portal alias?

PS - I dont regret the whole process. Learned a lot about the installation, dnn site upgrade and ftp process. Thanks also for your blog on this and have also made use of one of your modules.

Will go to your site and check out 3Essentials. Thanks again.

Miles

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Install 4.8 ..... Seemingly so close, yet ......Install 4.8 ..... Seemingly so close, yet ......


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