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 ...Migrating a 5.6 site from XP to a new 2008 R2 ServerMigrating a 5.6 site from XP to a new 2008 R2 Server
Previous
 
Next
New Post
12/17/2010 4:02 PM
 
I'm back again, and I'm dead in the water.

I have developed an intranet site that works great on my development system in XP.    Now I am trying to get it working on a brand new 2008 R2 server system,and failing.     A few weeks ago I had it at least running on the server, I got called away from it and now that won't work.  Sometimes I can get the home page loaded, but trying to go anywhere from there results it nothing happening (login and register Links), to an 'error' page that has only a DNN logo and the text 'DotNetNuke Error"

When it is all said and done what I'd like is to have 2 instances running, but for now I'd be thrilled just to have the live site running so we can start using it.  lol

Is there any documentation, videos, ... anything relating to the setup and configuration of IIS and DNS to get an Intranet site running on Server 2008 R2 server?  It is an intranet site, not to be seen outside of our network.    Everything I find talks about hosting service X or Y.   I don't have a registered URL for the site, the last company I worked for they could just type in a single name with no HTTP or .com and the site would load.  Would love to do that... but I have no clue how to do it.   Unfortunetly I am not a network guy; I'm a programmer, and in this case therein lies the problem...

Thanks in advance,
Lou
 
New Post
12/17/2010 10:08 PM
 
most likely, there is some issue with IIS web site configuration or windows file systems - but difficult to identify by few symptoms only, I am sorry.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
12/20/2010 12:43 PM
 
Well, at this point I am going going to take this back to square one, and document the process in case anyone else has the same problem.

I have a clean installation of Server 2008 R2 with Sql Server 2008r2
I created the directory c:\websites\iconintranet and copied the DNN 5.6 installtion files to it
In IIS (7.5) I created an "iconintranet" site under the sites tab, and assigned it to the default app pool, integrated pipeline, .NET framework 2.0
I added a line to my hosts file so iconintranet will go to the proper site.

I have given full control to the c:\websites\iconintranet directory to the following users:
Network Service
IIS IUsers
IIS AppPool
IUSR
(I realize full rights are overkill at this point, but I'm just trying to get it to work)

When I type http:\\iconintranet in IE on the webserver I get a DotNetNuke configuration error page from the installWizard.aspx page. 
It says that access to the page "c:\websites\iconintranet\web.config' is denied.   The file does exist, so it must be a rights issue - but I don't know which user I am missing...

If I create the site as an app under Default Web Site rather than its own site it works -  but I have to access the site with the url:  http://mnintranet/mnintrnet - which seems kind of redundant.   Is that the way it is supposed to be?
 
New Post
12/20/2010 4:25 PM
 
If you migrate from XP to a 2008 system, you have also to migrate the database, and modify the database on PortalAlias table to the correct URL.  Check the application pool and what is the user it used - this user must have full access.  The IUser must have read access.
 
New Post
12/20/2010 5:02 PM
 
I ported the database as well.   I have been trying different things, and I think I am almost there...

The code now resides in c:\inetpub\wwwroot\iconintranet.   I can now access the site by typing iconintranet in the browser at the server, or fromt he client after adding a line to a client's hosts file.

However nothing from the default page works.   At the server clickcing on register or login links do nothing.   Clicking on the header produces a 404 error trying to access home.aspx

At the client clickign anything brings u a page with the DNN logo that syas "DotNetNukeError.   Below is a big red X that says "An error occured.." twice.   I am looking at the PortalAlais table as you suggested, I removed all 'extra' records; there are 2 records, both pointing to PoralID of 0.   The HTTPAlais values are iconintranet and 192.168.1.32 (the name and bound address of the site in IIS).  Is there anything else I should include?  The site is using the DefaultAppPool, IIS AppPool has full rights to the directory.  

I am SO close to getting it up and running....    Thanks for your assistance!

Lou
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Migrating a 5.6 site from XP to a new 2008 R2 ServerMigrating a 5.6 site from XP to a new 2008 R2 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