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 ...Moved Installation to New ServerMoved Installation to New Server
Previous
 
Next
New Post
2/9/2007 7:19 PM
 

I've been running DNN fine on one of my dedicated servers for years. I just upgraded to a new machine. I moved over all of the files, folders, databases, etc. from the drive on the old server to the new one and confirmed that everything made it fine. The names of the machine, folders and everything else is identical on the new box to the old one. All of my non-DNN sites can up fine but none of my DNN sites. I've followed all of the installation instructions on filder permissions from the installation doc. Yet, all of my DNN sites are simply displaying the contents of Default.aspx, as follows. Lots of exposure with all my DNN sites down. Any ideas?

Thanks, John

<%@ Page Language="vb" AutoEventWireup="false" Explicit="True" Inherits="DotNetNuke.Framework.DefaultPage" CodeFile="Default.aspx.vb" %>
<%@ Register TagPrefix="dnn" Namespace="DotNetNuke.Common.Controls" Assembly="DotNetNuke" %>
<asp:literal id="skinDocType" runat="server"></asp:literal>
<html>
<head id="Head" runat="server">
    <meta id="MetaRefresh" runat="Server" name="Refresh" />
    <meta id="MetaDescription" runat="Server" name="DESCRIPTION" />
    <meta id="MetaKeywords" runat="Server" name="KEYWORDS" />
    <meta id="MetaCopyright" runat="Server" name="COPYRIGHT" />
    <meta id="MetaGenerator" runat="Server" name="GENERATOR" />
    <meta id="MetaAuthor" runat="Server" name="AUTHOR" />
    <meta name="RESOURCE-TYPE" content="DOCUMENT">
    <meta name="DISTRIBUTION" content="GLOBAL">
    <meta name="ROBOTS" content="INDEX, FOLLOW">
    <meta name="REVISIT-AFTER" content="1 DAYS">
    <meta name="RATING" content="GENERAL">
    <meta http-equiv="PAGE-ENTER" content="RevealTrans(Duration=0,Transition=1)">
    <style id="StylePlaceholder" runat="server"></style>
    <asp:placeholder id="CSS" runat="server"></asp:placeholder>
</head>
<body id="Body" runat="server" bottommargin="0" leftmargin="0" topmargin="0" rightmargin="0" marginwidth="0" marginheight="0">
    <noscript></noscript>
    <dnn:Form id="Form" runat="server" ENCTYPE="multipart/form-data" style="”height: 100%;">
        <asp:Label ID="SkinError" runat="server" CssClass="NormalRed" Visible="False"></asp:Label>
        <asp:PlaceHolder ID="SkinPlaceHolder" runat="server" />
        <input id="ScrollTop" runat="server" name="ScrollTop" type="hidden">
        <input id="__dnnVariable" runat="server" name="__dnnVariable" type="hidden">
    </dnn:Form>
</body>
</html>
 

 
New Post
2/12/2007 9:02 AM
 
Are you sure you've configured IIS so that your dnn installation is a web application.  Meaning, did you create a virtual directory that points to your dnn installation?
 
New Post
2/12/2007 12:41 PM
 

I found an obscure entry somewhere that helped me resolve this issue. I had a problem with IIS and had to uninstall and reinstall it. Once you do so, the DotNet framework sometimes doesn't work correctly. So, after reinstalling IIS, you need to uninstall and reinstall the DotNet 2.0 framework (and service packs). Once I did that and reassigned all of the sites to the new installation of the 2.0 framework, everything came up just fine.

Thanks, John

 
New Post
2/12/2007 12:54 PM
 
I'm looking to do a migration too and believe something has to be done in the web.config because the machineKey is generated by referencing the machine.config (I believe). I am interested as to see what other experienced migrator have to say on this subject.
 
New Post
2/12/2007 12:57 PM
 

It looks like your IIS isn't configured to serve ASPX pages.  You will want to ensure that IIS is registered on your server.

Regarding the machine key, as long as the value is in your web.config file you are set to go moving to a different server!


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
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 Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Moved Installation to New ServerMoved Installation to New Server


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