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 ...After Install CanAfter Install Can't Log In...
Previous
 
Next
New Post
4/7/2010 12:25 PM
 

I assume you are now working on a Hosting site?   How did you access the site to run the install wizard?  How did you access the site after the install?  What version?

You will need to create a portal alias records with the referencing the DSN name of your site (maybe a temporary one that you host gave you).  If you have access to the site's database - simply add the record to the portalalias table.

The Server error can be caused by you reapplying the DNN files and ASP.NET getting upset/ confused  You may be able to stop and restart you site based on the level of control given you my your hosting company.  Or you can wait for ASP.NET to clear the cache of your site.  Typically 20 minutes or so.

Hope this helps
Paul.

 
New Post
4/7/2010 1:34 PM
 

 Yes, I FTP'ed the unzipped install files to the server.  The first install was a success with the exception of the links for login and home were not accessible.... see first post.

After the first install, I was redirected to the Default.aspx page.... of the latest DNN version.

on the first install the portal alias was named correctly.

I have pretty much no control from the hosting provider... I've gone back and forth with it all day (no cache clearing...)

Here, have a look for yourself: http://www.djcyrenity.com/

 
New Post
4/7/2010 3:40 PM
 

If read the detailed error trace you will see the first thing it references is the lack of connection string.  So this brings me back to what was FTP'ed to the site.  If you over-wrote your Web.Config file,  you may no longer have a valid connection string present. 

If you can view the existing connection string via FTP, see if it makes sense -- pointing to SQLExpress file, or SQL sever database ..etc.  

If possible, I would start over from the beginning -- Copy a fresh copy of the DNN install to the host.  if using SQL Server delete and re-create the empty database and ensure the security settings on the file are proper.  (All of these steps you have obviously done once as you worked with the install wizard)

If possible, your host may provide this service for free.  Most do, as they have it setup to install and configure properly.  

Paul.

 

 

 
New Post
4/7/2010 3:48 PM
 

 Ok, I shall try... yet, another install.... 

Just to confirm, you say... 

1) use a NEW empty database...

2) upload a NEW set of install files with a modified connection string.

Correct?

(btw, my hosting provider does not support the third party software or applications.. unless it's one of theirs - and those are waaaay inferior to DNN.)

 

I shall give it a shot... thanks for the assistance.  Please check back for an update.

 

 

 
New Post
4/7/2010 4:03 PM
 

If you are use SQL Server and have the correct connection string, then yes I would proceed.

If you want to use SQLExpress. then just upload a clean new set of files.

Given that your host has that type of approach, I would consider another ... DotNetPark for example ..

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...After Install CanAfter Install Can't Log In...


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