HomeHomeGetting StartedGetting StartedNew to DotNetNu...New to DotNetNu...Run DotNetNuke Website on local machine using localhost.Run DotNetNuke Website on local machine using localhost.
Previous
 
Next
New Post
5/19/2010 5:30 PM
 
Hi,

I have a dotnetnuke website hosted using godaddy. The website was not created by me and I am new to dotnetnuke. I downloaded all the files with the database "datafile.bak" from the hosting site.

The rootname was like "filemain"

I wanted to run the website on my computer using a command like "http://localhost/filemain"

I did the following:

I made a new database and then restored it using the backup database file and changed the web config with the path to this database.
Also made a virtual directory "DOTNETNUKE" and assigned the physical path to the location "C:\filemain".

In the browser when I insert url "http://localhost/DotNetNuke/Default.aspx"

It gives the following error:

*************************************************************************************************************************************************************************

The XML page cannot be displayed

Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.


A name was started with an invalid character. Error processing resource 'http://localhost/DotNetNuke/Default.aspx'. Line 1...

<%@ Page Language="vb" AutoEventWireup="false" Explicit="True" Inherits="DotNetNuke.Framework.DefaultPage" CodeFile="Defa...

*************************************************************************************************************************************************************************
 

Please help with this error or kindly guide me on how to proceed to get a live website to run on local machine using localhost.
 
New Post
5/20/2010 10:29 AM
 
If you want the URL to be the same, the virtual directory should be setup using the extension you like.

Based on the XML rendering of the page, you must also make sure that ASP.NET is installed on your machine before you start.

-Mitchel Sellers
Microsoft C# MVP, MCITP
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 Consulting Quotes, and DNN Technical Support Services

I recommend PowerDNN and 3Essentials for DotNetNuke Hosting and BaseCamp for project management
 
New Post
5/20/2010 11:50 AM
 
I do that all the time. Did you change the contents of the PortalAlias table to the HTTPAlias you are using?
 
New Post
5/20/2010 5:44 PM
 
Thank you very much for the replies.

I have a new problem and I am stuck at this one.

I have setup the virtual directory on my machine which has windows xp with iis 5. When I use the "localhost/Directory/Default.aspx" it loads the page. Directory is name of the virtual diectory.

On Default.aspx all the further tabs work but the Links do not redirect properly. Example if I want to navigate to "LinkClick.aspx".

I am redirected to "http://localhost/LinkClick.aspx?link=92&tabid=52" and it should have been "http://localhost/Directory/LinkClick.aspx?link=92&tabid=52".

Also I have to access the website only using the default.aspx page http://localhost/Directory/Default.aspx but if I use only http://localhost/Directory it gives an error
the website declined to show this page http 403.

My main problem is that on the default page the links are not using the directory but rather taking path as http://localhost/LinkClick.aspx?link=92&tabid=52".
I know it should be http://localhost/Directory/LinkClick.aspx?link=92&tabid=52".

How to tell the application to navigate internally only thru the virtual directory that is "Directory"?

I know the website works fine since it is online.

I think it is not accessing the links thru the virtual directory.


Please help. I really need it.
 
New Post
5/21/2010 10:18 AM
 
In the PortalAlais table did you set HTTPAlias to localhost/Directory? If not, give that a try. If the links are referring to are in an HTML module, then you will have to edit the HTML module and change them. I have this problem when I move a production site to my development server. Tthe links in my HTML modules are always inserted as absolute URLs instead of relative URLs.
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedNew to DotNetNu...New to DotNetNu...Run DotNetNuke Website on local machine using localhost.Run DotNetNuke Website on local machine using localhost.


Forum Policy

These Discussion Forums are dedicated to the discussion of the DotNetNuke Web Application Framework.

For the benefit of the community and to protect the integrity of the project, 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 DotNetNuke.
2. Discussion or promotion of DotNetNuke product releases under a different brand name are strictly prohibited.
3. No Flaming or Trolling.
4. No Profanity, Racism, or Prejudice.
5. Site Moderators have the final word on approving/removing a thread or post or comment.
6. English language posting only, please.

Attend A Webinar
Start  Professional Edition Trial
Have Someone Contact Me

Like Us on Facebook Join our Network on LinkedIn Follow DNN Corporate on Twitter Follow DNN on Twitter

Advertisers

Sponsors

DotNetNuke Corporation

DotNetNuke (DNN) provides a suite of solutions that make designing, building and managing feature-rich sites and communities fast, easy and cost-effective. The DotNetNuke Platform CMS is the foundation for more than one million websites worldwide. DNN Social, our newest solution, enables businesses to create immersive, interactive communities. Thousands of organizations like True Value Hardware, Bose, Cornell University, Glacier Water, Dannon, Delphi, USAA, NASCAR, Northern Health and the City of Denver have leveraged DNN to deploy highly engaging business- critical websites. Our rapid growth in product sales and deployments resulted in DotNetNuke Corp. being named one of the fastest growing private companies in America by Inc. Magazine in 2011 and 2012.