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

HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Upgrade SQL and DNNUpgrade SQL and DNN
Previous
 
Next
New Post
2/11/2011 1:29 AM
 
One more piece of advice, that may save you some frustration: after making those changes, restart your browser.

____________________________________
The one-eyed in the land of the blind.
 
New Post
2/14/2011 11:44 AM
 
Marc (ម៉ាក) Vanhemelryck (វ៉ាន់ហេមិលរីក) wrote:
Try to work systematically: it is a 3-step process.

(1) make sure the domain you use goes to the correct ip address. If you use localhost, that should be okay. Otherwise, add the domain to your hosts file. Flush your dns cache and use ping to check.
(2) make sure iis sends the request to dnn: if you use localhost, create an application under 'Default Web Site", Say you call this application MyDnnSite. You will then be able to connect to your dnn installation with http://localhost/MyDnnSite/ Make sure your permissions are set correctly during this step.
(3) make sure DNN knows which portal to bring up: make an alias for localhost/MyDnnSite

Then browse to http://localhost/MyDnnSite.

 I've already attempted all this and it still doesn't work.

 
New Post
3/22/2011 12:10 PM
 
I am still trying to get this to work.

I am running Windows Server 2008 R2 Enterprise. It has SQL Server 2008 installed on it. I am running Windows Web Server 2008 R2 on a Hyper-V machine. Here is what I've done.

  1. Backed up database (from SQL Server 2000)
  2. Zipped up entire web directory
  3. Created new database with same name in SQL Server 2008 R2
  4. Restored old database into the newly created one
  5. Fixed the orphaned user issue
  6. Extracted zip into the wwwroot folder
  7. Give the folder proper permissions
  8. Created the Virtual Directory in IIS
  9. Converted VD to application
  10. Changed the web.config references to point to new server
I then went to http://localhost/dotnetnuke is just says "Hello World!"

If I go to http://localhost/dotnetnuke/default.aspx is directs me to the generic installation.

Can someone please offer some guidance? Thanks!
 
New Post
3/22/2011 3:01 PM
 
I think I am almost there!

Now, when I go to http://localhost/dotnetnuke I get redirected to my production server! I have localhost in my PortalAlias table. Do I need to delete all the other rows in order for this to not direct me to my production server?
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Upgrade SQL and DNNUpgrade SQL and DNN


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