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 ...DNN Migration from XP - IIS6 to Server 2008 - IIS7DNN Migration from XP - IIS6 to Server 2008 - IIS7
Previous
 
Next
New Post
1/26/2009 11:26 AM
 

It looks like this version of DNN isn't compatible with the IIS7 integrated pipeline.  IIS7 support came in DNN 4.8.0, so if this website is from before then, it won't work on IIS by default.  To get it working, you'll need to create a new Application Pool in IIS, and set its pipeline mode to Classic.  Then assign this application pool to the website you've created.

After you've got it up and running, I'd suggest upgrading to 4.9.1 (for IIS7 support, security, and other fixes).  Of course, make sure to backup everything before trying to upgrade.

Hope it helps,


Brian Dukes
Engage Software
St. Louis, MO
866-907-4002
DNN partner specializing in custom, enterprise DNN development.
 
New Post
1/26/2009 12:21 PM
 

Hi Oliver I have done as you suggested and here is the error report:

Source Error:
 

Line 236:            ServerName = Server.MachineName
Line 237:
Line 238:            If HttpContext.Current.Request.ApplicationPath = "/" Then
Line 239: ApplicationPath = "" Line 240: Else

Source File:

D:\inetpub\vhosts\whichedge.co.uk\httpdocs\App_Code\Global.asax.vb

   Line:

238



Stack Trace:

[HttpException (0x80004005): Request is not available in this context]
   System.Web.HttpContext.get_Request() +3465893
   DotNetNuke.Common.Global.Application_Start(Object Sender, EventArgs E) in D:\inetpub\vhosts\whichedge.co.uk\httpdocs\App_Code\Global.asax.vb:238

[HttpException (0x80004005): Request is not available in this context]
   System.Web.HttpApplicationFactory.EnsureAppStartCalledForIntegratedMode(HttpContext context, HttpApplication app) +3385130
   System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +125
   System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +182
   System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +259
   System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +245

[HttpException (0x80004005): Request is not available in this context]
   System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +3465475
   System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +69
   System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +675

However I think Brian may have hit the nail on the head, the site is DNN 04.04.01! It was my plan to get the site running then upgrade to 4.9. How do I assign an application pool to the website? From what I have read on-line this was sort of the conclusion that I had come to, but again I not sure how to do it.

Thanks inadvance

Chris

 
New Post
1/26/2009 2:40 PM
Accepted Answer 

whichedge wrote

However I think Brian may have hit the nail on the head, the site is DNN 04.04.01! It was my plan to get the site running then upgrade to 4.9. How do I assign an application pool to the website? From what I have read on-line this was sort of the conclusion that I had come to, but again I not sure how to do it.

Yes, I think he did too. It was quite awhile ago I upgraded my portal, and it was 4.8.0 when I made the switch to win2k8.

Anyways, onto the Application Pools...

  • Open IIS manager
  • Expand your server node
  • Select the Application Pools node

This should show you the current pools configured on your server, I'd create a new pool and then modify the IIS site to use this new pool. You could modify the current pool if you don't have any other websites configured to utilize it. It's really just a personal preference

  • Right Click on the Application Pools node, Select Add Application Pool
  • Name the new pools, select the target framework version (v2), and select Classic as the pipeline mode.
  • Now, Expand your sites node, Left and and select your website node, click Basic Settings from the right pane
  • Click on the Select button next to the application pool textbox, and select your pool from the dropdown menu.

Hopefully this helps somewhat more than my last post did :)

 

 
New Post
1/26/2009 5:13 PM
 

Thanks for your help Oliver, at last the site has loaded, all I need to do now is upgrade the DDN core, I assume that this is best done from the host account in host settings, I seem to remember see a link there is upgrade DotNetNuke.

Thanks again much appreciated.

Chris

 
New Post
1/27/2009 10:30 AM
 

An upgrade is best done according to the upgrade instructions.  :)

You really want to read:

http://www.mitchelsellers.com/blogs/articletype/articleview/articleid/244/upgrading-to-dnn-490-from-4x.aspx

Jeff

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DNN Migration from XP - IIS6 to Server 2008 - IIS7DNN Migration from XP - IIS6 to Server 2008 - IIS7


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