Now I can't even pull it up on the original webserver I've had it on for so long. [:'(]
Server Error in '/cuww' Application.
Parser Error
Description:
An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message: The 'CodeFile' attribute is not supported by the 'page' directive.
Source Error:
Line 1: <%@ Page language="vb" AutoEventWireup="false" Explicit="True" Inherits="DotNetNuke.Framework.CDefault" CodeFile="Default.aspx.vb" %> Line 2: <%@ Register TagPrefix="dnn" Namespace="DotNetNuke.Common.Controls" %> Line 3: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
DotNetNuke Version: 3.0.12
Data Provider: SqlDataProvider
.NET Framework: 1.1.4332.2032
ASP.NET Identity: NT AUTHORITY\NETWORK SERVICE
That's my current settings that WORK on the current server. And I'd rather keep the DotNetNuke Version and .NET Framework the same. Because I now it will work .... hopefully, lol.
.NET is so confusing to me. I've thought about updating to .NET 2.0 but I don't really know how, and my luck it won't work at all. On the new server we will remove apache tomcat when we are ready to move it over.
So ... what are the steps to move a ASP.NET IntraNET to another server?
2) Copy the entire dnn folder to the new server. Make sure NETWORK SERVICE has read, write, change to your new dnn directory.
3) Create and configure the dnn virtual directory in IIS. Make sure it matches the server alias in step 1 above.
4) Backup your dnn database from the old server, restore it to the new server. Make sure to add back any additional login users / security information you might use.
5) Confirm that your web.config file SQLServer entry is still correct.
Fire it up and see what happens.
The most common mistake here is that people fail to create the new alias BEFORE moving the site over, so when completed, they can't access it (it can be added directly into the database if this happens). Directory rights for the NETWORK SERVICE is the second
most common. And, finally, database connectivity is the third.
I think that should do it ...but your mileage might vary depending on server differences and such. Maybe someone more of an expert than I could help more.
xberserker
Member
109 Points
55 Posts
What are the steps to move a ASP.Net IntraNET to another server??
Jan 24, 2006 07:40 PM|LINK
I want to move it because on the other server the Networking guy backs that server up almost daily.
I've copied the files over but it doesn't pull up. In the IIS Manager I right click on the website folder and browse and I got this error....
Error - HTTP Status 404 - /cuww
type - status report
message - /cuww
description - The requested source (/cuww) is not available.
xberserker
Member
109 Points
55 Posts
Re: What are the steps to move a ASP.Net IntraNET to another server??
Jan 24, 2006 09:45 PM|LINK
Server Error in '/cuww' Application.
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.Parser Error Message: The 'CodeFile' attribute is not supported by the 'page' directive.
Source Error:
Source File: C:\Inetpub\wwwroot\cuww\Default.aspx Line: 1
Version Information: Microsoft .NET Framework Version:1.1.4322.2032; ASP.NET Version:1.1.4322.2032
TheNige
Participant
1475 Points
295 Posts
Re: What are the steps to move a ASP.Net IntraNET to another server??
Jan 24, 2006 11:50 PM|LINK
Is this a DNN application?
isn't the CodeFile for ASP.Net 2.0? Your error page is reporting the 1.1 runtime.
xberserker
Member
109 Points
55 Posts
Re: What are the steps to move a ASP.Net IntraNET to another server??
Jan 25, 2006 02:12 PM|LINK
xberserker
Member
109 Points
55 Posts
Re: What are the steps to move a ASP.Net IntraNET to another server??
Jan 26, 2006 03:58 PM|LINK
So what are the steps to move it to another server?
xberserker
Member
109 Points
55 Posts
Re: What are the steps to move a ASP.Net IntraNET to another server??
Feb 06, 2006 05:24 PM|LINK
HTTP Status 404 - /cuww/
type Status report
message /cuww/
description The requested resource (/cuww/) is not available.
Apache Tomcat/4.1.29
Any thoughts? [:^)]TheNige
Participant
1475 Points
295 Posts
Re: What are the steps to move a ASP.Net IntraNET to another server??
Feb 06, 2006 08:35 PM|LINK
Does apache tomcat run ASP.Net?
chief_cn
Member
210 Points
42 Posts
Re: What are the steps to move a ASP.Net IntraNET to another server??
Feb 07, 2006 09:51 AM|LINK
Have you installed DotNet 2 on your new server?
U are now run dotnetnuke 4.X on DotNet 1.1!
Config your IIS to run yoursite on DotNet 2.0.
http://www.dnnchina.net
xberserker
Member
109 Points
55 Posts
Re: What are the steps to move a ASP.Net IntraNET to another server??
Mar 20, 2006 05:01 PM|LINK
Data Provider: SqlDataProvider
.NET Framework: 1.1.4332.2032
ASP.NET Identity: NT AUTHORITY\NETWORK SERVICE
That's my current settings that WORK on the current server. And I'd rather keep the DotNetNuke Version and .NET Framework the same. Because I now it will work .... hopefully, lol.
.NET is so confusing to me. I've thought about updating to .NET 2.0 but I don't really know how, and my luck it won't work at all. On the new server we will remove apache tomcat when we are ready to move it over.
So ... what are the steps to move a ASP.NET IntraNET to another server?
ElecEagle
Member
135 Points
27 Posts
Re: What are the steps to move a ASP.Net IntraNET to another server??
Mar 21, 2006 11:28 AM|LINK
I am far from an expert, but here's a rough step by step to move a dnn site.
1) Add an entry in the server alias for the new site (what it will be when your move is done).
example: localhost/dotnetnuke, oldserver/dotnetnuke, >> newserver/dotnetnuk <<
2) Copy the entire dnn folder to the new server. Make sure NETWORK SERVICE has read, write, change to your new dnn directory.
3) Create and configure the dnn virtual directory in IIS. Make sure it matches the server alias in step 1 above.
4) Backup your dnn database from the old server, restore it to the new server. Make sure to add back any additional login users / security information you might use.
5) Confirm that your web.config file SQLServer entry is still correct.
Fire it up and see what happens.
The most common mistake here is that people fail to create the new alias BEFORE moving the site over, so when completed, they can't access it (it can be added directly into the database if this happens). Directory rights for the NETWORK SERVICE is the second most common. And, finally, database connectivity is the third.
I think that should do it ...but your mileage might vary depending on server differences and such. Maybe someone more of an expert than I could help more.