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...Administration ...Administration ...How to convert site from Virtual Directory to Web Site ?  How to convert site from Virtual Directory to Web Site ?
Previous
 
Next
New Post
4/8/2010 1:14 PM
 

Hello,

I install a new version of DotNetNuke (version  5.03.01) on my windows 2003 server. Everything work fine when i use Virtual Directory.  I can use home button, login button... 

the path is : http://localhost/VoyanceClo

But when I try to convert the Virtual Directory to a Web Site, the problem begin.  All the button stop working, and some pictore is missing on my default.aspx web page.

The path is : http://mydomain.com:3627

 

Before I change my Virtual Directory I add new portal aliases.  My list is localhost/VoyanceCLo , mydomaine.com:3627 and 205.151....100:3627

 

With this change I can see de Default.aspx page.   But when I click on home button or login button, I always receive ths error and I search away to resolve this error, could you help me ?

 

Server Error in '/' Application.

The resource cannot be found.

 Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable.  Please review the following URL and make sure that it is spelled correctly.

Requested URL: /Login.aspx

 
New Post
4/8/2010 2:24 PM
 
Problem looks like UrlRewriter module won't executed. Please check Home Directory -> Configuration -> find .aspx extension -> Edit -> check "Verify that file exist" should be unchecked.

Team Leader
CodingStaff Development Company
Check our dnn modules and dotnetnuke skins to see where you can start.
 
New Post
4/9/2010 9:23 AM
 

Hello Tanya,

I check this, and everything is OK.  Do you have any other solution for me ? :)

If I use the Virtual Directory everything is ok.  But if I use WebSite is IIS, all the problem begin.  It's look like a problem with DNN, but I don't find what is the problem. 

 

Tanks

David

 

 
New Post
4/9/2010 10:10 AM
 
I think I know what's the problem is. Check this issue http://support.dotnetnuke.com/issue/ViewIssue.aspx?ID=11854&PROJID=2

Team Leader
CodingStaff Development Company
Check our dnn modules and dotnetnuke skins to see where you can start.
 
New Post
4/9/2010 11:59 AM
 

But I forgot to say something.

I have another portal on my server who is located on port 3626.  This portal was created with DBB 4.0.6 and updated to 5.3.1 and this portal work great with the webserver on port 3626 this portal have a lot of portal alias lok like : mydomain.com, mydomain.com:3626 ...  and all is ok.

My problem can be issued because I install my new version of DNN and configure it, when DNN is running in Virtual Directory ?  and after I created a Webstie for this virtual directory ?

 

 

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...How to convert site from Virtual Directory to Web Site ?  How to convert site from Virtual Directory to Web Site ?


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