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 ...migrate DNN 5.1 website to dedicated server resulting in 404smigrate DNN 5.1 website to dedicated server resulting in 404s
Previous
 
Next
New Post
12/2/2010 10:52 AM
 

Hi Everyone - really need some expertise on this!

2 questions:
1.  I am moving a DNN 5.1.1 website to a new host.  This host is running IIS 7.5 (Windows Server 2008) so I was under the assumption I can install it directly in the root of the domain for a website with a static IP and it should work..? is this correct or do I need to create a virtual directory? 

2.  Here is what I have done so far:
  1. gave the root folder to the domain NETWORK SERVICE and IUSR / IWD users with read/write permission to the directory and all sub files/folders.  The server is running the Plesk console but I am bypassing this
  2. copied the DNN website files and folders into the root and made sure the NETWORK SERVICE account has full permissions on the files/folders
  3. restored the database
  4. added the new static ip for the domain to the PortalAlias table
  5. changed the web.config to support the new sql connection (both places)
  6. ran the website
here is where it gets interesting... the website came up as expected but all of the for the default page/or tab if you will.  However, all of the links on the website that are rewritten (ifinity friendlyUrls) are resulting in 404s as the website is now looking to a static resource on disk for the "pages" almost like DNN doesnt exist?  Even stranger is that if I add the module attribute of runAllManagedModulesForAllRequests="true" to the web.config  then the urls begin to read correctly for all GET requests.  The pages and links are being interpreted correctly by DNN but anything that calls a postback via the doPostBack() eventing with .net results again with 404s.  I even reverted back to the DNN friendly url and I get the same thing...?  

Side Note* when I fire of procmon on the server and watch the requests from the asp.net worker process the get requests are being interpreted correctly just not the POSTs.  

wondering if its becuase this is not in a virtual directory/application of the default website or what - but I was under the assumption that in IIS 7x you can create multiple websites and you dont have to have VDs...?  any/all help is FULLY appreciated...

thanks!
Kevin

 
New Post
12/2/2010 11:32 AM
 
Kevin instead of Network Service can you try a custom app pool? You also need to add this pool under ACL for website directory.

Or-Rouge Team Or-Rouge
Personally recommend Hostgator for hosting single or multiple DotNetNuke Websites.
DotNetNuke Tips and Tutorials
Install DotNetNuke to Godaddy root
DotNetNuke Türkçe Hakkinda Hersey
 
New Post
12/2/2010 11:49 AM
 
I am using a custom app pool but I set the identity to be NETWORK SERVICE.  I can change that to be the default (ApplicationPoolIdentity) is that what you mean?  Also Im not sure what ACL means...  can you give me more detail on what your suggesting I set up?  wI have complete control over the server so I can do whatever is necessary!

thanks so much - really need to get this running!

regards,
Kevin
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...migrate DNN 5.1 website to dedicated server resulting in 404smigrate DNN 5.1 website to dedicated server resulting in 404s


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