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 ...Converting a virtual directory install to a website...Converting a virtual directory install to a website...
Previous
 
Next
New Post
10/25/2006 2:37 PM
 

Robert, many thanks for your quick answer ! The v-dir is exact the problem ! I did exact what you have proposed - and I got a very interesting behavior: when I call it http://localhost/ - it makes an automatic redirect to my orginal server http://www.geopic.at - EXTREM isn't it ?!?! - But this behavior (the redirect) has been done from the DNN-site because I can see that on the first call DNN is compiled - I looked in my site-settings on DNN (Portal Aliases): there I have www.geopic.at AND localhost  as entry-point.

On the IIS (developing machine - [v-Dir]) I only changed the Local Path from the Default Web Site: c:\inetpub\wwwroot -> c:\inetpub\geopic

Many THX for your support !

Cheers,
Robert


Robert John Austria / Europe
 
New Post
10/26/2006 1:19 AM
 

It works now ! I found out the problem:

In the DNN-Portal Aliases I have to change the position: 1.) localhost 2.) www.geopic.at AND I have forgotten to remove the "Application Name" within the IIS.

Summary for changing a DNN-installation from a v-Dir (WinXP - developer machine) to a production environment (Windows Server 2003) without a v-Dir (real web-site with it's own app.pool):

Imagine that on the server (production) your DNN-portal is perfectly running on www.yourdomain.com with own application pool under IIS 6.0

  1. check your Portal Aliases (also the position): 1.) localhost 2.) www.yourdomain.com
  2. copy the whole directory from your server to your developer machine (e.g.: c:\inetpub\yourportal)

You have now the exact copy of your server on your dev. machine - next steps are:

  1. Open IIS
  2. Open Properties for "Default Web Site"
  3. Change to Tab "Home Directory"
  4. change your local path to "c:\inetpub\yourportal")
  5. Don't remove "Application Name" (should be "Default Application")
  6. Within IIS (within "Default Web Site" - tree structur) you have a tree-node: yourportal 
  7. Check the settings of this node:
  8. Local Path: c:\inetpub\yourportal - AND: remove the Application name (all within the Tab "Virtual Directory")

THAT's it  - hope I could help someone

Cheers,
Robert


Robert John Austria / Europe
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Converting a virtual directory install to a website...Converting a virtual directory install to a website...


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