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 ...Moving to Network Solutions HostMoving to Network Solutions Host
Previous
 
Next
New Post
12/10/2008 5:01 PM
 

Okay, I've built a site on my laptop using DNN and MS Visual Web Developer, it runs fine and now I want to move it to my hosting account at Network Solutions.  My first attempt was to simply copy all the files from my VWD project into a directory on the host server and point my domain name there.  I ran into problems there because I had to change the name of my directory because it had a "space" in it and NS doesn't allow directories with spaces.  I think that's why I got this Runtime Error.  I've now deleted all the files and installed DNN on the Network Solutions server.  What's the easiest way for me to get this site up and running on Network Solutions?? 

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

 
New Post
12/10/2008 10:53 PM
 

As for the steps to move a site from development to production, this blog from Mitchel Sellers should be of help to you:

http://www.mitchelsellers.com/blogs/articletype/articleview/articleid/204.aspx

Note in particular the need to add the site's new HttpAlias, migrate the database, and modify the connection strings in web.config to connect to the migrated database.

As for the application error you are seeing, you would have needed to edit your site's web.config file to change <customErrors mode="RemoteOnly"> to <customErrors mode="Off"> and then FTP the modified web.config back up to the site. This would allow you to see the actual error the next time you browsed to your site.


Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
12/10/2008 11:06 PM
 

Thanks, Bill.  Let me see what I can figure from reading Mitchel's blog.  This sounds more complicated than I had hoped for.  Thanks for your help.

John

 
New Post
12/11/2008 4:13 PM
 

Hi John,

I'm in technical support at Network Solutions. We offer a quick install for DotNetNuke through our hosting control panel, which may simplify the migration process a bit.

You should be able to migrate the site in a few steps:

Install DNN through your account manager
Backup your local database and upload the backup to your Network Solutions hosting package. Let us know where it is and we can import it into your DNN MSSQL 2005 database.

Upload any Non-Standard files that would not be installed by our DNN installation, such as custom images and the like.

If you'd like me to contact you to help you with the migration, let me know how to contact you, or send me a message:
cknutson [AT] NetworkSolutions.com

I can look up your contact details if you have your hosting package name, ########.netsolhost.com.

 

~Chris

 
New Post
12/11/2008 8:44 PM
 

Chris, I've unmoderated your user - we appreciate you coming to the DotNetNuke forums and being proactive.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Moving to Network Solutions HostMoving to Network Solutions Host


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